Edmund AI Documentation
/SETUP GUIDES

Setting up Entra ID for single sign-on

Let your people sign in to Edmund with their Microsoft accounts, and what Edmund needs from you to enable it.

Last reviewed October 2026

Edmund supports single sign-on through Microsoft Entra ID. Your people sign in with the Microsoft account they already use, and Edmund never handles their password.

Setup is short: you send Edmund your Entra tenant ID, Edmund maps it to your organization, and the Sign in with Microsoft button starts working for everyone in that tenant.

On a dedicated Edmund instance where your administrators register the Edmund application in your own tenant, there is one more step: the registration needs two redirect URIs for the instance’s domain. See When you register the application yourself.

How signing in works

  1. The user opens Edmund

    At edmund.app they choose Sign in with Microsoft instead of entering a password.

  2. Microsoft authenticates them

    They are redirected to Microsoft, sign in there, and come back to Edmund.

  3. Edmund matches the organization

    Edmund reads the tenant ID from the Microsoft response and looks up the organization it belongs to. This is why the tenant ID has to be registered first — without it, sign-in fails.

What Edmund needs from you

One value: your Directory (tenant) ID.

It is a UUID — 36 characters including hyphens, in the form xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx. For example a1b2c3d4-e5f6-7890-abcd-ef1234567890.

To find it:

  1. Sign in to the Azure portal.
  2. Open Microsoft Entra ID.
  3. On the Overview page, copy Tenant ID.

Send it to your Edmund contact. It is an identifier rather than a secret, so ordinary email is acceptable.

Note

One tenant maps to one Edmund organization. If your company uses several Entra tenants and people from more than one need access, tell Edmund — each tenant has to be registered separately.

Permissions

Edmund’s application registration asks for two delegated Microsoft Graph permissions, both for the person who is signing in:

PermissionWhy
User.ReadSign in and read the signed-in person’s own profile
emailThe email address that identifies the Edmund account

The standard OpenID Connect scopes openid, profile and offline_access belong to the same sign-in. If your consent tooling lists them separately, approve them too. Edmund uses the refresh token to check that the person is still allowed in your tenant.

Edmund uses no application (app-only) permissions and reads nothing else from your directory: no other users, no groups. User.ReadBasic.All, User.Read.All, GroupMember.Read.All, Group.Read.All and Application.Read.All are not needed. The SharePoint connector is a separate application registration with its own permissions, see Working with SharePoint.

A tenant administrator grants these permissions once for the whole organization (admin consent). Nobody else is asked for consent after that. On edmund.app, the consent link returns the administrator to https://edmund.app/auth/callback/azure, Edmund’s own address.

Granting consent takes a Microsoft Entra directory role: Global Administrator, Privileged Role Administrator, Cloud Application Administrator or Application Administrator. An Azure subscription role such as Owner or Contributor isn’t enough. To grant it, open Microsoft Entra ID › Enterprise applications, select Edmund, then Permissions › Grant admin consent.

Don’t add permissions beyond the ones listed above. Each extra permission is one more thing your administrator has to approve, and Edmund doesn’t use it.

Disabling a user in Entra ID ends their Edmund session the next time it is renewed, within minutes. The Edmund account itself stays and is removed by an administrator in Edmund.

When you register the application yourself

On a dedicated Edmund instance — Private SaaS or Private cloud — your Entra ID administrators may register the Edmund application in your own tenant rather than use Edmund’s. The instance runs on its own domain, and the registration has to know that domain: Microsoft returns a user to Edmund only at an address listed in the registration.

Add two redirect URIs of the platform type Web to the application registration:

Redirect URIUsed by
https://<instance domain>/auth/callback/azureThe Edmund web application, where the user lands after signing in
https://<API domain>/api/auth/social/complete/azuread-tenant-oauth2/The Edmund API, which completes the sign-in

Edmund sends you both addresses exactly as your instance uses them. Copy them rather than building them from the pattern: the API domain is not always the instance domain with api. in front.

