Connecting Microsoft Entra ID
Last Modified: 2026-11-19

Connecting Microsoft Entra ID

This connector links RSA Agent ID to Microsoft Entra ID through the Microsoft Graph API. It reads service principals, app registrations, permission grants, directory roles, users, and devices to surface AI agents, automation frameworks, and third-party integrations registered in your tenant.

The connector reads directory and credential metadata, never credential values—only key IDs, expiry dates, and federated issuer/subject fields. Owners and federated credentials are resolved only for service principals your tenant owns; third-party multi-tenant apps are not walked.

RSA Agent ID combines this connector with other data sources to build device- and process-level visibility; it is not an authoritative agent registry on its own.

Running processes and software inventory from Microsoft Defender are collected by the separate Microsoft Defender connector. For more information, see Connecting Microsoft Defender.

Before you begin 

Ensure you have the following:

Type

Requirement

Purpose

RolesApplication Developer role or higherTo register the application
Global Administrator or Privileged Role Administrator

To grant admin consent

No license tier substitutes for this role.

LicensesMicrosoft Entra ID Free, included with every Microsoft 365 and Azure tenantFor directory and application data
For Microsoft Graph, no license is required. Graph has no SKU and no per-call charge; directory reads are included in the tenant's existing subscription.For Microsoft Graph

Required Permissions

Note that both permissions are required together, with tenant-wide admin consent.

Permission

Type

Purpose
Application.Read.AllApplication

Service principals, app registrations, app-role assignments, owners, and federated identity credentials

Directory.Read.AllApplication

Delegated permission grants (oauth2PermissionGrants), users, devices, and directory role membership

Adding a permission is not the same as consenting to it. Without admin consent, the connector can still authenticate, but Test Connection shows Limited access and scans cannot read the affected directory data. Application.Read.All and Directory.Read.All are both required together—federatedIdentityCredentials does not accept Directory.Read.All, and oauth2PermissionGrants does not accept Application.Read.All.

Microsoft-side Setup (Entra Admin Center)

Procedure 

  1. Sign in to entra.microsoft.com and go to Entra ID > App registrations > New registration.

    You can also sign in through the Azure portal, under Microsoft Entra ID. If your account has access to multiple tenants, select the Settings icon in the top bar and switch to the tenant you want to scan.

  2. Enter a name (for example agent-discovery-api-app), select Accounts in this organizational directory only (single tenant), leave Redirect URI empty, and click Register.
  3. From the application's Overview page, copy the Application (client) ID and Directory (tenant) ID.
  4. Go to API permissions > Add a permission > Microsoft Graph > Application permissions, and add both Application.Read.All and Directory.Read.All.
  5. Click Grant admin consent for <tenant>, confirm, then verify both permissions show Granted for <tenant>. Delete the automatically added User.Read delegated permission.
  6. Go to Certificates & secrets > Client secrets > New client secret, set an expiration per policy, and copy the generated secret Value immediately (not the Secret ID). The Value is shown once. After you leave the page, it is masked permanently and you must create a new secret.
  7. Note the secret's expiration date. The connector stops working when the secret expires, so rotate it before that date.

Alternative: Certificate instead of Client Secret

RSA Agent ID can generate the certificate, so no shared secret is exchanged. Follow the below steps:

  1. In the connector form, enter the Display Name, Tenant ID, and Client ID.

  2. Select Certificate, then click Generate Certificate and download the public certificate.

    Download the public certificate before leaving the screen. It can be downloaded only once; if it is lost, you must delete the connector and start over.

  3. In Entra ID, go to Certificates & secrets > Certificates > Upload certificate.

    Upload the file downloaded in Step 2.

  4. Return to the connector form and click Confirm.

The private key stays encrypted in RSA Agent ID and is never displayed or exported.

The certificate expires two years after it is generated and is not renewed automatically. Record the expiry date. Similar to an expired secret, an expired certificate stops the connector from working.

Agent ID Setup

Procedure 

  1. On the Connectors page, click Add source, then click Connect on the Microsoft Entra ID card.

  2. Enter a Connection name, the Tenant ID, and the Client ID (application ID).
  3. Select Secret or Certificate in Authentication Method, and enter the Client secret or generate/upload a certificate.
  4. Click Test connection, confirm it succeeds, then click Save and start discovery.

    A certificate connection can only be verified after the certificate is generated and uploaded.

A successful Test Connection confirms the credential and Application.Read.All, but not Directory.Read.All; if that second permission is missing, the test can still pass while the affected data stays empty after the first scan.

Limited access means permissions or admin consent are incomplete. If admin consent was never granted, or either permission is missing, Test Connection still connects and shows a Limited access status, and the connector can still be saved. Scans from a connector in this state come back with missing data. Add any missing permission in Entra ID, grant admin consent, and run Test Connection again until both permissions appear in the list before relying on the scan results.

Troubleshooting

  • Test Connection shows "Connection failed — please verify the connector details"

    Incorrect tenant ID, client ID or secret, expired secret, or Secret ID pasted instead of Value. Re-check the Overview page, create a new secret, and copy the Value.

  • Authorization_RequestDenied

    Grant admin consent for both permissions.

  • No delegated permission grants found/Owners appear with blank names.

    Add/consent Directory.Read.All and rescan.

  • No federated credentials found.

    Add/consent Application.Read.All and rescan.

  • Grant admin consent is unavailable.

    Use a Global Administrator or Privileged Role Administrator account.

  • Connector worked, then stopped.

    Client secret or certificate expired. Create a new secret or certificate and update the connector.

  • Certificate lost before it was uploaded to Entra ID.

    The certificate can be downloaded only once, on the screen where it is generated. Delete the pending connector and add it again to generate a new certificate.

  • Some directory roles are absent.

    Expected. Graph returns activated roles only; inactive roles have no members.