SAML SSO with Azure AD
Configure SAML SSO with Azure AD
This guide walks through setting up SAML single sign-on between Microsoft Entra ID (formerly Azure Active Directory) and Screendesk. After completing these steps, your team members can log in to Screendesk using their Microsoft credentials.
Plan Availability: Enterprise only
Before starting, make sure you have admin access to both the Microsoft Entra admin center and your Screendesk workspace. You will also need your Screendesk service provider details — find them in Account Settings → Security → SAML SSO.
Configuration Overview
Setting up SAML SSO with Microsoft Entra ID involves creating an enterprise application in the Entra admin center, configuring SAML settings on both sides, and assigning users.
You will need these Screendesk values for the Microsoft side:
Reply URL (ACS URL)
https://app.screendesk.io/saml_callback
Identifier (Entity ID)
urn:screendesk.io:saml
Step 1 — Create an Enterprise Application in Entra ID
Open the Entra admin center
Sign in at entra.microsoft.com and navigate to Identity → Applications → Enterprise applications.
Configure Attributes & Claims
Click Edit on the Attributes & Claims card. Verify or set the following:
Required claim:
Unique User Identifier (Name ID)
user.userprincipalname or user.mail (must be the user's email address)
Additional claims (these should already be present by default in Entra ID):
http://schemas.xmlsoap.org/ws/2005/05/identity/claims/emailaddress
user.mail
http://schemas.xmlsoap.org/ws/2005/05/identity/claims/givenname
user.givenname
http://schemas.xmlsoap.org/ws/2005/05/identity/claims/surname
user.surname
http://schemas.microsoft.com/identity/claims/displayname
user.displayname
Entra ID includes these claims by default for new enterprise applications, so you typically won't need to add them manually. Just confirm they are present.
Click Save if you made changes.
Copy the Entra IdP details
Scroll down to the SAML Certificates card and the Set up Screendesk card. You will need three values:
Login URL — Copy this. You will paste it as the Single Sign On URL in Screendesk.
Microsoft Entra Identifier — Copy this. You will paste it as the IDP Entity ID in Screendesk.
Certificate (Base64) — Click Download next to "Certificate (Base64)." You will paste its contents as the IDP Certificate in Screendesk.
Assign users and groups
In the left sidebar, click Users and groups, then click Add user/group. Select the users or groups who should have access to Screendesk and click Assign.
Only users assigned to the enterprise application (directly or via group membership) will be able to log in via SAML. Unassigned users will receive an error from Microsoft.
Step 2 — Configure Screendesk
Enter the Entra IdP details
Using the values you copied from the Entra admin center in Step 1:
SSO Domain
Your company's email domain (e.g., yourcompany.com)
IDP Entity ID
The Microsoft Entra Identifier
Single Sign On URL
The Login URL
IDP Certificate
The contents of the downloaded Base64 certificate. Open it in a text editor and paste the full text, including the -----BEGIN CERTIFICATE----- and -----END CERTIFICATE----- lines.
Step 3 — Test the Connection
Troubleshooting
"SAML Authentication failed" error
This usually means the SAML response signature could not be verified. Check the following:
The IDP Certificate in Screendesk matches the Base64 certificate downloaded from Entra. Make sure you pasted the full PEM text including header and footer lines.
The Reply URL in Entra matches
https://app.screendesk.io/saml_callbackexactly.The Identifier in Entra matches
urn:screendesk.io:samlexactly.
"AADSTS700016" or application not found error
This means the user is not assigned to the Screendesk enterprise application in Entra. Go to Users and groups on the application page and add the user or their group.
Name or email not appearing correctly in Screendesk
Verify the Attributes & Claims in Entra are configured correctly. The NameID must resolve to the user's email address. If your organization uses user.userprincipalname values that differ from actual email addresses, switch the NameID source to user.mail instead.
Last updated
Was this helpful?