What's changed: Created MD-102 Chapter 5 (domain: Optimize endpoint operations). Automate management tasks (PowerShell/Microsoft Graph, custom compliance, Security Copilot agents in Intune), monitor/optimize health (Endpoint Analytics device health scores/startup performance/application reliability, proactive remediations detection/remediation scripts), and reporting/alerts (reporting/workbooks/dashboards/export, tenant health/service health dashboard/message center, alerts and notifications compliance drift/enrollment failures/configuration conflicts). This completes the MD-102 textbook: all 5 chapters / 13 sections.
5.3Reporting and alerts
Understand Intune reporting (reports/workbooks/dashboards/export), tenant health and Intune service communications, and alerts and notifications (compliance drift/enrollment failures/configuration conflicts).
Operational visibility splits into "reports", "service status", and "notifications"
5.3.1Reporting and service health
Reporting and data visibility covers customizing reports/filters, visualization with workbooks/dashboards, and exporting report data. Tenant health and Intune service communications use the service health dashboard and message center notifications to track service-side status/upcoming changes and establish operational baselines.
5.3.2Alerts and notifications
Alerts and notifications set alert rules to notify on policy/compliance changes. Common examples are compliance drift, enrollment failures, and configuration conflicts. Versus reports (past/current visibility), alerts create "awareness on thresholds/events"—and service incidents (service health) are tenant-side status, separate from these.
Cues: "customize reports/workbooks/dashboards/export" = reporting and data visibility. "service-side status/upcoming changes" = tenant health/service health dashboard/message center. "notify on compliance drift/enrollment failures/configuration conflicts" = alerts and notifications (alert rules).
Watch the mix-ups: (1) Reporting (past/current visibility) vs alerts (event/threshold notification). (2) Tenant health/service health (service-side status) vs reports/alerts. (3) Alert rules notify on events like compliance drift/enrollment failures/configuration conflicts.
5.3.3Section summary
- Reporting and data visibility covers reports/workbooks/dashboards/export
- Track service status via tenant health/service health dashboard/message center
- Alerts and notifications notify on compliance drift/enrollment failures/configuration conflicts
Sign in to track progress — Log in.
Quick check
(just a quick review)Q1. You want to visualize Intune device/compliance status with report filters and workbooks/dashboards and export the data. Best?
Q2. You want to auto-notify admins on compliance drift, enrollment failures, or configuration conflicts. Best?
Q3. You want to track Intune service-side incidents, upcoming changes, and service health. Best?
Q4. What correctly distinguishes reporting from alerts and notifications?
Q5. Which is an example of an event that alert rules notify on?
Keep track of your progress
The full study guide is free to read. Sign up free to practice with the question bank, track what you have read, review your mistakes, and highlight passages.