/
Private Endpoint Should be Configured for Key Vault

Private Endpoint Should be Configured for Key Vault

Description:

An Azure Private Endpoint is a network interface that connects you privately and securely to a service powered by Azure Private Link.

The private endpoint uses a private IP address from your VNet, effectively bringing the service into your VNet.  All traffic to the service can be routed through the private endpoint, so no gateways, NAT devices, ExpressRoute or VPN connections, or public IP addresses are needed.

Traffic between your virtual network and the service traverses over the Microsoft backbone network, eliminating exposure from the public Internet.  You can connect to an instance of an Azure resource, giving you the highest level of granularity in access control.



Solution/Reference: 

Full instructions to perform this can be found here:

https://docs.microsoft.com/en-us/azure/key-vault/general/private-link-service?tabs=portal#establish-a-private-link-connection-to-key-vault-using-the-azure-portal

Related content

Firewall Should be Enabled on Key Vault
Firewall Should be Enabled on Key Vault
More like this
Storage account should use Private Link Connection
Storage account should use Private Link Connection
More like this
App Configuration Should Use Private Link
App Configuration Should Use Private Link
More like this
Private Endpoint Should Be Enabled for PostgreSQL Servers
Private Endpoint Should Be Enabled for PostgreSQL Servers
More like this
Container Registries Should Use Private Link
Container Registries Should Use Private Link
More like this
Private Endpoint Connections on Azure SQL Database Should Be Enabled
Private Endpoint Connections on Azure SQL Database Should Be Enabled
More like this