Issue with Creating Linked Server from Azure SQL Managed Instance to On-Premises

  • Hi,

    Interestingly, I was able to create a linked server in the reverse direction—from the on-premises SQL Server to my Azure SQL MI—using a remote login and password for authentication.

    However, when I attempt to establish the link from Azure SQL MI to the on-premises SQL Server, it consistently fails.

    Additional Details:

    I have an Azure VM within the same VNET as the SQL MI. From this VM, I successfully tested connectivity to the on-premises SQL Server using both ping and telnet.

    Despite verifying inbound and outbound rules for the SQL MI in Azure (ensuring the necessary ports and IPs are open), the connection fails with the following errors:

    Error 1:

    Data Source: tcp:DB1.xx,1433

    Provider: MS OLEDB Driver for SQL Server

    TCP Provider: No such host is known.

    OLE DB provider "MSOLEDBSQL" for linked server "MYLINKED" returned message "Login timeout expired."

    OLE DB provider "MSOLEDBSQL" for linked server "MYLINKED" returned message "A network-related or instance-specific error has occurred while establishing a connection to SQL Server."

    Error 2:

    Data Source: DB1.xx

    Provider: MS OLEDB Driver for SQL Server

    Named Pipes Provider: Could not open a connection to SQL Server [53].

    OLE DB provider "MSOLEDBSQL" for linked server "MYLINKED" returned message "Login timeout expired."

    OLE DB provider "MSOLEDBSQL" for linked server "MYLINKED" returned message "A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible."

    Error 3:

    Data Source: Directly specifying the linked server name

    Named Pipes Provider: Could not open a connection to SQL Server [53].

    OLE DB provider "MSOLEDBSQL" for linked server "DB1.xx" returned message "Login timeout expired."

    OLE DB provider "MSOLEDBSQL" for linked server "DB1.xx" returned message "A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible."

     

    Given these errors, I am wondering if this configuration is truly possible or supported.

    Any insights, suggestions, or guidance would be greatly appreciated.

Viewing 2 posts - 1 through 1 (of 1 total)

You must be logged in to reply to this topic. Login to reply