How does Azure work with Envoy?
The Azure Active Directory 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.
Important Note: Azure is available on Microsoft GCC High (Government Community Cloud) accounts and GCC High is compatible with our Azure directory integration.
Step One: Azure AD account and employees setup
Make sure you have you Azure account created and you have added your employees to your account. Create groups as needed in Azure and assign users to those groups.
You’ll need to have admin privileges to complete this installation. Either become an admin or ask your admin for help before completing these steps.
Step Two: Enable Envoy + Azure AD
On the Envoy dashboard, go to your Apps page.
Under Directory and SSO click on Directory Settings.
Click Install under Microsoft Azure AD.
Choose from one of the following options for syncing employees to your directory and click Save:
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.
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).
Copy the OAuth Bearer Token from Envoy and note to be entered into Azure later.
Step Three: Configure Azure AD settings
Open the Azure portal and select Azure Active Directory > Enterprise applications > New application > Add from the gallery > search for Envoy and select Add.
Open the Provisioning tab and set Provisioning Mode as Automatic.
Copy Envoy’s SCIM endpoint
https://app.envoy.com/scim/v2into the Tenant URL field.
Paste the OAuth Bearer Token copied from the Envoy Dashboard.
Click on Test Connection, once successful, click Save.
Click on Users and groups on the left hand side and then assign users or groups to the application. **Azure does not support nested groups for SCIM provisioning.
Once users are assigned, click on Provisioning on the left hand side and scroll down to the bottom and turn Provisioning Status On.
(Optional) To test provisioning on a single user, utilize the Provision on demand feature in Azure.
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.
Navigate to the Envoy Enterprise App > Provisioning > Mapping and click on Provision Azure Active Directory Users.
Find and delete
telephoneNumberfrom the mapping list.
mobileand click onto it so it brings up the editing pane.
Change the mapping to
phoneNumbers[type eq "work"].value.
Configuring Single Sign On
In the Envoy dashboard go to Apps > Directory and SSO and click Directory settings and then click Install on the SAML integration.
In the Azure portal, on the Envoy application page, select Single sign-on.
On the Select a Single sign-on method dialog, select SAML to enable single sign-on.
On the Set up Single Sign-On with SAML page, click the edit icon to open the Basic SAML Configuration dialog.
On the Basic SAML Configuration section, enter the following URLs:
Once all URL’s are entered correctly, hit “Save”.
In the SAML Signing Certificate section, click the edit icon to open SAML Signing Certificate dialog.
In the SAML Signing Certificate section, copy the Thumbprint and save it on your computer.
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”.
Login to your Envoy dashboard and go to your Apps page and “Install” SAML.
Take the Thumbprint from step 3 in Azure of the setup and enter that value into the Fingerprint field provided in Envoy.
Paste the Login URL value, which you have copied from the Azure portal into the IDENTITY PROVIDER HTTP SAML URL text box.
Choose whether you want SAML Required and toggle ON if needed, then Save.
Envoy makes it easy for our customers on Visitors Enterprise and Workplace Premium Plus to automatically provision their admin users from Okta using Azure.
Create groups as needed in Azure and assign users to those groups.
Assign the group to the Envoy app
Navigate to Home → Enterprise applications → select Envoy app
Click `Add user/group`
Click the `None Selected` link under Users and groups
Search for your group and select it
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)
Navigate to Home → Enterprise applications → select Envoy app
Click provision on demand
Search for and select your group, select the members you’d like to be included, then click the Provision button
Here’s additional information on how to create groups in Azure AD.
Sync your directory with Envoy. You can follow these instructions, if you have not already set up your integration with Envoy.
After you've configured Azure with Envoy, navigate to Employee directory > Admin roles.
Click on Sync Settings at the top of the page.
Under Sync admins, select the group you want to assign roles to.
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.)
Click Add > Done.
Admin Provisioning FAQ
Admins can only have one location role and one company role using SCIM.
Front desk 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.