What changes
The enabled_clients field is no longer the supported way to read or update client assignments within connection payloads. Integrations must use the dedicated enabled-client endpoints.
Who is affected
- Provisioning tools that patch connection objects with
enabled_clients. - Configuration-as-code pipelines that read client assignments from connection responses.
- Internal administration tooling built around the legacy schema.
Timeline
The change was enforced on 13 July 2026.
Required action
- Find Management API calls that depend on the inline field.
- Move reads and writes to the dedicated endpoints.
- Update tests for response-shape and permission differences.
What is not affected
The record does not claim that connection objects or all connection-management endpoints are retired.
PlatformTrace analysis
This is a workflow migration rather than a product retirement. Automation can fail even when the underlying tenant configuration remains valid.
Sources
Corrections and updates
No correction is currently open. Any compatibility extension or endpoint amendment will be dated.