Postman supports SCIM provisioning through Microsoft Entra ID (formerly Azure Active Directory), allowing you to automate user provisioning and de-provisioning for your team.
You must be a Postman Team Admin or Super Admin to enable SCIM for your team. It's recommended that you enable SCIM with a service account assigned the Super Admin role.
With SCIM enabled, users won't have the option to leave your team on their own, and won't be able to change their account email or password. Only Team Admins and Super Admins have permission to remove team members. Only administrators in Microsoft Entra ID have permission to use SCIM to change user account emails if they're associated with a domain your team verified.
Postman is available as an app in the Microsoft Entra application gallery. Once connected, Microsoft Entra ID queries the Postman SCIM endpoint every 40 minutes for assigned users, and creates or modifies them according to the assignment details you set.
To set up provisioning with Microsoft Entra ID, do the following:
https://api.getpostman.com/scim/v2/
.HTTP 200 OK
with an empty SCIM ListResponse
message.Next, you will configure the Microsoft Entra ID integration.
After you set up SCIM in Microsoft Entra ID, you can configure the integration with Postman for users. Optionally, you can also configure the integration for groups.
The attributes you select as Attribute Mappings are used to match the users or groups in Postman for update operations.
To map Postman user attributes to Microsoft Entra ID user attributes, do the following:
In the Microsoft Entra ID Mappings section, select Yes to turn on Provision Azure Active Directory Users. This is the set of attribute mappings for user objects.
Under Target Object Actions, select Create, Update, and Delete.
Under Attribute Mappings, select Add New Mapping to map the following attributes:
Microsoft Entra ID attribute | Target attribute | Postman attribute | Mapping type | Match objects using this attribute | Apply this mapping |
---|---|---|---|---|---|
userPrincipalName * | userName | email | Direct | Yes | Always |
surname | name.familyName | name | Direct | No | Always |
givenName | name.givenName | name | Direct | No | Always |
Not([IsSoftDeleted]) | active | active | Expression | No | Always |
* For userPrincipalName
, set the value for Matching precedence to 1
.
You must remove any existing attribute mappings that aren't on this list to avoid any conflicts or mismatches. Select Delete next to any mappings that aren't on this list to remove them.
Select Save to commit any changes.
To map Postman group attributes to Microsoft Entra ID group attributes, do the following:
In the Microsoft Entra ID Mappings section, select Yes to turn on Provision Azure Active Directory Groups. This is the set of attribute mappings for group objects.
Under Target Object Actions, enable Create, Update, and Delete.
Under Attribute Mappings, select Add New Mapping to map the following attributes:
Microsoft Entra ID attribute | Target attribute | Postman attribute | Mapping type | Match objects using this attribute | Apply this mapping |
---|---|---|---|---|---|
displayName * | displayName | Group name | Direct | Yes | Always |
members | members | Group members | Direct | No | Always |
* For displayName
, set the value for Matching precedence to 1
.
You must remove any existing attribute mappings that aren't on this list to avoid any conflicts or mismatches. Select Delete next to any mappings that aren't on this list to remove them.
Select Save to commit any changes.
Once the first cycle has started, you can select Provisioning logs in the Microsoft Entra ID left pane to monitor the actions done in Postman by the provisioning service.
Last modified: 2022/11/30