Policy effect in Azure that inserts fields only while a resource is being created or updated; resources that already exist are not corrected by it.
Also called Policy effect.
Read more: Microsoft Learn
In the Ultra Transcenders books
Each book explains Append in context, with comparison tables and the common traps.
Related terms
- Audit
Policy effect that lets a request proceed but flags the resource as non-compliant and logs a warning to the activity log. Microsoft suggests beginning there and later moving to something enforcing, like Deny.
- Audit effect
Policy effect in Azure that records a warning and flags matching resources as non-compliant, without ever blocking or altering them.
- BlockBlobStorage
Premium, SSD-backed account kind dedicated to block and append blobs, giving the lowest latency; redundancy is limited to LRS or ZRS and access tiers aren't available.
- Flow
The unit of work inside a Lakeflow pipeline that takes data from a source, transforms it and lands it in a destination like a streaming table. Streaming flows either append or update, and
CREATE FLOWlets you declare a flow apart from the table it feeds. - Load to Tables
Lakehouse explorer shortcut: pick a CSV or Parquet file (or a whole folder) already uploaded under Files and it becomes a Delta table. You can append or overwrite, but nothing is transformed, and it runs once.
- Modify
Policy effect in Azure that can add, replace or remove tags and other properties. Resources that already exist are brought into line by running a remediation task.
- Modify effect
With this policy effect, Azure can add, replace or strip tags and other properties. For resources that already exist, a remediation task makes the change, running under the managed identity of the assignment.
- Output mode
Decides which rows a stateful Structured Streaming query writes out at each trigger: append, the default, for finalised rows only; update for rows that changed, which Delta sinks don't support; or complete for the entire result.