Unverified50% confidenceFactExact time
The choice of Name ID format (such as unspecified, UPN, email address) directly affects how the service provider identifies the user; if the format the SP expects differs from what AD FS sends, login will fail.
1
Sources
50%
Confidence
Long-term
Relevance
11/4/2026
First Seen
Sources
Related Entities
Related Claims
UnverifiedDuring reconciliation, the unique user identifier should use the IdP-side id as the primary key rather than userName or email, because the latter may change due to rename operations.70% similarUnverifiedIdentity propagation means the caller's identity information is carried intact across the service-to-service call chain rather than being dropped at some hop or replaced with the service's own identity; if the identity is lost, auditing and permission re-checks based on the original caller become impossible.63% similarUnverifiedAfter a domain is flagged as an email service provider, users may face additional identity verification, reduced sending quotas, disabling of certain automated features, and even a greater likelihood of emails being classified as spam63% similarUnverifiedA completely legitimate customer ID may still point to the wrong customer; schema validation can catch malformed requests but cannot prove that a request is appropriate.62% similarUnverifiedIn Azure AD, oid (Object ID) is the immutable unique identifier for each user within a tenant, remaining unchanged even if the user modifies their email address, UPN, or display name.62% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1134557API
curl https://kongchang.com/api/v1/knowledge/claims/1134557MCP
get_claim(id=1134557)