Bluebeam Single Sign-On (SSO) Configuration for Microsoft Entra ID (Formerly Azure AD)


Thank you for your interest in leveraging Bluebeam support for single sign-on (SSO) to enhance security, improve the user experience, and reduce support costs. The step-by-step instructions in this document will help to ensure successful configuration of SSO leveraging the Microsoft OpenID Connect Protocol (OIDC) when using Microsoft Entra ID (formerly Azure Active Directory [AD]).

Configuring SSO requires that your organization has at least 100 seats on either a Basics, Core, or Complete Bluebeam Plan and that end users are using versions under Core Support (see Supported versions and support tiers).

With a Bluebeam subscription, named user licenses can access Revu offline for up to 14 days — even with SSO. To refresh their token, a user will need to sign into Revu 21 again after the grace period. For more information, see this article.

If you have any questions regarding these instructions, contact us.


This guide covers how to set up your SSO configuration and the information that needs to be sent to/from Bluebeam and your organization’s Entra ID.

SSO configuration supports multi-factor authentication (MFA) as defined by the identity provider.

Important considerations before you begin:

  • You’ll need the Active Directory Global Administrator to grant permissions for the application.
  • Pay close attention to avoid any inconsistencies between the email of a user in your Entra ID and the email used in an existing Bluebeam ID (BBID), which can be caused by things like name changes or adjustments to account information. As part of the onboarding process for Bluebeam single sign-on (SSO), we will send you a CSV file that lists your organization’s users who currently exist in our system, including those who may be active Bluebeam Studio users. For SSO, Bluebeam matches according to email address, which must match the legacy BBID contained in the files we send.

Please let us know if you need assistance in matching any user email addresses. We can double-check the admin’s name/email with the Account Manager or consult the licensing system.

Prepare for setup

First, contact Technical Support to let us know you’ll be configuring SSO. Once you’ve been added in our system, you’ll see a new option in that will allow you to securely submit the necessary information.

Inputs for home system

Within Azure, you’ll need to set up redirect URIs for users in their respective regions. You can either:

  • Set up one configuration that contains multiple regions.
  • Set up different configurations for each region in which you have users.

Use the table below to determine the redirect URI to set up in your Entra ID:

Region Redirect URI

Outputs to send to the Bluebeam system

You’ll need to share the redirects you set up with the Bluebeam SSO Engineering team by logging into your Bluebeam Accounts Page and using our secure form to provide the following information:

  • Client Secret Value.
  • Application Client ID.
  • OpenID Connect (OIDC) metadata file.
  • Domains list (Bluebeam needs a list of all domains managed in your Entra ID.).

Configure your Entra ID

To set up Entra ID for OpenID Connect (OIDC):

  1. Go to The Microsoft Azure Portal.
  2. Click Microsoft Entra ID.
  3. Click App registrations in the sidebar. Then click + New registration.
  4. Enter an application name (for example, Bluebeam SSO). Then:
    1. Under Redirect URI, select Web as the platform.
    2. Consult the chart above to find your Redirect URI and input the link.
    3. Click Register.
  5. Click Certificates & secrets in the sidebar. Then:
      1. Click + New client secret.
      2. Enter a Description.
      3. Set the expiration date.
        The default expiration is six months. However, we suggest using the the maximum value of two years, if possible, based on your security needs.
      4. Click Add.
      5. Copy the Client Value into your notes.
        You will need the Client Value later. Open a text editing program, like Notepad or Word, to paste the Client Value you copied. You cannot retrieve this value later, so you should save and store it in a secure place.
  6. Click Overview in the sidebar, and:
    1. Under Essentials, copy the Application (client) ID into your notes.
    2. Click Endpoints.
    3. Copy and save the URL for OpenID Connect metadata document.
      Format your OpenID Connect metadata document as:{tenant-id}/v2.0/.well-known/openid-configuration
  7. Click Token configuration in the sidebar. Then click + Add optional claim. Add the following claims to the ID token:
    • Claim: family_nameToken type: ID
    • Claim: given_name, Token type: ID
    • Claim: preferred_username, Token type: ID 
    • Claim: email, Token type: ID

    The token must have the preferred_username/email, first name, last name, username (i.e., email) Claims above for creating a user in the Bluebeam system. Please let us know if your system uses any other Claims.

  8. Click API permissions in the sidebar, and click + Add a permission.
  9. Click Microsoft Graph at the top of the page. Then click Delegated Permissions.
    You will need the Active Directory Global Administrator to grant these permissions for the application.
  10. Select checkboxes for the following OpenID permissions:
    • email
    • openid
    • profile
  11. Click Add Permissions.
  12. On the Configured permissions dialog, click Grant admin consent for <your organization>.
    The image below illustrates the minimum required permissions to grant.

Restrict user access to SSO using “Users and groups”

Use the following procedure to either assign SSO access to all users in your Azure instance, or to assign SSO access to only a specified subset of users in your Azure instance.

  1. Go to
  2. Select Microsoft Entra ID.
  3. Click Enterprise Applications in the sidebar.
  4. Select the Application you created (ex. Bluebeam SSO).
  5. Click Properties in the sidebar.
  6. If you want to allow SSO login for all users in your Active Directory, keep Assignment required? set to No.Restricting SSO to application
  7. If you want to restrict SSO login to specific users, toggle Assignment required? to Yes and:
    1. Use the Entra ID Users and Groups feature to assign SSO to those users.
    2. Notify the Bluebeam admin of this setting.
      Bluebeam activates SSO across the entire domain. Not including a specific user from your AD will result in that user being restricted from logging in.

Submit information to Bluebeam

Once you’ve gathered all the information in the Outputs to send to Bluebeam’s systems section, you can submit them through our secure form. To submit:

    1. Sign in to with your BBID.
      If you don’t see the SSO Identity Provider section, make sure you’re using the same BBID that you provided to Technical Support.
    2. Next to SSO Identity Provider, click Change.
    3. Select Azure as your Identity Provider. Then enter the following information for your organization:
    4. When you’re ready to configure SSO, click Save.

    Once submitted, this information will be reviewed by our internal teams, and Bluebeam Technical Support will reach out to coordinate an activation timeline.



    Revu 21

    Revu 20

    Revu 2019

    Revu 2018

    Learn how to start configuring your Revu licenses for SSO with Microsoft Azure.