Azure SAML configuration for Dynatrace
Follow the examples below to configure Azure as the SAML identity provider (IdP) for Dynatrace SSO.
This page describes the IdP (Azure) end of your SAML SSO configuration, not the Dynatrace end. Use it as part of the entire SAML configuration procedure for Dynatrace SaaS if you're using Azure.
While we do our best to provide you with current information, Dynatrace has no control over changes that may be made by third-party providers. Always refer to official third-party documentation as your primary source of information for third-party products.
In the Azure portal, choose
Enterprise Applicationsfrom the Azure Active Directory.
Select New Application and choose
Add from the gallery, then type
Dynatracein the search box and then select Dynatrace.
Type the name of the application (for example,
Dynatrace) and select Create to add the application. The Overview page of your application will open automatically.
Choose Single sign-on from the application’s left-hand navigation menu and choose
SAMLas the single sign-on method.
At Save single sign-on setting, select Yes.
In Basic SAML Configuration, set Logout Url to
https://sso.dynatrace.com:443/saml2/sp/logoutand save your changes.
In SAML Signing Certificate, download Federation Metadata XML.
Choose User and groups from the application’s left-hand navigation to configure user access to the Dynatrace application.
In Dynatrace Account Configuration, provide the metadata you downloaded as Federated Metadata XML and set the following attributes:
First name attribute
Last name attribute
Security group claim attribute
Note that in the SAML message returned by Azure, groups are identified with an
ObjectId, not a group name. When configuring the user group mapping, make sure you use
ObjectId in Security group claims.
The number of user groups that Azure Active Directory adds to a SAML token is limited to 150. If this limit is exceeded, a link to the Graph API endpoint is returned instead of a group list. Dynatrace doesn’t support retrieving user groups this way, because it would require additional authentication between Dynatrace and Azure AD.
If you exceed the 150 limit, consider one of the following options:
- Limit the number of groups that users are assigned to.
- Configure Azure AD to send only groups assigned to the application.
Error AADSTS50105 - The signed in user is not assigned to a role for the application occurs during federated authentication with Azure Active Directory (Azure AD), it indicates that the user hasn't been granted access to the application in Azure AD.
For details, see the Microsoft documentation: