Skip to main content

An overview

One work account, one password policy, one place to switch access off. Here's what Microsoft Entra ID single sign-on gives your organisation in TestCollab.

Why single sign-on is worth it

Every extra password is an extra thing to lose. Single sign-on removes that problem: your team signs in to TestCollab with the same Microsoft work account they already use for everything else.

For the organisation, the gain is control. The protections you have already invested in - strong password rules, multi-factor authentication, conditional access, sign-in monitoring, now cover TestCollab too, without any extra work. Joining, moving teams, and leaving are handled in one place: your directory. When someone leaves the organisation, closing their Microsoft account closes their way in to TestCollab as well.

And because access is driven by group membership rather than a list of roles in TestCollab, what your directory says is always what TestCollab does.

What you can set up

TestCollab's Entra ID integration has three parts. You can use just the first, or build up to all three.

What it does

Who sets it up

Single sign-on

People sign in to TestCollab with their Microsoft work account.

Entra administrator, then TestCollab administrator

Group-based access

A user's TestCollab role comes from their Entra group or app role.

TestCollab administrator

Automatic user provisioning

TestCollab accounts are created and removed as people join and leave your groups and apps in Entra.

TestCollab administrator, then Entra administrator

Who does what

Setting this up is a short back-and-forth between two people. It can be the same person if they hold both the roles.

  • The Entra administrator registers TestCollab as an application in your Microsoft Entra ID directory and hands over two identifiers and a secret value.

  • The TestCollab administrator pastes those into TestCollab, turns single sign-on on, and decides how groups map to roles.

Each article below says clearly which of the two is acting at every step.

Before you begin

  • TestCollab single sign-on is available on the Enterprise plan.

  • In TestCollab, the SSO settings page is open to the company account owner.

  • In Microsoft Entra ID, you need permission to register an application and to grant admin consent.

  • A company can have one single sign-on provider active at a time. If Okta is currently enabled, turn it off before enabling Microsoft Entra ID.

  • For automatic user provisioning, your directory needs a Microsoft Entra ID P1 or P2 licence.

Where to go next

Did this answer your question?