Fivetran says Managed Data Lake Write Credentials are now generally available, letting query engines run DDL and DML against lake tables. Engines authenticate via OAuth2 client credentials—one Client ID and Secret per destination—so each gets a distinct identity against the hosted catalog. For teams running a dual-format Iceberg and Delta lake, the real question is how to scope write access tightly enough that an engine can delete rows or drop a table without broad bucket permissions, while Fivetran retains sole authority over metadata and schema evolution. This article explains how Fivetran strikes that balance, and what to set up before you rely on it.
Why it matters
For data engineers, the practical consequence is that permission management collapses into a single policy layer. Fivetran's catalog returns per-user access rules through the Iceberg REST protocol, so an organization defines governance once rather than re-encoding it for every engine.…