A visual aid might help. Within the Meraki Enterprise Application in Azure, the Single Sign-On with SAML has a section about your SAML claim and its attributes. In documentation, Meraki says they CAN receive more than 1 role but that SAML token must present as a semicolon separated list. For an enterprise level deployment I might have cameras in BuildingA, BuildingB and so on. So building Entra ID (Azure AD) groups usually by building (or site), I have a group SG-CAM-BldgA-ViewLive (with an associated App role cam_bldga_viewlive) ... and so on. So if a user appears in multiple groups and that user goes through the single sign on - I want it to send that multiple group membership (also called multiple roles) back in the SAML token so that upon authentication that user is given the access to each role received in the token. There are 3 or 4 articles that have pieces of the SAML puzzle and this one says it supports multiple roles being passed: Configuring SAML Single Sign-on for Dashboard - Cisco Meraki Documentation But as detailed a configuration example as is provided in this Azure specific EA setup: Configuring SAML SSO with Microsoft Entra ID - Cisco Meraki Documentation they stop without saying "and here is how you could pass more than one role" which is absolutely maddening when you have multiple sites and buildings to give only that access that is needed in the performance of ones job function.
... View more