Tutorial: Configure Fuze for automatic user provisioning

The objective of this tutorial is to demonstrate the steps to be performed in Fuze and Azure Active Directory (Azure AD) to configure Azure AD to automatically provision and de-provision users and/or groups to Fuze. For important details on what this service does, how it works, and frequently asked questions, see Automate user provisioning and deprovisioning to SaaS applications with Azure Active Directory.

Capabilities supported

  • Create users in Fuze
  • Remove users in Fuze when they do not require access anymore
  • Keep user attributes synchronized between Azure AD and Fuze
  • Single sign-on to Fuze (recommended)


The scenario outlined in this tutorial assumes that you already have the following prerequisites:

  • An Azure AD tenant.
  • A user account in Azure AD with permission to configure provisioning (e.g. Application Administrator, Cloud Application administrator, Application Owner, or Global Administrator).
  • A Fuze tenant.
  • A user account in Fuze with Admin permissions.

Step 1. Plan your provisioning deployment

  1. Learn about how the provisioning service works.
  2. Determine who will be in scope for provisioning.
  3. Determine what data to map between Azure AD and Fuze.

Step 2. Configure Fuze to support provisioning with Azure AD

Before configuring Fuze for automatic user provisioning with Azure AD, you will need to enable SCIM provisioning on Fuze.

  1. Start by contacting your Fuze representative for the following required information:

    • List of Fuze Product SKUs currently in use at your company.
    • List of location codes for your company‚Äôs locations.
    • List of department codes for your company.
  2. You can find these SKUs and codes in your Fuze contract and configuration documents, or by contacting your Fuze representative.

  3. Once the requirements are received, your Fuze representative will provide you with the Fuze authentication token that is required to enable the integration. This value will be entered in the Secret Token field in the Provisioning tab of your Fuze application in the Azure portal.

Add Fuze from the Azure AD application gallery to start managing provisioning to Fuze. If you have previously setup Fuze for SSO you can use the same application. However it is recommended that you create a separate app when testing out the integration initially. Learn more about adding an application from the gallery here.

Step 4. Define who will be in scope for provisioning

The Azure AD provisioning service allows you to scope who will be provisioned based on assignment to the application and or based on attributes of the user / group. If you choose to scope who will be provisioned to your app based on assignment, you can use the following steps to assign users and groups to the application. If you choose to scope who will be provisioned based solely on attributes of the user or group, you can use a scoping filter as described here.

  • Start small. Test with a small set of users and groups before rolling out to everyone. When scope for provisioning is set to assigned users and groups, you can control this by assigning one or two users or groups to the app. When scope is set to all users and groups, you can specify an attribute based scoping filter.

  • If you need additional roles, you can update the application manifest to add new roles.

Step 5. Configuring automatic user provisioning to Fuze

This section guides you through the steps to configure the Azure AD provisioning service to create, update, and disable users and/or groups in Fuze based on user and/or group assignments in Azure AD.

To configure automatic user provisioning for Fuze in Azure AD:

  1. Sign in to the Azure portal. Select Enterprise Applications, then select All applications.

    Enterprise applications blade

  2. In the applications list, select Fuze.

    The Fuze link in the Applications list

  3. Select the Provisioning tab.

    Screenshot of the Manage options with the Provisioning option called out.

  4. Set the Provisioning Mode to Automatic.

    Screenshot of the Provisioning Mode dropdown list with the Automatic option called out.

  5. Under the Admin Credentials section, input the SCIM 2.0 base url and SCIM Authentication Token value retrieved earlier from the Fuze representative in Tenant URL and Secret Token. Click Test Connection to ensure Azure AD can connect to Fuze. If the connection fails, ensure your Fuze account has Admin permissions and try again.

    Tenant URL Token

  6. In the Notification Email field, enter the email address of a person or group who should receive the provisioning error notifications and check the checkbox - Send an email notification when a failure occurs.

    Notification Email

  7. Click Save.

  8. Under the Mappings section, select Synchronize Azure Active Directory Users to Fuze.

  9. Review the user attributes that are synchronized from Azure AD to Fuze in the Attribute Mapping section. The attributes selected as Matching properties are used to match the user accounts in Fuze for update operations. Select the Save button to commit any changes.

    Attribute Type
    userName String
    name.givenName String
    name.familyName String
    emails[type eq "work"].value String
    active Boolean
  10. To configure scoping filters, refer to the following instructions provided in the Scoping filter tutorial.

  11. To enable the Azure AD provisioning service for Fuze, change the Provisioning Status to On in the Settings section.

    Provisioning Status Toggled On

  12. Define the users and/or groups that you would like to provision to Fuze by choosing the desired values in Scope in the Settings section.

    Provisioning Scope

  13. When you are ready to provision, click Save.

    Saving Provisioning Configuration

This operation starts the initial synchronization of all users and/or groups defined in Scope in the Settings section. The initial sync takes longer to perform than subsequent syncs, which occur approximately every 40 minutes as long as the Azure AD provisioning service is running.

Step 6. Monitor your deployment

Once you've configured provisioning, use the following resources to monitor your deployment:

  1. Use the provisioning logs to determine which users have been provisioned successfully or unsuccessfully
  2. Check the progress bar to see the status of the provisioning cycle and how close it is to completion
  3. If the provisioning configuration seems to be in an unhealthy state, the application will go into quarantine. Learn more about quarantine states here.

Connector limitations

  • Fuze supports custom SCIM attributes called Entitlements. These attributes are only able to be created and not updated.
  • The Fuze SCIM API does not support filtering on the userName attribute. As a result, you may see failures in the logs when trying to sync an existing user who does not have a userName attribute but exists with an email that matches the userPrincipalName in Azure AD.

Change log

  • 06/15/2020 - Rate Limit of integration adjusted to 10 requests/second.

Additional resources

Next steps