Managing external identities to enable secure access for partners, customers, and other non-employees
Is a Graph-created multi-valued directory extension a supported claim source in an External ID (external) tenant?
I'm building a partner portal on Microsoft Entra External ID (external tenant) and I'd like to check whether something we rely on is supported or just happens to work.
Each user has a multi-valued directory extension attribute: a String collection created through Microsoft Graph (POST /applications/{id}/extensionProperties with isMultiValued: true, target object User). A claims mapping policy assigned to the app's service principal emits it in the ID token:
{
"ClaimsMappingPolicy": {
"Version": 1,
"IncludeBasicClaimSet": "true",
"ClaimsSchema": [
{ "Source": "user", "ExtensionID": "extension_<appId>_partnerAssignments", "JwtClaimType": "partnerAssignments" }
]
}
}
In my tests this works. One value arrives as a string, two or more as a JSON array, and I tested up to 100 values on one user.
What worries me is the claims customization reference (identity-platform/reference-claims-customization, "Claim schema entry elements"): "The only available multi-valued claim sources on a user object are multi-valued extension attributes that have been synced from Active Directory Connect." My attribute isn't synced from on-premises, and as far as I can tell Connect sync isn't available in external tenants at all.
So my first question is whether a Graph-created multi-valued extension attribute is a supported claim source in an external tenant, or whether the array I'm getting is undocumented behavior that could change.
The second thing I noticed: after the attribute is changed with PATCH /users/{id}, a new sign-in keeps getting the old values in the ID token for about five minutes. That happens even after revokeSignInSessions and a full interactive sign-in, while a Graph read already returns the new values. I'd like to know whether that delay is expected and whether anything shortens it.
Thanks!