How to Get a SharePoint Test Environment in 2026

The cleanest SharePoint Online test environment is a separate Microsoft 365 tenant. Microsoft still offers renewable 90-day developer sandboxes, but eligibility is restricted: qualifying Visual Studio subscribers, eligible ISV Success or Microsoft AI Cloud Partner Program members, and certain Premier or Unified Support customers can qualify. Joining the Microsoft 365 Developer Program alone does not guarantee a sandbox.

If you are not eligible, use an organisation-provided development tenant or obtain a paid trial/test tenant through Microsoft or a partner. GitHub Codespaces, a Fabric trial and a local SharePoint Framework workstation are useful tools, but none is a SharePoint Online tenant.

Fact-checked against Microsoft Learn on 7 August 2026.

The short answer

What you need to test	Best starting environment
SharePoint Online configuration, permissions, search and integrations	Separate Microsoft 365 development/test tenant
SharePoint Framework code before tenant deployment	Local workstation or cloud development machine, then a test tenant
Power Apps or Power Automate solution changes	Separate Power Platform environment plus representative SharePoint test data
SharePoint Server	Properly licensed isolated virtual machines or lab infrastructure
A quick disposable demonstration	Eligible Microsoft 365 developer sandbox or a time-limited trial whose terms fit

Do not put customer, employee or irreplaceable project data in a temporary developer subscription.

Option 1: Microsoft 365 Developer Program sandbox

Microsoft’s developer sandbox is the closest thing to a ready-made SharePoint Online lab. A qualifying subscription provides a Microsoft 365 E5 developer environment with 25 user licences and can remain active for up to 90 days. Microsoft can renew it when the owner remains eligible and demonstrates qualifying development activity.

Who currently qualifies

Microsoft’s current FAQ lists these routes:

• Visual Studio Professional or Enterprise subscribers;
• members with a qualifying offer through ISV Success or eligible Microsoft AI Cloud Partner Program tiers; and
• Premier or Unified Support customers who obtain access through their Microsoft contact.

Eligibility can change and Microsoft makes the final decision. A free Developer Program membership is useful for documentation and community resources, but it no longer means every member can provision a free tenant.

What the sandbox is good for

Use it for development and testing such as:

• SharePoint sites, lists, libraries, content types and permissions;
• Microsoft Graph and SharePoint APIs;
• SharePoint Framework packages;
• Teams and Microsoft 365 integrations;
• test users, groups and realistic permission scenarios; and
• demos that do not rely on permanent data.

Eligible subscriptions include sample data packs, but you should still create the exact users, structures and edge cases your solution needs.

What it is not for

Microsoft says the subscription is for development purposes only. Do not use it for production services, normal business operations or long-term storage.

The subscription can expire. Keep source code, deployment packages, scripts, sample-data definitions and configuration notes outside the tenant. If the only copy of a solution lives inside the sandbox, it is not a disposable sandbox.

How to set up the Microsoft developer sandbox

1. Join or sign in to the Microsoft 365 Developer Program.
2. Complete the profile and confirm whether Microsoft offers you an E5 developer subscription.
3. Choose the available setup option. Microsoft may offer an instant or configurable sandbox depending on the qualifying account and programme state.
4. Create the administrator identity and record recovery information in your approved password/identity system.
5. Add only synthetic or approved test data.
6. Configure at least two test personas: a normal member and a restricted/external-style user where the scenario allows.
7. Export or version every artefact needed to rebuild the solution.

Do not promise colleagues that provisioning always takes five minutes or that every subscriber immediately receives Global Administrator access. Follow the current setup screen and Microsoft documentation for the account in front of you.

Option 2: an organisation-owned development tenant

For ongoing internal development, a separately governed organisation tenant is often stronger than a personal developer subscription.

It can provide:

• stable ownership and offboarding;
• approved licences and test identities;
• tenant-level settings similar to production;
• controlled integrations and service principals;
• longer-lived test data; and
• supportable change and access records.

The trade-off is cost and administration. It also needs guardrails so a “test” tenant does not become an unmanaged production system.

Create a small environment charter covering:

• owner and backup owner;
• permitted data classes;
• licence budget;
• external sharing;
• test account lifecycle;
• connector and app approval;
• reset/rebuild process; and
• which settings deliberately differ from production.

Option 3: a paid trial or test tenant

Microsoft and partners may offer time-limited Microsoft 365 trials. Availability, product bundle, geography, payment requirements and terms change, so use the current sales/trial route rather than a decade-old blog link.

A trial can work for short evaluation when:

• the required SharePoint features are included;
• the expiry date is accepted;
• no irreplaceable data will be stored;
• conversion or closure is planned; and
• the organisation—not one employee’s personal account—owns access.

Do not repeatedly create trials to avoid licensing a continuing business workload. That is neither a reliable lab nor a governance strategy.

