Expand billing setup troubleshooting - #285
akagarwa-msft wants to merge 2 commits into
Conversation
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
PoliCheck Scan ReportThe following report lists PoliCheck issues in PR files. Before you merge the PR, you must fix all severity-1 and severity-2 issues. The AI Review Details column lists suggestions for either removing or replacing the terms. If you find a false positive result, mention it in a PR comment and include this text: #policheck-false-positive. This feedback helps reduce false positives in future scans. ✅ No issues foundMore information about PoliCheckInformation: PoliCheck | Severity Guidance | Term |
There was a problem hiding this comment.
🟡 Changes recommended
A few new troubleshooting steps contain internal inconsistencies/unclear wording (and one quoted UI-string punctuation issue) that should be corrected to avoid confusing administrators and developers.
Get a fresh assessment by requesting another Copilot review.
Pull request overview
This PR expands the troubleshooting guidance for Microsoft 365 Developer Program sandbox billing setup by adding explicit billing account prerequisites and a more detailed checklist for resolving empty/ineligible billing account selections and “already exists” setup states.
Changes:
- Adds a consolidated “Billing account requirements” section for MCA billing accounts used in sandbox setup.
- Expands troubleshooting to cover empty/ineligible billing dropdowns and existing-account error states.
- Introduces a billing administrator validation checklist, including least-privilege and supported billing roles.
File summaries
| File | Description |
|---|---|
| docs/microsoft-365-developer-program-get-started.md | Adds billing account requirements and expanded troubleshooting/checklist for MCA billing account eligibility and permissions during sandbox setup. |
Review details
- Files reviewed: 1/1 changed files
- Comments generated: 4
- Review effort level: Lite
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
PoliCheck Scan ReportThe following report lists PoliCheck issues in PR files. Before you merge the PR, you must fix all severity-1 and severity-2 issues. The AI Review Details column lists suggestions for either removing or replacing the terms. If you find a false positive result, mention it in a PR comment and include this text: #policheck-false-positive. This feedback helps reduce false positives in future scans. ✅ No issues foundMore information about PoliCheckInformation: PoliCheck | Severity Guidance | Term |
There was a problem hiding this comment.
🟡 Changes recommended
The new troubleshooting checklist contains wording inconsistencies/ambiguities (notably around which account identity should be granted billing roles) that could misdirect users during setup.
Get a fresh assessment by requesting another Copilot review.
Review details
Suppressed comments (1)
Previously missed (1) — in code that hasn't changed since the last review.
docs/microsoft-365-developer-program-get-started.md:242
- This doc earlier states a "Microsoft account" is used to sign in (see prerequisites), but this step explicitly says "Microsoft Entra account". To avoid conflicting guidance and reduce confusion about which identity should receive the billing role assignment, refer to the signed-in account used for Developer Program/sandbox setup without narrowing it to Entra here.
- Files reviewed: 1/1 changed files
- Comments generated: 1
- Review effort level: Lite
| If an existing MCA billing account doesn't appear, verify that an active Azure subscription was created with an Azure plan under the billing profile and invoice section that you intend to use during sandbox setup. If the account doesn't have an Azure subscription, follow the instructions in [No Azure subscription exists under the billing account](#no-azure-subscription-exists-under-the-billing-account). | ||
|
|
||
| If the billing account still doesn't appear, or if the system shows **BillingAccountAlreadyExists** or displays "Your billing account is ready," check for the following: | ||
| If the billing account dropdown is empty, shows no eligible account, or the billing account still doesn't appear, check the following sections. |
|
Learn Build status updates of commit 3d66c84:
|
| File | Status | Preview URL | Details |
|---|---|---|---|
| docs/microsoft-365-developer-program-faq.yml | View | Details | |
| docs/microsoft-365-developer-program-get-started.md | ✅Succeeded | View |
docs/microsoft-365-developer-program-faq.yml
- Line 347, Column 173: [Warning: bookmark-not-found - See documentation]
Cannot find bookmark '#billing-account-not-appearing-in-the-dropdown' in 'microsoft-365-developer-program-get-started.md'.
For more details, please refer to the build report.
Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
Summary
Scope