Join us at FabCon Atlanta from March 16 - 20, 2026, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.
Register now!To celebrate FabCon Vienna, we are offering 50% off select exams. Ends October 3rd. Request your discount now.
I have setup an Azure SQL mirror in a workspace using a service principal and the fabric REST API.
When I view the mirror on the workspace and choose "Start replication" it then switches to running. However the tables never replicate. If I then choose to "Configure Replication" I get a permissions error as the connection is owned by the service principal.
If I run `EXEC sp_help_change_feed;` on the source database, I can see everything is at State 1 (pending) while a manually setup (not using the API) mirror on another workspace generates state 4 results.
There is the issue that we cannot see the connection or configure replication as its owned by the principal. I am not sure if we can set that as shared using the API? But the main issue is the tables are not replicating even though the mirror shows as running.
Has anyone seen these issues?
Solved! Go to Solution.
For anyone reading this in the future, when the mirror is created by the API, you need to set the SAMI permissions either by going to the mirror in the portal and choosing share or by using an API call. I had not done that.
For anyone reading this in the future, when the mirror is created by the API, you need to set the SAMI permissions either by going to the mirror in the portal and choosing share or by using an API call. I had not done that.
User | Count |
---|---|
25 | |
15 | |
13 | |
9 | |
8 |
User | Count |
---|---|
36 | |
31 | |
25 | |
22 | |
15 |