Windows 365 Cloud PCs
What the network Cloud PCs are provisioned on needs for provisioning and health checks, from the Windows 365 network requirements.
Managed device · Commercial · checked against its pages today 02:28 UTC · Windows 365
Where these entries come from
15 from 1 publisher page- Network requirements 1 section · 15 entries · read today 02:28 UTC
Changes in the last 90 days
None of these pages added or removed a destination in the sections this bundle reads.
ChangeIntel reads each page once a day: the destinations in its tables, lists and code blocks, under the sections named above. Entries follow the page; nothing is added that it does not publish.
Downloads
Built from the pages and endpoint sets above, as last read| Format | Destinations | Left out | Download |
|---|---|---|---|
| Plain list, one per line | 15 | 0 | Open |
| GSA V1 domain list | 15 | 0 | Open |
| GSA V1 Graph request body | 15 | 0 | Download |
| GSA V2 rules (review JSON) | 15 | 0 | Download |
| GSA V2 rules (CSV) | 15 | 0 | Download |
About these formats and checking them on a device
"Left out" counts entries a format cannot hold: IP ranges in web filtering, mid-name wildcards, URLs in a V1 domain list, and unfilled values. The V2 JSON is a review format; Microsoft publishes no Graph request shape for V2 rules yet. See how V1 and V2 evaluate.
The same entries are JSON at /api/v1/access-bundles/windows-365-cloud-pcs. To check them from the workstation itself, run Test-ChangeIntelAccessBundle -Bundle windows-365-cloud-pcs from the ChangeIntel PowerShell module there: it resolves DNS and tries TCP and TLS to each published host, and reports certificate issuers that suggest TLS inspection.
The profile each destination goes to is inferred from Microsoft's published material, not confirmed. Confirm in the Global Secure Access client: Advanced diagnostics, Forwarding profile.
Expected to reach web filtering
11expected to go through the Internet Access profile, where a block-by-default web filtering policy would have to allow the ones your scenario needs
| Destination | Why it's needed | Source |
|---|---|---|
global.TCP 443, 5671 |
443 & 5671 outbound | Network requirements · Windows 365 serviceInternet Access profile · indicated, not confirmedNot in the Microsoft 365 endpoint list the Microsoft traffic profile is built from, so it is expected to go through the Internet Access profile when that profile is on. Not confirmed: the Entra system profile's hosts aren't published. |
hm-iot-in-2-prod-preu01.TCP 443, 5671 |
443 & 5671 outbound | Network requirements · Windows 365 serviceInternet Access profile · indicated, not confirmedNot in the Microsoft 365 endpoint list the Microsoft traffic profile is built from, so it is expected to go through the Internet Access profile when that profile is on. Not confirmed: the Entra system profile's hosts aren't published. |
hm-iot-in-2-prod-prna01.TCP 443, 5671 |
443 & 5671 outbound | Network requirements · Windows 365 serviceInternet Access profile · indicated, not confirmedNot in the Microsoft 365 endpoint list the Microsoft traffic profile is built from, so it is expected to go through the Internet Access profile when that profile is on. Not confirmed: the Entra system profile's hosts aren't published. |
hm-iot-in-3-prod-preu01.TCP 443, 5671 |
443 & 5671 outbound | Network requirements · Windows 365 serviceInternet Access profile · indicated, not confirmedNot in the Microsoft 365 endpoint list the Microsoft traffic profile is built from, so it is expected to go through the Internet Access profile when that profile is on. Not confirmed: the Entra system profile's hosts aren't published. |
hm-iot-in-3-prod-prna01.TCP 443, 5671 |
443 & 5671 outbound | Network requirements · Windows 365 serviceInternet Access profile · indicated, not confirmedNot in the Microsoft 365 endpoint list the Microsoft traffic profile is built from, so it is expected to go through the Internet Access profile when that profile is on. Not confirmed: the Entra system profile's hosts aren't published. |
hm-iot-in-4-prod-prna01.TCP 443, 5671 |
443 & 5671 outbound | Network requirements · Windows 365 serviceInternet Access profile · indicated, not confirmedNot in the Microsoft 365 endpoint list the Microsoft traffic profile is built from, so it is expected to go through the Internet Access profile when that profile is on. Not confirmed: the Entra system profile's hosts aren't published. |
hm-iot-in-prod-prap01.TCP 443, 5671 |
443 & 5671 outbound | Network requirements · Windows 365 serviceInternet Access profile · indicated, not confirmedNot in the Microsoft 365 endpoint list the Microsoft traffic profile is built from, so it is expected to go through the Internet Access profile when that profile is on. Not confirmed: the Entra system profile's hosts aren't published. |
hm-iot-in-prod-prau01.TCP 443, 5671 |
443 & 5671 outbound | Network requirements · Windows 365 serviceInternet Access profile · indicated, not confirmedNot in the Microsoft 365 endpoint list the Microsoft traffic profile is built from, so it is expected to go through the Internet Access profile when that profile is on. Not confirmed: the Entra system profile's hosts aren't published. |
hm-iot-in-prod-preu01.TCP 443, 5671 |
443 & 5671 outbound | Network requirements · Windows 365 serviceInternet Access profile · indicated, not confirmedNot in the Microsoft 365 endpoint list the Microsoft traffic profile is built from, so it is expected to go through the Internet Access profile when that profile is on. Not confirmed: the Entra system profile's hosts aren't published. |
hm-iot-in-prod-prna01.TCP 443, 5671 |
443 & 5671 outbound | Network requirements · Windows 365 serviceInternet Access profile · indicated, not confirmedNot in the Microsoft 365 endpoint list the Microsoft traffic profile is built from, so it is expected to go through the Internet Access profile when that profile is on. Not confirmed: the Entra system profile's hosts aren't published. |
hm-iot-in-prod-prna02.TCP 443, 5671 |
443 & 5671 outbound | Network requirements · Windows 365 serviceInternet Access profile · indicated, not confirmedNot in the Microsoft 365 endpoint list the Microsoft traffic profile is built from, so it is expected to go through the Internet Access profile when that profile is on. Not confirmed: the Entra system profile's hosts aren't published. |
Not determined
2public material doesn't settle it; check the client's forwarding profile
| Destination | Why it's needed | Source |
|---|---|---|
*. |
Windows 365 service | Network requirements · Windows 365 serviceProfile not determined · possibly the Microsoft traffic profileIn Microsoft 365 Common endpoint set 50 (Default category). Microsoft documents that the Microsoft traffic profile is built from this list, combined by traffic category, but not which categories it includes. |
login. |
Windows 365 service | Network requirements · Windows 365 serviceProfile not determined · possibly the Microsoft traffic profileIn Microsoft 365 Common endpoint set 97 (Default category). Microsoft documents that the Microsoft traffic profile is built from this list, combined by traffic category, but not which categories it includes. |
Probably taken before Internet Access
2public material indicates the Microsoft Entra system profile or the Microsoft traffic profile takes them first, so web filtering wouldn't evaluate them; not confirmed
| Destination | Why it's needed | Source |
|---|---|---|
enterpriseregistration. |
Windows 365 service | Network requirements · Windows 365 serviceMicrosoft Entra system profile · indicated, not confirmedIn Microsoft 365 endpoint set 59, one of the Entra identity sets. Microsoft documents that the always-on Entra system profile covers sign-in and Graph, and that the Microsoft traffic profile is built from this list, so it is expected to be taken before Internet Access. Microsoft publishes neither profile's host list. |
login. |
Windows 365 service | Network requirements · Windows 365 serviceMicrosoft Entra system profile · indicated, not confirmedIn Microsoft 365 endpoint set 56, one of the Entra identity sets. Microsoft documents that the always-on Entra system profile covers sign-in and Graph, and that the Microsoft traffic profile is built from this list, so it is expected to be taken before Internet Access. Microsoft publishes neither profile's host list. |