… 2 unchanged lines …
  
  ## Key facts
  - The connector reads Delta format only. CSV and Parquet tables in the lakehouse are not selectable, and Fabric Data Warehouse tables aren't supported.
- - Fabric shortcuts are honoured, so tables that physically live in another workspace can still be ingested through the target workspace.
+ - Fabric shortcuts are honoured, so tables that physically live in another workspace can still be ingested through the target workspace — but only if the service principal can reach the target. A shortcut using **passthrough authentication** needs **Dynamics 365 AI for Customer Insights** granted either Contributor on the target workspace, or the target lakehouse shared with **Read** plus **Read all with Apache Spark**. `Read all with SQL analytics endpoint` on its own is not enough, because the connector reads through OneLake APIs. Shortcuts using **delegated authentication**, including external shortcuts, go through their own connection identity and need nothing extra.
  - Two tenant settings have to be on, both set by a Fabric admin: "Users can access data stored in OneLake with apps external to Fabric" under OneLake settings, and "Service principals can call Fabric public APIs" under Developer settings.
  - The **Dynamics 365 AI for Customer Insights** service principal must be added to the Fabric workspace with the Contributor role. The person configuring the data source needs at least Viewer on the workspace.
  - Every table needs a primary key column with unique, non-null values, typed String, Integer or GUID. Where it can't be auto-detected you assign it during set-up.
    … 19 unchanged lines …
  - Delta log expiry is the failure mode that bites in month three, not week one. The refresh worked fine until the logs the connector needed were vacuumed away.
  - Upstream table changes in the lakehouse — a schema change, a table rewritten by a pipeline — propagate straight into Customer Insights. There's no staging copy absorbing it any more, which is the point and also the risk.
  - Someone will point the connector at a Data Warehouse item because it looks like a lakehouse in the Fabric UI. It isn't supported.
+ - A passthrough shortcut to a lakehouse in another workspace looks identical in the picker to a local table and fails only at read time. Contributor on the workspace Customer Insights connects to does nothing for the shortcut's target — that's a second, separate grant, and it's the sort of thing a Fabric admin will assume is already covered.
  - Link to Microsoft Fabric on the Dataverse side consumes Dataverse storage, because the linked tables are held in delta parquet. Check the client's capacity position before enabling it on a large environment.
  - One Dataverse environment links to a single Fabric workspace, so if the client already used that link for something else, your output plan needs revisiting.