Configuring Vouched SSO with Azure AD / Microsoft Entra ID
Configure Azure Active Directory (Microsoft Entra ID) as your SAML 2.0 identity provider for Vouched SSO using your Vouched SP metadata values.
Configuring Vouched SSO with Azure AD / Microsoft Entra ID
Configure Microsoft Entra ID (formerly Azure Active Directory) as your SAML 2.0 identity provider (IdP) for Vouched SSO.
Prerequisites
Before you begin:
- Complete Steps 1–2 in the SSO / SAML Configuration guide.
- Copy your Vouched SP metadata values from the IdP Configuration section.
- Sign in to the Azure portal with permission to create and manage enterprise applications.
Configure Microsoft Entra ID for Vouched SSO
1. Create an enterprise application
- Log in to the Azure portal.
- Navigate to Microsoft Entra ID > Enterprise applications.
- Click New application.
- Click Create your own application.
- Give the app a name, such as
Vouched. - Select Integrate any other application you don't find in the gallery.
- Click Create.
2. Configure single sign-on
- In your new application, click Set up single sign-on.
- Select SAML.
- In the Basic SAML Configuration section, click Edit.
- Enter the following values from your Vouched IdP Configuration section:
| Azure field | Value |
|---|---|
| Identifier (Entity ID) | Use the Entity ID from Vouched |
| Reply URL (Assertion Consumer Service URL) | Use the ACS URL from Vouched |
Leave "Sign on URL" blank. Do not paste the Vouched Sign-On URL into this field. If it's filled in, the My Apps tile and Azure's Test button send users to a Microsoft error page.
- Click Save.
3. Configure attributes and claims
- In the Attributes & Claims section, click Edit.
- Make sure the following claims are present. Add or edit them if needed:
| Claim name | Source attribute |
|---|---|
firstName | user.givenname |
lastName | user.surname |
- Make sure the Unique User Identifier (Name ID) is in email format. By default, Azure uses the user's UPN (user principal name). If your users' UPNs don't match their email addresses, change the source attribute to
user.mail.
4. Add your Azure metadata to Vouched
- In the SAML Signing Certificate section, find App Federation Metadata Url.
- Copy the URL, or download the Federation Metadata XML file.
- In Vouched, go to Settings > SAML Security. Paste the URL into Metadata URL (recommended), or paste the XML into Metadata XML.
- Click Save.
5. Assign users
In your enterprise application, go to Users and groups and assign the users or groups who should have access to Vouched through SSO.
6. Enable SAML and test
- In Vouched, go to Settings > SAML Security and turn on Enable SAML.
- Right away, open a private or incognito window and sign in to Vouched through SSO as an admin.
- If sign-in fails, turn Enable SAML off and contact Vouched support (see below).
What changes when SAML is on
- SSO can only be tested while SAML is on. While it's off, the Vouched login page goes straight to password login.
- Users who are already logged in stay logged in.
- From then on, non-admin users must sign in through SSO. Admins can still sign in with their password.
Troubleshooting
| Symptom | Likely cause | Fix |
|---|---|---|
| A blank Microsoft page says login failed (from the My Apps tile or Azure's Test button) | Sign on URL is filled in | Clear Sign on URL in Basic SAML Configuration |
| The Vouched login page only asks for a password | Enable SAML is off | Turn on Enable SAML (Step 6) |
| SSO reaches Vouched but login fails | Missing name claims or the wrong Name ID format | Check Step 3 |
Need help?
Contact Vouched support with:
- The step where the issue occurs
- A screenshot of any Microsoft error, including the AADSTS error code
Updated about 14 hours ago
Did this page help you?
