Within Synapse I followed the example How to pause and resume dedicated SQL pools with Synapse Pipelines - Azure Synapse Analytics | Micro... to build a pipeline to pause or resume the SQL Dedicated pools.
This worked on the POC environment I built. When I rebuilt Synapse into a more secure environment, I included Managed Virtual Network. In executing the same pipeline against this environment, I receive a failure when running the first Web API call to retrieve the the SQL Pool ID's. (Response status code: 'Unknown'. More details:Exception message: 'An error occurred while sending the request.'.)
The only difference I can see in the 2 environments is Public vs Managed Virtual Network. If this is the issue, what adjustments need to be made to be able to do the API call to Pause/Resume the Dedicated SQL Pools.
