An Azure analytics service that brings together data integration, enterprise data warehousing, and big data analytics. Previously known as Azure SQL Data Warehouse.
For Dynamics 365 Finance and Operations, Dataverse Link to Fabric and Azure Synapse Link replicate selected tables/entities—not AxDB SQL views, stored procedures, or user-defined functions—and Fabric Mirroring supports source views only for Snowflake, not as a general SQL-object replication feature.
Support matrix
| Integration / source | SQL views | Stored procedures | UDFs |
|---|---|---|---|
| Fabric Mirroring — Azure SQL Database | Not documented as replicated | Not replicated | Not replicated |
| Fabric Mirroring — Snowflake | Supported, including materialized views; refreshed every 12 hours | Not listed as supported | Not listed as supported |
| Dataverse Link to Fabric — F&O | Not replicated | Not replicated | Not replicated |
| Azure Synapse Link for Dataverse — F&O | Not replicated | Not replicated | Not replicated |
| Objects created downstream in Fabric/Synapse | Supported, depending on endpoint | Supported with endpoint-specific limitations | Supported with endpoint-specific limitations |
Fabric Mirroring
Fabric Mirroring support depends on the source connector; it should not be interpreted as mirroring every database object that exists in the source.
- Azure SQL Database: The documented replication unit is the table. Its limitations, selection rules, schema changes, and reseeding behavior are all table-based. The documentation does not identify source views, stored procedures, or UDFs as mirrored objects.^1^
- Snowflake exception: Snowflake is currently the only documented mirroring source that supports views. Fabric executes each selected view and materializes its results as a Delta table in OneLake every 12 hours; this is not near-real-time replication of the view definition or behavior.^2^
- Snowflake supports ordinary and materialized views, while several other object types are explicitly unsupported.^3^
Therefore, a view-support statement for Snowflake cannot be applied to an F&O AxDB or Azure SQL source.
Dataverse Link to Fabric
Link to Fabric exposes a Select Tables step. For an environment linked to Finance and Operations, F&O tables can be added, while Dataverse tables are selected according to their table/change-tracking eligibility.^4^
The documented selection and synchronization scope is tables:
- Standard and custom Dataverse tables.
- Eligible Finance and Operations tables.
- Table rows and associated schema/metadata changes.
There is no selection or synchronization mechanism for AxDB SQL views, stored procedures, or UDFs. Those objects are consequently outside the documented Link to Fabric replication contract.^5^
Azure Synapse Link for Dataverse
For Finance and Operations, Azure Synapse Link supports continuous replication of standard and custom entities and tables, including create, update, and delete changes.^6^
It does not replicate AxDB:
- SQL views
- Stored-procedure definitions or executable procedures
- Scalar or table-valued UDF definitions
The broader Dataverse documentation likewise describes initial and incremental writes for table data and metadata, rather than general database-object replication.^7^
Re-create the logic downstream
Replication should be separated from the analytical objects built over the replicated data.
For example, an Azure SQL mirrored database receives an automatically generated, read-only SQL analytics endpoint. In that endpoint, users can create:
- SQL views
- Inline table-valued functions
- Stored procedures
These are new downstream objects over the mirrored Delta tables; they are not replicated copies of source objects.^8^
Azure Synapse SQL also supports views, procedures, and UDFs, but capabilities differ by pool:
- Dedicated SQL pool: views, user-defined procedures, and UDFs are supported.
- Serverless SQL pool: views and read-oriented procedures are supported; only inline table-valued UDFs are supported, not scalar UDFs.^9^
The practical migration pattern is therefore:
- Replicate the required F&O tables/entities.
- Inventory each source view, procedure, and UDF plus its table dependencies.
- Reimplement reporting views and compatible read-only logic in the Fabric SQL analytics endpoint or Synapse.
- Rewrite unsupported procedural, scalar-UDF, cross-database, or source-specific logic using the target platform’s supported SQL or data-engineering layer.
- Validate results independently; source permissions, masking settings, and object-level permissions are not automatically carried into Azure SQL mirrored data.^1^
Direct AxDB replica access is a separate access model and is not evidence that any of these managed link or mirroring services will replicate AxDB programmable objects.
References
- Limitations in Microsoft Fabric mirrored databases from Azure SQL Database
- Mirroring views in Fabric
- Limitations in Microsoft Fabric mirrored databases from Snowflake
- Link to Microsoft Fabric
- Microsoft Fabric Link for Dataverse FAQ
- Choose finance and operations data in Azure Synapse Link for Dataverse
- What is Azure Synapse Link for Dataverse?
- Mirroring Azure SQL Database
- Transact-SQL features supported in Azure Synapse SQL