Directory sync with Microsoft Entra ID
Entra ID provisions users and groups into Wytness over SCIM 2.0. People are created, updated and deactivated from the directory, and directory groups map to Wytness roles, so access follows your joiner, mover and leaver process without manual steps. Directory sync is available on Business and Enterprise plans; an organisation owner sets it up.
1. Generate the token in Wytness
- In the Wytness app, open Organisation → Team. The Directory sync card reads Not connected.
- Select Connect Entra ID, then Generate token.
- Copy the Tenant URL and the Secret token. The token is shown once; Wytness keeps only a fingerprint of it. If you lose it, choose Manage → Rotate token.
- Choose which Entra groups give which role (the next section), then select Save mapping.
2. Map groups to roles
Each Wytness role can follow one Entra group, matched on the group's display name, ignoring case. These are the defaults; change any of them in the dialog, or later through Manage → Edit group mapping.
| Entra group (default name) | Wytness role |
|---|---|
| Wytness Owners | Owner |
| Wytness Admins | Admin |
| Wytness Members | Member |
| Wytness Viewers | Viewer |
Someone in several mapped groups gets the highest of those roles. Someone in no mapped group gets Viewer. Roles come only from this mapping: a role attribute sent by the directory is ignored.
3. Connect the enterprise application in Entra ID
- Sign in to the Microsoft Entra admin center as at least an Application Administrator.
- Browse to Entra ID → Enterprise apps, select New application → Create your own application, name it (for example Wytness), choose Integrate any other application you don't find in the gallery, and select Add.
- In the application, select Provisioning, then New configuration.
- Paste the Wytness Tenant URL into Tenant URL and the Wytness token into Secret Token.
- Select Test Connection. Entra ID looks up a user that does not exist and expects an empty answer; Wytness returns exactly that. Then select Create.
- On Users and groups, assign the people and groups that should have Wytness access, including the groups from your role mapping. With the scope Sync only assigned users and groups, nothing is provisioned until you assign someone.
4. Check the attribute mapping
Under Attribute mapping there is one set for users and one for groups. Wytness reads these attributes:
| Wytness attribute | What Wytness does with it |
|---|---|
| userName | The person's email address and sign-in name. Keep it as the matching attribute. It must be an email address. |
| active | false turns sign-in off and keeps history; true restores it. Keep the default IsSoftDeleted-based mapping. |
| externalId | Stored and filterable, so Entra ID can match on it. |
| name.givenName, name.familyName | First and last name shown on the Team page. |
| Group displayName | Matched against your role mapping. Group names must be unique. |
| Group members | Membership drives the person's role. |
Other attributes Entra ID sends, such as phone numbers or the enterprise extension, are accepted and not stored. Wytness accepts both PATCH styles Entra ID uses, with or without the aadOptscim062020 compliance flag on the tenant URL.
5. Test with one person, then start
- Select Provision on demand, search for one assigned person and provision them. They appear on the Wytness Team page with the role their groups give them.
- On Overview → Properties, add a notification email for quarantine alerts and turn on accidental deletions prevention.
- Select Start provisioning. The first cycle takes longest; later cycles run about every 40 minutes. The Wytness card then shows the last sync time and how many people and groups are synced.
How synced people sign in
Synced people sign in with Sign in with Microsoft, exactly as before; directory sync does not change sign-in. The first time, Wytness asks them to confirm that their Microsoft account belongs to the account the directory created, and to accept the privacy policy.
Rotate, edit or disconnect
| Action | Effect |
|---|---|
| Rotate token | A new token replaces the current one at once. Paste it into Secret Token in Entra ID; provisioning pauses until you do. |
| Edit group mapping | Saving re-derives every synced person's role from the new mapping straight away. |
| Disconnect | Revokes the token. Synced people keep their access and roles; manage them on the Team page from then on. |
Every provisioning change is written to your organisation's Audit log with the actor directory-sync: person provisioned, updated or deactivated, and group changes. Token creation, rotation and revocation and mapping edits are recorded against the owner who made them.
Limits
Nested groups are not expanded; only direct members of a mapped group get its role. Each token may make up to 1,000 requests a minute, and Entra ID retries anything over that. Sign-in with SAML is not part of directory sync.