Microsoft Entra ID

Configure Microsoft Entra ID (formerly Azure AD) as a SAML identity provider for sfp.

Use the URL that matches your deployment mode. Self-hosted: replace <your-domain> with your sfp server domain. Cloud: use auth.flxbl.io. See URL convention.

1. Create the application

Sign in to the Azure Portal.
Go to Microsoft Entra ID → Enterprise applications → New application.
Choose Create your own application.
Select Integrate any other application you don't find in the gallery (Non-gallery).
Name it (e.g. "sfp SSO") and click Create.

2. Configure SAML

In the new application, go to Single sign-on → SAML and click Edit on Basic SAML Configuration.

Field	Value
Identifier (Entity ID)	`https://<your-domain>/auth/v1/sso/saml/metadata`
Reply URL (ACS URL)	`https://<your-domain>/auth/v1/sso/saml/acs`
Sign on URL	leave blank
Relay State	leave blank
Logout URL	leave blank

Click Save.

3. Configure attributes and claims

Entra ships only emailaddress by default. displayname, givenname, and surname are NOT in the default claim set — you must add them explicitly below, or sfp users will end up with empty first/last names.

Click Edit on Attributes & Claims and ensure these are set:

Claim name	Source attribute
Unique User Identifier (Name ID)	`user.mail` (Format: Email address)
`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`

The Name ID format must be Email address — sfp matches users by email.

4. Copy the federation metadata URL

In the SAML Certificates section, copy App Federation Metadata URL. It looks like:

https://login.microsoftonline.com/<tenant-id>/federationmetadata/2007-06/federationmetadata.xml?appid=<app-id>

This is the only thing you need to hand to sfp.

5. Assign users

In the application, go to Users and groups → Add user/group.
Pick the users (or groups) who should have sfp access.
Click Assign.

Users not assigned here will be rejected at the IdP before they ever reach sfp.

Next step

Continue with Self-Hosted Setup or Cloud Setup to register the IdP with sfp.