Announcements
I've been tasked with migrating from Dataverse to Azure SQL such that power apps behaves the same as now except that it's backed by Azure SQL. Until last week I knew nothing about Dataverse so I'm still learning fast and the hard way. Initially it appears that the solution is to shift the data to an Azure SQL DB, then create a new power apps env with all the user tables recreated as virtual tables linked to the new DB, then copy over all the relationships to the virtual tables, then recreate the relationships as FKs in the SQL DB. I've spent several days investigating and scratching my head and concluded that's no non-painful solution. I've figured out that Synapse and can copy data as per what appears to be the MS approved method https://learn.microsoft.com/en-us/power-apps/maker/data-platform/azure-synapse-link-pipelines?tabs=synapse-analytics and this works but feels wrong, and it also fills up the new SQL tables with multiple columns that I assume that the Synapse copy process uses internally. Has anyone ever done before and can advise on a path? It feels like MS really don't want it to be easy. Thanks 🙂
Hello, @Dextor, I will start the answer but we difintly need @dpoggemann , the Master of Synapse, ADF, ADLS, and Azure SQl.
So to get some clarification: Is your Data now in Dataverse and you have Power apps that are GRUD'ing on this data?
Hi! Yes, they're CRUDing. So the idea is that I have a new env that's identical to the old one with the exception that the tables/entities are backed by Azure SQL, and the new SQL DB has all the user defined FKs set.
Under review
Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.
Jump in, show your community spirit, and win prizes!
Expanding mentorship, skilling, and AI innovation
These are the community rock stars!
Stay up to date on forum activity by subscribing.
Valantis 404
timl 344 Super User 2026 Season 1
WarrenBelz 320 Most Valuable Professional
