Activity Insights – Microsoft Entra ID Connector: No Activity Data After 24+ Hours

Hello SailPoint Community,

I’m currently configuring the Activity Insights – Microsoft Entra ID connector in SailPoint ISC and wanted to understand how the integration works and where the activity data should appear.

Our current setup is:

  • We have an existing VA-based Azure Active Directory connector that is aggregating accounts and entitlements successfully.

  • We created a separate Activity Insights – Microsoft Entra ID connector.

  • The Identity Governance Source Name is configured to match the existing Azure AD source.

  • The Activity Insights connector’s Test Connection is successful.

  • We performed an account aggregation on the existing Azure AD governance source.

  • It has been more than 24 hours since the configuration and aggregation, but we haven’t been able to see any Activity Insights data.

I also attempted an account aggregation directly on the Activity Insights connector, but received the following error:

unsupported command: std:account:list

I understand that this connector may not support standard account aggregation and is intended to collect activity data associated with the existing governance source.

I have a few questions:

  1. Is there any additional configuration required to enable activity collection after connecting the Activity Insights source?

  2. Where exactly should the collected activity data appear in the ISC interface? Is there a specific page or view where we can verify that the integration is working?

  3. Is account aggregation on the existing governance source sufficient to initiate activity collection, or is another process required?

  4. Does Activity Insights require any additional tenant-level licensing or feature enablement beyond configuring the connector?

  5. Has anyone successfully implemented this with the VA-based Azure AD connector? If so, could you share how the activity information appears in the tenant, preferably with screenshots?

Any guidance or examples would be greatly appreciated.

Thank you!

Hi Mayur Suresh,

what you’re seeing is expected, and the most likely culprit is account correlation on the governance source.

About the std:account:list error

You’re right. The Activity Insights source isn’t an account source. Per my understanding, account data is gathered by correlating accounts and running an aggregation on the Entra ID (VA-based) source, and activity data then starts syncing and can typically take up to 24 hours to display, updating daily after that. So aggregating the Activity Insights source directly will therefore fail.

  1. Is more configuration needed after connecting?

Nothing beyond the connector setup, but the docs call for accounts on the Entra ID source to be correlated to identities. If your Azure AD accounts aren’t correlated to identities, there’s nothing to attach activity to. That’s where I’d look first. Also confirm that the Identity Governance Source Name exactly matches your VA source. A mismatch fails the test connection, so yours is probably fine.

  1. Where does the data appear?

There isn’t a dedicated Activity Insights page. The data surfaces inside other features:

Access History, where you can see how many times an identity logged in to an application compared with the company average.
Access Modeling, which shows the percentage of identities that engaged with an entitlement’s source over the past 90 days.
Access Requests, which shows activity data for the related sources.
Certifications, which shows the number of days an identity was active in a 90-day period.

worth trying to open an identity you know signed in to Entra recently and look at its Access History. Make sure that identity has a correlated Entra account.

  1. Is aggregating the governance source enough?

Yes, once accounts are correlated, no other process is required as per my knowledge. Activity should begin syncing immediately but can take up to 24 hours to show as I said. Since you’re past that, I’d verify correlation (and that the test identity actually signed in recently) before suspecting anything else.

  1. Licensing or feature enablement?

There are two things:

Microsoft side: All grant types need a Microsoft Entra ID P1 or P2 license for sign-in logs. Without it, the sign in log call returns a 403 even when AuditLog.Read.All is granted. In Your case test connection probes this, and yours passed, so this looks fine.

SailPoint side: The isn’t any tenant toggle. They do tell you to contact your Customer Success Manager about the Activity Insights feature. If correlation checks out and there’s still no data, then only way is SailPoint Support to confirm the feature is entitled on your tenant.

Suggested next steps:
Confirm your Azure AD accounts are correlated to identities.
Pick a test identity that signed in to Entra in the last few days and check its Access History.
Check that the app registration still has admin consent for AuditLog.Read.All, User.Read.All, Application.Read.All and a license read permission.
If all of that is fine, open a SailPoint Support case with both source names and a sample identity.

Thank you.

Hello Mayur. Bhagat is right about correlation. Your VA-based Azure AD source with a separate Activity Insights source is a supported configuration. The unsupported command: std:account:list error is expected. Activity Insights does not support account aggregation. Keep aggregation and correlation on your existing Azure AD source.

Your successful Test Connection validates the documented Graph checks, including /auditLogs/signIns?$top=1, Entra P1/P2 licensing, and the Identity Governance Source Name match. However, it does not confirm activity ingestion or SailPoint feature entitlement. Since more than 24 hours have passed, I would check:

  1. Tenant entitlement: Confirm Activity Insights is included in your tenant’s subscription tier. SailPoint lists it under Human Fabric Business and Business Plus (licensing).
  2. Correlation: Verify that a recently active Entra account is correlated to an ISC identity, not just aggregated.
  3. Sign-in records: Using the same app credentials, query Microsoft Graph /auditLogs/signIns with a recent createdDateTime range and the user’s userId or userPrincipalName. Confirm records exist.

To check activity, go to Admin > Identity Management > Access History, select the identity, and choose View Activity. If Access History is inaccessible, check permissions. SailPoint recommends Report Admin access. Activity also appears in Access Modeling, Access Requests, and Certifications. The official overview includes screenshots.

No separate workflow or Activity Insights aggregation is required. SailPoint documents automatic synchronization, up to 24 hours for initial display, and daily updates afterward. If these checks pass but activity is still missing, I would raise a SailPoint Support case with both source IDs, a correlated identity, and a recent sign-in timestamp. Ask them to verify backend ingestion.

Could you confirm whether View Activity is available and Graph returns sign-ins for the same user?