“Windows Autopilot Deployment Status”
Autotask PSA Datto RMM Datto Backup Microsoft 365 SmileBack HubSpot IT Glue All reports
AI-GENERATED REPORT
You searched for:

Windows Autopilot Deployment Status

Device enrollment progress and failure analysis across your managed Intune tenants.

Built from: M365 Lighthouse
How this report was made
1
Autotask PSA
Multiple data sources combined
2
Proxuma Power BI
Pre-built MSP semantic model, 50+ measures
3
AI via MCP
Claude or ChatGPT writes DAX queries, executes them, formats output
4
This Report
KPIs, breakdowns, trends, recommendations
Ready in < 15 min

Windows Autopilot Deployment Status

Device enrollment progress and failure analysis across your managed Intune tenants.

The data covers the full scope of Autotask PSA records relevant to this analysis, broken down by the key dimensions your team needs for day-to-day decisions and client reporting.

Who should use this: MSP operations teams and service delivery managers

How often: As needed for specific analysis or reporting requirements

Time saved
Manual data extraction and formatting takes hours. This report delivers results in minutes.
Operational clarity
Key metrics and breakdowns that would otherwise require custom queries.
Decision support
Data-driven evidence for operational decisions and process improvements.
Report categoryOther
Data sourceAutotask PSA · Datto RMM · Datto Backup · Microsoft 365 · SmileBack · HubSpot · IT Glue
RefreshReal-time via Power BI
Generation timeUnder 15 minutes
AI requiredClaude, ChatGPT or Copilot
AudienceMSP operations teams
Where to find this in Proxuma
Power BI › Report › Windows Autopilot Deployment Status
What you can measure in this report
Summary Metrics
Enrollment Status by Tenant
Failure Analysis by Error Type
Alert Risk Matrix
Alert Detail by Category
Device Fleet Health Overview
Key Findings
Strategic Recommendations
Frequently Asked Questions
Total Devices
Successfully Enrolled
Failed Enrollments
AI-Generated Power BI Report
Windows Autopilot Deployment Status

Device enrollment progress and failure analysis across your managed Intune tenants.

Demo Report: This report uses synthetic data to demonstrate AI-generated insights from Proxuma Power BI. The structure, DAX queries, and analysis reflect real MSP data patterns.
1.0 Summary Metrics
Total Devices
233
Autopilot device registrations
Successfully Enrolled
15
Enrollment batches submitted
Failed Enrollments
18
Distinct hardware models
Pending
3
HP, Dell, Microsoft
View DAX Query - Summary Metrics
EVALUATE
ROW(
  "TotalDevices", COUNTROWS('BI_MicrosoftPartnerCenter_Devices'),
  "TotalBatches", COUNTROWS('BI_MicrosoftPartnerCenter_Device_Batches'),
  "UniqueModels", DISTINCTCOUNT('BI_MicrosoftPartnerCenter_Devices'[model_name]),
  "UniqueOEMs", DISTINCTCOUNT('BI_MicrosoftPartnerCenter_Devices'[oem_manufacturer_name])
)
2.0 Enrollment Status by Tenant

Breakdown of Autopilot enrollment outcomes per managed tenant.

Contoso Ltd
89.2% success
Fabrikam Inc
91.4% success
Woodgrove Bank
85.1% success
Adventure Works
93.7% success
Tailspin Toys
78.3% success
Litware Inc
95.2% success
TenantDevicesEnrolledFailedPendingSuccess Rate
Contoso Ltd842751523989.2%
Fabrikam Inc624570312391.4%
Woodgrove Bank510434482885.1%
Adventure Works478448141693.7%
Tailspin Toys395309543278.3%
Litware Inc3122978795.2%

Litware Inc leads with a 95.2% enrollment success rate, while Tailspin Toys lags at 78.3% with 54 failures. The failure concentration at Tailspin correlates with older hardware that lacks TPM 2.0 support. Woodgrove Bank also shows an elevated failure rate at 85.1%, primarily due to network proxy issues during OOBE.

View DAX Query - Enrollment Status by Tenant
EVALUATE
SUMMARIZECOLUMNS(
    BI_Microsoft_Autopilot[tenant_name],
    "TotalDevices", COUNTROWS(BI_Microsoft_Autopilot),
    "Enrolled", CALCULATE(COUNTROWS(BI_Microsoft_Autopilot), BI_Microsoft_Autopilot[status] = "Enrolled"),
    "Failed", CALCULATE(COUNTROWS(BI_Microsoft_Autopilot), BI_Microsoft_Autopilot[status] = "Failed")
)
ORDER BY [TotalDevices] DESC
3.0 Failure Analysis by Error Type

Most common Autopilot enrollment failure reasons.

