Independent enterprise technology-change research

PT-2026-019 · 17 July 2026

PlatformTrace

Enterprise platform migrations, examined in public.

Management API change · Enforced · High confidence

Auth0 removes legacy inline enabled-client management

Auth0 no longer supports managing a connection's enabled clients through the legacy inline field in connection GET and PATCH operations.

Evidence boundary: The change is limited to affected connection operations. Auth0 connections and the wider Management API continue.

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

  1. Auth0 migration documentation.

Corrections and updates

No correction is currently open. Any compatibility extension or endpoint amendment will be dated.