How to configure Windows 365 Enterprise in Microsoft Endpoint Manager

10-24-2021 11:50 AM


Disclaimer: All information and content in this blog post is provided without any warranty whatsoever. The entire risk of using this information or executing the provided content remains with you. Under no circumstances should the mentioned persons or vendors, the author, or anyone else involved in creating these blog posts be held liable for any damage or data loss.

Attention: Microsoft has paused their free Windows 365 trial program while they provision additional capacity!

Sign up to learn more about Windows 365

The word on Twitter is that Windows 365 trial license may be available. Well, for some at least! I donΒ΄t see it in my tenants yet! So, the reality is that the trial license may only be available in certain countries for now.

Didn’t you get a Windows 365 trial license in first round? Try again - You might be lucky...

Source: Twitter


In this blog post we'll take a first look at Windows 365 Enterprise and how to configure it in Microsoft Endpoint Manager Admin Center. Windows 365 is a cloud-based service also known as Software/Desktop as a Service (SaaS/DaaS) provided by Microsoft which delivers a personalized Windows Cloud PC experience and is accessible from anywhere, on any endpoint. By default, Windows 365 Enterprise Cloud PCs are joined to your Active Directory domain, synced to Azure AD and fully managed by Microsoft Endpoint Manager. Each Cloud PC is assigned to an individual user and is their dedicated Windows device. Assigning a Cloud PC to a user is just like assigning an Exchange Online mailbox to a user. When a Windows 365 license is assigned to a user, provisioning of a new Cloud PC automatically starts and the Cloud PC is enrolled into Microsoft Endpoint Manager. As mentioned, Windows 365 does require a user-based license and the license price depends on the size and performance of the Cloud PC needed - More details about Windows 365 plans and pricing Source: Microsoft Docs

Prerequisites and Requirements

  • An active Azure subscription

  • Sufficient Azure subscription permissions (e.g. Subscription Owner) to grant Windows 365 each of the following:

    • A reader role on the subscription

    • Network contributor permissions on the resource group

    • A network contributor role on the virtual network (VNet)

  • A valid and working Intune and Azure AD tenant.

  • Azure virtual network (VNet) with access to an enterprise domain controller, either in Azure or on-premises and it must be able to resolve DNS entries for your Active Directory Domain Services (AD DS) environment

  • Site-to-Site VPN or Express route for connectivity to your on-premises Active Directory

  • A subnet within the virtual network (VNet) and available IP address space

  • An Active Directory user account with sufficient permissions to join the computer to your Active Directory domain

  • The Active Directory must be in sync with Azure AD to provide hybrid identity in Azure AD (AD Connect)

  • Users that are assigned Cloud PCs must have a synced identity available in both Active Directory and Azure AD

  • Supported Azure regions for Cloud PC provisioning (The virtual network (VNet) should be in a supported region)

    • US East, US East 2, US West 2, US South central, Asia Southeast, Australia East, Europe North, Europe West, UK South, Canada Central, India Central, Japan East, France Central

  • Microsoft Intune supported licenses (e.g. Microsoft 365 E3) in order to manage the devices

  • Users must have licenses for Windows, Intune, Azure AD, and Windows 365 to use their Cloud PC (e.g. Microsoft 365 E3 + Windows 365 Enterprise 4 vCPU, 16 GB, 128 GB)

  • Microsoft Endpoint Manager Admin Center for Cloud PC management

  • The new built-in Cloud PC Administrator role in MEM or one of the following permissions in AAD

    • Global Administrator

    • Intune Administrator

Source: Microsoft Docs

Note: I will be skipping the part about Azure subscription, Azure Virtual Network (VNet), Site-to-Site VPN and Hybrid Azure AD join configuration, since I've already got these prerequisites in place for my Azure Virtual Desktop (AVD) configuration.

For more information about that, please take a look at the following sites.

Purchase and assign Windows 365 licenses

Okay, let's get started! - The first thing we need to do is purchase a Windows 365 Enterprise license. Go to

Expand β€œBilling”, select β€œPurchase services” and click on β€œWindows 365” As you can see on this page, there are 3 x Windows 365 editions available.

  • Windows 365 Business

  • Windows 365 Business (with Windows Hybrid Benefit)

  • Windows 365 Enterprise

In this blog post we will be focusing on the enterprise edition. Are you looking for a Windows 365 Business vs. Enterprise comparison? - More details about get started with Windows 365 Business

Click on β€œLicenses” From the licenses page you can select products to view and assign licenses (not recommended). As you can see, I've added a β€œWindows 365 Enterprise 4 vCPU, 16GB, 128GB” trial license for the purpose of this blog post.

Let's assign license directly to a user. Go to

Important: Group based license assignment will block the Windows 365 Cloud PC resize feature.

Click on β€œGroups”, create a new user-based security group and give it a friendly group name and description (optional). Note. We recommend using a synced user-based security group from your on-premises Active Directory.

Select your newly created security group. Click on β€œMembers” and then click β€œAdd members”. Click on the user we just added to the group.

Click on β€œLicenses” and assign your Windows 365 license to the user.

Windows 365 Configuration

We can continue with the Windows 365 configuration, when all the prerequisites and requirements are met. Click on β€œDevices” and select β€œWindows 365” from the β€œProvisioning” section in Microsoft Endpoint Manager Admin Center.

On-premises network connection

First we'll need to configure a on-premises network connection, which is required so that the Cloud PCs can be created, domain joined and managed with Microsoft Endpoint Manager. Click on the β€œOn-premises network connection” tab and select β€œCreate connection”

On the β€œNetwork details” page, we need to give the configuration a friendly name. Next, select your Azure subscription, Resource group, Virtual network and Subnet from the drop-down menus. Note. If you have multiple locations, we recommend that you add the region to the name (e.g. MINDCORELAB West Europe) Click β€œNext”

On the β€œAD domain” page, we need to enter the required Active Directory domain information and credentials. Note. The β€œOrganizational Unit” field is optional. Click β€œNext”

Review the information and click β€œReview + create”

After completing the on-premises network connection configuration, a service called Watchdog runs in the background and will check your environment for all the prerequisites and requirements needed to use Windows 365 Enterprise. Within 5-10 minutes we should be able to check the on-premises network connection status. Click on the status.

If you see any errors or warnings on the status page, I would suggest that you address those before continuing the Windows 365 configuration. I encountered a warning for "Azure AD device sync" during my first try and it turned out that I forgot to add the new Active Directory device OU for Windows 365 devices in AD Connect - Everything passed after I fixed that small issue.

To review or change the on-premises network connection details, select the β€œProperties” tab.

Provisioning policy

Once the on-premises network connection is created and with all check successful passed, you can go ahead and configure the provisioning policy. Click on β€œWindows 365” from the β€œProvisioning” section, select the β€œProvisioning policies” tab and then click on β€œCreate policy”

Give the policy a friendly name and a description (optional). Select your on-premises network connection and click β€œNext” Note. If you have multiple locations, we recommend that you add the region to the name (e.g. MINDCORELAB West Europe)

Select your image type and click β€œSelect” - I will be using one from the PC OS image gallery. Note. It is possible to upload and use a custom image.

Select an image and click β€œSelect”

Click β€œNext”

Select the user-based security group we created earlier and click β€œNext”

Review the information and click β€œCreate”

You'll see the new policy in the list of provisioning policies.

Provisioning of a new Cloud PC starts automatically for each user in the assigned security group. Click on the β€œAll cloud PCs” tab.

After 20-50 minutes the Cloud PCs are ready to use and the status has changed to β€œProvisioned” Whoopsie… In my eager to get started with Windows 365 I accidentally selected the wrong user (a cloud only user) DOH!

At this point we should be able to see the Cloud PCs in our Active Directory, Azure AD and Intune. Access you domain controller, open β€œActive Directory Users and Computers” and navigate to the OU as provided during the creation of the on-premises network connection.

The view from β€œAll devices” in Azure AD.

The view from β€œWindows devices” in Intune.

Self-service purchases (Enabled by default)

Here is something to consider! - Do you want to allow your end users to make self-service purchases? If not, you should consider disable that option since it's enabled by default. More details about Self-service purchases


We are finally ready to test the newly created Windows 365 Cloud PC. Go to or

Click β€œNext, Next, Next…”

Windows 365 web portal

From within the web portal you should see your cloud PC and its configuration.

If you click on the gear icon in the right corner, you will find the self-service capabilities for end users (Restart, Rename and Troubleshoot). To start the Cloud PC from within the web portal, click on β€œOpen in browser”

Click β€œAllow”

Enter your credentials.

And we are connected - Awesome! Note. By default the users does not have local admin rights. However, it is possible to provide local admin rights to a user-based security group through "User settings" for Windows 365 in Microsoft Endpoint Manager Admin Center.

From a Command Prompt, I can confirm that the Cloud PC is hybrid joined and it can communicate with on-premises devices.

Let's start writing on a word document and then close the web browser.

Remote Desktop

From within the web portal, click on the β€œdownload icon” and download the β€œMicrosoft Remote Desktop for Windows”

Install the β€œMicrosoft Remote Desktop for Windows” and start the β€œRemote Desktop” app. Choose to subscribe with URL and you should see your Cloud PC workspace appear within a few seconds.

Double-click on your Cloud PC and enter your credentials.

You will immediately notice that the word document is still open and that we can continue our writing.


That was our very first look at Windows 365 Enterprise edition! There are many prerequisites and requirements to address before setting up Windows 365 Enterprise - Microsoft has announced that native Azure AD support will be available for Windows 365 Enterprise soon, which will simplify the process even further and at a lower cost. But once the prerequisites and requirements are met, Windows 365 was quite simple to configure and easy to use from both a web browser and remote desktop app. - That's it folks. Happy testing! If you have any questions regarding this topic, feel free to reach out to me. I am most active on Twitter!

Last updated