Tech Community Live: Endpoint Manager edition
Jul 21 2022, 08:00 AM - 12:00 PM (PDT)

Cloud Attach Co-Management (SCCM+Intune) to Intune Standalone Migration

%3CLINGO-SUB%20id%3D%22lingo-sub-3255776%22%20slang%3D%22en-US%22%3ECloud%20Attach%20Co-Management%20(SCCM%2BIntune)%20to%20Intune%20Standalone%20Migration%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3255776%22%20slang%3D%22en-US%22%3E%3CP%3EHi%3C%2FP%3E%3CP%3EWe%20have%20requirements%20where%20client%20already%20configured%20co-management%20cloud%20attach%20(SCCM%2BIntune)%20hybrid%20model%20deployed%20and%20due%20to%20some%20organization%20requirements%20they%20plan%20to%20migrate%20on%20Intune%20Standalone%20without%20SCCM%20client%20which%20means%20all%20devices%2Fpolices%20will%20be%20managed%20by%20Intune%20only.%20I%20just%20go%20through%20different%20Microsoft%20blogs%20but%20did%20not%20find%20proper%20documentation%20instead%20of%20this.%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fmem%2Fconfigmgr%2Fcomanage%2Fhow-to-switch-workloads%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fmem%2Fconfigmgr%2Fcomanage%2Fhow-to-switch-workloads%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ECan%20anyone%20guide%20how%20to%20do%20that.%20In%20case%20if%20it%20is%20manual%20approach%20any%20step%20or%20considerations%20or%20end%20user%20impact.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-3255776%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3Ecomanagement%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3262089%22%20slang%3D%22en-US%22%3ERe%3A%20Cloud%20Attach%20Co-Management%20(SCCM%2BIntune)%20to%20Intune%20Standalone%20Migration%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3262089%22%20slang%3D%22en-US%22%3EHi%20Rahul%2C%3CBR%20%2F%3EOk%2C%20got%20it%20well%20devices%20are%20already%20enrolled%20so%20once%20get%20clarity%20will%20definitely%20share%20the%20experience.%20Thanks%20once%20again.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3262024%22%20slang%3D%22en-US%22%3ERe%3A%20Cloud%20Attach%20Co-Management%20(SCCM%2BIntune)%20to%20Intune%20Standalone%20Migration%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3262024%22%20slang%3D%22en-US%22%3EWell%20Autopilot%20is%20used%20for%20provisioning%20devices.%20It%20works%20well%20with%20AAD%2C%20but%20hybrid%20join%20is%20supported.%20So%20if%20you%20are%20planning%20to%20use%20autopilot%20to%20provision%20new%20devices%20using%20AAD%20then%20you%20should%20definitely%20go%20for%20it.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3261974%22%20slang%3D%22en-US%22%3ERe%3A%20Cloud%20Attach%20Co-Management%20(SCCM%2BIntune)%20to%20Intune%20Standalone%20Migration%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3261974%22%20slang%3D%22en-US%22%3EHi%20Rahul%2C%3CBR%20%2F%3E%3CBR%20%2F%3EThanks%20again%20for%20the%20clarification%2C%20If%20requirement%20is%20not%20hybrid%20then%20do%20we%20need%20to%20take%20care%20autopilot%20too%20or%20not%3F%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3261852%22%20slang%3D%22en-US%22%3ERe%3A%20Cloud%20Attach%20Co-Management%20(SCCM%2BIntune)%20to%20Intune%20Standalone%20Migration%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3261852%22%20slang%3D%22en-US%22%3EIf%20your%20devices%20are%20already%20in%20co-managed%20state%20then%20your%20main%20work%20is%20done.%20You%20can%20start%20moving%20all%20the%20workloads%20to%20Intune%20and%20when%20ready%2C%20remove%20the%20ConfigMgr%20agent%20from%20the%20devices.%20There%20isn't%20any%20user%20impact%20because%20of%20this%2C%20but%20a%20lot%20will%20depend%20on%20your%20policy%20configuration%20in%20Intune.%20For%20example%20-%20Update%20rings.%20The%20only%20other%20thing%20that%20you%20will%20probably%20need%20to%20get%20sorted%20is%20the%20identity%20state%20during%20Autopilot.%20If%20the%20requirement%20is%20still%20hybrid%20then%20you%20will%20need%20to%20ensure%20the%20pre-reqs%20are%20in%20place%20for%20this%20to%20work.%20Like%20VPN%20profile.%3C%2FLINGO-BODY%3E
Occasional Contributor

Hi

We have requirements where client already configured co-management cloud attach (SCCM+Intune) hybrid model deployed and due to some organization requirements they plan to migrate on Intune Standalone without SCCM client which means all devices/polices will be managed by Intune only. I just go through different Microsoft blogs but did not find proper documentation instead of this. 

https://docs.microsoft.com/en-us/mem/configmgr/comanage/how-to-switch-workloads

 

Can anyone guide how to do that. In case if it is manual approach any step or considerations or end user impact.

 

Thanks.

 

 

4 Replies
If your devices are already in co-managed state then your main work is done. You can start moving all the workloads to Intune and when ready, remove the ConfigMgr agent from the devices. There isn't any user impact because of this, but a lot will depend on your policy configuration in Intune. For example - Update rings. The only other thing that you will probably need to get sorted is the identity state during Autopilot. If the requirement is still hybrid then you will need to ensure the pre-reqs are in place for this to work. Like VPN profile.
Hi Rahul,

Thanks again for the clarification, If requirement is not hybrid then do we need to take care autopilot too or not?
Well Autopilot is used for provisioning devices. It works well with AAD, but hybrid join is supported. So if you are planning to use autopilot to provision new devices using AAD then you should definitely go for it.
Hi Rahul,
Ok, got it well devices are already enrolled so once get clarity will definitely share the experience. Thanks once again.