… 2 unchanged lines …
  
  ## Key facts
  - Setting it up creates a Fabric lakehouse, a SQL endpoint and a Power BI semantic model, and points shortcuts at your Dataverse tables.
- - Prerequisites: System Administrator in the Power Platform environment, admin of the Power BI workspace, and a Power BI premium licence or Fabric capacity **in the same Azure geography** as the Dataverse environment. Fabric tenant settings must also allow item creation, workspace creation and external OneLake access.
+ - Prerequisites: System Administrator in the Power Platform environment, admin of the Power BI workspace, and a Power BI premium licence or Fabric capacity. As of October 2026 that capacity **no longer has to be in the same Azure geography or region** as the Dataverse environment; cross-geography and cross-region links are supported. Fabric tenant settings must also allow item creation, workspace creation and external OneLake access.
  - Three authentication options for the connection — organisational account, service principal, or workspace identity. Workspace identity is a Fabric-managed service principal bound to one workspace, and it has to be added as an application user in Dataverse with an appropriate role.
  - By default the wizard selects every non-system Dataverse table with **Track changes** enabled. Tables without change tracking aren't supported at all.
  - Initial sync can take up to 60 minutes including the delta parquet conversion, longer for large tables. Shortcuts show as "unidentified" until it finishes. Incremental updates typically appear within an hour, depending on churn and load.
    … 9 unchanged lines …
  ## Configuration decisions
  - Which authentication method the connection uses. Workspace identity avoids secret management and is the cleanest option if the workspace can support it; organisational account ties the link to one person's credentials.
  - Which tables actually sync. The wizard selects everything with change tracking on, and accepting that default is how storage bills surprise people.
- - Whether to create a fresh Fabric workspace or link into an existing one, bearing in mind the region constraint.
+ - Whether to create a fresh Fabric workspace or link into an existing one, and which capacity pays for it. Since the same-region rule went, that can be a capacity in another geography.
  - Who gets Owner versus Reader on the Dataverse connection, and separately who gets access to the workspace and the lakehouse.
  - Whether to secure at lakehouse or table level using OneLake security before sharing data more widely.
  
  ## Gotchas
- - The region rule is absolute. No Fabric capacity in the same geography as the environment and the wizard simply blocks you, usually discovered halfway through a workshop.
+ - The same-geography rule has gone. Microsoft's October 2026 documentation says the wizard accepts a Fabric capacity and workspace in a different geography or region, and the error that used to demand a capacity in the environment's region has been reworded. Older advice, including ours before this refresh, treated it as a hard block. Confirm it in the client's own tenant before you promise it.
+ - Cross-region doesn't mean free of data-movement questions. Dataverse data now sits in a Fabric capacity outside the environment's geography, so residency and sovereignty need a decision, not an assumption.
  - `SinkModifiedOn` is later than `ModifiedOn` by design, and for long-running finance and operations transactions a record can sync repeatedly with `SinkModifiedOn` showing the *last* sync. Building a latency dashboard on that difference gives you a misleading picture.
  - Adding a column to a linked table doesn't propagate until you use **Refresh Fabric tables**, and even then only after the next data change on that table.
  - The connection is created with the credentials of whoever ran the wizard. If that person leaves, the link breaks. Share the connection or move it to workspace identity on day one.
    … 7 unchanged lines …
  
  ---
  
- *Worth revisiting once low-latency sync has finished its global rollout, or if the 2,000-table ceiling moves.*
+ *Worth revisiting once low-latency sync has finished its global rollout, or if the 2,000-table ceiling moves. Refreshed 2026-10-24: same-region capacity requirement removed.*