Windows 365: When Deprovisioning Goes Wrong

By Rory Monaghan

SHARE

Recently, I encountered an interesting issue  when I tried to deprovision one of my Windows 365 Enterprise Cloud PCs. I went through the normal procedure of un-assigning the user from the Provisioning Policy and then ending the grace period on the existing Cloud PC but this resulted in an error.

I expected since there was an error, the PC would remain in a grace period but instead the PC disappeared. It never showed as deprovisioning but was no longer in Microsoft Endpoint Manager. I thought maybe it was a false negative. I tried to provision a fresh PC by adding the user back to the provisioning policy but it failed claiming the user didn’t have an available license. Then when I removed the user from the provisioning policy again, a PC appeared in a Pending state. From this point I was stuck, the PC was in limbo. No matter what I did a PC kept coming back in a Pending state.

Lucky for me, Fabian at Microsoft support was awesome and told me exactly what to do and it fixed the issue. These are the steps:

  1. Delete the existent provisioning policy within Intune.
  2. Remove the Windows 365 license from the affected user.
  3. Go to Azure > Azure Active Directory > Users > Click on the affected user > Licenses > Click on Reprocess.
  4. Wait 5-10 minutes.
  5. Reassign the license back to the user.
  6. Click on reprocess again.
  7. Create a new provisioning policy and target a group containing your user.

This did the trick and got me back to a working state and since I didn’t see this in the support docs or on anyone else’s blog, I figured I would share it to save others time but full credit to Fabian at Microsoft.

Photo by Pero Kalimero on Unsplash

 

Let's make virtualization easier!

Be amongst the first to know when I publish new reviews, guides and tools to simplify your projects.

By signing up, you agree to our Terms of Use and acknowledge the data practices in our Privacy Policy. You may unsubscribe at any time.