Skip to content

Commit 0330b85

Browse files
Update known-limitations.mdx - Windows 365 limitations (#26146)
* Update known-limitations.mdx - Windows 365 limitations In order to connect to Windows 365, on a PC that is running WARP, and while using the Windows App, specific networks now require exclusion. * Apply suggestions from code review Co-authored-by: Kate Tungusova <[email protected]> * Update known-limitations.mdx Removing the term tunnels as its confusing (could be confused with Cloudflared tunenls) * Apply suggestions from code review Good. Co-authored-by: Kate Tungusova <[email protected]> --------- Co-authored-by: Kate Tungusova <[email protected]>
1 parent 233801b commit 0330b85

File tree

1 file changed

+15
-0
lines changed

1 file changed

+15
-0
lines changed

src/content/docs/cloudflare-one/team-and-resources/devices/warp/troubleshooting/known-limitations.mdx

Lines changed: 15 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -159,6 +159,21 @@ Name: connectivity-check.warp-svc
159159
Address: 127.0.2.3
160160
```
161161

162+
## Windows App connection issue with WARP
163+
164+
When the WARP client is active on a local machine, users may be unable to connect to a Windows 365 PC using the [Windows App](https://aka.ms/WindowsApp). This issue does not affect browser-based connections to Windows 365.
165+
166+
To resolve this, exclude the networks specified below from any relevant WARP [device profiles](/cloudflare-one/team-and-resources/devices/warp/configure-warp/device-profiles/). The required networks are listed under the `WindowsVirtualDesktop` service tag in the [Azure IP Ranges and Service Tags – Public Cloud](https://www.microsoft.com/en-us/download/details.aspx?id=56519) resource (search for `"name": "WindowsVirtualDesktop"`).
167+
168+
Microsoft previously provided a [PowerShell script](https://github.com/microsoft/Windows365-PSScripts/tree/main/Windows%20365%20Gateway%20IP%20Lookup) to retrieve these networks, but it has since been deprecated. The relevant networks are now consolidated to the following subnets and should be excluded from any relevant WARP device profiles:
169+
170+
```
171+
40.64.144.0/20
172+
51.5.0.0/16
173+
2603:1061:2010::/48
174+
2603:1061:2011::/48
175+
```
176+
162177
## Windows 10 in Microsoft 365 Cloud PC is not supported
163178

164179
Use of the WARP client in a Microsoft 365 Windows 10 Cloud PC is not supported. To work around this limitation, use Windows 11.

0 commit comments

Comments
 (0)