Azure Data Factory映射数据流：Azure Managed Instance连接器失效问询

Yep, you’re not alone with this issue—plenty of other ADF users hit the same wall back in late 2020 when Azure Managed Instance (MI) suddenly stopped working as a valid dataset in Mapping Data Flow, even though it had been functioning perfectly just weeks before September 2020.

Here’s what we know from community discussions and official updates:

• Other users reported the same problem: Multiple threads in Azure’s official ADF community forums popped up around August-September 2020 from folks facing identical behavior—MI datasets that worked in Data Flows one day were unrecognized or unsupported the next.
• Microsoft’s documentation update was the official notice: While there wasn’t a flashy, widespread service announcement (like a targeted alert in the Azure Portal), the August 31, 2020 update to the ADF connector overview docs was the formal notice that MI would no longer be a supported connector for Mapping Data Flow. This change tied into backend updates to Mapping Data Flow’s connector framework, which narrowed down the list of supported data stores.
• Workaround options: Most users who ran into this switched to using the SQL Server connector in Mapping Data Flow to connect to their MI instances. Since MI is compatible with standard SQL Server connectivity protocols, this works as a reliable alternative—you just need to make sure your network setup (like VNet integration, private endpoints, or public endpoint access) lets the Data Flow runtime reach your MI instance.

内容的提问来源于stack exchange，提问作者user1278953