You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 26, 2022. It is now read-only.
This makes it easier for the users to sign in using the Microsoft 365 App Launcher
This step pre-enters the organisation identifier in the Bitwarden SSO Page when accessed from the M365 App Launcher.
Select Branding from the navigation
Enter the Home page URL as your domain
Select Manifest from the navigation
Find the signInUrl JSON Key and replace the value (entered in step 2) with a URL that includes your organisation's identifier in the format: https://vault.bitwarden.com/#/sso?identifier=YOUR-ORG-ID or https://your.domain.com/#/sso?identifier=YOUR-ORG-ID
{% callout info %} Azure AD doesn't allow URLs with parameters when using the GUI (step 2), hence, the URL has to be entered again with the parameters in the JSON (step 4). {% endcallout %}
New section
After this section: https://bitwarden.com/help/article/oidc-azure/#register-a-redirect-uri
START
Include a sign on/homepage url (optional):
This makes it easier for the users to sign in using the Microsoft 365 App Launcher
This step pre-enters the organisation identifier in the Bitwarden SSO Page when accessed from the M365 App Launcher.
https://vault.bitwarden.com/#/sso?identifier=YOUR-ORG-ID
orhttps://your.domain.com/#/sso?identifier=YOUR-ORG-ID
{% callout info %} Azure AD doesn't allow URLs with parameters when using the GUI (step 2), hence, the URL has to be entered again with the parameters in the JSON (step 4). {% endcallout %}
END
For things related to Bitwarden apps:
The text was updated successfully, but these errors were encountered: