Any easier way to test private endpoint than deploying a VM?

Najam ul Saqib 280

Hi,Whenever I create a private endpoint on Azure, I need to test it of whether or not its resolving to the private IP address, but the only method I know is deploying a VM in the same VNet and then pinging it. Is there any easier (quicker) method? Can we do it via cloud shell or something?

Wallraf 5 Reputation points

2024-09-13T06:20:25.58+00:00

You can use this tool to test connectivity without a VM.

Go to Azure Portal > Network Watcher.

Select Connection troubleshoot under Network Diagnostic Tools.

For Source, pick any existing resource (like a VM) if available.

For Destination, enter your private endpoint's FQDN.

Run the test to see if it resolves and connects properly.
Najam ul Saqib 280 Reputation points

2024-09-14T14:06:44.3333333+00:00

Interesting solution Wallraf but again for this we need to have a VM, what if we don't have one at all?

1 answer

KapilAnanth-MSFT 44,556 Reputation points Microsoft Employee

2024-09-13T06:14:50.69+00:00
@Najam ul Saqib ,

Welcome to the Microsoft Q&A Platform. Thank you for reaching out & I hope you are doing well.

I understand that you would like to test connectivity to a PE in a Virtual Network without having to deploy a VM in it.

I am afraid there are no such methods.

The main intention of having a Private EndPoint is to provide access to PaaS Services from VMs and OnPrem servers via VPN /ExR (Private Network)

I tried to do a Lab with NSG diagnostics, but it failed with the error "NetworkInterfaceNotAssociatedToVm"

So we have to deploy a testVM to test connectivity

Hope this clarifies

Thanks,

Kapil

Please don’t forget to close the thread by clicking "Accept the answer" wherever the information provided helps you, as this can be beneficial to other community members.
Please sign in to rate this answer.
KapilAnanth-MSFT 44,556 Reputation points Microsoft Employee

2024-09-16T05:12:29.2366667+00:00

@Najam ul Saqib ,

Currently, if the Private DNS Zone is linked to the VNET and the VNET has a default Azure DNS

The DNS resolution configuration will be correct.

If you want to "test" it hands on, you must deploy a resource into the VNET

NOTE : VMs can always be configured the override the VNET's DNS.

If you feel like this feature could be included in Network Watcher or the VNET itself, you may raise a post in Azure Feedback Hub forum requesting this feature.

All the feedback shared in these forums are monitored and reviewed by the Microsoft engineering teams responsible for building Azure

Thanks,

Kapil

Please don’t forget to close the thread by clicking "Accept the answer" wherever the information provided helps you, as this can be beneficial to other community members.

Najam ul Saqib 280 Reputation points

2024-09-18T10:47:15.5333333+00:00

@KapilAnanth-MSFT done, https://feedback.azure.com/d365community/idea/333dd851-ab75-ef11-a4e6-000d3a059eeb

KapilAnanth-MSFT 44,556 Reputation points Microsoft Employee

2024-09-18T11:26:34.38+00:00

@Najam ul Saqib ,

Thanks for keeping the thread updated :)

Cheers,

Kapil

Please Accept an answer if correct.

Original posters help the community find answers faster by identifying the correct answer.
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

Any easier way to test private endpoint than deploying a VM?

1 answer

Your answer