You are viewing an earlier version of the admin guide. For the latest version, please visit EmpowerID Admin Guide v7.211.0.0.

Connect Azure License Manager to Azure AD

After setting up Azure and publishing the EmpowerID Azure AD SCIM microservice to your Azure tenant, you need to connect EmpowerID to the tenant to bring the user and group information in that tenant into EmpowerID, where it can be managed and synchronized with data in any connected back-end user directories.

Step 1 – Create an account store for Azure AD

  1. On the navbar, expand Azure License Manager and select Configuration.

  2. Select the Tenants tab and click the Add button on the Tenant grid header.

     

  3. Enter the following information in the Tenant form that appears:

    • Account Store Name – Name of your tenant

    • Azure App Service URL – URL for the SCIM app service you created in Azure

    • Azure Application (Client) ID – Client ID of the service principal application you registered in Azure for EmpowerID

    • Azure Directory (Tenant) ID – Your Tenant ID

    • Azure App Certificate Thumbprint – Thumbprint of the certificate you uploaded to Azure for the service principal application

       

  4. Click Save.

EmpowerID creates the Azure AD account store and the associated resource system. The next step is to verify the resource system parameters match your tenant information.

Step 2 – Verify Resource System Parameters

  1. On the navbar, expand Admin > Applications and Directories and select Account Stores and Systems.

  2. On the Find Account Store page, select the Account Stores tab and search for the Azure AD account store you just created.

  3. Click the Account Store link for the account store.


    This directs you to the Account Store and Resource System page for the account store. This page contains several tabs related to the account store that you can access to view and manage the account store and resource system.

     

  4. Select the Resource System tab and then expand the Configuration Parameters accordion on the page.

  5. Verify the following parameters are correct for your system:



  6. To edit the value of a parameter, click the Edit button for the parameter you want to edit.

     

  7. Enter the new value in the Value field and click Save.

  8. Repeat as needed.

Now that the Configuration Parameters have been updated, the next step is the configure Attribute Flow.

Step 3 – Configure Attribute Flow

Now that the attribute flow has been set, the next steps include configuring the account store and enabling EmpowerID to inventory it.

Step 4 – Configure Account Store Settings

  1. On the Account Store Details page, select the Account Store tab and then click the Edit link to put the account store in edit mode.


    This opens the edit page for the account store. This page allows you to specify how you want EmpowerID to handle the user information it discovers in your Azure tenant during inventory. Settings that are relevant to the account store are described in the table below the image.




  2. Edit the account store as needed and then click Save to save your changes.

Step 5 – Enable the Account Inbox Permanent Workflow

  1. On the navbar, expand Infrastructure Admin > EmpowerID Server and Settings and select Permanent Workflows.

  2. On the Permanent Workflows page, click the Display Name link for Account Inbox.

     

  3. On the Permanent Workflow Details page that appears, click the pencil icon to put the workflow in edit mode.

     

     

  4. Check Enabled.

     

  5. Click Save to save your changes.

Step 6 – Enable Inventory on the Account Store

  1. Return to the Account Store Details page for the account store.

  2. Click the Edit link to put the account store in edit mode.

     

  3. Select the Inventory tab and check Inventory Enabled.

     

  4. Click Save.

Now that the Account Inbox Permanent workflow is turned on and inventory for the account store is enabled you can monitor the inventory of users and groups from the Users and Groups tabs of the Account Store Details page.

 

 

IN THIS ARTICLE

 

Â