
Remember the free Microsoft 365 developer sandboxes that let us test things in SharePoint, Teams, and Power Platform without breaking production? Some of those tenants are now on borrowed time. To be clear, Microsoft is retiring legacy sandboxes, not shutting down the Microsoft 365 Developer Program or eliminating free E5 developer sandboxes. That’s an important distinction before everyone starts panicking.

The announcement is worth reading, but the immediate question is simpler: Which sandbox do you have, and do you need to move anything?
First, check your dashboard
Open the Microsoft 365 Developer Program dashboard and sign in with the account you used to join the program. That might not be the same account you use as global admin inside your developer tenant, which is an easy detail to miss.
Look at the label on your subscription. Legacy sandbox means the retirement applies to you. Add-on enabled sandbox means this particular retirement doesn’t affect your subscription. Legacy sandboxes associated with Visual Studio subscriptions are included, too.

If you have a legacy sandbox, start planning now
If you’re still eligible for a replacement, Microsoft says your legacy sandbox will receive one final 60-day renewal. Check your dashboard and notification email for your actual expiration date. If you’re no longer eligible, you won’t get that final renewal, and your subscription expires at the end of its current term.
Once the subscription expires, it enters a 30-day read-only period, with administrator-only access for data recovery. After that, Microsoft permanently deletes the tenant and its data. Don’t mistake the recovery window for another month of normal development and migration activity.
Here’s the part that matters more than the countdown: you cannot convert the legacy sandbox to the new model. Your replacement is a separate tenant with a new domain and tenant ID, and nothing transfers automatically. If you’re eligible, create the replacement as soon as the option appears in your dashboard. You can use both tenants during the final 60-day window to move and test your work. That means you need to inventory and rebuild whatever actually matters.
Think beyond the files. Export your Power Platform solutions, preserve SharePoint sites and list data you need, back up SPFx packages and source code, and document Microsoft Entra app registrations, permissions, and secrets. Then account for your Copilot agents, Teams apps, connections, test users, scripts, and pipelines that reference the old tenant. Recreating a test environment is one thing. Discovering that your working demo depended on an app ID you no longer have is another.
Already on an add-on enabled sandbox?
Good news: this retirement doesn’t apply to that sandbox, and the qualifying Microsoft 365 E5 developer subscription remains free. Newer sandboxes support optional paid add-ons, including Microsoft 365 Copilot. Microsoft requires a billing account when setting up a new sandbox, but that verification step doesn’t, by itself, charge you for the free subscription.
The new sandbox starts with a 90-day term, followed by 60-day renewals as long as you remain eligible. Unlike replacing a legacy sandbox, these renewals keep the same tenant, users, content, and configuration. Your sandbox still isn’t permanent storage, though. Renewals depend on qualifying development activity, so check your dashboard for the current expiration date rather than treating the schedule as a lifetime guarantee.
My advice? Use developer tenants as places to experiment, not as the only place your work exists. Take five minutes to check your dashboard. If it says Legacy sandbox, make an inventory before you start moving things. That will save you from learning, the hard way, how many dependencies were hiding in a tenant you thought was disposable.
For the full details, including eligibility and the recovery timeline, read Microsoft’s announcement and the legacy subscription retirement FAQ.
For more information about the program itself, see the Microsoft 365 Developer Program overview.