A local development machine is not a SharePoint Online sandbox

For SharePoint Framework development, you can write and test parts of a web part on a local workstation or cloud development machine. This is a code environment. It does not reproduce a Microsoft 365 tenant’s identity, permissions, search, app catalogue, Graph access or service behaviour.

A realistic flow is:

1. develop and lint code locally;
2. use mocks or sample data for isolated UI behaviour;
3. package the solution;
4. deploy to an app catalogue in a test tenant;
5. verify with different users and permissions; and
6. move through a governed release process.

GitHub Codespaces can host the development tools in a browser. It still does not give you SharePoint Online.

Power Platform environments solve a different problem

A Power Platform environment can isolate apps, flows, connections and Dataverse data. It is useful when you are building Power Apps or Power Automate solutions around SharePoint.

It does not automatically create an isolated SharePoint tenant. A canvas app connected to a production SharePoint list is still touching production data, even if the app sits in a “development” Power Platform environment.

Use separate SharePoint test sites/lists and test connections. Apply environment variables and connection references where the solution model supports them. Our Power Apps time-tracker build is a useful scenario to practise—but create it with synthetic staff and time records.

Microsoft Fabric is not a SharePoint sandbox

A Microsoft Fabric trial supplies Fabric capacity and analytics experiences. It can help test data ingestion, modelling and reporting, including scenarios that read SharePoint data through supported connectors.

It does not provide a SharePoint Online tenant, site administration or a safe copy of your production SharePoint configuration. Treat it as an analytics trial, not a way to host SharePoint.

Azure is not “free SharePoint Online”

An Azure subscription can host virtual machines and supporting infrastructure. It does not include a free SharePoint Online tenant.

You can build a SharePoint Server lab in Azure virtual machines, but that means a different product and a real infrastructure project. You must account for:

• SharePoint Server and Windows/SQL licensing;
• supported topology and prerequisites;
• identity, certificates and DNS;
• patching and security;
• compute, storage and network costs; and
• teardown or long-term ownership.

Do not use an Azure credit as evidence that the SharePoint software and operation are free.

Shared community tenants: useful but tightly bounded

Community demonstration tenants can be useful for exploring approved samples. For example, the Microsoft 365 and Power Platform Community may provide controlled access to community resources under its own rules.

Never assume a shared tenant is private. Do not upload customer data, proprietary source code, secrets or anything you could not disclose to other participants. You may also lack the administrator permissions needed to test tenant configuration.

Build a test environment that actually teaches you something

Use representative personas

At minimum, test as:

• site owner;
• member with edit rights;
• visitor/read-only user;
• user with no access; and
• external/guest user if external collaboration is in scope.

Testing everything as Global Administrator hides permission defects.

Use representative structure, not sensitive data

Recreate the shape of production:

• similar columns and content types;
• realistic item and file counts;
• versioning and approval settings;
• groups and permission breaks;
• representative file names and metadata; and
• fake personal/customer records.

Synthetic data should reproduce awkward cases—long names, blanks, duplicates, special characters and large files—without copying confidential content.

Record the differences from production

No test tenant perfectly matches production. Maintain a short difference register:

Difference	Why it matters	Compensating test
Fewer licences or features	Behaviour may vary by licence	Confirm entitlement in a production-like pilot
Smaller data volume	Search, delegation or migration performance may differ	Generate safe volume or run a controlled scale test
Different security policies	Sign-in or sharing paths may differ	Ask security owner to validate assumptions
No legacy customisation	Upgrade/migration result may be cleaner than reality	Inventory production before planning

If you are using the lab to prepare a migration, pair it with the discovery and validation steps in our SharePoint migration tools guide.

Frequently asked questions

Can anyone get a free Microsoft 365 developer tenant?

No. Microsoft currently limits sandbox subscriptions to qualifying groups such as eligible Visual Studio subscribers, approved partner/ISV programmes and certain support customers.

Is the Microsoft 365 developer sandbox permanent?

No. It is issued for up to 90 days and can renew when Microsoft determines that the owner remains eligible and has qualifying development activity. Build it as a disposable environment.

Can GitHub Codespaces host SharePoint Online?

No. Codespaces can host development tools and source code. You still need a Microsoft 365 tenant to test SharePoint Online services, identity and permissions.

Keep the boundary clear

Programme eligibility, trials, licences and Microsoft 365 features change. Confirm the current terms shown for your account before relying on a free environment. This guide does not authorise bypassing organisational IT controls; a test tenant still needs an accountable owner and safe data.

Join the SharePoint & Teams Admins Space for practical SharePoint administration, governance and test-before-production guidance.

Sources

• Microsoft: Microsoft 365 Developer Program FAQ
• Microsoft: Set up a Microsoft 365 developer sandbox subscription
• Microsoft 365 Developer Program