This guide explains how to configure automatic user provisioning between Microsoft Entra ID (formerly Azure Active Directory) and Teamgo using a custom Enterprise Application in Microsoft Entra ID.
This configuration is recommended if your organisation needs any of the following capabilities:
Sync User PINs — Map a Microsoft Entra ID user attribute to the PIN field in Teamgo, allowing employees to quickly check in at a Teamgo kiosk using their PIN.
Assign Users to Teamgo Groups Based on Entra ID Groups — Automatically assign employees to designated Teamgo Groups according to their Microsoft Entra ID group membership.
Assign Users to Teamgo Kiosks Based on Entra ID Groups — Automatically assign employees to designated Teamgo kiosks and locations according to their Microsoft Entra ID group membership.
If you do not need group attributes or PIN support, please follow this guide instead.
When configured, it provisions and de-provisions users and groups to Teamgo using the Microsoft Entra ID Provisioning service.
Create users in Teamgo
Update existing Teamgo users when their details change in Microsoft Entra ID
Remove users in Teamgo when they no longer require access
Keep user attributes synchronized between Microsoft Entra ID and Teamgo
Assign users to Teamgo Groups using supported mapping rules.
Assign users to designated Teamgo kiosks and locations.
Synced users' notifications will be set based on default notification settings
Single sign-on to Teamgo (recommended)
Important: Set up the Microsoft Entra ID integration in Teamgo first. Configure your attribute mappings, group assignments, and kiosk mapping rules before starting the initial provisioning process in Microsoft Entra ID. Changes made after the initial synchronisation may require users or groups to be reprocessed before the updated settings take effect.
1. Enable Entra ID in Teamgo
Open a new browser tab/window, navigate to the Teamgo Integrations page (https://my.teamgo.co/integrations), click Enable or Configure on the Microsoft Entra ID integration, and copy the required credentials under the SCIM credentials tab (SCIM bearer token and Tenant URL).
1.1 Choose synchronisation option
Under the User synchronisation tab, select one of the following options.
Option A: Sync all users
Synchronises users without applying city-based or Entra-group-based kiosk mapping rules.
This will assign users to all kiosks.
Option B: Sync user city to a location and kiosk
Uses the user's City attribute in Microsoft Entra ID to determine which Teamgo location and kiosks they should be assigned to.
For each Teamgo location:
Locate the location in the Location and kiosk mappings section.
Select the matching condition.
Enter the City value used in Microsoft Entra ID.
Select the kiosk or kiosks to which matching users should be assigned.
Repeat for other locations as required.
For example, users whose Entra ID City attribute is Adelaide can be assigned to kiosks at the Adelaide location.
Option C: Sync user group to a location and kiosk
Uses Microsoft Entra ID group membership to determine which Teamgo kiosks users should be assigned to.
This is the recommended option if your organisation uses Entra ID groups to manage employee access across multiple locations or kiosks.
1.2 Configure default groups (optional)
Under Default groups, select the Teamgo Groups that should be assigned to every user imported from Microsoft Entra ID.
These groups apply to all synchronised users, regardless of their individual Entra ID group membership or department.
1.3 Configure Teamgo Group Assignment Rules Based on Entra ID Department and/or Group Membership (Optional)
If you want users to be assigned to different Teamgo Groups according to their Entra ID Department and/or Group Membership attributes:
Locate Department group rules.
Click + Add rule.
Configure a rule(s) that matches the relevant Entra ID Department value and/or Group Membership.
Select the Teamgo Group or Groups to assign.
Repeat for additional departments/groups.
2. Microsoft Entra ID Configuration
Go to https://portal.azure.com and log in using your Azure administrator credentials and follow these steps:
2.1 Click on Enterprise applications to start creating a new custom app.
2.2 Click on the + New application option (Manage > All Applications sidebar option).
2.3 Enter a name for your application, select the Integrate any other application you don't find in the gallery (Non-gallery) radio button, and click Create.
2.4 In the application’s Manage section, click Provisioning.
2.5: Click + New configuration.
2.6 Copy and paste the Tenant URL and Secret Token from Step 1 into the New provisioning configuration form, and click Test Connection to verify.
If successful, click Create.
3. Setup Users Mapping
Follow the steps below to for User attribute mapping. You may skip this step if not required.
Important Notes:
Teamgo implement the urn:ietf:params:scim:schemas:extension:enterprise:2.0:User:employeeNumber data as the user PIN field. Map this field to your Microsoft Entra ID attribute if usage is required. The PIN field allows user to quickly check-in on the tablet kiosk.
3.1 Click on Manage -> Provisioning
Expand the Mapping accordion list to see options to configure Users and Groups.
3.2 To perform Attribute Mapping for Users, click on Provision Microsoft Entra ID Users
You may change the mapping or add new mapping as required.
Review the user attributes that are synchronized from Microsoft Entra ID to Teamgo in the Attribute-Mapping section. The attributes selected as Matching properties are used to match the user accounts in Teamgo for update operation.
The following attributes are supported.
Attribute | Type | Supported for filtering |
userName | String | ✓ |
active | Boolean |
|
displayName | String |
|
title | String |
|
emails[type eq "work"].value | String |
|
name.givenName | String |
|
name.familyName | String |
|
addresses[type eq "work"].streetAddress | String |
|
addresses[type eq "work"].locality | String |
|
addresses[type eq "work"].region | String |
|
phoneNumbers[type eq "mobile"].value | String |
|
externalId | String |
|
urn:ietf:params:scim:schemas:extension:enterprise:2.0:User:department | String |
|
urn:ietf:params:scim:schemas:extension:enterprise:2.0:User:employeeNumber | string |
|
Important Notes: urn:ietf:params:scim:schemas:extension:enterprise:2.0:User:employeeNumber is PIN field on Teamgo.
4. Setup Groups Mapping
Follow the steps below to for Groups mapping. You may skip this step if not required.
Make sure Enabled is Yes.
Step 4.1 To perform Attribute Mapping for Groups, click on Provision Microsoft Entra ID Groups
Step 4.2 Change Enabled to Yes, Save and return to previous screen.
Step 4.3 Go to the Users and groups section and assign the necessary users and groups to the application.
5. Provision your app
Use Provision on demand to test your deployment. Once successful, click Start provisioning
6. Monitor your deployment
Once you configure provisioning, use the following resources to monitor your deployment:
Use the provisioning logs to determine which users are provisioned successfully or unsuccessfully
Check the progress bar to see the status of the provisioning cycle and how close it's to completion
If the provisioning configuration seems to be in an unhealthy state, the application goes into quarantine. Learn more about quarantine states the application provisioning quarantine status article.