Thank you for participating in the StarLeaf Azure Active Directory integration beta program.

On this page:

Organizations that use Azure Active Directory (Azure AD) for user management can integrate that with their StarLeaf account. Azure AD integration is an additional option on your StarLeaf account.


  • Push new users from Azure AD to StarLeaf
  • Push user updates from Azure AD to StarLeaf
  • Push user deactivation from Azure AD to StarLeaf

Pre-requisites for beta trialing

StarLeaf will create a trial organization for you to use for the purposes of beta trialing the Azure AD integration.

We also encourage you to sign up to a free Azure AD account. This is to ensure that the beta program does not disrupt your production environment while allowing you to explore and exercise the features made available to you to their full extent. To get your free trial account, go to

We will have a short preliminary call with you to discuss your deployment before you begin the trial.

Azure AD integration is in beta development and is still undergoing testing. We strongly discourage the deployment of this in your production environment. StarLeaf will not be liable for any loss, either direct or indirect, suffered as a result of deploying this feature in your production environment and services.

How to set up the integration

Before you can configure StarLeaf provisioning in Azure AD, you need to know the Tenant URL and Secret Token. We will tell you what these are during our short preliminary call.

  1. Log in to the Azure portal .
  2. Go to Azure Active Directory > Enterprise applications > Add an application -> Non-gallery application.
  3. Give the application a name and choose Add.
  4. In the new application:
    1. Choose Provisioning and change the Provisioning Mode to Automatic.
    2. Enter the Tenant URL and Secret Token.
    3. Choose Test Connection and this confirms that you have used the correct credentials.
    4. Choose Save.
  5. Configure Mappings so that the table looks like this:
    Azure AD attributeCustomapp attributematching precedence
      Compulsory attributes
    userPrincipalNameemails[type eq “work”].value
    The following attributes are dependent on your AD configuration, but will include some of:
    mobilephoneNumbers[type eq “mobile”]
    telephoneNumberphoneNumbers[type eq “work”]

    Save the attribute mappings and Azure will synchronize the users to the Portal. This may take a few minutes depending on how many users there are.

How do I report an issue or send feedback?

Please email with any feedback you might have.