Check AzureAD Identity Mapping Rule - Low Mapping Rate (0.01%)

Summary

The AzureAD identity mapping percentage is critically low at 0.01% (1 mapped out of 15,841 staged records). This was identified during the daily health check.

Current State

• Staging_AD (AzureAD): 15,841 records
• IdentityMap (AzureAD): 1 mapped record
• Mapping Rate: 0.01% (expected range: 45%-75%)

Investigation Needed

1. Review the AzureAD identity mapping rule configuration
2. Check if the mapping rule criteria are too restrictive
3. Verify the data quality in Staging_AD for AzureAD records
4. Compare with other domain mapping rates for reference:

• AD_KC: 99.31% (6,054/6,096)
• AD_apac: 69.05% (406/588)
• AD_JA: 65.53% (211/322)
• AD_EU: 56.21% (1,240/2,206)
• AD: 40.89% (3,142/7,684)

Possible Causes

• Identity mapping rule may be misconfigured for AzureAD/Entra ID
• Different attribute format between AzureAD staging and Profile table
• Missing or incorrect join keys (e.g., UPN, ObjectGUID, EmployeeID)
• Cleanup job may have removed mappings incorrectly

Action Items

• [ ] Review mapping_target configuration for AzureAD target
• [ ] Check identity mapping SQL/stored procedure logic
• [ ] Validate sample AzureAD staged records against Profile table
• [ ] Determine if this is a data issue or configuration issue

Health Check Output

AD : 7684 staged, 3142 mapped (40.89%)
AD_apac : 588 staged, 406 mapped (69.05%)
AD_CA : 332 staged, 66 mapped (19.88%)
AD_EU : 2206 staged, 1240 mapped (56.21%)
AD_JA : 322 staged, 211 mapped (65.53%)
AD_KC : 6096 staged, 6054 mapped (99.31%)
AD_KO : 159 staged, 43 mapped (27.04%)
AzureAD : 15841 staged, 1 mapped (0.01%)  <-- ISSUE

🤖 Generated with Claude Code