Forum Discussion

AmithDebnath's avatar
AmithDebnath
Copper Contributor
Jul 21, 2026

M365 Developer E5 Sandbox provisioning failed despite active Visual Studio Enterprise subscription

Hi everyone,

I'm looking for some help with an issue I'm facing while setting up a Microsoft 365 Developer E5 sandbox.

I have an active Visual Studio Enterprise subscription (valid until 2029), and it is successfully linked to my Microsoft 365 Developer Program account.

What happened

  1. I joined the Microsoft 365 Developer Program.
  2. I selected Instant Sandbox.
  3. I entered the required information and selected my Visual Studio Enterprise subscription.
  4. The portal initially displayed the following message:

    "It's taking longer than expected. Your setup is being processed. There is no action required from you at this time."

  5. After waiting for nearly 24 hours, the dashboard changed to:

    "You don't currently qualify for a Microsoft 365 Developer Program sandbox subscription."

What I've verified

  • Visual Studio Enterprise subscription is active and linked to my Developer Program account.
  • A developer tenant appears to have been created.
  • I can access the tenant through the Microsoft Entra Admin Center.
  • An Azure subscription named similar to devProgram_... is visible.
  • In the Microsoft 365 Admin Center (Billing → Your products), only Microsoft Entra ID Free is listed.
  • No Microsoft 365 E5 Developer subscription was provisioned.
  • No sample users or Microsoft 365 workloads (Exchange, Teams, SharePoint, etc.) appear to have been created.

My understanding

It appears that the developer tenant was created successfully, but the Microsoft 365 Developer E5 sandbox provisioning either failed or never completed. As a result, I don't have a usable Microsoft 365 developer environment for testing Declarative Agents and MCP integrations.

Has anyone experienced this before?

  • Is there a way to retry the E5 provisioning without creating a new Developer Program account?
  • Is there anything I can check on my side?
  • Does this require intervention from the Microsoft Developer Program team?

Any guidance would be greatly appreciated.

Thank you!

1 Reply

  • Jamony's avatar
    Jamony
    MCT
    Jul 25, 2026

    Your tenant was created, but E5 licenses and sample data were not provisioned, after which the dashboard changed to not qualified. Visual Studio Enterprise qualifies only when it is a standard subscription, not a monthly subscription, and it must be linked through the same Microsoft identity used for the Developer Program. In Visual Studio My Benefits, confirm that the Microsoft 365 Developer subscription benefit is present, then launch or relink it from there. Verify that the Developer Program dashboard shows the same account and subscription. The Entra tenant and Azure subscription do not prove E5 provisioning completed; the missing E5 product confirms it did not. There is no documented customer-side command to resume a failed provisioning job. Do not create repeated accounts or tenants. Capture the subscription type, benefit status, account, tenant ID, and screenshots, then contact Developer Program or Visual Studio subscription support to reconcile eligibility and provisioning.