Skip to content

Windows 365 Connection Quality (7 days)

The question it answers: Which Cloud PCs had slow round trips, low bandwidth or slow sign-ins in the last 7 days, and which were not used?

A Cloud PC is only as good as the connection to it. Round-trip times above 100 ms feel sluggish and above 200 ms are painful; low bandwidth and slow sign-ins are the other complaints. Worst connections first, so you can check the user’s network or move them to a closer region.

Where in the appIntune › Service & Operations › Windows 365 Connection Quality
WorkloadIntune
KindTable · dashboard tile
DataA scan: it runs only when someone presses Run scan (or calls the API’s scan action) and can take minutes. The last result is kept until the next scan.
LicenceWindows 365 Enterprise.
Report id (API and MCP)intune.service.cloud-pc-connection-quality
ColumnKeyType
Cloud PCDisplayNameText
UserUserPrincipalNameText
Round trip P50 (ms)RoundTripMsP50Status
Worst session (ms)WorstRoundTripMsP50Text
Min bandwidth (MBps)MinBandwidthMBpsText
Sign-in (s)AvgSignInSecondsText
SessionsSessionsText
Hours usedUsageHoursText
FindingsFindingsText
ErrorErrorText
FilterKey (API)On when the page opens
Only Cloud PCs with quality issuesissuesYes

Licence: Windows 365 Enterprise.

Application permissions on the IntensiveReports app registration (all permissions):

PermissionAPIWhat it allowsNote
CloudPC.Read.AllMicrosoft GraphRead Cloud PCs
Data sources it reads
  • GET /v1.0/deviceManagement/virtualEndpoint/cloudPCs
  • POST /beta/deviceManagement/virtualEndpoint/reports/getRemoteConnectionHistoricalReports (per Cloud PC)
GET /ir-api/v1/reports/intune.service.cloud-pc-connection-quality?size=100
GET /ir-api/v1/reports/intune.service.cloud-pc-connection-quality?filter=issues
POST /ir-api/v1/reports/intune.service.cloud-pc-connection-quality/scan

An AI assistant reads it with the MCP tool get_report and the id intune.service.cloud-pc-connection-quality. The client needs the Run scan grant for Intune. See Using the API.