search

MicrosoftDocs / SCCMdocs

Configuration Manager documentation public repo
https://docs.microsoft.com/sccm/
Creative Commons Attribution 4.0 International
252 stars 362 forks source link

Multible ConfigMgr Instances #2305

Closed mattwailes closed 4 years ago

mattwailes commented 4 years ago

Can you clarify if there are any limitations to multiple instances of ConfigMgr in a single tenant using Co-Management? Can each instance of ConfigMgr in a single tenant have their own CMG that the individual instances can manage?

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

aczechowski commented 4 years ago

Hi @mattwailes, good questions. I'm not aware of any limitations with co-management and multiple tenants.

For CMG, see this FAQ

NOTE: I do have an update planned for that FAQ to further distinguish proper terminology around subscription vs tenant. The user accounts are in the tenant, the CMG is in the subscription that’s associated with that tenant. One tenant (AAD instance) can have multiple subscriptions (billing, resources, services), but not vice versa. Look for an update to that FAQ coming soon.

mattwailes commented 4 years ago

My org will have multiple domains in a single tenant. Users from multiple domains will be in a single Azure tenant. We will have multiple instances of CM that will be doing co-management (each domain has a different instance of CM).

There is no technical limitation to hosting the CMG's from the different domains(different CM hierarchies) using a single Azure sub and tenant correct?

From: Aaron Czechowski notifications@github.com Sent: Tuesday, April 21, 2020 9:11 PM To: MicrosoftDocs/SCCMdocs SCCMdocs@noreply.github.com Cc: mattwailes matthew.wailes@outlook.com; Mention mention@noreply.github.com Subject: Re: [MicrosoftDocs/SCCMdocs] Multible ConfigMgr Instances (#2305)

Hi @mattwaileshttps://eur05.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fmattwailes&data=02%7C01%7C%7C9a6142af838c406e917108d7e65a246f%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637231147135009890&sdata=lKPDjE1UELFBB5CVyp9OzC0oRqmSjGlspepFjAdwUsc%3D&reserved=0, good questions. I'm not aware of any limitations with co-management and multiple tenants.

For CMG, see this FAQhttps://eur05.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.microsoft.com%2Fmem%2Fconfigmgr%2Fcore%2Fclients%2Fmanage%2Fcmg%2Fcloud-management-gateway-faq%23do-the-user-accounts-have-to-be-in-the-same-azure-ad-tenant-as-the-tenant-associated-with-the-subscription-that-hosts-the-cmg-cloud-service&data=02%7C01%7C%7C9a6142af838c406e917108d7e65a246f%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637231147135019885&sdata=xzhyacmudm17zLoaYMfLrNX5S4ZB0J2YvdTaHR1v2fo%3D&reserved=0

NOTE: I do have an update planned for that FAQ to further distinguish proper terminology around subscription vs tenant. The user accounts are in the tenant, the CMG is in the subscription that’s associated with that tenant. One tenant (AAD instance) can have multiple subscriptions (billing, resources, services), but not vice versa. Look for an update to that FAQ coming soon.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHubhttps://eur05.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2FSCCMdocs%2Fissues%2F2305%23issuecomment-617473264&data=02%7C01%7C%7C9a6142af838c406e917108d7e65a246f%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637231147135019885&sdata=oySgEjEd3luMJ%2BeDFCVrQMO4M%2FcU7tPV74ERSWcYIEs%3D&reserved=0, or unsubscribehttps://eur05.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAJNJ35LAZLK4Q4EYKAOXJITRNY75RANCNFSM4MDNEZTA&data=02%7C01%7C%7C9a6142af838c406e917108d7e65a246f%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637231147135019885&sdata=pq8r6wONESBtD%2F6gwRulI5%2B1GWxRZQyYcMSXkc1XEZw%3D&reserved=0.

aczechowski commented 4 years ago

Not that I'm aware of. It's the same as having dev/test/prod environments with a single prod AAD tenant. For site A, you create CMG A. For site B, you create CMG B. Clients in site A only know about CMG A because that's the only one defined in the site, so the only one they are provided in policy. The two services operate side-by-side in your subscription with zero interaction.