6.2. Monitor and Optimize Health
💡 First Principle: You can only improve what you measure against something. Every monitoring tool in this section pairs a measurement with a reference point: a compliance report with your policy, a startup score with the median of all organizations, a connector status with its credential's expiry date, a detection script with the state you expect. Find the reference point and you know what the tool can and can't tell you.
Why care? Many help desk tickets are symptoms a report already showed: an expired connector explains why new iPhones won't enroll, and a CPU-hungry startup process explains the "slow in the morning" calls. Given a symptom, the exam asks which tool shows the cause:
| Question you're asking | Tool | Section |
|---|---|---|
| Which devices fail a policy, and why? | Intune reports (operational, organizational, historical) | 6.2.1 |
| Fast and stable compared with others? | Endpoint analytics scores and baselines | 6.2.2 |
| Can a known fault be fixed automatically? | Remediations | 6.2.3 |
| Microsoft's side or a connector? | Tenant status, Service health, Message center | 6.2.4 |
| Who should hear about it, and when? | Noncompliance notifications, Azure Monitor alerts, Cloud PC alerts | 6.2.4 |
⚠️ Common Misconception: Because platform scripts ship with Intune, it's easy to assume every Intune license includes Remediations too. It doesn't. Remediations needs Windows Enterprise E3 or E5 (included in Microsoft 365 F3, E3 and E5), Windows Education A3 or A5 (included in Microsoft 365 A3 and A5) or Windows VDA per user, and an Intune Service Administrator must confirm the tenant has that licensing before first use. Intune Plan 1 alone with Windows Pro licensing doesn't qualify.