title: Why can I connect to a Synapse serverless SQL pool but cannot connect to a dedicated SQL pool in the same Synapse Workspace
body: <p>Recently, we deployed a dedicated SQL Pool to a Synapse Workspace in production. In development we can access both the serverless SQL pool and the dedicated SQL pool. However, in production we can access the serverless SQL pool, but we cannot reach the dedicated SQL pool (either in the portal where upon trying to view the database objects we get an AjaxError or when trying to connect via SSMS where we get a Named Pipes Error message):</p>
  <p><a href="https://i.stack.imgur.com/2Y3HC.png" rel="nofollow noreferrer">Named Pipes Error message</a></p>
  <p>Both the development and the production Synapse instance have private endpoints (in separate vnets and subnets). We access both using a VM that is associated to a virtual network that is peered with the network with the private endpoints of the Synapse instances.</p>
  <p>Any ideas what could cause this behavior and how to fix it?</p>
  <p>Thanks in advance!</p>