Cloud PC Troubleshooting Reports Revamped: Major Enumeration Update & What Entra Admins Must Do Next

WHAT JUST CHANGED

Microsoft has updated the cloudPCTroubleshootReportType enumeration, central to Cloud PC troubleshooting workflows. The following changes are now live and affect all Microsoft Entra ID tenants leveraging Windows 365/Cloud PC reporting via Microsoft Graph or the admin center:

• Removed troubleshootDetailsReport
• Removed troubleshootTrendCountReport
• Removed troubleshootRegionalReport
• Removed troubleshootIssueCountReport
• Added troubleshootTenantGlobalFilterReport
• Added troubleshootTenantNetworkTrendReport
• Added troubleshootTenantNetworkAggregatedReport
• Added troubleshootTenantConnectionFailureRateTrendReport
• Added troubleshootTenantConnectionFailureRateAggregatedReport
• Added troubleshootTenantCloudPCHealthTrendReport
• Added troubleshootTenantCloudPCHealthAggregatedReport
• Added troubleshootTenantActiveConnectionCountTrendReport
• Added troubleshootTenantActiveConnectionCountAggregatedReport
• Added troubleshootTenantMeanTimeToRecoveryTrendReport
• Added troubleshootTenantMeanTimeToRecoveryAggregatedReport

Effective date: June 2024. Rollout status: General Availability (GA). All tenants with Cloud PC/Windows 365 workloads and Entra ID device objects are affected. This change is immediately relevant for admins running automated reporting, custom dashboards, or troubleshooting via Microsoft Graph.

WHAT’S NEXT ON THE ROADMAP

Microsoft is actively investing in richer analytics and troubleshooting telemetry for cloud-based endpoints:

• Enhanced Intune-Graph integration: More granular device status, posture, and health metrics are slated for later in 2024, including expanded support for app lifecycle and endpoint compliance reporting.
• Unified Endpoint Management: Microsoft is consolidating reporting surfaces. Expect Cloud PC, physical device, and app health to be accessible via a single Entra admin portal pane.
• Automation/Remediation APIs: Preview endpoints for automated issue detection and remediation are rolling out, allowing for custom workflows triggered by tenant-wide health metrics.
• Conditional Access for Devices: Upcoming releases will allow tighter CA policies based on real-time device state. Start reviewing your device-based CA rules for compatibility.

Admins should monitor the Microsoft Graph beta endpoints and Intune release notes, as new device and app troubleshooting APIs are typically surfaced there first before GA.

WHY THIS DIRECTION IS BETTER

This update shifts reporting from legacy, per-device and regional view to holistic, tenant-wide metrics. Concrete improvements include:

• Tenant-level visibility: Aggregated and trend reports provide actionable insights across all Cloud PCs, not just isolated device events.
• Improved troubleshooting context: New metrics such as MeanTimeToRecovery and ConnectionFailureRate directly support SLA tracking and proactive support.
• Streamlined API/portal navigation: Report requests now align with modern Entra device management workflows, eliminating legacy enumeration confusion and reducing API errors.
• Competitive parity: Azure AD (now Entra), VMware Workspace ONE, and Okta Device Cloud all trend towards tenant-wide analytics. Microsoft’s update closes gaps and delivers more in-depth reporting natively.

For admins, this means less time spent parsing device-by-device logs and more focus on actionable tenant-wide trends.

ADJACENT ENTRA ID CHANGES YOU NEED TO KNOW

• Device Lifecycle: Recent Entra ID updates for device registration and automatic cleanup (stale device removal) are now live. Check for device join/deletion automation scripts and review your lifecycle policies.
• Authentication Methods: Passwordless sign-in for devices is rolling out, with FIDO2, phone sign-in, and push notifications supported for Cloud PCs.
• Microsoft.Graph PowerShell: The latest Microsoft.Graph.DeviceManagement module supports new troubleshooting report types. Update your scripts accordingly.
• Conditional Access: Device state and health can now be used in CA policies. Review your CA rules for compatibility with new device health metrics.
• Licensing: Windows 365 licenses are required for Cloud PC reporting. Ensure your tenant licensing matches your reporting needs.

WHAT TO DO: ADMIN ACTIONS

1. Audit existing report automations: Review any scripts, dashboards, or workflows referencing the removed report types. Update to use the new enumerations.
2. Update PowerShell and Graph queries: Ensure you’re using the current Microsoft.Graph.DeviceManagement module. Switch out deprecated enumeration members with new tenant-level report types.
3. Review portal workflows: Validate your device troubleshooting actions in the Entra admin center, noting new report options and navigation changes.
4. Prepare for upcoming roadmap features: Subscribe to Intune and Microsoft Graph release notes. Plan for unified endpoint reporting and remediation APIs.
5. Test device-based Conditional Access: Incorporate new health metrics into CA policies for improved security posture.

CHECK IT YOURSELF: POWERSHELL AUDIT

Use the Microsoft.Graph module to list all available Cloud PC troubleshooting report types, check for legacy references, and validate tenant compatibility. This script reports, does not change data:

# Requires Microsoft.Graph.DeviceManagement module
Import-Module Microsoft.Graph.DeviceManagement

try {
    $reportTypes = Invoke-MgGraphRequest -Uri 'https://graph.microsoft.com/v1.0/deviceManagement/cloudPCReports/enumerationValues' -Method GET
    Write-Output "Current Cloud PC Troubleshoot Report Types:"
    $reportTypes.value | ForEach-Object { $_.name }

    $deprecated = @('troubleshootDetailsReport', 'troubleshootTrendCountReport', 'troubleshootRegionalReport', 'troubleshootIssueCountReport')
    $foundDeprecated = $reportTypes.value | Where-Object { $deprecated -contains $_.name }
    if ($foundDeprecated) {
        Write-Warning "Deprecated report types detected: $($foundDeprecated.name)"
    } else {
        Write-Output "No deprecated report types found."
    }
} catch {
    Write-Error "Failed to enumerate report types: $_"
}

This script uses modern Graph endpoints, handles errors, and never modifies or deletes data.

PORTAL PATH

To view troubleshooting reports in the Entra admin center:

• Go to https://entra.microsoft.com
• Navigate: Devices > Windows 365 (Cloud PC) > Reports > Troubleshooting
• Review available report types and options. Newly added tenant-level reports are now selectable.

BOTTOM LINE

Prioritise review and update of all Cloud PC troubleshooting workflows, scripts, and automations. Remove references to deprecated report types, adopt tenant-level reporting for richer analytics, and stay ahead of upcoming unified endpoint management features.