Forum Discussion

GnanakumaranM's avatar
GnanakumaranM
Copper Contributor
Jul 08, 2026

Microsoft 365 E5 configuration grayed out - TrackingID#2607060030007237

Hello Team,

We are currently facing an issue while setting up the Microsoft 365 E5 Sandbox through Microsoft 365 Developer Program.

Users are only seeing the option to create an Instant Sandbox, which appears to require billing details. However, the Configurable Sandbox option, which does not involve any cost, is currently grayed out and cannot be selected.

We tested this with multiple users within our organization, and the same behavior was observed for both users. This issue was not encountered earlier, as users were previously able to view and select both options — Instant Sandbox and Configurable Sandbox — by default.

All impacted users are signing in with organizational email accounts associated with valid Visual Studio Dev Essentials, Professional, or Enterprise subscriptions.

We also raised a MS Support case regarding this issue. However, we were informed that this falls outside the scope of a break/fix support case and were advised to post the issue in Microsoft 365 Developer Community forum. This is surprising, as the issue appears to be impacting multiple organizational users and may potentially affect many more members.

Requesting your support to review this issue on priority and advise on why the Configurable Sandbox option is disabled, along with the recommended resolution or next steps.

Previous Microsoft Support Case related to M365 Developer program different issue: 2601080030003703

Thank you.

e5
E5 Subscriptions
M365 Developer

1 Reply

  • Jamony's avatar
    Jamony
    MCT
    Jul 08, 2026

    Hi, if multiple eligible users in the same organization see the same thing, I would not troubleshoot this like a local browser issue.

     

    The Microsoft 365 Developer Program sandbox options have changed over time, and availability can depend on account eligibility, tenant state, region, program rules, and what Microsoft is currently allowing for new sandbox creation. A Visual Studio subscription helps with eligibility in some scenarios, but it does not always guarantee that every sandbox type is available at that moment.

     

    I would capture screenshots, the affected sign-in accounts, subscription type, region, and the tracking ID, then keep pushing through the Developer Program/community channel as advised. Also test from a clean browser session and a different network just to rule out cached state, but the grayed-out Configurable Sandbox option sounds more like a backend eligibility or program availability decision than something the user can fix from the portal.