MD-101 Co-management with Microsoft Endpoint Configuration Manager 3

Question 1

Which feature in the Microsoft Endpoint Manager admin center provides device health insights such as startup performance and application reliability for co-managed devices?

Accepted Answer

Endpoint Analytics in Microsoft Endpoint Manager

Answer

Microsoft Sentinel device health workbooks

Answer

Azure Monitor Workbooks with the Intune data source

Answer

Microsoft Defender for Cloud device posture reports

Question 2

In the Configuration Manager console, where can administrators view the co-management enrollment status and workload assignments of devices?

Accepted Answer

Monitoring workspace > Co-management > Co-management Status dashboard

Answer

Assets and Compliance workspace > Devices > Co-management Status node

Answer

Administration workspace > Cloud Services > Co-management overview

Answer

Software Library workspace > Overview > Co-management Workloads

Question 3

Which built-in Windows tool generates the MDMDiagReport.xml file used for troubleshooting co-management and MDM enrollment issues?

Accepted Answer

MDMDiagnosticsTool.exe run with the -out parameter

Answer

Windows Management Instrumentation (WMI) diagnostic console

Answer

Configuration Manager client diagnostics utility (CCMDiag)

Answer

Windows Event Log export tool from Event Viewer

Question 4

What is the primary business benefit of choosing co-management over immediately switching to a pure Intune-only deployment?

Accepted Answer

Organizations can gradually transition to cloud management while preserving existing Configuration Manager capabilities and workflows

Answer

Co-management reduces Microsoft 365 licensing costs compared to Intune-only management

Answer

Co-management eliminates the need for Azure AD Connect synchronization infrastructure

Answer

All security baselines are automatically enforced without additional configuration in co-management

Question 5

A co-managed device shows 'MDM Enrolled: No' in Configuration Manager despite co-management being configured. What is the most likely root cause?

Accepted Answer

Automatic MDM enrollment is not properly configured in Azure AD or the relevant Group Policy, preventing silent enrollment

Answer

The device is running a Windows version below Windows 10 1709

Answer

The Configuration Manager client is uninstalled or reporting in an error state

Answer

The device lacks internet connectivity to reach Intune enrollment endpoints

Question 6

Which Configuration Manager report helps administrators identify which devices are eligible for co-management but have not yet been enrolled?

Accepted Answer

Co-management Eligibility report under Monitoring > Co-management

Answer

Device Compliance Summary report in the Monitoring workspace

Answer

Intune Device Enrollment Failures report in the Microsoft Endpoint Manager admin center

Answer

Azure AD Device Registration Status report exported from the Azure portal

Question 7

When configuring co-management workloads, what does setting a workload slider to 'Pilot Intune' mean?

Accepted Answer

Only devices in the designated pilot collection have that workload managed by Intune; all others remain with Configuration Manager

Answer

The workload is fully managed by Intune for all co-managed devices in the organization

Answer

The workload is in a testing mode where neither Configuration Manager nor Intune enforces policies

Answer

Intune manages the workload only for new devices enrolled via Autopilot, not existing clients