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?
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" ;)
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.
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?
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.
This Client apps feature was first introduced in version 1806 as apre-release feature. Beginning with version 2002, it's no longer a pre-release feature.
This feature may appear in the list of features asMobile apps for co-managed devices.
Hi, great article! Just a question in mind regarding the network diagram, maybe for @Betty_Jia : when a user self-deploy a ConfigMgr app from Company Portal, is the traffic flowing: a) from the device to MECM infra ; or b) from the device to Intune, which relays the communication (ie. the app or package) from MECM infra to the device?
If the workload is moved to intune completely and the device are co managed can I deploy autodesk apps with large size(8GB+) from sccm to user group still? and will they be getting installed on the workstation?
moving the workloads to Intune does not affect the ability we deploy apps from SCCM. You can still use SCCM to deploy the apps & if SCCM support over 8GB app, then it is supported(depends on SCCM side)
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.
In a co management environment when we have the workload moved to intune and If we deploy an app from SCCM to user can we see the app on company portal.
Because I did deploy a test app to user group from SCCM and it showed up on company portal as well as in software center. But when I am trying using a real app it's not working.
And for But when I am trying using a real app it's not working, is this app not appear in Company portal app or you click install button but with no response?
I'm having a problem similar to what @chpranay described and was wondering if there are any tips to resolving an issue where co-management is set to pilot for client apps but apps in software center don't display in Company Portal. Not sure if it is a factor or not but all of our software deployments are to user collections rather than device.
Hi there! This guidance is out of date, the latest version can be found here: Co-management for Windows devices - Configuration Manager | Microsoft Docs. Should anyone need further assistance with configurating workloads in a co-managed environment, please open a new support request via the Microsoft Endpoint Manager admin center's Help and support blade, or any of the methods here, as this will help the team capture all the information needed to resolve the issue. Thanks!