The Microsoft 365 Developer Program gives eligible members a free Microsoft 365 E5 developer sandbox with 25 user licenses, but it is not open to everyone: you qualify through Visual Studio Professional or Enterprise, the ISV Success Program or eligible Microsoft AI Cloud Partner Program tiers, or a Premier or Unified Support contract. Setup needs a valid billing account, takes a few minutes, and the tenant renews for as long as you keep doing qualifying development work in it.
Who this is for
This guide is for developers, admins and learners who want a safe Microsoft 365 tenant to test Graph calls, Teams apps, SharePoint Framework solutions or admin tasks without touching production. By the end you will know whether you are eligible, what the sandbox includes, how to set it up and sign in, and how renewal and expiry work. It is also a sensible place for help desk learners to practise licence and user administration, as long as the activity is development or testing. See the entry-level IT support resume guide for how to describe that practice honestly.
All details below come from Microsoft Learn pages for the Developer Program, last updated in September 2026, checked on 25 October 2026. The program changes, so confirm current rules on the dashboard.
Eligibility
Microsoft lists these ways to qualify for a Microsoft 365 E5 developer subscription:
| Path | Details |
|---|---|
| Visual Studio subscribers | Eligible Visual Studio Professional or Enterprise standard subscription. Microsoft employees are not eligible. The sandbox renews automatically while the Visual Studio subscription is active and you remain eligible |
| ISV Success Program or Microsoft AI Cloud Partner Program | Companies in the ISV Success Program or eligible partner levels, including Solutions Partners, Specialization Partners, Managed Partners, Microsoft Action Pack subscribers, and legacy Gold or Silver partners, can request a subscription using a corporate email address |
| Premier or Unified Support customers | Request goes through your Microsoft support partner contact, such as a Customer Success Account Manager, and uses the same email address you registered with |
Other eligibility facts:
- A Microsoft 365 enterprise or production subscription is a separate environment and does not by itself create or qualify you for a sandbox.
- The program is not offered in government clouds such as GCC, GCC High or DoD.
- Full-time Microsoft employees cannot receive a sandbox.
- You get one developer subscription per membership, and one Developer Program account per phone number.
- Microsoft may require identity verification. If a Visual Studio subscriber is told they do not qualify, Microsoft suggests checking that the subscription is active and assigned to your account, then retrying validation.
Accounts that can sign up are a work account, a Visual Studio ID or a personal Microsoft account. Phone numbers and *.onmicrosoft.com accounts are not supported. Try your corporate or work account first to avoid creating a second membership.
If you do not qualify, the Azure free account lab guide covers a different free route for practising Azure and Entra topics.
What the sandbox includes
Every qualifying subscription is provisioned as an instant sandbox, ready within minutes, with:
- Microsoft Teams, SharePoint, Outlook and Office pre-provisioned.
- 24 test users plus one admin, 25 licenses in total. Microsoft's setup page describes 16 fictitious sample users plus the admin account pre-populated, and the remainder can be added in the admin center.
- Sample data: Microsoft Graph user, mail and calendar data, and a Teams sample data pack.
- Pre-configured custom apps and Office Add-in and SharePoint Framework sample data.
Microsoft states the E5 developer subscription has the same licensing and capabilities as a regular Microsoft 365 E5 subscription, except that inbound connectors for mail flow in Exchange Online are not supported. It includes products such as Microsoft Entra ID P1 and P2, Microsoft Intune, Exchange Online Plan 2, SharePoint Online Plan 2, Teams, Phone System and Power BI Pro (not Power BI Premium). Power Automate use is limited to the rights bundled with Microsoft 365 licenses: standard connectors yes, premium connectors, custom connectors, on-premises gateways, RPA and AI Builder capacity no.
Limits to know:
| Limit | Value |
|---|---|
| User licenses | 25 including the administrator, for development only |
| Tenant storage | Developer-only tenants capped at 300 GB pooled |
| OneDrive per user | 10 GB for Developer SKU users |
| Domain name | Pre-configured, for example yourtenant.onmicrosoft.com, and cannot be customised after sign-up |
| Data center region | Chosen at setup and cannot be changed |
Instant sandboxes issued from July 2026 to new eligible enterprise customers include add-on purchase capability, for example to buy Microsoft 365 Copilot licenses. An existing developer tenant without commerce capability cannot be converted.
The billing account requirement
A valid billing account is required to set up the sandbox and Microsoft states this cannot be bypassed. It is used for verification and to enable optional future purchases. You are not charged for the sandbox, and creating or linking a billing account does not itself incur charges.
You can use an individual billing account (which you can create during setup) or an existing organizational one you have permission to use. If you use an existing account, check that:
- The billing account is a Microsoft Customer Agreement (MCA) account, its status is Active, and the agreement has been accepted.
- The billing profile and an invoice section are active.
- An active Azure subscription with an Azure plan exists under the billing profile and invoice section you intend to use.
- Any Azure subscription spending limit is removed. See the Azure spending limit documentation before you do so, and read the caution below.
- You hold View Asset and Add Asset (Write) permissions on an invoice section. Invoice Section Contributor is the least-privilege role Microsoft names. Reader roles are not enough.
Caution: removing a spending limit means Azure resources in that subscription can generate charges. Microsoft says to stop and ask your billing administrator if you are not the billing owner or do not understand the effect. It also says not to create duplicate billing accounts to work around missing permissions.
Set up the sandbox
- Join the program at the Developer Program site with a supported account, then open your Microsoft 365 Developer Program dashboard.
- Choose Set up E5 subscription. If you qualify, setup starts automatically after you join.
- In the dialog, select Instant sandbox (Add-on purchases enabled), the default, and choose Next.
- On the billing screen, choose the Country/region for your data center. You cannot change it later.
- Open the Billing account dropdown. If your account is not listed, choose Add a new billing account and complete the three-step wizard: account details (name, business address, business phone number), sign-in details, and payment setup with acceptance of the Microsoft Customer Agreement. Then close that window.
- Select the refresh icon next to the dropdown and choose the billing account. The billing profile and invoice section fill in automatically; check them, then choose Set up.
- Enter an Admin username and an Admin password, and optionally choose to set one alternative password for all 16 fictitious users. Record the credentials, then choose Set up again.
- When provisioning completes, you return to the dashboard with an Active subscription. The Users sample data pack must be installed before others.
First sign-in and configuration
- On the dashboard, choose Go to subscription and sign in as
[email protected], not with your Developer Program account. - Use the app launcher to open the admin center and choose Go to guided setup for the Microsoft 365 E5 Developer Setup page.
- Step through installing Office apps, personalising sign-in and email, adding users and assigning licenses, and sharing credentials.
- Set up multifactor authentication by signing in as admin, choosing Admin, then Setup, then Configure multifactor authentication (MFA), and linking the email and phone you used at setup. This is also your recovery route if you forget the password.
Renewal, expiry and backups
| Topic | Rule |
|---|---|
| Length | Up to 90 days depending on activity |
| Renewal | Renewed by qualified development activity, such as Microsoft Graph development, SPFx work, Teams app development, Power Platform solutions or automated testing. Artificial activity may not qualify |
| Linking GitHub | Linking your GitHub account on the profile settings page accrues toward renewal |
| Visual Studio subscribers | Renewed automatically while the Visual Studio subscription is active |
| After expiry | 30 days to migrate data, then 30 days of admin-only access, and on day 60 the subscription and all data are deleted |
| Recreating | You can get a new subscription after deleting your account only if you have had your current subscription for more than 60 days |
Microsoft warns that tenants are short-lived and that it may require them to be recreated every 90 days. Keep scripts, configuration and any data you care about in a source repository or backup outside the tenant.
Troubleshooting
| Symptom | Likely cause | Fix |
|---|---|---|
| No Set up E5 subscription option | Not eligible, or validation failed | Check your qualifying path and that the Visual Studio subscription is active and assigned |
Sign-in error with phone or .onmicrosoft.com account | Unsupported sign-in type | Use a work account, Visual Studio ID or personal Microsoft account |
| Billing account missing from dropdown | Not MCA or active, no Azure subscription under it, wrong permissions, or recent changes | Check the account requirements, wait a few seconds and refresh; sign out and back in if needed |
| Set up button greyed out | Billing account, profile or invoice section not all selected | Select all three, refresh and retry |
BillingAccountAlreadyExists or similar | An account already exists | Use the same troubleshooting checks, and do not create duplicates |
| Microsoft Customer Agreement not signed | Agreement not accepted | An authorized user accepts it in the Microsoft 365 admin center, then retry |
| Provisioning is slow | Normal delay | Refresh the dashboard; contact program support with the correlation ID if it persists |
To find the correlation ID, open the dashboard, press F12, perform the failing action, enter correlationid in the console, and copy the result. Send support the complete error message, time and time zone, and a screenshot, but never passwords, codes or payment details.
Checklist
- You have confirmed which eligibility path applies to you.
- You have a billing account that meets the MCA requirements, and you understand what removing a spending limit means.
- The sandbox is set up with credentials stored safely and MFA configured.
- You use it only for development or testing, never for production data.
- Important work lives outside the tenant, with a plan for the 90-day cycle.
References
- Microsoft 365 Developer Program FAQ: https://learn.microsoft.com/en-us/office/developer-program/microsoft-365-developer-program-faq
- Set up a Microsoft 365 developer sandbox subscription: https://learn.microsoft.com/en-us/office/developer-program/microsoft-365-developer-program-get-started
- Microsoft 365 Developer Program: https://developer.microsoft.com/en-us/microsoft-365/dev-program
- Azure spending limit: https://learn.microsoft.com/en-us/azure/cost-management-billing/manage/spending-limit
Comments
Questions and tips are welcome. Comments are checked by the EpiFive team before they appear; please do not share passwords, phone numbers or other private details.