linked service connectivity issues in Azure Synapse Studio

Surendra Yadav 45 Reputation points

Hi Team,

We are not able to test connection when Key vault link service checking that time gating error as mentions below.

👁 User's image

  1. SAI JAGADEESH KUDIPUDI 3,470 Reputation points • Microsoft External Staff • Moderator

    Hi @Surendra Yadav ,
    Is the Synapse workspace Git-enabled, and are you deploying via ARM/Bicep/CI templates (or Synapse publish artifacts)?

    1. When you deployed the workspace, did your template include Managed Virtual Network configuration?
    2. What is the Authentication method used in the Key Vault linked service (system-assigned managed identity / service principal / key-based)?
    3. Does your workspace have data exfiltration protection / private networking / managed private endpoints enabled?
    4. Is this happening in a specific branch/environment only, or consistently in all environments?
  2. SAI JAGADEESH KUDIPUDI 3,470 Reputation points • Microsoft External Staff • Moderator

    Hi @Surendra Yadav ,
    Could you please let us know if you had a chance to review the earlier queries and share your inputs? This information will help us proceed further with the investigation.

  3. Surendra Yadav 45 Reputation points

    Hi @SAI JAGADEESH KUDIPUDI ,

    Please find the details below:

    • Synapse workspace is Git-enabled and deployed through CI/CD using published Synapse artifacts.
    • Managed Virtual Network and Managed Private Endpoints are enabled.
    • The Key Vault linked service uses the Synapse Workspace System-Assigned Managed Identity for authentication.
    • Private networking is enabled, and Key Vault access is configured through Private Endpoints.
    • The issue is occurring consistently in both QA and Production environments.

    Additional observation: When Key Vault Public Network Access is temporarily enabled (with Trusted Microsoft Services allowed), the Linked Service Test Connection succeeds. When Public Access is disabled, the connection fails with Error 9054, indicating the issue is likely related to the private connectivity path (Private Endpoint, Managed Private Endpoint, DNS resolution, or network configuration).

    we implemented our synapse as per below url but we are facing issue when connecting link service keyvaults

    https://learn.microsoft.com/en-us/azure/synapse-analytics/security/synapse-workspace-managed-vnet

Sign in to comment
Sign in to answer

Your answer