All Collections
Microsoft Azure Active Directory Integration
Microsoft Azure Active Directory Integration

Use Microsoft Azure AD to automatically sync employees into your Envoy directory.

Updated over a week ago

How does Azure work with Envoy?

The Azure Active Directory (also known as Microsoft Entra ID) integration allows for real-time employee provisioning through Azure Active Directory utilizing SCIM API.

With the Envoy + Azure Active Directory integration, Envoy will allow employee provisioning and Single Sign-On (SSO) by utilizing the Envoy Enterprise app within Azure’s Active Directory portal.

Azure is available on Microsoft GCC High (Government Community Cloud) accounts and GCC High is compatible with our Azure directory integration.

Note: From August 2023, Azure AD is undergoing a name change to Microsoft Entra ID. Only the name is changing. All features and services remain the same. Microsoft expects the name change from Azure AD to Microsoft Entra ID to be complete across most product experiences by the end of 2023.

Employee Provisioning

Azure AD account and employees setup

Make sure you have your Azure account created, and you have added your employees to your account. Create groups as needed in Azure and assign users to those groups.

To complete this installation, you’ll need to have admin privileges. Either become an admin or ask your admin for help before completing these steps.

Step 1: Enable Envoy + Azure AD

  1. On the Envoy dashboard, go to your Apps page.

  2. Under Directory and SSO click on Directory Settings.

  3. Click Install under Microsoft Azure AD.

  4. Choose from one of the following options for syncing employees to your directory and click Save:

    1. Sync all users: This is good for companies with one location, or if you prefer to have the same master Envoy employee directory at all locations within your company.

    2. Sync specific users per location: Choose this option if you’d like to sync certain users to certain locations (i.e., creating different Envoy employee directories per location).

  5. Copy the OAuth Bearer Token from Envoy and note to be entered into Azure later.

Step 2: Configure Azure AD

  1. Open the Azure portal and select Azure Active Directory > Enterprise applications > New application > Add from the gallery > search for Envoy and select Add.

  2. Open the Provisioning tab and set Provisioning Mode as Automatic.

  3. Copy Envoy’s SCIM endpoint into the Tenant URL field.

  4. Paste the OAuth Bearer Token copied from the Envoy Dashboard.

    1. Note: Tenant URL above is for new instances, if existing, do not update.

  5. Click on Test Connection, and once successful, click Save.

  6. Click on Users and groups on the left hand side and then assign users or groups to the application.

    1. Azure does not support nested groups for SCIM provisioning.

    2. Configure any optional attributes (primary location, manager, remote status) before assigning users and groups.

  7. Once users are assigned, click on Provisioning on the left hand side and scroll down to the bottom and turn Provisioning Status On.

  8. (Optional) To test provisioning on a single user, utilize the Provision on demand feature in Azure.

Optional Attributes:

Primary Location

Set a user's Primary location via SCIM. Setting a user's primary location will help fill out valuable occupancy data in the Analytics section

Primary location does not affect which location the employee will first see when logging in. It is for analytic purposes only.


This will set the manager field in the Employee Directory and Occupancy Analytics.

Remote Status

Set the Remote Status of the employee within the Employee Directory and Occupancy Analytics.

Only certain values will be accepted for remote status - we encourage using Remote and In person. Please see the following table for other values that can be used to map Remote status. We recommend using the "Office location" field if this is not already populated in Azure user profiles.

Accepted Value in Azure



working from home



in person


in-office, in office

on-site, on site, onsite

office-based, office based




In person


Adding the Attributes

