Let me quickly share something that I discovered this week. The licenses in my demo environment expired and the Cloud PCs entered grace period. I was neatly informed about this with the alerts that I enabled as described in my previous blog post.
Pending Resize
No problem! I can easily assign a new license and have this problem fixed. I however wanted to use this moment to scale-up some of my Cloud PCs to a higher Windows 365 SKU.
As you might remember from one of my earlier blog post, the resize process is tied to a specific flow that you have to follow to make sure the resize is done correctly. As my assignment is also done through group assignments, the normal flow here would be to have the licenses available in my tenant, which I had; and first resize the Cloud PCs so they would enter a “license pending” state before changing the group membership.
After I initiated the resize I waited for the license pending warning but it never came. I tried to resize again to make sure I initiated the resize correctly. This resulted in receiving the message that the resize was already pending.
Stuck
I was now in a state that I could not recover the Cloud PCs from grace period without buying new licenses. This for a SKU that I wanted to get rid of. The grace period expired while the Cloud PC still gave the “already resizing” message and the Cloud PC was removed automatically.
Conclusion
Although this is not a big deal for me as this is not a production environment. It still leaves a bad taste in my mouth. I can easily see customers waiting to resize their Cloud PCs until their existing licenses are about to expire. If I had initiated the resize with the licenses still active, I wouldn’t have been stuck as the grace period wouldn’t have been triggered.
I’m still wondering if I did something wrong or if I hit a bug within Windows 365. Let me know what you think that happened so I can make sure this won’t happen again.
Leave a Reply