… 10 unchanged lines …
  - Storage and compute costs sit with you, in your subscription, rather than showing up as Dataverse storage consumption.
  - Low-latency sync — the redesigned engine that writes straight to delta parquet — applies to Fabric Link configurations, not to Synapse Link. Synapse Link continues to function on the existing pipeline.
  - The **Delta parquet / Delta Lake export** option is itself now deprecated (announced September 2026): closed to new customers from 15 October 2026, removed December 2027. The stated replacement for delta parquet output is Link to Microsoft Fabric, not another Synapse Link setting.
+ - In **append only** mode a deleted row isn't removed from the lake straight away — it's appended with `isDeleted = True`. Synapse Link then hard-deletes that record from the lake after 30 days. Delta Lake output behaves the same way: soft delete on the next sync, hard delete at 30 days. To keep deleted rows longer, enable [long-term retention](https://learn.microsoft.com/en-us/power-apps/maker/data-platform/data-retention-set) on the table.
  - Export to Data Lake (the old COMO service) has been deprecated and is being retired, with no further extension or exception process planned as of the June 2026 announcement.
  
  ## When to use / skip
    … 13 unchanged lines …
  - Because it's a push rather than a scheduled pull, there's no refresh interval to tune when things are slow, and no obvious dial for people used to dataflows.
  - Costs are distributed. Dataverse storage doesn't move, but the client picks up storage, compute and integration charges in Azure, and those land on a different budget line than they expect.
  - Deletes replicate. Downstream consumers built on the assumption that the lake is append-only will get a surprise.
+ - Append only isn't the archive people assume it is. The `isDeleted` tombstone survives 30 days and then the row goes for good, so a lake being used as the audit trail of record quietly loses deleted history a month later. Microsoft only documented the 30-day window in September 2026 — plenty of profiles were built before anyone knew. Long-term retention on the table is the fix, and it's a Dataverse setting, not a Synapse Link one.
  
  ## Consultant notes
  - Ask early whether Fabric is in the client's future. If the answer is yes, either go straight to Link to Fabric or at minimum set the profile up as delta parquet so the option stays open.
    … 3 unchanged lines …
  
  ---
  
- *Revisit as the December 2027 Delta Lake export removal approaches, or if managed identity profiles become linkable to Fabric.*
+ *Revisit as the December 2027 Delta Lake export removal approaches, if managed identity profiles become linkable to Fabric, or if the 30-day deleted-record window changes.*
  

    … 9 unchanged lines …
  - Where Link to Fabric selects all change-tracked tables by default, Synapse Link has system administrators pick the tables they want.
  - Storage and compute costs sit with you, in your subscription, rather than showing up as Dataverse storage consumption.
  - Low-latency sync — the redesigned engine that writes straight to delta parquet — applies to Fabric Link configurations, not to Synapse Link. Synapse Link continues to function on the existing pipeline.
+ - The **Delta parquet / Delta Lake export** option is itself now deprecated (announced September 2026): closed to new customers from 15 October 2026, removed December 2027. The stated replacement for delta parquet output is Link to Microsoft Fabric, not another Synapse Link setting.
  - Export to Data Lake (the old COMO service) has been deprecated and is being retired, with no further extension or exception process planned as of the June 2026 announcement.
  
  ## When to use / skip
    … 7 unchanged lines …
  - Whether the profile is a stepping stone to Fabric or the permanent destination, because that decides the format choice above.
  
  ## Gotchas
+ - **Deprecated 2026-09-07:** the Delta Lake (Parquet) export option is going. From 15 October 2026 it isn't available to new customers, and existing customers must move to CSV output in Synapse Link or to Link to Microsoft Fabric by December 2027. See [Export Dataverse data in Delta Lake format](https://learn.microsoft.com/en-us/power-apps/maker/data-platform/azure-synapse-link-delta-lake).
  - Choosing CSV closes the Fabric door. It reads like a harmless format preference during setup and it isn't.
  - Managed identity is the security choice most enterprises want, and it's currently the choice that blocks Fabric linking. Worth calling out to the security team before they mandate it.
  - Because it's a push rather than a scheduled pull, there's no refresh interval to tune when things are slow, and no obvious dial for people used to dataflows.
    … 8 unchanged lines …
  
  ---
  
- *Revisit when the Export to Data Lake retirement completes, or if managed identity profiles become linkable to Fabric.*
+ *Revisit as the December 2027 Delta Lake export removal approaches, or if managed identity profiles become linkable to Fabric.*