Microsoft 365 Developer Program – No billing accounts found despite active MCA, Invoice Section and Azure Plan

Assign Invoice Section Contributor on the intended invoice section to the exact Entra account used to sign in to the Developer Program; merely being able to view that invoice section does not establish the required Add Asset (Write) permission.

Verify the effective billing role

The sandbox flow requires both View Asset and Add Asset (Write). The least-privilege role providing them is Invoice Section Contributor; Invoice Section Owner, Billing Profile Owner, and Billing Account Owner also qualify. Reader roles are insufficient.^1^

Have a billing administrator perform these steps:

1. Sign in to the Azure portal with an account allowed to manage billing permissions.
2. Open Cost Management + Billing.
3. Select the MCA billing account, then the intended Billing profile.
4. Open Invoice sections and select the section containing the Azure Plan subscription.
5. Select Access control (IAM) → Add → Add role assignment.
6. Assign Invoice Section Contributor to the exact corporate account used on the Microsoft 365 Developer Program dashboard.
7. Allow several minutes for the role assignment to propagate.
8. Sign out of all Microsoft accounts, close the browser, and sign back in using that authorized account before returning to Set up E5 subscription.

MCA billing permissions are distinct from Azure resource RBAC roles such as Subscription Owner or Contributor. Microsoft documents the billing roles separately, including their inheritance across billing-account, billing-profile, and invoice-section scopes.^2^

If a qualifying write role is already effective

Since the MCA status, Azure Plan subscription, tenant association, and selector refresh have already been checked, do not create another subscription or duplicate billing account. Check only the remaining documented eligibility conditions:

• The Microsoft Customer Agreement has been accepted, not merely created.
• The billing profile has a valid payment method.
• No spending limit or other billing restriction blocks provisioning.
• The Azure subscription is under the exact billing profile and invoice section intended for sandbox setup.

These are explicit sandbox billing requirements, and an applicable spending limit must be removed.^3^

If all of those conditions and a qualifying write-capable role are confirmed, the remaining symptom is consistent with a billing-account discovery or provisioning-association problem that cannot be corrected through the dashboard. The empty dropdown alone does not establish its backend cause, so Microsoft must inspect the association.

Correct escalation path

Use separate escalation routes depending on what needs investigation:

1. Azure billing configuration or effective MCA permissions
   Open an Azure Support request from Azure portal → Help + support → Create a support request. Ask the billing team to confirm:
   • effective MCA role inheritance for the Developer Program user;
   • accepted agreement and active billing scope;
   • payment/spending restrictions;
   • the Azure Plan subscription’s billing-profile and invoice-section association.
   The sandbox setup documentation specifically directs billing-account configuration problems to Azure Support.^3^
2. Developer Program discovery/provisioning after Azure validates the account
   Escalate to Microsoft Developer Support through Services Hub. Access depends on the organization’s paid support agreement.^4^
   For a Premier or Unified Support customer, the Developer Program FAQ says the request is managed through the organization’s Microsoft support partner contact, such as its CSAM.^1^

Include the following in the case, but provide identifiers only through the private support ticket:

• Developer Program sign-in UPN and tenant ID
• Billing account, billing profile, and invoice-section IDs
• Azure subscription ID and plan
• Screenshot of the empty dropdown
• Screenshot/export showing the user’s effective billing role
• Confirmation that the MCA is accepted, payment method is valid, and no spending limit applies
• UTC timestamp and correlation/request ID, if the setup page exposes one
• Request: “Validate Microsoft 365 Developer Program billing-account discovery, tenant association, eligibility response, and sandbox provisioning state.”

References

1. Microsoft 365 Developer Program FAQ
2. Understand Microsoft Customer Agreement administrative roles in Azure
3. Set up a Microsoft 365 developer sandbox subscription
4. Microsoft 365 E5 Developer subscription not provisioning or expiring unexpectedly - Microsoft Q&A