How to provide internet access for Parallels DaaS virtual machines
Problem
Why do my Parallels DaaS virtual machines no longer have internet access, and how can I restore outbound connectivity?
Solution
Microsoft is retiring default outbound internet access for Azure virtual machines. As a result, new and existing Parallels DaaS deployments can no longer rely on implicit outbound connectivity provided by Azure. This means:
For new Azure virtual machines, default outbound access is no longer available.
Virtual machines must now be deployed in a VNet and subnet that explicitly allows outbound internet connectivity.
If outbound connectivity is not explicitly configured, Parallels DaaS virtual machines will be unable to:
Access the internet
Download updates
Reach activation, licensing, or external services
Communicate with cloud‑based management or monitoring tools
This change affects all Parallels DaaS environments deployed on Azure after Microsoft’s enforcement dates.
How to Restore Internet Access for Parallels DaaS VMs
To ensure your virtual machines have internet access, you must configure an explicit outbound connectivity method in Azure. Microsoft recommends the following supported options:
Azure NAT Gateway (Recommended)
Attach a NAT Gateway to the subnet used by Parallels DaaS VMs
Provides scalable, reliable outbound internet access
No inbound ports are exposed
Azure Firewall
Suitable for environments requiring advanced traffic control, filtering, or logging
Requires routing outbound traffic through the firewall
Network Virtual Appliance (NVA)
Use an NVA that provides outbound internet access
Ensure correct user‑defined routes (UDRs) are configured
Public IP on the VM (Not Recommended)
Technically supported but discouraged due to security risks
Not suitable for production Parallels DaaS environments
Important: Simply creating a VNet or subnet is not sufficient. Outbound connectivity must be explicitly enabled using one of the supported approaches listed above.
Last updated