Each optional attribute will require the creation of a custom Envoy attribute within Azure.

  1. Go to Microsoft Entra ID (formerly known as Azure Active Directory)

  2. Go to Enterprise Applications, search for your application > select Envoy.

  3. In the left sidebar, go to Provisioning. Under Manage Provisioning, select Edit attribute mappings > expand the Mappings section > Provision Microsoft Entra ID Users.

  4. Scroll down and select Show Advanced options.

  5. Select Edit attribute list for Envoy.

    1. Note: if this option is not available and instead, there are links to request additional attributes for Envoy and Microsoft Entra ID, restart the process from this link. More info here.

  6. Scroll down to the bottom of the list and create a new attribute. The name, type, and Referenced Object Attribute (only for Manager) must exactly match the descriptions below:

    1. For Primary Location

      1. Name = defaultLocationName

      2. Type = String

    2. For Manager

      1. Name = urn:ietf:params:scim:schemas:extension:enterprise:2.0:User:manager.value

      2. Type = Reference

      3. Referenced Object Attribute: urn:ietf:params:scim:schemas:extension:enterprise:2.0:User

    3. For Remote Status

      1. Name = remoteStatus

      2. Type = String

  7. Click Save and confirm.

Mapping Custom Attributes

After you create the custom attributes, you'll need to add mappings.

  1. From the Provision Microsoft Entra ID Users mapping page, select Add New Mapping in the list of attribute mappings:

    1. For Primary Location:

      1. Mapping type: Direct

      2. Source attribute: city (or whichever attribute you choose to map)

      3. Default value if null (optional): leave empty

      4. Target attribute: defaultLocationName

      5. Match objects using this attribute: No

      6. Matching precedence: leave empty

      7. Apply this mapping: Always

    2. For Manager

      1. Mapping type: Direct

      2. Source attribute: manager

      3. Default value if null (optional): leave empty

      4. Target attribute: urn:ietf:params:scim:schemas:extension:enterprise:2.0:User:manager.value (this is the attribute just created in Envoy)

      5. Match objects using this attribute: No

      6. Matching precedence: leave empty

      7. Apply this mapping: Always

    3. For Remote Status

      1. Mapping type: Direct

      2. Source attribute: {{whichever attribute you are choosing to use}}

        1. If using the Office location field in Azure, then it would be "physicalDeliveryOfficeName"

      3. Default value if null (optional): leave empty

      4. Target attribute: remoteStatus

      5. Match objects using this attribute: No

      6. Matching precedence: leave empty

      7. Apply this mapping: Always

  2. Click Ok > Save and confirm

Primary Location: Assigning location values in Envoy

After the SCIM attributes are set for Primary location, the location values must be assigned to specific locations in the Envoy Dashboard.

Location names that exactly match the name on the SCIM attribute will automatically map

  1. In Envoy, navigate to Employee Directory > Sync settings.

  2. Next to Primary location, select Get started, then Start sync.

  3. Once your Azure instance syncs with Envoy, you'll need to define which locations are mapped to which defaultLocationName attribute. Exact location matches will automatically be assigned to the corresponding Envoy location.

  4. Click Save once you have appropriately defined primary locations.

Important Notes:

Phone Number:

Envoy is in the process of updating our official documentation Envoy app within the Microsoft Azure store. If you want Mobile phone instead of Office phones please change the following within Azure.

  1. Navigate to the Envoy Enterprise App > Provisioning > Mapping and click on Provision Azure Active Directory Users.

  2. Find and delete telephoneNumber from the mapping list.

  3. Find mobile and click onto it so it brings up the editing pane.

  4. Change the mapping to phoneNumbers[type eq "work"].value.

