Microsoft 365 Developer Program – Sandbox Created in Wrong Tenant & 60‑Day Lockout Confusion

[ranj]

Hi

Does anyone use or have any experience with Microsoft 365 developer subscription which you can get through a Enterprise visual studio MSDN subscription? 

 

I’m trying to understand the behaviour of the Microsoft 365 Developer Program after running into an issue that support couldn’t resolve.

I previously had a Microsoft 365 Developer E5 subscription linked to my main environment (the one I actively use with my Azure MSDN subscription). That Developer E5 subscription was deleted by mistake, which removed all Microsoft 365 workloads from that environment.

 

When I attempted to recreate the Developer E5 subscription, the Developer Program automatically created a completely new sandbox tenant instead of letting me attach it to my existing environment. This new sandbox is not useful to me.

I contacted Microsoft support to request a reset of my Developer Program entitlement so I could recreate the Developer E5 subscription in the correct environment. Support closed the case and told me I must wait 60 days before I can create a new Developer subscription.

 

My questions:

 

• Why does the Developer Program enforce a 60‑day lockout after deleting a profile? Is this a recent change, and is there any official documentation explaining the reasoning?
• When accessing the Developer Program through my Visual Studio benefits, it shows an old mobile number. Does anyone know where this is stored as its not within my profile, and how can it be updated?
• After the 60‑day period, can I confirm that I will be able to create a new Developer E5 subscription and link it to my existing environment rather than creating another new sandbox tenant?

 

Any clarification or guidance would be greatly appreciated.

 

Thanks.