Exit
  • Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
  • 한국 커뮤니티
3

Multiple admin consoles connected to one Azure Ad

Community Beginner ,
Oct 31, 2023 Oct 31, 2023

Hi,

We manage the IT for several municipalities. The users for these different municipalities are located in 1 Microsoft Entra ID (Azure AD), the difference being that the users have their own domain name per municipality.

Is it possible to link different Adobe admin consoles (one admin console per municipality) to one and the same Entra ID?

TOPICS
Admin console , Enterprise , Identity and SSO , Manage account , Teams , Users and groups
752
Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines

correct answers 1 Correct answer

Adobe Employee , Sep 18, 2024 Sep 18, 2024

One OIDC app will connect to only one directory/admin console. I highly doubt Microsoft will allow the creation of the second OIDC app under the same Azure tenant for another admin console. You could use the "Adobe Identity Management (SAML)" app to configure SSO for another admin console in the same Azure tenant. 

Translate
Adobe Employee ,
Oct 31, 2023 Oct 31, 2023

Hi @Pascal32534701z2ga 

 

Thanks for reaching out to us.

Admin consoles are unique and so they can be linked to an azure tenant.

 

If azure supports multi tenants, Multiple Admin consoles should not have an issue since each admin console would have a unique connection with Azure

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Beginner ,
Oct 31, 2023 Oct 31, 2023

So Adobe knows which portal to use when a user logs in with user@domainA or user@domainB when they both exists in the same Azure AD?


Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Sep 16, 2024 Sep 16, 2024

Hi

 

I have the same question, if the 1 admin console is already configured for SSO via OIDC, if you connect a second admin console, would it create a new enterprise application in Azure, or just use the existing integration?

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Adobe Employee ,
Sep 17, 2024 Sep 17, 2024

If you have a separate admin console, you can use a different Azure tenant with a different domain to configure SSO using the OIDC app. You can also use the "Adobe Identity Management (SAML) app to configure SSO in the same admin console, however, with a different domain.  

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Sep 17, 2024 Sep 17, 2024

Thanks for the feedback, but i need to confirm if i can connect a 2 seperate admin consoles to the same Azure tenant via OIDC, and also if it would create a seperate instance in Azure or would it use the same OIDC app.

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Adobe Employee ,
Sep 18, 2024 Sep 18, 2024
LATEST

One OIDC app will connect to only one directory/admin console. I highly doubt Microsoft will allow the creation of the second OIDC app under the same Azure tenant for another admin console. You could use the "Adobe Identity Management (SAML)" app to configure SSO for another admin console in the same Azure tenant. 

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines