Archived | Support Tip: Configuring workloads in a co-managed environment

Hi Jan & Anantha,

Thank you for posting comments. 

Once the workloads is switched to Intune, Intune will have the capability to deploy apps, and at the same time for SCCM, the capabilities is not removed. 

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.

I just finished testing deploying .msi app installer as available type from SCCM to co-management devices after client app workload switched to Intune. The app will still appear in Software center and can be installed without any issue. 

Can this article be updated to reflect the new co-management capability numbers in SCCM 2111? They no longer max at 255. 

Hi Betty

Great article, you should join the team that writes the documentation! :-)

I do have one additional question that I hope you may be able to answer.

Once the workload for 'Client Apps' is switched to Pilot/Intune, what happens to the SCCM capabilities to deploy applications? Can SCCM and Intune now both be used to deploy apps or is it Intune only from that point on?

Thanks,

Jan

Yes- I do exactly have the same question as Jan. Thanks Jan for bringing this up. We are currently working on Autopilot managed through Intune- but would like to have the SCCM agent installed on these devices - so that we want to make our users use our internal shopping portal for which apps, when shopped, get delivered via CM. So wanted to know- can we make the apps delievered by both CM and Intune as we would like? I wish- i get the response as "yes" ;) 

Thanks,

Anantha

Hi Arnaud Layec ,

if we deploy the Configuration manager client installer from Intune, we need to setup the CMG for SCCM. The CM client will connect CMG for communication with SCCM local server, instead of through Intune to reach the SCCM server. 

https://docs.microsoft.com/en-us/mem/configmgr/comanage/quickstart-paths#bkmk_path2

Path 2: Bootstrap with modern provisioning

Here's what you need to set it up:

1. Setup enhanced HTTP
2. Create the cloud services in Azure
3. Configure the management point and clients to use the cloud management gateway
4. Use Intune to deploy the Configuration Manager client

Thanks for raising your questions Jan and Anantha! Betty will respond to your question shortly.

Jet Zhu

Microsoft Intune Support Team

Thanks much Betty. This does clear few things. Thanks again.

Cheers,

Anantha

Hi Betty - 

Sorry-another one just dawned on my mind. With this setting of Co-management as briefed in this article, may I know what will be the impact of the existing devices managed by SCCM. I mean we are currently not looking at our on-prem devices to be co-managed from Intune, but only want the Autopilot devices to be co-managed by SCCM. Can you advice?

Many Thanks

Anantha

I guess as long as the on-prem device is NOT Hybrid Azure AD joined, the on-prem devices will continue to be managed ONLY by SCCM whereas for the Autopilot devices, it can leverage the CM SW deployment features as mentioned in your earlier response even its just Azure AD joined. Do correct me if am wrong in my understanding.

Many Thanks,

Anantha

Hi Betty_Jia

Thanks for that clarification!