How to delete a private network connector

Question

Hello!

I created a private network connector (PNC) in Azure to test out an app proxy.

I have uninstalled the connector on the server being used for test but I cannot delete the PNC.

I'm logged in as global admin but the delete option is 'greyed' out. I do have a delete option for the group that contains the PNC but that fails to delete.

Answer 1

Hi cspell,

Welcome to Microsoft Q&A and thank you for posting your query here!

The deletion option for your Azure private network connector (PNC) is grayed out because Azure manages the lifecycle of connectors differently than many other resources. Unused or unregistered connectors are not always immediately deletable by admins, even if you have already uninstalled the server agent and have global admin rights. Microsoft Entra automatically marks connectors as "inactive" and removes them after a specific retention interval, typically 10 days after inactivity.

Why Can't You Delete the PNC Directly?

• The "Delete" button might be unavailable if the connector is still registered in Azure or if Azure hasn't yet marked it as inactive after your local uninstall.​
• Group-level deletion can fail if resources within the group (such as connectors) are still considered in use or have pending cleanup actions.

Steps and Best Practices to Delete the Connector:

Confirm the connector agent is fully uninstalled on the server.

• Wait for Azure to automatically mark the connector as inactive (this normally happens within 10 days of last activity, after which Azure removes it; manual intervention is not generally supported for forced deletion).​

For further details and periodic updates on PNC lifecycle management, you may refer to the official Microsoft Entra documentation: https://learn.microsoft.com/en-us/entra/global-secure-access/concept-connectors

Please do let me know if you need anything on this.

If the information resolved your issue, kindly consider accepting the answer — it will help others who might be facing similar challenges.

Thanks,

Harish.