Skip to content

Microsoft SSO Setup

Once SSO is on, everyone on your Amalgam team signs in with their Microsoft (Entra ID) account instead of an Amalgam password. All future sign-ins and sign-ups for the team will require SSO.

The rollout takes three things from your side: your Directory (tenant) ID, admin consent for a few basic permissions if user consent is turned off, and each existing user clicking a link to connect their account. Amalgam handles the rest.

You’ll need someone with admin access to your Microsoft Entra tenant. Have these ready:

  • Your Directory (tenant) ID, found in the Entra admin center under Overview.
  • Permission to grant admin consent, in case user consent is turned off in your tenant for any of these permissions: openid, profile, email, User.Read.
  • A secure way to share the tenant ID with us, like a one-time secret link.
  1. Share your Directory (tenant) ID with your Amalgam contact through a secure link. One-time secret links expire, so send it when we’re ready to act on it, and re-share if we let you know it expired.
  2. If user consent is turned off for openid, profile, email or User.Read, have an admin open the consent link we send and approve the permissions. The page you’re redirected to afterwards will show an error. That’s expected and the consent still goes through.
  3. Let us know once consent is done. We’ll confirm on our end and switch SSO on for your team. This only takes a few minutes.
  4. Everyone already on your Amalgam team gets an email with a link to connect their Microsoft account. We’ll let you know when the emails are out so you can test the login.

Each existing user connects their account once, and it takes about 30 seconds:

  1. Open the email from Amalgam and click the link to connect.
  2. Sign in with your current Amalgam email and password one last time.
  3. Sign in with your Microsoft account when prompted. From then on, you’ll use Microsoft to sign in.

Why the one last Amalgam login? It tells us exactly which Amalgam account to link to which Microsoft account, so we don’t have to match them by email. It should be a 1:1 match anyway, but this covers any edge cases.

You don’t need to create new users in Amalgam first. New users get a link with a button to create their account through Microsoft SSO, and the account is created in your company’s Amalgam team. There’s no Amalgam password and no linking step for them.

They can also start from the My Apps tile below, which sends anyone without an account straight to sign-up.

The My Apps tile is a simple URL redirect. Point it to:

https://api.amalgam.me/auth/sso/entra/authorize

This sends users straight to their Amalgam account if it’s already created and linked, or to create a new account in your team if it isn’t. Don’t point the tile to amalgam.me, since that goes to the website rather than the sign-in flow.

Disabling or removing the user in Entra is enough to cut off access right away. Their Amalgam login stops working and the account becomes inactive.

The user still exists on the Amalgam side, even though nobody can get into it. We recommend deleting them from your Amalgam team too, for cleanup. It isn’t time-sensitive, so it doesn’t need to be part of your same-day offboarding checklist.

The page after admin consent shows an error. Did it work?

Yes. The redirect after the consent screen is expected to fail. Just let us know consent is done and we’ll confirm it on our end.

The tenant ID link we sent expired. What now?

Send a new one. One-time secret links can expire before we open them, especially over a weekend.

Can users still sign in with their Amalgam password after SSO is on?

No. Once SSO is switched on, all sign-ins and sign-ups for your team go through Microsoft.

A user didn’t get the connection email.

Ask them to check spam, then reach out to us and we’ll resend it.