Microsoft Entra ID
Set up single sign-on and SCIM provisioning with Microsoft Entra ID (Azure AD).
Before you start
- You need admin access to your Microsoft Entra ID (Azure AD) tenant.
- Vectis support completes the configuration on the Vectis side, so be ready to send them the details below.
Step 1: Register an application in Entra ID
Open App registrations
In the Azure Portal, go to Microsoft Entra ID → App registrations.
Create a registration
Select New registration and set:
- Name:
Vectis SSO - Supported account types: "Accounts in this organizational directory only"
- Redirect URI: choose Web and enter
https://<your Vectis address>/sso/callback
- Name:
Register
Select Register, then note the Application (client) ID and the Directory (tenant) ID.
Step 2: Create a client secret
- Go to Certificates & secrets → Client secrets → New client secret.
- Add a description, such as "Vectis SSO", and choose an expiry period.
- Select Add and copy the secret value immediately. It isn't shown again.
Step 3: Configure API permissions
- Go to API permissions → Add a permission.
- Select Microsoft Graph → Delegated permissions.
- Add
openid,profile,emailandUser.Read. - If you'll use group claims for role mapping, also add
GroupMember.Read.All, which needs admin consent. - Select Grant admin consent for the permissions.
Step 4: Configure group claims (optional, for role mapping)
- Go to Token configuration → Add groups claim.
- Select Security groups and/or All groups.
- For the ID token, make sure Group ID is selected.
- Select Add.
Step 5: Send the details to Vectis
Send Vectis support:
- Name: a display name for the connection, such as "Contoso SSO".
- Tenant ID: the Directory (tenant) ID from step 1.
- Client ID: the Application (client) ID from step 1.
- Client secret: the secret value from step 2.
- Domain: your organisation's email domain, such as
contoso.com. - The enforcement mode you want, and whether new users should be created automatically on first sign-in (JIT provisioning).
Step 6: Verify your domain
Vectis adds your email domain to the configuration and gives you a verification token. Create a DNS TXT record with that token, then let Vectis know so the domain can be verified.
SCIM provisioning
To provision users automatically:
- Ask Vectis support for a SCIM token and the SCIM base URL (it ends in
/scim/v2). The token is shown only once, so store it safely. - In Entra ID, go to Enterprise applications, find Vectis, and open Provisioning.
- Set the provisioning mode to Automatic.
- Enter the SCIM base URL as the Tenant URL, and the SCIM token as the Secret Token.
- Select Test Connection.
- Configure attribute mappings and turn provisioning on.
See SCIM provisioning for the attributes Vectis uses.
Troubleshooting
| Issue | Solution |
|---|---|
| "Invalid redirect URI" | Make sure the redirect URI in Entra ID exactly matches https://<your Vectis address>/sso/callback. |
| "AADSTS50011" error | The redirect URI doesn't match. Check for trailing slashes. |
| "No matching user found" | Ask Vectis to turn on JIT provisioning, or invite the user first. |
| Groups not appearing | Make sure GroupMember.Read.All has admin consent and group claims are configured. |
| Token validation fails | Check the tenant ID and client ID you sent to Vectis. |