To add them:

  1. Sign in to the Azure portal.
  2. Open Microsoft Entra ID, then App registrations, and select the Edmund application.
  3. Open Authentication, add both addresses under the Web platform, and save.
Note

Both addresses start with https://, and the trailing slash of the second one is part of it. Microsoft compares the address character by character, so http:// or a missing slash is enough for sign-in to fail.

Under API permissions, add the same two delegated Microsoft Graph permissions, User.Read and email, as described in Permissions.

Alongside the tenant ID, Edmund then needs the registration’s Application (client) ID and a client secret. The client secret is a credential, unlike the tenant ID: transfer it over a secure channel agreed with your Edmund contact, not by ordinary email.

What happens the first time someone signs in

The result depends on whether that person already has an Edmund account with the same email address.

SituationPassword sign-in afterwardsSSO sign-inRole and settings
Account exists and is activeStill worksWorksPreserved
Account exists but is inactiveStill worksWorksPreserved, account reactivated
No account yetNot until a password is setWorksNew account, User role

An existing account is linked, not replaced. Roles, team membership and settings survive, and the person can carry on using their password if they prefer.

An inactive account is reactivated by a successful SSO sign-in. Worth knowing before you enable SSO: if you deactivated someone by making their account inactive, they will be able to sign in again. Remove them from the organization, or from the tenant, rather than relying on the inactive flag.

A new person gets an account automatically, placed in the organization the tenant maps to and given the User role. Nobody arrives as an administrator.

After the first sign-in

To change someone’s role, an administrator opens organization settings, goes to Users, and edits the person’s role there. Roles are Reader, User, User Expert and Administrator, in ascending order.

To let a new SSO user also sign in with a password, they use Forgot password? on the sign-in page. After setting one, both methods work.

Removing people

Edmund reads only the profile of the person signing in, so it doesn’t see changes in your directory. When someone leaves:

  • Removing them from Entra ID, or from the Edmund application, stops their Microsoft sign-in.
  • Their Edmund account stays. An administrator removes them in organization settings under Users, or you ask Edmund to.

Automatic removal is being considered. It would need SCIM provisioning, where Entra ID sends user changes to Edmund, or extra directory permissions such as User.Read.All or GroupMember.Read.All. Edmund will agree any change in permissions with you before making it.

Troubleshooting

Sign-in fails immediately after Microsoft authentication. The tenant ID is usually the cause: either not registered with Edmund, or the person’s Microsoft account belongs to a different tenant than the one registered. Check also that the organization is active in Edmund.

Microsoft shows error AADSTS50011, “The redirect URI … does not match”. This applies only when you register the application yourself. The registration is missing one of the two redirect URIs, or lists it with http:// or a different path. The error quotes the address Edmund sent; add exactly that address under the Web platform.

Microsoft shows “Need admin approval” (AADSTS90094), and the app may be marked unverified. Admin consent hasn’t been granted yet. Your tenant doesn’t let users approve apps themselves, which is common. An administrator with one of the roles under Permissions grants consent once, and then it works for everyone.

Microsoft says the user isn’t assigned to the application (AADSTS50105). The Edmund enterprise application has Assignment required turned on. Assign the users or groups who should have access, under Users and groups.

Sign-in succeeds but nothing is visible. The account is signed in but has no access yet. Check that the account is active, that a role is assigned, and that the person belongs to a team with access to the relevant projects — a new SSO user starts as User and sees only what that role allows.

What to send Edmund

Success

One value, and confirmation of who should administer the organization. Two more when you register the application yourself.

ValueNotes
Directory (tenant) IDThe UUID from your Entra ID overview page
Intended administratorsEdmund raises their role after their first sign-in, since everyone starts as User
Application (client) IDOnly when you register the application yourself. From the Overview page of the application registration
Client secretOnly when you register the application yourself. Over a secure channel agreed with your Edmund contact