Azure Active Directory single sign-on (SSO) integration with Meraki Dashboard

[Bipin-Kumar]

https://learn.microsoft.com/en-us/azure/active-directory/saas-apps/meraki-dashboard-tutorial

I've used the above-mentioned URL to configure the Azure SSO. This is working fine for Sunquest Information Systems India Pvt Ltd organization in the Meraki portal. However, when we are configuring this for the Sunquest Information System organization this is not working. After troubleshooting we found out that the Application created in Azure portal has a pre-populated field named Entity-ID and this value cannot be the same for two apps. Screenshot attached.

how can we make this work for both organizations using the same Azure tenant??

[MyHomeNWLab]

There was a workaround to add #{Number} (e.g. #1) to the end of the Identifier (Entity ID).

The following is an example for AWS.

https://github.com/MicrosoftDocs/azure-docs/issues/57571

> Adding "#" and followed by a unique number is required only when there are multiple instances of Amazon Web Services (AWS) enterprise application added to the same Azure AD tenant.

I'm interested in MSP-specific considerations. This topic is nice.

[Bipin-Kumar]

https://learn.microsoft.com/de-de/azure/active-directory/saas-apps/amazon-web-service-tutorial

I'm assuming you are referring to this article from Microsoft. This also is not working.

I've tried using https://dashboard.meraki.com/saml#1 and https://dashboard.meraki.com/#1

[PhilipDAth]

Why are you trying to register Azure SSO twice in the same Azure tennancy?  Why wouldn't you register it just one?

[Bipin-Kumar]

We have two Sunquest organization in Meraki dashboard based on the geographical location one for India and another for US. SAML config in Meraki dashboard is Organization level. So we need two enterprise application in the Azure portal for both the organization.

i've tested this for Sunquest India and it is working fine however for the US one we are getting an error on Azure portal. Error - We cannot use the same entity id for two apps.

[JonnyM]

You can probably work around this now by opting into the new SP-initiated SSO feature and using the custom entity ID that you set, but personally I'd have one SSO configuration and use roles to determine who has access to which organisations.