mirror of
https://github.com/bitwarden/help
synced 2025-12-16 00:03:41 +00:00
* jekyll redirect from * Organizations rev (#262) * Organizations revisions initial commit. * API doc updates * Fix absolute link causing build failure. * Add import to org article, and downstream order changes. * Bitwarden 101 videos: 1st steps toward proliferating these throughout /help. * Added 'Create Your Account' article, which references B101 Videos. * About SSO redirect & promote importing for orgs up the list * Create Org FAQs & trim Feature FAQs accordingly. * Image for Org FAQs * Move 'About the Business Portal' to Orgs category, and re-order accordingly. * Final edits. * Dchoi/bootstrap upgrade (#264) * bootstrap 4 upgrade and cleanup update gulp tasks * bootstrap package updates * renaming file convention * general outline of help outline * bitwarden help cleanup * article cleanup * article general styling complete * bootstrap help page upgrades * sidebar updates * Dchoi/bootstrap upgrade (#267) * bootstrap 4 upgrade and cleanup update gulp tasks * bootstrap package updates * renaming file convention * general outline of help outline * bitwarden help cleanup * article cleanup * article general styling complete * bootstrap help page upgrades * sidebar updates * toc dynamic and more updates * fix callout conditions * sidebar collapse functionality added * sidebar header toggle functionality * sidebar article fixes * Update sidebar.html Fix sidebar Release Notes link. * Update releasenotes.md Remove unnecessary category tag. * Delete release-notes.md Remove unnecessary category. * Update why-choose-bitwarden-for-your-team.md Test table image differentiation * Update why-choose-bitwarden-for-your-team.md Second image differentiation test * removed links from category breadcrumb and replaced with badges Co-authored-by: fred_the_tech_writer <69817454+fschillingeriv@users.noreply.github.com>
87 lines
3.7 KiB
Markdown
87 lines
3.7 KiB
Markdown
---
|
|
layout: article
|
|
title: Configuring directory sync with Azure Active Directory
|
|
categories: [directory-connector]
|
|
featured: true
|
|
popular: false
|
|
hidden: false
|
|
tags: []
|
|
---
|
|
|
|
This article will cover how to connect the Bitwarden Directory Connector application to your Azure Active Directory.
|
|
|
|
## Requirements
|
|
|
|
- Read through the following article: [Syncing users and groups with a directory]({% link _articles/directory-connector/directory-sync.md %})
|
|
- Install Bitwarden Directory Connector
|
|
- Using Directory Connector, log into your Bitwarden account and select your enterprise organization
|
|
|
|
## Create a New Application Registration
|
|
|
|
1. Go to <https://portal.azure.com>
|
|
2. Select the **Azure Active Directory** resource
|
|
3. Navigate to **App registrations** and select **New registration**
|
|
{% image directory-connector/azure/new-application.png %}
|
|
4. **Name** your application "Bitwarden"
|
|
5. Click the **Create** button to create the application.
|
|
{% image directory-connector/azure/create-application.png %}
|
|
|
|
## Grant Application Permissions
|
|
|
|
1. Select the **Bitwarden** application you created in the previous section.
|
|
2. Select **API Permissions**.
|
|
3. Select the **Add** button to create a new API permission set.
|
|
4. For step 1, **Select an API** for **Microsoft Graph**.
|
|
5. For step 2, **Select Permissions** for the following:
|
|
- Application Permissions:
|
|
- "Read all users' full profiles"
|
|
- "Read all groups"
|
|
- Delegated Permissions:
|
|
- "Read all groups"
|
|
- "Read all users' full profiles"
|
|
- "Read all users basic profiles"
|
|
6. Click the **Select** button and then **Done** to add the Microsoft Graph API permissions.
|
|
{% image directory-connector/azure/graph-permissions.png %}
|
|
7. Click the **Grant Permissions** button to grant the permissions to the application.
|
|
{% image directory-connector/azure/grant-permissions.png %}
|
|
|
|
## Create Application Secret Key
|
|
|
|
1. Go back to the **Bitwarden** application that you created.
|
|
2. Select **Certificates & Keys**.
|
|
3. Add a new **Password** key by entering a **Name** and **Duration**. We recommend selecting "Never Expires" for the duration.
|
|
4. Click **Save** to create a new secret key.
|
|
5. Copy the key's value to safe place. We will need to reference it later.
|
|
{% image directory-connector/azure/key.png %}
|
|
|
|
## Get Your Application ID
|
|
|
|
1. Go back to the **Bitwarden** application that you created.
|
|
2. Copy the **Application (client) ID** to a safe place. We will need to reference it later.
|
|
{% image directory-connector/azure/application-id.png %}
|
|
|
|
## Get Your Tenant Hostname
|
|
|
|
1. Select the **Directory and Subscription** filter in the top right corner of the Azure Portal.
|
|
2. Note the **Current directory** (ex. acmeinc.onmicrosoft.com). This is your **Tenant** hostname. Copy the **Tenant** hostname to a safe place. We will need to reference it later.
|
|
{% image directory-connector/azure/tenant.png %}
|
|
|
|
## Configure Directory Connector
|
|
|
|
1. Launch the Directory Connector desktop application.
|
|
2. Go to the **Settings** tab.
|
|
3. Select **Azure Active Directory** as the directory type.
|
|
6. Enter the **Tenant** hostname that you copied from the steps above (ex. company.onmicrosoft.com).
|
|
7. Enter the **Application ID** that you copied from the steps above.
|
|
8. Enter the Application **Secret** Key that you copied from the steps above.
|
|
|
|
Congrats! You are done configuring Azure Active Directory with the Bitwarden Directory Connector.
|
|
|
|
## Testing
|
|
|
|
{% callout info %}
|
|
It can take up to 15 minutes for the granted permissions for your application to properly propagate. You may receive "Insufficient privileges to complete the operation" errors in the meantime.
|
|
{% endcallout %}
|
|
|
|
Test your configuration by running a sync test. You should see your Azure Active Directory groups and/or users printed to the screen.
|