Choose your country or region

Staff sign-in with Microsoft Entra ID, built for banks.

Your staff use the work account they already have. Entra ID signs them in, your groups decide their roles, and leavers lose access the moment you switch them off. Everbranch builds small and medium banks their banking app and staff portal; your staff sign in to the portal with Microsoft Entra ID.

The connector for Microsoft Entra ID is built and ready to configure for your bank.

Staff sign-in

How we connect to Microsoft Entra ID

Microsoft Entra ID is Microsoft's cloud identity service, formerly Azure Active Directory. It signs people in to enterprise applications over SAML 2.0 or OpenID Connect, and its provisioning service creates, updates and deactivates users and groups in applications over SCIM 2.0. Many banks already run their staff accounts in it.

Single sign-on over OpenID Connect or SAML

Your admin adds the staff portal as an enterprise application in Entra ID and registers it with us over OpenID Connect or SAML 2.0; we require signed responses and check every one.

SCIM provisioning

Entra ID's provisioning service creates, updates and deactivates staff in your bank over SCIM 2.0, with a bearer token your bank admin issues.

Groups mapped to roles

Your bank maps Entra groups to staff roles; someone in no mapped group gets no access, and a deactivated account loses every session at once.
Data

What moves between Microsoft Entra ID and your app

  • Sign-in results for each staff member, checked and turned into a session
  • Name, work email and group membership from the token or SCIM
  • New joiners and changes provisioned over SCIM
  • Deactivations that end every session of that person immediately
  • Fresh sign-ins for sensitive actions, forced through Entra ID

Passwords, multi-factor methods and Conditional Access stay in your Entra tenant. We never see a staff password, and SCIM accounts never get one.

Use cases

What your bank can do with it

One work account for the staff portal

Onboarding officers, compliance teams and operations sign in with the account they use for email.

Joiners and leavers handled in one place

HR changes flow through Entra ID; a leaver deactivated there is signed out of the portal straight away.

Roles that follow your org chart

Put someone in the compliance group and they get compliance permissions, and nothing else.
Why it matters

What it changes for your bank

Your security policies apply

Multi-factor rules and Conditional Access in Entra ID protect the staff portal too.

A way in when the directory is down

Named break-glass admins keep a password and authenticator code, are never linked to Entra ID, and every use is audited.

Sensitive actions ask again

Approving a decision or a payment can force a fresh Entra ID sign-in by the same person.
Rollout

From first call to live

  1. Step 1: Create the enterprise applicationYour Entra admin adds the staff portal and chooses OpenID Connect or SAML 2.0.
  2. Step 2: Register it in your admin consoleYour bank admin enters the provider details, trusted email domains and the group-to-role mapping.
  3. Step 3: Connect provisioningYour bank admin issues a SCIM token, and your Entra admin points provisioning at our SCIM address.
  4. Step 4: Test, then enforceStaff try single sign-on with passwords still allowed; once it works, you switch to single sign-on only.
Questions

Microsoft Entra ID: what IT teams ask

Is Everbranch certified or listed by Microsoft for Entra ID?
No. It works through the open standards Entra ID supports: OpenID Connect, SAML 2.0 and SCIM 2.0. We tested it against standard mock providers, and you set it up as your own enterprise application.
Do we use OpenID Connect or SAML with Entra ID?
Either works. OpenID Connect is usually quicker to set up. SAML responses must be signed with SHA-256 or stronger; encrypted assertions are not accepted today.
What happens when someone leaves the bank?
Deactivate them in Entra ID. Over SCIM the account is disabled and every session and open sign-in ends in the same step. Their records and audit trail stay.
Can our bank still get in if Entra ID is unavailable?
Yes. Under single sign-on only, named break-glass admins keep a password and authenticator code. We refuse to enforce single sign-on until a usable one exists.
Related

Okta

Staff sign in with Okta, Okta groups decide what they can do, and a deactivation in Okta ends their access in the portal straight away.
Okta integration

Salesforce

Your relationship managers work in Salesforce. Your customers bank in your app. We keep the two in step, so nobody re-types an application or misses a complaint.
Salesforce integration

Twilio

Reach customers by text and WhatsApp from your banking app, using the Twilio account your bank already runs. Your notice rules and customer preferences stay the same.
Twilio integration
Pilot programme

Running Microsoft Entra ID? Let's map it.

Tell us your version and how your teams use it. We'll show where it plugs in and what your customers get.

  • Your name and colours in the demo
  • Straight answers for risk, compliance and IT
  • No commitment