![]() When a group is renamed in Azure, it will be updated in Bitwarden as long as the initial sync has been made. Groups linked in this way will have their members synced from Azure. When a group that already exists in your Bitwarden organization is assigned in Azure, the Bitwarden group is linked to Azure through the displayName and externalId/ objectId values. Group members who are not already members of your Bitwarden organization are invited to join. Group members who are already members of your Bitwarden organization are added to the group. When a new group is assigned in Azure, the group is created in Bitwarden. ![]() When an assigned user is removed from a group in Azure, the user is removed from that group in Bitwarden but remains a member of the organization. When an assigned user is deleted in Azure, the user is removed from the organization. When an assigned user is suspended in Azure, the user has their access to the organization revoked. Users linked in this way are still subject to the other workflows in this list, however values like displayName and externalId/mailNickname are not automatically changed in Bitwarden. When a user who is already a member of your organization is assigned in Azure, the Bitwarden user is linked to the Azure user through their UserName value. When a new user is assigned in Azure, the user is invited to your Bitwarden organization. The following sections describe how modifying users and groups in Azure will impact their counterparts in Bitwarden: Users Select the Add user/group button to assign access to the SCIM application on a user or group level.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |