If you are interested in modernising your cloud computing, check out our previous post about Windows 365 to better understand what it entails and who can benefit from it. Entering this new era of computing with seamless integration of Cloud PCs and your local network sounds pretty straightforward if you read Microsoft’s introduction and overview.
At The Missing Link, we had the opportunity to access Windows 365 trials at an early stage and recommend having a closer look at what this model entails because there are some requirements, components and cost considerations that aren’t immediately apparent.
“After running Proof of Concepts, we found that there is more to Windows 365 than just buying your subscription and provisioning the Cloud PCs,” explains James Morrow, Senior Solutions Consultant at the Missing Link.
One catch, for example, is that your existing Group Policies may impact the provisioning of new Windows 365 Cloud PCs if you are blocking the WinRM app or the SOAP protocol for security reasons.
Windows 365 requires specific background infrastructure for it to work and we highly recommend considering the following:
Ensure that you enable Intune and configure it with your company applications, security and compliance policies.
Azure tenancy and subscription
Azure VNET for Windows 365 Cloud PCs
Domain controller with Azure AD Sync with Device Writeback (Enterprise subscription only). This domain controller could be in Azure (not ADDS) or on-premise.
VPN Connectivity to the domain controller (Enterprise subscription only) if the domain controller is on-premise. If the domain controller is in Azure, you need to establish connectivity between the VNETs.
Every user who accesses a Cloud PC needs to be a licensed Microsoft 365 user, which enables them to use Intune.
On top of the Microsoft 365 subscriptions for end-users and the Windows 365 Cloud PC subscriptions, there are additional costs to consider:
Azure traffic on Cloud PC VNET – All internet access to the Cloud PCs runs through the Azure VNET, as such all traffic will be charged at standard Azure rates. For example, 5TB of internet egress traffic will cost approximately AU$775 per month.
Azure VPN Gateway – Depending on which gateway type you selected, this device will be charged at standard Azure rates. For example, a VPN Gateway 1 SKU (up to 650Mbps and no zone redundancy) with a single site-to-site VPN will cost approximately AU$210 per month. If you have an ExpressRoute in place, you don’t need this VPN gateway.
Azure VPN traffic – All traffic that traverses the VPN will be charged at the standard Azure rates. For example, 1TB of outbound VPN traffic from the VPN will cost approximately AU$155 per month. If you have an ExpressRoute in place, the traffic charges for this connection will apply instead.
Public IP Addresses – The VPN gateway will need a static IP address, this will be charged at standard Azure rates. A single public IP is approximately $5 per month.