Configuring Single Sign On

  1. In the Envoy dashboard go to Apps > Directory and SSO and click Directory settings and then click Install on the SAML integration.

  2. In the Azure portal, on the Envoy application page, select Single sign-on.

  3. On the Select a Single sign-on method dialog, select SAML to enable single sign-on.

  4. On the Set up Single Sign-On with SAML page, click the edit icon to open the Basic SAML Configuration dialog.

  5. On the Basic SAML Configuration section, enter the following URLs:

    1. Reply URL (Assertion Consumer Service URL) -

    2. Sign on URL -, your specific sign on URL will be found in Apps > Directory and SSO > Configure SAML.

  6. Once all URL’s are entered correctly, hit “Save”.

  7. In the SAML Signing Certificate section, click the edit icon to open SAML Signing Certificate dialog.

  8. In the SAML Signing Certificate section, copy the Thumbprint and save it on your computer.

  9. On the Set up Envoy section, copy the Login URL. This URL is what you will enter into the Envoy integrations page for SAML as your “IDENTITY PROVIDER HTTP SAML URL”.

  10. Login to your Envoy dashboard and go to your Apps page and “Install” SAML.

  11. Take the Thumbprint from step 3 in Azure of the setup and enter that value into the Fingerprint field provided in Envoy.

  12. Paste the Login URL value, which you have copied from the Azure portal into the IDENTITY PROVIDER HTTP SAML URL text box.

  13. Choose whether you want SAML Required and toggle ON if needed, then Save.

Configuring assistants

Please be aware that Azure does not support the assistant feature of Envoy. If you would like to use assistants in Envoy manually, please alert Support to whitelist your account.

Admin Provisioning

Envoy makes it easy for our Visitors Enterprise and Workplace Premium Plus customers to automatically provision their admin users from Okta using Azure.

Sync admins

  1. Create groups as needed in Azure and assign users to those groups.

    1. Assign the group to the Envoy app

      1. Navigate to Home → Enterprise applications → select Envoy app

      2. Click `Add user/group`

      3. Click the `None Selected` link under Users and groups

      4. Search for your group and select it

      5. Click `Assign`

    2. Now provision the group to Envoy (Optional, do this if you want to have immediate access to the groups in Envoy. Otherwise the groups will get provisioned on the pre-defined schedule)

      1. Navigate to Home → Enterprise applications → select Envoy app

      2. Click provisioning

      3. Click provision on demand

      4. Search for and select your group, select the members you’d like to be included, then click the Provision button

    3. Here’s additional information on how to create groups in Azure AD.

  2. Sync your directory with Envoy. You can follow these instructions, if you have not already set up your integration with Envoy.

  3. After you've configured Azure with Envoy, navigate to Employee directory > Admin roles.

  4. Click on Sync Settings at the top of the page.

  5. Under Sync admins, select the group you want to assign roles to.

  6. Select an Envoy role and one or more location from the dropdown menu for each group. (The list of group names is pulled from Azure.)

  7. Click Add > Done.

Admin Provisioning FAQ

  • Admins can only have one location role and one company role using SCIM.

    • Location roles:

      • Location admin

      • Front desk admin

      • Deliveries

      • Security admin

    • Company roles:

      • Global admin

      • Billing admin

  • Envoy will give admins the higher role assigned. For example, If a user is in multiple groups in Azure and each group is mapped to two different location roles (Front Desk Admin and Location Admin), then the admin will be assigned the Location Admin role.

  • If you already have manual entries in the directory and sync with a SCIM, this will take over and delete the manual entries.

  • Synced roles will take priority over manual only if the synced role has higher priority permissions. If you have a front desk admin role (manual) and you are SCIM mapped to the security admin role, you will still have a manual front desk admin role for that location.

  • If you disconnect Azure, your roles will turn into manual roles and will stop syncing. Your mappings won't be saved and you will start from scratch the next time you sync with a SCIM.

  • You cannot manually delete synced roles. You must remove that person from the Azure group first.

  • If you are not seeing the roles you are looking for, be sure to check the filters at the top of the page.


Users are not being synced into all Envoy locations or users are missing custom attributes

If your Azure users are not syncing into all locations as they should, try manually re-provisioning your users. Please note the order is important.

  1. Unassign the users and groups from the Envoy app within Azure.

  2. Go to the Envoy Dashboard > Employee directory > Sync Settings

  3. Regenerate the token.

  4. Go back to the Envoy app in Azure > Provisioning > Enter and enter the token in Admin Credentials

  5. Test the token and make sure you get a success message.

  6. Reassign the users and groups.

This should kick-start the provisioning of users and any new attributes assigned.

Did this answer your question?