Microsoft Entra ID

An institution that runs Microsoft Entra ID can use it for two things in Full Fabric, set up independently:

What it does Set up in Full Fabric
Sign-in (SAML 2.0) Staff sign in with their Entra account instead of a Full Fabric password. Settings > Access & security > Authentication > Providers
Provisioning (SCIM 2.0) Entra creates staff accounts, keeps their names and email up to date, suspends people it disables, and fills teams from its groups. Settings > Access & security > Authentication > Provisioning

Both are configured on one enterprise application in the Entra admin center. Outlook email and calendar are a separate integration (Settings > Microsoft integrations > Outlook email & calendar).

1. Sign-in with SAML 2.0

In the Entra admin center, create an enterprise application ("Create your own application", non-gallery) and open Single sign-on > SAML.

  1. In Full Fabric, add a SAML provider (Authentication > Providers > Add SAML IdP) and note its slug.
  2. In Entra, edit Basic SAML Configuration and save it before anything else:
    • Identifier (Entity ID): https://<your-host>/auth/saml/p/<slug>/metadata
    • Reply URL (Assertion Consumer Service URL): https://<your-host>/auth/saml/p/<slug>/callback
  3. Only then copy the App Federation Metadata Url and paste it into the provider's metadata import in Full Fabric. Imported before step 2 is saved, the metadata lists certificates Entra will not sign with, and every sign-in fails with an invalid signature.
  4. Keep Unique User Identifier (Name ID) as the user's email, and map the claims Full Fabric reads (first name, last name, and the object ID) in the provider's attribute mappings.
  5. Under Users and groups, assign the people (or groups) who may sign in. Entra refuses anyone not assigned (AADSTS50105).

Full Fabric stores the Entra object ID on the person the first time they sign in, and from then on only that Entra account can sign in as them. If someone is deleted and recreated in Entra, an admin clears the stored ID from their profile (Miscellaneous > Clear single sign-on identity) and the next sign-in stores the new one.

2. Provisioning with SCIM 2.0

  1. In Full Fabric, open Authentication > Provisioning:
    • Switch Enabled on.
    • Optionally pick a Default staff role; without one, provisioned staff get the role staff added manually get.
    • Copy the SCIM 2.0 base URL (https://<your-host>/scim/v2).
    • Create a SCIM token (this opens the API tokens page with SCIM provisioning selected). Copy the token: it is shown once. It does not expire by default, because an expired token silently stops provisioning.
  2. In Entra, open the enterprise application's Provisioning page and set Provisioning Mode to Automatic:
    • Tenant URL: the SCIM 2.0 base URL.
    • Secret Token: the SCIM token.
    • Test Connection should succeed.
  3. Under Mappings > Provision Microsoft Entra ID Users:
    • Match on userName (the user principal name or email).
    • Map externalId from objectId. Entra's default maps it from mailNickname; left that way, the ID stored on provisioned staff does not match the one SAML sends, and their sign-in is refused.
  4. Set Scope to "Sync only assigned users and groups", assign users or groups, and start provisioning.

What provisioning does

  • Creates an active staff member with the default staff role and no invitation email (they sign in through Entra).
  • Updates names, and the login email of people it created. The email of someone created in Full Fabric is left to Full Fabric.
  • Disables (or deletes, 30 days after someone leaves Entra) by suspending the person: they are signed out, and their profile and history stay.
  • Never touches applicants, students, contacts, Full Fabric support accounts, or people whose data was scrubbed or anonymized. An email that belongs to an applicant is refused rather than turned into a staff account.
  • Every change shows on the person's audit trail as "SCIM provisioning: ".

Groups and team roles

Entra groups assigned to the application become teams of the same name, and group membership drives team membership. Deleting a group in Entra empties its team and detaches it; the team itself stays, because other parts of Full Fabric refer to teams.

Under Provisioning > Team roles, an admin can map a team to a staff role: joining the group grants the role, leaving it takes the role away again, unless another of the person's teams maps to the same role or it is their only staff role. The Support team is never provisioned.

Keep Entra's group matching on displayName (its default, under Mappings > Provision Microsoft Entra ID Groups). That is how a group finds a team that already exists, such as one an admin created or one detached by an earlier group deletion. Matched on externalId instead, creating that group is refused because the team name is taken.

Assigning groups to an enterprise application needs Entra ID P1 or P2; on the free tier only users can be assigned.

Troubleshooting

Symptom Cause
AADSTS50011 reply URL mismatch The sign-in started on a host other than the Reply URL's. Use the same host, or add the other one in Entra.
AADSTS700016 application not found The Identifier (Entity ID) was not saved in Basic SAML Configuration.
AADSTS50105 user not assigned Assign the user, or a group they are in, to the enterprise application.
"Invalid Signature on SAML Response" The metadata was imported before Basic SAML Configuration was saved. Import it again.
Provisioned staff are refused at sign-in externalId is mapped from mailNickname, not objectId.
Test Connection fails with 404 Provisioning is switched off in Full Fabric.
Test Connection fails with 401 The Secret Token is not a SCIM provisioning token, or it was revoked or suspended.