Careers and workplace integration · Updated November 15, 2026

Microsoft Entra ID integration

Staff, members and partners sign in to the private parts of your website with their Microsoft Entra ID accounts. We register the app in your tenant, connect it by OpenID Connect or SAML, and let in only the groups you choose. On Webflow, the signed-in area runs as a separate app.

Rated 5.0 out of 5,72 Google reviews

Microsoft Entra ID at a glance

Connects
Sign-in by OpenID Connect or SAML, group claims, B2B guests and External ID for customers.
WordPress
No Microsoft plugin. A maintained SSO plugin, or a small OpenID Connect plugin we write.
Webflow
No visitor login since User Accounts ended on January 29, 2026. Private areas run in a separate app.
Astro or Next.js with Sanity
Server-side sign-in with Auth.js or MSAL; every protected route checks the session and group.
Custom software
MSAL libraries, app roles in the token, Microsoft Graph for profile and group data.
Complexity
Medium. Sign-in is quick; tenant approvals and group design take the time.
Typical setup
1 to 3 days for staff sign-in on one site, 5 to 12 days for a member or partner portal with guests.

How we connect Microsoft Entra ID

  • WordPress

    Microsoft doesn't publish a WordPress plugin. We set up a maintained SSO plugin, such as miniOrange's, or write a small OpenID Connect plugin with fewer moving parts. The app registration stays in your tenant either way. As of November 15, 2026, mapping Entra groups to WordPress roles is a paid feature in miniOrange's plugin.

  • Webflow

    Webflow retired User Accounts on January 29, 2026, so there's nothing in Webflow for Entra ID to sign people in to. Pages publish as static files, and a script that hides content after sign-in can't protect text already sent to the browser. We keep the public site in Webflow and put the Entra-protected area in a small Astro or Next.js app on a subdomain.

  • Astro or Next.js with Sanity

    Sign-in runs on the server through Auth.js's Microsoft Entra ID provider or Microsoft's MSAL Node. A tenant-specific issuer keeps out accounts from other organizations; Auth.js otherwise defaults to the common endpoint. Middleware checks the session and group claim before any protected page or Sanity query runs.

  • Custom software

    Line-of-business apps use the MSAL libraries and app roles, so the token says what each person may do. When an app needs more, such as a staff directory, it calls Microsoft Graph with the narrowest permission that works. Apps that require user assignment need an administrator's consent, which keeps access to the people and groups you list.

What organizations use Microsoft Entra ID for

  • Staff areas and intranets

    Staff sign in with the account they use for email, and your tenant's multifactor rules apply. We require assignment so only listed groups get in, and pass group membership in the token so HR forms show to HR and field guides show to crews.

  • Partner and member portals

    People from other organizations join as B2B guests and sign in with their own work, school or social accounts. Email one-time passcodes are on by default for guests without such an account. Cross-tenant access settings decide which outside organizations get in, and your admins can block domains.

  • Customer and public accounts

    For customers or the public, an External ID tenant keeps them out of your staff directory. Sign-up can use email, Google, Apple, Facebook or another OpenID Connect provider. As of November 15, 2026, core features are free for the first 50,000 monthly active users; Azure AD B2C hasn't been sold to new customers since May 1, 2025.

What to watch out for

  • Licences for the extras

    Conditional Access needs Entra ID P1, which Microsoft 365 Business Premium and E3 include. A branded sign-in page needs P1, Business Standard or SharePoint Plan 1, and tenants created after January 5, 2026 can't use custom CSS on it. External ID add-ons have no free tier. We check your licences before quoting any of these.

  • No Canada location for Entra ID

    A Canadian tenant's directory data sits in Microsoft's North America geo, and multifactor logs can be stored in North America. Microsoft's Canada commitments cover Exchange, SharePoint and Teams, not Entra ID. External ID's in-country Go-Local add-on covers only Australia and Japan as of November 15, 2026.

  • Admin steps in your tenant

    Registering the app, granting admin consent and assigning groups all happen in your tenant, by someone with the right Entra role. We send a checklist and do it with them on a screen share. Book that time early.

Sources

Checked against Microsoft's docs on November 15, 2026.

Questions about Microsoft Entra ID

Can the Microsoft sign-in page appear in French?

Yes. With a licence that includes company branding, you can add French text and images that show to browsers set to French. The pages after sign-in are your site's, so we build their French versions too.

OpenID Connect or SAML?

OpenID Connect for anything we build, since Auth.js, MSAL and miniOrange's free plugin support it and it returns tokens Microsoft Graph accepts. SAML when a plugin or vendor portal supports only SAML.

Does staff sign-in change our privacy notice?

It should. Each sign-in sends Microsoft a name, email and group data and leaves a log entry that may be stored outside Canada. Name Microsoft as a service provider. If the portal serves people in Quebec, Law 25 calls for an assessment before their sign-in data leaves the province.

Putting a login on your site with Entra ID?

Tell us who needs to sign in, whether staff, partners or the public, and which Microsoft 365 licences you hold. We'll say which tenant setup fits and what your admins need to approve.

Book a call