Automatic user provisioning keeps your TestCollab user list in sync with your directory, using SCIM - the standard way Microsoft Entra ID sends user changes to other applications. This is worth setting up when your team is large enough that maintaining the list by hand has become a chore.
Setup happens in two parts: TestCollab first, then Azure.
Part 1 - Generate the connection details
Who does this: the TestCollab administrator.
Go to Enterprise → Single Sign On → Microsoft Entra ID.
Scroll to Automatic user provisioning (SCIM).
Copy the Tenant URL shown there. It is specific to your company, so use exactly this one.
Select Generate token and copy the token - TestCollab shows it once and never again.
The status next to the panel changes to Enabled.
Hand the Tenant URL and the token to your Entra administrator.
Part 2 - Set up provisioning in Azure
Who does this: the Entra administrator.
Two things to know first. Automatic provisioning needs a Microsoft Entra ID P1 or P2 licence - if the Provisioning section is missing or greyed out, that is why. And you do not need to publish anything to the Microsoft application gallery; an application you create in your own directory is all that is required.
Go to Enterprise applications → select your application
Open Provisioning → Get started and set Provisioning Mode to Automatic.
Under Admin Credentials, paste the Tenant URL and the Secret Token from TestCollab, then select Test Connection. It should succeed.
Under Mappings, keep Provision Microsoft Entra ID Users on. The default settings work - TestCollab identifies people by their email address, so make sure the username and email fields carry real email addresses.
Under Settings, set Scope to Sync only assigned users and groups, and set Provisioning Status to On.
Under Users and groups, assign the groups whose members should have TestCollab accounts.
Save.
💡 After the settings are saved; to push a single user immediately, use Provision on demand.
What happens from here
When someone is added to an assigned group A TestCollab account is created and linked to your company, and they are put on your projects with the default role from your group mapping. Their exact role - Tester, Manager, and so on - is applied the first time they sign in.
When someone is removed from the group or the application On the next sync, TestCollab checks their assignments with Microsoft and removes their access to your company - they disappear from your team list and lose their project roles, and their account is removed.
If you reach your plan's user limit New accounts stop being created and the reason appears in Entra's provisioning logs. Add seats, or narrow the assigned groups.
Managing the token
Action | What it does |
Regenerate token | Issues a new token. The current one stops working straight away, so paste the new one into Azure. |
Disable SCIM | Stops Entra from creating or removing accounts. Existing accounts are unaffected. Generate a new token to start again. |
Your Tenant URL is tied to your company, so a token generated for one TestCollab company cannot be used with another.