|
1 | 1 | --- |
2 | 2 | title: Configure networking |
3 | 3 | description: Learn how to configure networking for Managed DevOps Pools. |
4 | | -ms.date: 06/18/2025 |
| 4 | +ms.date: 07/08/2025 |
5 | 5 | --- |
6 | 6 |
|
7 | 7 | # Configure Managed DevOps Pools networking |
@@ -158,11 +158,13 @@ If you have systems in place on your network (NSG, Firewall, etc.) that restrict |
158 | 158 | * `packages.microsoft.com` - Provisioning Linux machines |
159 | 159 | * `ppa.launchpad.net` - Provisioning some specific Linux distros |
160 | 160 | * `dl.fedoraproject.org` - Provisioning certain Linux distros |
161 | | -* Optional, but required for specific Azure DevOps features to work on your pipelines. In the following set, the wildcard can be replaced with the specific Azure DevOps organization hosting your pipeline. For example, if your organization is named `contoso`, you can use `contoso.services.visualstudio.com` instead of `*.services.visualstudio.com`. These entries are the minimum domains required. If you have any issues, see [Azure DevOps allowlist](/azure/devops/organizations/security/allow-list-ip-url) for the full list of domains required. |
| 161 | +* Optional, but required for specific Azure DevOps features to work on your pipelines. In the following set, the wildcard can be replaced with the specific Azure DevOps organization hosting your pipeline. For example, if your organization is named `contoso`, you can use `contoso.services.visualstudio.com` instead of `*.services.visualstudio.com`. |
162 | 162 | * `*.services.visualstudio.com` |
163 | 163 | * `*.vsblob.visualstudio.com` - Used for Artifacts, both uploading and consuming |
164 | 164 | * `*.vssps.visualstudio.com` - Used for authentication with Azure DevOps for certain features |
165 | 165 | * `*.visualstudio.com` |
| 166 | + > [!NOTE] |
| 167 | + > The previous entries are the minimum domains required. If you have any issues, see [Azure DevOps allowed IP addresses and domain URLs](../organizations/security/allow-list-ip-url.md) for the full list of required domains. |
166 | 168 | * Azure related endpoints: |
167 | 169 | Azure VMs may route traffic to certain Azure features through your subnet. For these requests, you have the option of routing requests through Azure directly, or enabling access through your network. |
168 | 170 | 1. [Configuring Azure traffic to run through Service Endpoints](/azure/virtual-network/virtual-network-service-endpoints-overview) |
@@ -195,3 +197,4 @@ If you're migrating from Azure Virtual Machine Scale Set agents and are already |
195 | 197 | ## See also |
196 | 198 |
|
197 | 199 | * [Configure pool settings](./configure-pool-settings.md) |
| 200 | +* [Azure DevOps allowed IP addresses and domain URLs](../organizations/security/allow-list-ip-url.md) |
0 commit comments