Hi @Erik Larsen ,To diagnose the issue, we can follow the below steps:
- Check the Private Link configuration by browsing the resource.
a. Go to Private Link Center.
b. On the left pane, select Private link services.
c. Filter and select the private link service that you want to diagnose.
d. Review the private endpoint connections.
- Make sure that the private endpoint that you're seeking connectivity from is listed with an Approved connection state.
- If the state is Pending, select it and approve it.
- Go to the private endpoint that you're connecting from by selecting the name. Make sure the connection status shows as Approved.
- After both sides are approved, try the connectivity again.
e. Review Alias on the Overview tab and Resource ID on the Properties tab.
- Make sure the Alias and Resource ID information matches the Alias and Resource ID you're using to create a private endpoint to this service.
- Check if data is flowing using Azure Monitor.
a. On the private endpoint resource, select Metrics.
- Select Bytes In or Bytes Out.
- See if data is flowing when you attempt to connect to the private endpoint. Expect a delay of approximately 10 minutes.
- Check if there are any issues with the VM connectivity to the virtual network that hosts the private endpoints.
a. Use VM Connection troubleshoot from Azure Network Watcher.
b. Select the client VM.
c. Select Connection troubleshoot, and then select the Outbound connections tab.
d. Select Use Network Watcher for detailed connection tracing.
e. Select Test by FQDN.
f. Select Test, and validate the test results.
If none of the above steps help, you can try the private endpoint troubleshooting guide for further assistance. Please also let me know so I can help you further.
If this answer helps you please mark "Accept Answer" so other users can reference it.
Thank you,
James