SAML (Azure AD) with multiple Organizations

ksumann
Getting noticed

SAML (Azure AD) with multiple Organizations

Hello everyone,

 

 

are there any suggestions for implementing SAML with multiple organization?
My idea was to create specific roles for each organization (like: ORG_ABC_write, ORG_DCF_read) but users who have rights in multiple orgs should see them after the initial login.

We followed this instructions: https://documentation.meraki.com/General_Administration/Managing_Dashboard_Access/Configuring_SAML_S...

 

But users who have assigned multiple roles usually sees only one organization after login.


Thanks

4 Replies 4
double_virgule
Getting noticed

Are the multiple organizations in one Azure tenant? 

 

Edit: Sorry, today must be a second Monday. I reread your question. To my understanding, the SAML connection link is different for each Cisco Meraki organization. Do you see a different SSO config url for the different organizations? 

double_virgule_1-1730819121221.png

 

 

 

ksumann
Getting noticed

Hi,

 

yes. The organization settings menu gives me another replay url for each organization.

double_virgule
Getting noticed

I wonder if you need to create a different EA for each organization and map it that way. I don't know how the interplay for users would work on that, but it might be a requirement, especially if the URLs are different for each org.  

ksumann
Getting noticed

I guess EA means Entra Application? But having an application for each org is kinda clunky and not user friendly.

 

To my knowledge, it is only possible to give one role per user. So this role needs to be present in all orgs the user should have access to.
This role can have different permissions in different orgs.

 

BUT it seems completly impossible to "build" user permissions based on different roles.

For each permission-org requirement, you need to create a new role.
This could get complex if you have a lot of orgs and users.

The reply url that needs to be configured points to a specific org. In order to work, the role needs to be defined in this org or the access would be denied. But if the user shouldn't have rights in this org you ether need to have a dummy org, containing all roles, or create a dummy network and give permission to it.

This feels not like a clean solution.

Get notified when there are additional replies to this discussion.