My experience deploying Windows 365 — Part 1 — Pre-Requisites
I’m going to give the Microsoft published guidance a whirl, and intertwine my notes. Essentially, this is all the stuff that needs to be done prior to the Endpoint Manager Console will actually showing you the option to create provisioning policies, on prem connections,etc.
Here is Microsoft’s overview
First we will assign user licenses.
It turns out MSDN Subscriptions aren’t eligible for W365 deployment (at the moment, or at least just for me).
I provisioned a pay as you go subscription and I was then able to purchase a trial license of Windows 365 Cloud PC.
Also strangely, I was unable to access the W65 trial. I had to purchase a license.
I was then able to navigate to the Microsoft Admin portal and assign myself a license.
In a related note, it turns out there was an outage as it related to the free trial. Seems like they were consumed before I could sign up for one.
To summarize the next steps:
I created a valid vnet in Azure, and subsequently deployed a Domain Controller within a Virtual Machine in Azure, Updated the previously created vnet to point to my newly created DC in azure, installed Azure AD Connect with default settings, enabled hybrid join/device registration, and created a test user. I purchased a test domain for this (nathanblab.com), and verified/added this domain in the Microsoft Admin portal as well. I ensured my newly created user was sync’d to the cloud, and then applied a new Windows 365 Enterprise license to it.
After struggling to see the policies in the portal for a week, it turns out you need an enterprise license for Cloud PC to create/manage them via provisioning policies. I switched my license from Business to enterprise and this worked out.
Now we finally see more options instead of the default landing page.
I’ll cover the actual deployment experience in part 2.
