Intune Licensing for Testing

Question

Intune Licensing for Testing

Girish Balekate Ramachandra 45

We are planning to automate Windows 11 Hotpatch testing using Intune APIs and would like to understand the licensing requirements.

What is the recommended way for an organization to obtain an Microsoft Intune license for testing purposes?

Is there a way to get a trial or demo license for Intune specifically for development or automation testing?

Can an existing Microsoft Azure tenant be used to enable an Intune trial, or do we need to create a separate tenant?

Are there any sandbox environments or developer programs (for example via Microsoft 365 Developer Program) that provide temporary access to Intune for API testing?

The goal is to build a test environment to validate Hotpatch deployment workflows using Intune APIs without impacting production systems.

Pauline Mbabu 1,835 Reputation points Microsoft Employee

2026-04-17T16:19:37.2233333+00:00

Hello Girish,
For building a nonproduction test environment to validate Windows 11 Hotpatch workflows using Intune APIs, the recommended approach is to use either the Microsoft Intune free trial or a Microsoft 365 Developer Program sandbox, both of which are designed specifically for evaluation and development scenarios. The Intune free trial automatically creates a new Microsoft Entra tenant and provides an Enterprise Mobility + Security trial that includes Intune and Entra ID P1 or P2, allowing you to enroll devices, assign licenses, and exercise Intune APIs without impacting production resources, but it does not support enabling the trial directly on an existing tenant. For longer term or repeated API testing, the Microsoft 365 Developer Program is often the most practical option because it provides a renewable Microsoft 365 E5 developer subscription with access to Microsoft Intune in an isolated sandbox tenant that is explicitly intended for development and automation testing, including Microsoft Graph and Intune APIs. This sandbox is separate from production by design, supports Hotpatch related testing when licensing and OS prerequisites are met, and avoids production risk, though eligibility requirements apply and it cannot be attached to an existing tenant. Relevant references include the Intune free trial documentation at https://learn.microsoft.com/en-us/intune/intune-service/fundamentals/free-trial-sign-up, the Microsoft 365 Developer Program overview at https://developer.microsoft.com/microsoft-365/dev-program and https://learn.microsoft.com/en-us/office/developer-program/microsoft-365-developer-program, and Hotpatch prerequisites and management details at https://learn.microsoft.com/en-us/windows/deployment/windows-autopatch/manage/windows-autopatch-hotpatch-updates.

1 answer

Your answer

Pauline Mbabu 1,835 Reputation points Microsoft Employee

2026-04-17T16:19:37.2233333+00:00

Hello Girish,
For building a nonproduction test environment to validate Windows 11 Hotpatch workflows using Intune APIs, the recommended approach is to use either the Microsoft Intune free trial or a Microsoft 365 Developer Program sandbox, both of which are designed specifically for evaluation and development scenarios. The Intune free trial automatically creates a new Microsoft Entra tenant and provides an Enterprise Mobility + Security trial that includes Intune and Entra ID P1 or P2, allowing you to enroll devices, assign licenses, and exercise Intune APIs without impacting production resources, but it does not support enabling the trial directly on an existing tenant. For longer term or repeated API testing, the Microsoft 365 Developer Program is often the most practical option because it provides a renewable Microsoft 365 E5 developer subscription with access to Microsoft Intune in an isolated sandbox tenant that is explicitly intended for development and automation testing, including Microsoft Graph and Intune APIs. This sandbox is separate from production by design, supports Hotpatch related testing when licensing and OS prerequisites are met, and avoids production risk, though eligibility requirements apply and it cannot be attached to an existing tenant. Relevant references include the Intune free trial documentation at https://learn.microsoft.com/en-us/intune/intune-service/fundamentals/free-trial-sign-up, the Microsoft 365 Developer Program overview at https://developer.microsoft.com/microsoft-365/dev-program and https://learn.microsoft.com/en-us/office/developer-program/microsoft-365-developer-program, and Hotpatch prerequisites and management details at https://learn.microsoft.com/en-us/windows/deployment/windows-autopatch/manage/windows-autopatch-hotpatch-updates.

Answer 1

For testing and automation of Windows 11 Hotpatch deployment via Intune APIs, the supported options in the provided context are:

Use an Intune free trial in a tenant
- Sign up for a Microsoft Intune free trial, which creates a new tenant and provides an Enterprise Mobility + Security (EMS) trial that includes Microsoft Intune and Microsoft Entra ID P1 or P2.
- This trial gives access to the Microsoft Intune admin center and Microsoft 365 admin center, and allows adding users, assigning Intune licenses, and managing devices and policies for testing.
- The trial provides 25 Intune licenses, which can be assigned to test users to enroll test devices and exercise Intune APIs and workflows.
Licensing requirements for testing
For a realistic Hotpatch deployment test environment using Intune APIs:
- At minimum, an Intune subscription is required so devices can be enrolled and managed.
- If testing compliance-based or Conditional Access–driven workflows (for example, enforcing rules before Hotpatch deployment), Microsoft Entra ID P1 or P2 is also required. These are included in the EMS trial and many Microsoft 365 E3/E5 plans.
- Each test user or userless test device that accesses Intune must have an appropriate Intune license assigned.
Using an existing Azure/Microsoft Entra tenant vs. a separate tenant
- When signing up for the Intune free trial, a new tenant is automatically created as part of the process described in the context. That flow is designed for evaluation and testing without affecting an existing production tenant.
- The context does not describe enabling an Intune trial directly on an existing tenant, only that the free trial sign-up creates a new tenant and then you can confirm the trial licenses. For strict separation between test and production, using this separate trial tenant is the recommended pattern in the provided material.
Sandbox / developer environments
- The context does not describe any special developer program or sandbox (such as a Microsoft 365 Developer Program tenant) that includes Intune specifically for API testing.
- Instead, it explicitly recommends using the Intune free trial and the associated EMS subscription as the evaluation path for planning and testing an Intune deployment.
How to structure the test environment
Within the Intune trial tenant:
- Add test users and assign them Intune licenses from the trial pool.
- Enroll non-production Windows 11 devices into Intune.
- Use the Intune admin center and Intune APIs to create and deploy policies and profiles, and to validate Hotpatch deployment workflows end-to-end without touching production devices.

References:

Share via

Intune Licensing for Testing

1 answer

Your answer