TPM Attestation Failed
72 devices
Network Timeout
48 devices
Profile Mismatch
38 devices
ESP Timeout
31 devices
Azure AD Join Failed
18 devices
License Missing
11 devices
Error TypeCountShareTop TenantResolution
TPM Attestation Failed7233.0%Tailspin ToysUpdate BIOS / replace hardware
Network Timeout4822.0%Woodgrove BankWhitelist Autopilot endpoints
Profile Mismatch3817.4%Contoso LtdReassign deployment profile
ESP Timeout3114.2%Fabrikam IncIncrease ESP timeout to 90 min
Azure AD Join Failed188.3%Datum CorpCheck hybrid join config
License Missing115.0%Proseware IncAssign Intune license

TPM attestation failures account for one-third of all enrollment issues, concentrated at Tailspin Toys where 42 of their 54 failures stem from this cause. Network timeouts at Woodgrove Bank point to a firewall configuration that blocks required Microsoft endpoints. These two root causes, if resolved, would eliminate 55% of all failures portfolio-wide.

View DAX Query - Failure Analysis by Error Type
EVALUATE
SUMMARIZECOLUMNS(
    BI_Microsoft_Autopilot[error_type],
    FILTER(BI_Microsoft_Autopilot, BI_Microsoft_Autopilot[status] = "Failed"),
    "DeviceCount", COUNTROWS(BI_Microsoft_Autopilot)
)
ORDER BY [DeviceCount] DESC
4.0
Alert Risk Matrix
Categorizing clients by alert severity and device health.
HIGH RISK
4 entities
Performance significantly below portfolio average. Immediate action required.
MODERATE RISK
7 entities
Performance below target but stable. Review within 2 weeks.
LOW RISK
12 entities
Performance above target level. Standard monitoring sufficient.
NOT ASSESSED
3 entities
Insufficient data available for risk assessment.

The risk matrix shows that most entities fall in the low-risk category, but the high-risk group demands immediate attention. The moderate-risk group shows a declining trend that could escalate without intervention.

5.0
Alert Detail by Category
Granular breakdown of alert types and resolution status.
CategoryItemsPrimarySecondaryStatus
Category A23494.2%14Healthy
Category B18789.3%20Review
Category C15691.7%13Healthy
Category D9886.7%13Review
Category E6782.1%12At Risk
Category F4595.6%2Healthy

The detailed breakdown shows clear performance differences. The bottom two categories require targeted action to improve overall portfolio health.

6.0
Device Fleet Health Overview
Overall health indicators across the managed fleet.
92.4% health score
Portfolio Health
87.3% of 100%
Coverage
23 action items
Open Items

Overall portfolio health is strong at 92.4%, but the 87.3% coverage rate suggests that roughly 1 in 8 entities is not fully monitored. The 23 open action items represent a manageable backlog if addressed within 2 weeks.

7.0
Key Findings
!

Performance Gap Requires Attention

The gap between top and bottom performers is wider than expected. The bottom 20% scores more than 25 percentage points below the portfolio average, indicating structural issues that require targeted intervention.

!

Declining Trend in Moderate Risk Group

Entities in the moderate risk category show a declining trend over the past quarter. Without intervention, 3-4 of these entities may shift to the high-risk category within 60 days.

Top Performers Remain Consistent

The top 30% of the portfolio maintains stable performance above target, indicating current best practices are effective and can serve as a model for the rest.

8.0
Strategic Recommendations

1. Conduct a targeted review of all high-risk entities within 2 weeks. Document the root cause for each entity and create a remediation plan with clear deadlines and accountable owners.

2. Implement automated monitoring for the moderate-risk group. Set thresholds that trigger an alert when performance drops 5 percentage points below target, enabling early intervention before entities slip into high risk.

3. Schedule this report monthly as part of the QBR process. Use the trend data to verify that improvement initiatives are delivering measurable results across multiple quarters.

9.0
Frequently Asked Questions
What is a normal Autopilot success rate?

A healthy MSP portfolio should see 90%+ enrollment success. Below 85% indicates systemic issues that need investigation.

How long should enrollment take?

Standard Autopilot enrollment typically completes in 30-60 minutes. If devices consistently exceed 90 minutes, check network throughput and ESP configuration.

What causes TPM attestation failures?

Older devices without TPM 2.0 chips, outdated BIOS firmware, or devices previously enrolled in another tenant can all trigger TPM attestation failures.

Can we retry failed enrollments automatically?

Yes. Devices can be reset and re-enrolled. For persistent failures, the Autopilot device record may need to be deleted and re-imported.

Generate this report from your own data

Connect Proxuma Power BI to your PSA, RMM, and M365 environment, use an MCP-compatible AI to ask questions, and generate custom reports - in minutes, not days.

See more reports Get started