Hello Team, In entra account created Azure team confirms, All attributes are populating. But Sailpoint not showing up in the source accounts. I checked provisioning plan its creating the accounts adding all mandatory attributes but while running the aggregation account not showed up in Sailpoint. A…

Hi @ravikumar7284 If I read your requirement correctly, the first thing to say, is that your Entra admins are using a sub-optimal naming convention for UPN and that should be changed. However, looking at your data, perhaps the Display Name offers what you are after? ie startswith(displayName,'ADM…

Hi @ravikumar7284 Your filter isn’t syntactically correct, you need to bracket the NOT clauses. Try (startsWith(userPrincipalName,‘ADM’) AND NOT(startsWith(userPrincipalName,‘ADM.’)) …etc. Also alway good to check filter syntax using a Graph API explorer.

To create a privileged account,. Please contact your Entra team and ask them to create the appropriate privileged group. Also, I noticed that the account in the target system does not have the entitlement that was assigned through SailPoint. Once the Entra team creates the privileged group, you can…

Hello Ravi, The part I would check here is the third filter clause: NOT startsWith(userPrincipalName,'admin') The UPN for this account is: ADMIndrajithSaseendran1@ChubbGlobal.onmicrosoft.com The first five characters are ADMIn, which effectively forms admin when compared without case sensitivity.…

Hi @punna0001 Thank you for your response, Can you please suggest the correct filter.

Hi Harish, I removed NOT startsWith(userPrincipalName,‘admin’) this condition in the filter, I am able to aggregate that filter. However few more accounts also aggregated that starts with admin123, admin_tets also. How to exclude that UPN starts with admin accounts.

Hi @ravikumar7284 , The filter in aggregation, how it will work is, whatever accounts satisfying this criteria they will be filtered out, that means they will not come to Sailpoint, so according to your filter, basically you are filtering out users whose userprincipalname starts with ADM, I suspect…

[image] Ravikumar Kuruba: (startsWith(userPrincipalName,‘ADM’) AND NOT startsWith(userPrincipalName,‘ADM.’) AND NOT startsWith(userPrincipalName,‘admin’)) Hey Ravi, glad we were able to narrow down the root cause here. It’s the case-insensitive behavior of startsWith in the Microsoft Graph AP…

Hi Harish, Thank you for your time, Please let me know if you find any solution for this.

Hi Jerry, I tried the following filter: (startsWith(displayName,‘ADM’) AND NOT startsWith(displayName,‘ADM.’) AND NOT startsWith(displayName,‘admin’)) ADMIndrajith was successfully aggregated into ISC. Accounts such as admin123 and admin_test were excluded from aggregation. Thank you for your …

Account created in Entra but aggregating into SailPoint IC

Identity Security Cloud (ISC) ISC Discussion and Questions

YanCoelho (Yan Coelho) June 29, 2026, 7:56pm 4

Hello,
Please check this extension this will help the debug:

SailPoint SaaS Connectivity Extension for Visual Studio Code - Identity Security Cloud (ISC) / ISC Community Knowledge Base - SailPoint Developer Community

Topic		Replies	Views
Issue with User Filtering in Microsoft Entra with Multiple Sources ISC Discussion and Questions aggregation , identity-security-cloud , connectors	13	396	March 26, 2025
Account filter under SAP source modification ISC Discussion and Questions identity-security-cloud	12	194	January 29, 2025
Azure accounts are not being aggregated in sailpoint IIQ Discussion and Questions aggregation , identityiq	5	160	July 4, 2024
Entitlement aggregation is not successful for AD integrated Application ISC Discussion and Questions	1	1663	December 14, 2021
Entitlement Aggregation ISC Discussion and Questions aggregation , identity-security-cloud , entitlements	2	175	February 19, 2025

Account created in Entra but aggregating into SailPoint IC

Related topics