Special considerations when joining two CM sites to single Intune/Azure tenant

Todd Miller 41 Reputation points
2020-09-15T16:02:09.54+00:00

Are there any special considerations that need to be taken into account when tenant attaching two different CM sites to a single Azure/Intune tenant? Both sites are > v1906

Is it "just 4 clicks" on both?

The two CM sites are entirely separate but are in the same forest (different domains) and clients from both are hybrid joined to the Azure tenant.

One of the CM sites already has CMG configured in a subscription on the tenant - but is not tenant attached for co-management

Microsoft Configuration Manager
0 comments
Accepted answer
  1. Jason Sandys 31,151 Reputation points Microsoft Employee
    2020-09-15T16:30:35.427+00:00

    There's nothing special here, it's fully supported: https://learn.microsoft.com/en-us/mem/configmgr/comanage/overview#configuration-manager

    Assuming the clients are already AAD/HAAD joined, then yes, the "four clicks" is still all that's really required.

    Note that tenant attach and co-management are two completely different features though.

    0 comments

2 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Todd Miller 41 Reputation points
    2020-09-15T22:31:50.207+00:00

    Thanks Jason. Some guy ( haha ) has a good explanation of the difference between co-management and tenant attach over on reddit eli5_comanagement_vs_tenant_attach_in_configmgr

    If I enable Desktop Analytics - that is the thing I'm most interested in to start - will it be difficult to keep the clients from the two Configmgr sites segregated?

    0 comments
  2. Jason Sandys 31,151 Reputation points Microsoft Employee
    2020-09-16T18:30:10.837+00:00

    I'm not sure exactly how it'll look, but it is fully supported (although I don't think this is specifically documented anywhere). Note that this is also unrelated to co-management and tenant attach as well.

    0 comments