You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: memdocs/configmgr/comanage/workloads.md
+12-5Lines changed: 12 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,9 +15,9 @@ ms.collection: highpri
15
15
16
16
# Co-management workloads
17
17
18
-
You don't have to switch any of the workloads, but youcan do them individually or several or all at the same time when you're ready. However, until you switch the workloads over to Intune, Microsoft Endpoint Configuration Manager continues to manage those workloads that you don't switch to Intune, along with all other features of Configuration Manager that co-management doesn't support.
18
+
You don't have to switch any of the workloads. When you're ready, you can switch them individually, several at once, or all at the same time. However, until you switch the workloads over to Intune, Configuration Manager continues to manage the workloads that you don't switch to Intune, along with all other features of Configuration Manager that co-management doesn't support.
19
19
20
-
If you switch a workload to Intune, but later change your mind, you can switch it back to Configuration Manager, although there might be an impact, for example, Windows and Office versions will remain at a later version if installed by Intune.
20
+
If you switch a workload to Intune, but later change your mind, you can switch it back to Configuration Manager, although there might be an impact. For example, Windows and Office versions will remain at a later version if installed by Intune.
21
21
22
22
Co-management supports the following workloads:
23
23
@@ -43,7 +43,10 @@ For more information on the Intune feature, see [Use compliance policies to set
43
43
44
44
## Windows Update policies
45
45
46
-
Windows Update for Business policies let you configure deferral policies for Windows 10 or later feature updates or quality updates for Windows 10 or later devices managed directly by Windows Update for Business. Note that this workload needs to be managed by Intune for the Windows Autopatch feature to work on these devices.
46
+
Windows Update for Business policies let you configure deferral policies for Windows 10 or later feature updates or quality updates for Windows 10 or later devices managed directly by Windows Update for Business.
47
+
48
+
> [!NOTE]
49
+
> To use Windows Autopatch with these devices, this workload needs to be managed by Intune. For more information, see [Prerequisites for Windows Autopatch](/windows/deployment/windows-autopatch/prepare/windows-autopatch-prerequisites).
47
50
48
51
For more information on the Intune feature, see [Manage Windows software updates in Intune](../../intune/protect/windows-update-for-business-configure.md).
49
52
@@ -94,7 +97,9 @@ For more information on the Intune feature, see [Windows 10 (and later) settings
94
97
95
98
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.
96
99
97
-
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](../compliance/deploy-use/create-configuration-baselines.md). 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. Note that this workload needs to be managed by Intune for the Windows Autopatch feature to work on these devices.
100
+
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](../compliance/deploy-use/create-configuration-baselines.md). 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.
101
+
102
+
To use Windows Autopatch with these devices, this workload needs to be managed by Intune. For more information, see [Prerequisites for Windows Autopatch](/windows/deployment/windows-autopatch/prepare/windows-autopatch-prerequisites).
98
103
99
104
For more information on the Intune feature, see [Create a device profile in Microsoft Intune](../../intune/configuration/device-profile-create.md).
100
105
@@ -124,7 +129,9 @@ Updates can be managed using either of the following features:
124
129
125
130
-[Use Update Channel and Target Version settings to update Microsoft 365 with Microsoft Intune Administrative Templates](../../intune/configuration/administrative-templates-update-office.md)
126
131
-[Manage Microsoft 365 Apps with Configuration Manager](../sum/deploy-use/manage-office-365-proplus-updates.md).
127
-
Note that this workload needs to be managed by Intune for the Windows Autopatch feature to work on these devices.
132
+
133
+
> [!NOTE]
134
+
> To use Windows Autopatch with these devices, this workload needs to be managed by Intune. For more information, see [Prerequisites for Windows Autopatch](/windows/deployment/windows-autopatch/prepare/windows-autopatch-prerequisites).
128
135
129
136
For more information on the Intune feature, see [Add Microsoft 365 apps to Windows devices with Microsoft Intune](../../intune/apps/apps-add-office365.md).
0 commit comments