Thank you for joining. You don't current qualify for a Microsoft 365 Developer Program sandbox subscription.

Question

I am a decision maker, and wanted to showcase the capabilities of Microsoft Purview to the senior leadership.
For that I tried to subscribe to Microsoft Developer account so I can clearly demonstrate the purview features, namely sensitivity labels and DLP.
I have, in the past, been a power user of Microsoft Purview and work for a Microsoft Partner with access to several demo and developer tenancies.

But Microsoft does not want our business. When I have the ear of the leaders.

"Thank you for joining. You don't current qualify for a Microsoft 365 Developer Program sandbox subscription."
I understand that you may have withdrawn the facility, but then why are you harvesting data?

OK, then.

Let us investigate alternative products!
If we implemented in Australia, we would have implemented around the world.
Ah well.
Thank you, Microsoft.

Answer 1

The Microsoft 365 Developer Program sandbox subscription is only available to qualifying members under the current program rules. Membership and access to a Microsoft 365 E5 developer sandbox are governed by the program’s terms and conditions and technical eligibility checks.

Key points from the current program behavior:

1. Membership vs. sandbox eligibility
   • Joining the Microsoft 365 Developer Program and getting access to the dashboard is separate from qualifying for a Microsoft 365 E5 developer sandbox subscription.
   • The program explicitly reserves the right not to provide or to revoke a developer subscription if terms are violated or eligibility criteria are not met. In some cases, members may be unable to sign in to or use their sandbox if they violate the Terms and conditions.
2. What the sandbox is for
   • The Microsoft 365 E5 developer subscription is intended strictly for development and testing, not for production or general business use. It includes 25 user licenses and is short-lived by design (up to 90 days, renewable based on qualified developer activity).
   • The subscription can be revoked if used for purposes other than development.
3. Who can sign up and how many accounts
   • Supported sign-in identities are:
     • Work account (Microsoft Entra ID / organizational account)
     • Visual Studio ID (for Professional or Enterprise subscribers)
     • Microsoft account (consumer account such as Outlook.com)
   • Phone numbers and *.onmicrosoft.com accounts are not supported for sign-up; using them results in an error and requires signing in with a supported email.
   • Only one Developer Program account can be associated with a given phone number. To switch to a different email or account type, the existing Developer Program account must be deleted first.
4. Visual Studio subscriber path
   • Visual Studio Professional or Enterprise subscribers can join via the Visual Studio subscription portal and receive a Microsoft 365 E5 developer subscription that renews automatically as long as the Visual Studio subscription is active.
   • This route is not subject to expiration due to inactivity (within the scope of the program’s monitoring).
5. Sandboxes and Purview-style scenarios
   • Qualifying members can set up an E5 developer sandbox (instant or configurable). The E5 SKU includes Microsoft 365 services suitable for demonstrating capabilities such as sensitivity labels and DLP in a non-production environment.
   • Instant sandboxes come pre-provisioned with Microsoft 365 apps and security/identity components (including Enterprise Mobility + Security and Microsoft Entra ID), which can be used to build and demo security and compliance scenarios.
6. Why access may be denied
   • The program may not allow members to sign in to or obtain a sandbox if:
     • Terms and conditions have been violated.
     • The account type or sign-in method is unsupported.
     • Internal eligibility checks fail (for example, multiple accounts tied to the same phone number, or other policy-based restrictions).
   • In such cases, the message “You don’t currently qualify for a Microsoft 365 Developer Program sandbox subscription” reflects that the account does not meet the current criteria for provisioning a sandbox, even if the user can still sign up for the program itself.
7. Options to proceed
   • Verify that sign-up is done with a supported account type (work account, Visual Studio ID, or Microsoft account—not a phone number or *.onmicrosoft.com address).
   • If already a Visual Studio Professional or Enterprise subscriber, use the “Join with Visual Studio” path to obtain an E5 developer subscription that is linked to the Visual Studio subscription.
   • If a previous Developer Program account exists tied to the same phone number, delete that profile from the Developer Program dashboard and then rejoin, subject to the 60-day rule for obtaining a new subscription.

These constraints are program-wide and not specific to a region or individual organization. Demonstrations of Microsoft Purview capabilities in a sandbox environment must use a tenant that complies with these Developer Program rules or another appropriately licensed, non-developer tenant.

---

References:

• Microsoft 365 developer subscription in Visual Studio subscriptions
• Set up a Microsoft 365 developer sandbox subscription
• Microsoft 365 Developer Program FAQ
• Welcome to the Microsoft 365 Developer Program