Has anyone implemented infrastructure as code for deploying and managing enterprise Microsoft 365 Cloud PCs? I'm looking for a platform-agnostic approach using tools such as Terraform or Ansible, ideally integrated with a CI/CD pipeline. I'm also considering whether a straightforward PowerShell-based CI/CD solution would be more practical. I'd appreciate advice on what should actually be automated and which approach has worked well in real environments.
3 Answers
Terraform or OpenTofu combined with a CI/CD platform can work well, especially for the infrastructure around the Cloud PCs. You can manage networking, images, policies, and related resources as code, while letting licensing and provisioning policies handle user assignment. There are also reusable modules and Microsoft Graph-based automation options that may help with policy configuration.
Cloud PCs are mostly policy-driven rather than individually created. Once the provisioning policy is configured, assigning the appropriate license to a user generally triggers provisioning automatically. Because of that, there may not be much value in creating each Cloud PC through Terraform or PowerShell. IaC could still be useful for surrounding resources such as networking, images, policies, and other supporting configuration.
That matches what I suspected. I’ve managed larger virtual desktop environments with Terraform, but my experience with Cloud PCs is limited, so I’m mainly trying to understand which parts are worth automating.
A PowerShell deployment process for individual Cloud PCs would probably be unnecessary overengineering. The normal workflow is license assignment plus a provisioning policy. Automation can still help with joiner, mover, leaver processes, license management, and reprovisioning, but the Cloud PC lifecycle itself is largely handled by the service.
That makes sense. I’m comfortable managing virtual desktop environments with Terraform, but I’d like to find a module or proven pattern specifically for Cloud PC policies and supporting resources.