Hi Dani,
I am very excited about the MI Link feature for SQL MI. Kudos to you and your team on the work in this space.
1. It supports seamlessly, smooth and instant migration - this is a great improvement for us as we have over 200 hosted instances.
2. Scaling out R/O workloads to Azure - this opens architectural options for us to provide on-premise only clients (they are usually large) analytics and ML benefits Azure has to offer.
3. It introduces migration consolidations - this is very attractive to us for cost savings.
I did raise up a question on migration consolidations in the Q&A session on "What's New in Azure SQL MI" in PASS summit, where unfortunately you were absent, and would appreciate your insights on it: for our hosted applications, all clients have the same set of SQL DBs, many of them are very small, even 2 vcore( from instance pool) would result into resource underutilization. When we take advantage of migration consolidations, how would we differentiate Client A's DBs from Client B's?
Again, thanks for the great work in MI Link, and we cannot wait to preview it.
Best,
Junli