You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
>Opening these URLs is essential for a reliable Windows Virtual Desktop deployment. Blocking access to these URLs is unsupported and will affect service functionality. These URLs only correspond to Windows Virtual Desktop sites and resources, and don't include URLs for other services like Azure Active Directory.
102
101
103
-
Here are a list of URLs that are optional for your Azure virtual machines to hve access to:
102
+
The following table lists optional URLs that your Azure virtual machines can have access to:
104
103
105
104
|Address|Outbound TCP port|Purpose|Service Tag|
106
105
|---|---|---|---|
@@ -116,7 +115,7 @@ Here are a list of URLs that are optional for your Azure virtual machines to hve
116
115
>[!NOTE]
117
116
>Windows Virtual Desktop currently doesn't have a list of IP address ranges that you can whitelist to allow network traffic. We only support whitelisting specific URLs at this time.
118
117
>
119
-
>For Officerelated URL’s, visit https://docs.microsoft.com/en-us/office365/enterprise/urls-and-ip-address-ranges. This documentation also covers required AAD related URL’s.
118
+
>For a list of Office-related URLs, including required Azure Active Directory-related URLs, see [Office 365 URLs and IP address ranges](/office365/enterprise/urls-and-ip-address-ranges).
120
119
>
121
120
>You must use the wildcard character (*) for URLs involving service traffic. If you prefer to not use * for agent-related traffic, here's how to find the URLs without wildcards:
0 commit comments