Enterprise SSO
Migrayt supports enterprise Single Sign-On via Microsoft Azure AD (OIDC) and SAML 2.0. When SSO is enabled, your organisation's users log in to Migrayt using their existing corporate credentials — no separate password required.
Microsoft Azure AD (Recommended)
Azure AD SSO works for any organisation using Microsoft 365. It requires no IT setup — users click "Sign in with Microsoft" and authenticate with their corporate email and MFA.
How it works
- User clicks Continue with Microsoft on the Migrayt login page
- Browser redirects to
login.microsoftonline.comfor authentication - After successful authentication, the user's Azure AD claims (email, name, tenant) are used to find or create their Migrayt account
- The user is logged in to Migrayt
Admin consent
For organisations where IT restricts third-party app consent, an admin needs to pre-approve Migrayt once. Share this URL with your IT administrator:
https://login.microsoftonline.com/common/adminconsent?client_id=77ad40d2-4016-4347-933d-d4a3975f9e55After admin consent is granted, all users in the tenant can sign in without an approval prompt.
What Microsoft permissions Migrayt requests
| Permission | Reason |
|---|---|
openid | Authenticate the user |
email | Identify the user's email address |
profile | Get the user's display name |
Migrayt does not request access to emails, calendar, files, or any Microsoft 365 data. These permissions are only for login identification.
SAML 2.0
SAML is available for enterprise customers who require centralised IdP management (Okta, Ping Identity, Azure AD with SAML, ADFS, or any SAML 2.0 compliant IdP).
With SAML, your IT team configures Migrayt as a Service Provider in your IdP. Users are provisioned and deprovisioned centrally — when an employee leaves, revoking their IdP access automatically revokes Migrayt access.
Setup process
- Contact support@migrayt.ai to request SAML enablement for your organisation
- Provide your IdP's metadata XML URL or XML document
- Migrayt support configures Cognito to trust your IdP
- Your IT admin adds Migrayt as a Service Provider using the SP metadata:
SP Entity ID: https://migrayt-auth.auth.eu-west-1.amazoncognito.com/saml2/idpresponse ACS URL: https://migrayt-auth.auth.eu-west-1.amazoncognito.com/saml2/idpresponse - Test with a single user account before rolling out to the organisation
Required SAML attributes
| SAML Attribute | Description |
|---|---|
http://schemas.xmlsoap.org/ws/2005/05/identity/claims/emailaddress | User's email |
http://schemas.xmlsoap.org/ws/2005/05/identity/claims/name | User's display name |
http://schemas.xmlsoap.org/ws/2005/05/identity/claims/nameidentifier | Unique user ID |
Azure AD SAML configuration
In Azure portal → Enterprise Applications → Add application → Create your own:
- Set Identifier (Entity ID) to the SP Entity ID above
- Set Reply URL (ACS URL) to the ACS URL above
- Under Attributes & Claims, ensure the three required attributes are mapped
- Download the Federation Metadata XML and send it to support@migrayt.ai
Account Provisioning
| Scenario | Behaviour |
|---|---|
| First SSO login (new user) | Migrayt account created automatically; role set to member |
| First SSO login (email matches existing account) | Existing account linked to the SSO identity |
| User deprovisioned in IdP | Next login attempt fails; existing Migrayt data preserved |
| User's email changes in IdP | Old and new emails treated as separate accounts; contact support to merge |
Mixed Authentication
Organisations can use both SSO and email/password authentication simultaneously. Some users may log in via Microsoft while others use email/password. Access controls are applied based on role, not authentication method.