A manufacturing firm is merging with a subsidiary that uses a separate identity provider.

Option B restores consistency between the directory of record and the authorization data that the ZPA policy actually evaluates. Successful SAML authentication proves identity but does not substitute for SCIM group membership when the Access Policy criterion is a SCIM group. The administrator should trigger or correct synchronization, inspect the resulting membership, and review synchronization events before granting access. Zscaler’s SCIM Groups documentation states that these groups are pulled from the identity provider, while SCIM Sync Logs record changes to users, attributes, groups, and memberships for troubleshooting. Keeping the policy bound to SCIM groups preserves role-based intent and an auditable source of truth. NameID is an identity value, not reliable group authorization. A provisional local group creates drift, and rerouting authentication does not repair the subsidiary’s authoritative SCIM membership.