Step-by-step deployment guide
The Microsoft Entra PIM for Azure resources connector for Elimity Insights fetches Privileged Identity Management data for Azure role-based access control (Azure RBAC).
Microsoft Entra PIM for Azure resources
The Microsoft Entra PIM for Azure resources connector for Elimity Insights fetches Privileged Identity Management data for Azure roles — Azure role definitions, active role assignments, and eligible (not-yet-activated) role assignments, together with the management group, subscription, resource group or resource they apply to — so you can keep control over privileged access to your Azure resources. Follow the instructions below to set up the connector.
1. Which data is imported
The following entity types are imported:
Principals — the users, groups, and service principals that hold or are eligible for an Azure role
Roles — Azure role definitions, built-in and custom (e.g. Owner, Contributor, Reader)
Role Assignment Schedule Instances — active PIM role assignments (permanently assigned or currently activated)
Role Eligibility Schedule Instances — eligible (not-yet-activated) PIM role assignments
Rather than linking principals to roles directly, each PIM grant is modelled as its own entity (the schedule instance). A single principal-role pair can carry state a plain link can't hold — the scope it applies to, its start/end window, how it was granted (direct, inherited, or via a group), and whether it's active or merely eligible. Each instance sits between a Principal and a Role and carries that context as attributes, letting Elimity model just-in-time and time-bound access as a standard identity graph.
Attributes imported per entity type:
Principal — Email, Type (User, Group, ServicePrincipal, ForeignGroup, or Device)
Role — Description, Type (BuiltInRole or CustomRole)
Role Assignment Schedule Instance — Principal, Role, Assignment type (Assigned or Activated), Type, Member type (Direct/Inherited/Group), Condition, Scope ID, Scope name, Scope type (tenant / managementgroup / subscription / resourcegroup / resource), Start time, End time, Status
Role Eligibility Schedule Instance — the same attributes, except Assignment type
Schedule instances are imported for every scope in your tenant: the root scope (/), the root management group and every management group, subscription, resource group and resource below it. The Azure resources themselves are not imported as entities: each schedule instance carries the scope it applies to in its Scope ID, Scope name and Scope type attributes.
2. Creating a dedicated app registration in Entra ID
As usual we recommend creating a dedicated account for this connector. Follow the steps below to set up a new app registration in Entra ID:
In Azure, open your tenant's app registrations by typing 'app registrations' in the global search bar and clicking the App registrations service.
Click the New registration button.
Choose a name for this registration (e.g.
elimity-insights-pim-azure-resources).Leave the defaults for 'Supported account types' and 'Redirect URI' and click Register.
Note down both the client identifier and the tenant identifier for this new app registration.
3. Generating credentials for the new app registration
The connector authenticates as the app registration using a client secret. Click Certificates & secrets in the menu on the left and add a new client secret. Immediately note down the value of your new secret (Entra shows it only once). Note the secret's expiry date: imports fail once it expires, so plan to rotate it.
4. Granting read access to the root management group
Grant the app registration read access to your tenant's root management group:
Temporarily elevate your Global Administrator access to manage the root management group (refer to the official documentation for detailed instructions).
Open the overview of your tenant's management groups by typing 'management groups' in the global search bar and clicking the Management groups service.
Click the Tenant Root Group and then click Access control (IAM) in the side navigation menu.
Click Add in the top-left corner of the main content panel, and select Add role assignment.
Select the Reader role and click Next.
Click Select members, search for your newly created app registration, select it and click Next again.
Click Review + assign.
Remove your elevated Global Administrator access again.
The connector always reads from the tenant root management group (its identifier equals your tenant identifier); a Reader assignment on a lower management group or subscription is not enough.
5. Creating a source in Elimity Insights
Go to Sources in the left navigation bar and click Add Source.
Search for Custom and click Set Up.
Click Set Up again and give the source a name (e.g.
Microsoft Entra PIM for Azure resources).Select Upload export file, click Continue, and upload the data model file:
data-model-export.json.Open the Config tab and click Edit.
Set Enable automatic imports via custom gateway to
trueand fill in the Gateway URL:https://microsoft-entra-pim-gateway-75801044224.europe-west1.run.app.Click Add configuration value and add the entries below. Keys are case-sensitive.
Click Save and run to launch your first import. The Imports tab shows the summary for each run.
Tenant ID
tenantId
Tenant identifier you noted down in step 2.
Client ID
clientId
Client identifier you noted down in step 2.
Client secret
clientSecret
Client secret value you noted down in step 3 (store as a password).

