You don't have to switch the workloads, or you can do them individually when you're ready. Configuration Manager continues to manage all other workloads, including those workloads that you don't switch to Intune, and all other features of Configuration Manager that co-management doesn't support.
If you switch a workload to Intune, but later change your mind, you can switch it back to Configuration Manager.
Co-management supports the following workloads:
Compliance policies define the rules and settings that a device must comply with to be considered compliant by conditional access policies. Also use compliance policies to monitor and remediate compliance issues with devices independently of conditional access. Beginning in Configuration Manager version 1910, you can add evaluation of custom configuration baselines as a compliance policy assessment rule. For more information, see Include custom configuration baselines as part of compliance policy assessment.
For more information on the Intune feature, see Use compliance policies to set rules for devices you manage with Intune.
Windows Update policies
Windows Update for Business policies let you configure deferral policies for Windows 10 feature updates or quality updates for Windows 10 devices managed directly by Windows Update for Business.
For more information on the Intune feature, see Manage Windows 10 software updates in Intune.
Resource access policies
Starting in Configuration Manager version 2103, these company resource access features of Configuration Manager and this co-management workload are deprecated. Use Microsoft Intune to deploy resource access profiles.
Resource access policies configure VPN, Wi-Fi, email, and certificate settings on devices.
For more information on the Intune feature, see Deploy resource access profiles.
The resource access workload is also part of device configuration. These policies are managed by Intune when you switch the Device Configuration workload.
The Endpoint Protection workload includes the Windows Defender suite of antimalware protection features:
- Windows Defender Antimalware
- Windows Defender Application Guard
- Windows Defender Firewall
- Windows Defender SmartScreen
- Windows Encryption
- Windows Defender Exploit Guard
- Windows Defender Application Control
- Windows Defender Security Center
- Windows Defender for Endpoint (now known as Microsoft Defender for Endpoint)
For more information on the Intune feature, see Windows 10 (and later) settings to protect devices using Intune.
When you switch this workload, the Configuration Manager policies stay on the device until the Intune policies overwrite them. This behavior makes sure that the device still has protection policies during the transition.
The Endpoint Protection workload is also part of device configuration. The same behavior applies when you switch the Device Configuration workload.
When the Endpoint Protection workload resides with Intune, Windows Information Protection settings will apply from both Configuration Manager and Intune. Configuration Manager will continue to apply Windows Information Protection policy until the Device Configuration workload is moved to Intune.
The Microsoft Defender Antivirus settings that are part of the Device restrictions profile type for Intune Device configuration are not included in scope of the Endpoint protection slider. To manage Microsoft Defender Antivirus for co-managed devices with the endpoint protection slider enabled, use the new Antivirus policies in Microsoft Endpoint manager admin center > Endpoint security > Antivirus. The new policy type has new and improved options available, and support all of the same settings available in the Device restrictions profile.
The Windows Encryption feature includes BitLocker management. For more information on the behavior of this feature with co-management, see Deploy BitLocker management.
The device configuration workload includes settings that you manage for devices in your organization. Switching this workload also moves the Resource Access and Endpoint Protection workloads.
You can still deploy settings from Configuration Manager to co-managed devices even though Intune is the device configuration authority. This exception might be used to configure settings that your organization requires but aren't yet available in Intune. Specify this exception on a Configuration Manager configuration baseline. Enable the option to Always apply this baseline even for co-managed clients when creating the baseline. You can change it later on the General tab of the properties of an existing baseline.
For more information on the Intune feature, see Create a device profile in Microsoft Intune.
When you switch the device configuration workload, it also includes policies for the Windows Information Protection feature. Only policies from Intune will apply once the Device Configuration workload is moved to Intune.
Office Click-to-Run apps
This workload manages Microsoft 365 Apps on co-managed devices.
After moving the workload, the app shows up in the Company Portal on the device
Office updates may take around 24 hours to show up on client unless the devices are restarted
There's a new global condition, Are Office 365 applications managed by Intune on the device. This condition is added by default as a requirement to new Microsoft 365 applications. When you transition this workload, co-managed clients don't meet the requirement on the application. Then they don't install Microsoft 365 deployed via Configuration Manager.
Updates can be managed using either of the following features:
- Use Update Channel and Target Version settings to update Microsoft 365 with Microsoft Intune Administrative Templates
- Manage Microsoft 365 Apps with Configuration Manager.
For more information on the Intune feature, see Add Microsoft 365 apps to Windows 10 devices with Microsoft Intune.
This feature was first introduced in version 1806 as a pre-release feature. Beginning with version 2002, it's no longer a pre-release feature.
This feature may appear in the list of features as Mobile apps for co-managed devices.
Use Intune to manage client apps and PowerShell scripts on co-managed Windows 10 devices. After you transition this workload, any available apps deployed from Intune are available in the Company Portal. Apps that you deploy from Configuration Manager are available in Software Center.
For more information on the Intune feature, see What is Microsoft Intune app management?
In Windows 10 version 1903 and later, PowerShell scripts still run on co-managed devices even if you haven't switched the Client Apps workload to Intune.
When you enable Microsoft Connected Cache on your Configuration Manager distribution points, they can serve Microsoft Intune Win32 apps to co-managed clients. For more information, see Microsoft Connected Cache in Configuration Manager.
Diagram for app workloads
Starting in version 2006, you can configure the Company Portal to also show Configuration Manager apps. If you change this app portal experience, it changes the behaviors described in the above diagram. For more information, see Use the Company Portal app on co-managed devices.
Applies to version 2006 and earlier
When the Endpoint Protection workload is moved over to Intune, the client may still honor policies set by Configuration Manager and Microsoft Defender.
To work around this issue, apply the CleanUpPolicy.xml using ConfigSecurityPolicy.exe after the Intune policies have been received by the client using the steps below:
Copy and save the below text as
<?xml version="1.0" encoding="UTF-8"?> <SecurityPolicy xmlns="http://forefront.microsoft.com/FEP/2010/01/PolicyData" Name="FEP clean-up policy"><PolicySection Name="FEP.AmPolicy"><LocalGroupPolicySettings><IgnoreKey Name="SOFTWARE\Policies\Microsoft\Microsoft Antimalware"/><IgnoreKey Name="SOFTWARE\Policies\Microsoft\Windows Defender"/></LocalGroupPolicySettings></PolicySection></SecurityPolicy>
Open an elevated command prompt to
ConfigSecurityPolicy.exe. Typically this executable is in one of the following directories:
- C:\Program Files\Windows Defender
- C:\Program Files\Microsoft Security Client
From the command prompt, pass in the xml file to clean up the policy. For example,