Okta SCIM provisioning attribute mapping limit of 100 per rule

The Okta SCIM 2.0 provisioning API permits attribute mappings within provisioning rules, with an observed ceiling of 100 attributes per rule. Engineers designing large-scale provisioning flows need clarity on whether this ceiling functions as an enforceable hard limit or a practical threshold that may be exceeded without immediate failure. The provisioning engine's behavior when the attribute count surpasses 100 entries remains undocumented, and no official guidance specifies error handling, truncation, or rule rejection mechanisms. This uncertainty impacts the design of organization-wide provisioning strategies that require granular attribute control beyond the commonly cited limit.

Does the provisioning rule reject creation or update when the attribute count exceeds 100, or does it silently truncate the mapping? Is the limit consistent across Free, Professional, and Enterprise editions, or does it vary by subscription tier? Are there supported patterns for splitting attribute mappings across multiple rules without losing mapping integrity?