Auth0 Terraform Keeps Generating "enabled_clients" Depnote Logs Despite Update - Legacy Management of Connection's Enabled Clients

Auth0 is deprecating Enabled Client Management from Management API’s Get All Connections, Get Connections, and Update a Connection.

The Migrate Enabled Client Management to Dedicated Connection Endpoints documentation lists Auth0 Terraform Provider versions 1.29.0 and above as supporting this change, and no action is required. However, even when using a supported version, the deplogs still appear.

• Terraform
• Auth0 Terraform Provider
• Depnote
• Migrate Enabled Client Management to Dedicated Connection Endpoints
• Legacy Management of Connection's Enabled Clients

When running terraform plan or terraform apply, Terraform must first fetch the current state of the infrastructure to compare it against the code. It does this by making a GET request to fetch the connection details.

Auth0's backend currently emits this deprecation warning whenever the enabled_clients field is accessed, regardless of whether it's being read (GET) or modified (PATCH).

Because the Auth0 API still returns that field in the JSON payload when Terraform reads the connection state, Auth0 flags it with a deprecation notice. Up-to-date Terraform Provider versions know how to handle this correctly behind the scenes and are already using the new endpoints for any modifications.

If an up-to-date Auth0 Terraform Provider (1.29.0+) is being used, full compliance is achieved. No additional action is needed. The depnote log entries can be safely filtered out when searching tenant logs.