> For the complete documentation index, see [llms.txt](https://docs.parallels.com/landing/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.parallels.com/landing/daas-guides/daas-administrators-guide/frequently-asked-questions/how-to-provide-internet-access-for-parallels-daas-virtual-machines.md).

# 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:

1. 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
2. Azure Firewall
   * Suitable for environments requiring advanced traffic control, filtering, or logging
   * Requires routing outbound traffic through the firewall
3. Network Virtual Appliance (NVA)
   * Use an NVA that provides outbound internet access
   * Ensure correct user‑defined routes (UDRs) are configured
4. Public IP on the VM (**Not Recommended**)
   * Technically supported but discouraged due to security risks
   * Not suitable for production Parallels DaaS environments

{% hint style="warning" %}
**Important**: Simply creating a VNet or subnet is not sufficient. Outbound connectivity must be explicitly enabled using one of the supported approaches listed above.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.parallels.com/landing/daas-guides/daas-administrators-guide/frequently-asked-questions/how-to-provide-internet-access-for-parallels-daas-virtual-machines.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.