General availability for Private Endpoints and Customer-Managed Keys

Two important security features for App Configuration are now officially GA.

**Private Endpoints** allows clients on a virtual network (VNet) to securely access data over a [private link](https://docs.microsoft.com/azure/private-link/private-link-overview). The private endpoint uses an IP address from the VNet address space for your App Configuration store. Network traffic between the clients on the VNet and the App Configuration store traverses over the VNet using a private link on the Microsoft backbone network, eliminating exposure to the public internet. [Read more](https://docs.microsoft.com/azure/azure-app-configuration/concept-private-endpoint) about private endpoints for Azure App Configuration.

**Customer-Managed Keys** provide enhanced data protection by allowing you to manage your encryption keys. App Configuration always encrypts data using a Microsoft-managed key. When customer-managed key encryption is used, all sensitive information in App Configuration is also encrypted with a user-provided Azure Key Vault key. This provides the ability to rotate the encryption key on demand. It also provides the ability to revoke Azure App Configuration's access to sensitive information by revoking the App Configuration instance's access to the key. [Read more](https://docs.microsoft.com/azure/azure-app-configuration/concept-customer-managed-keys) about customer-managed keys for Azure App Configuration.

*Note: In the **Central India** region, Private Endpoints and Customer-Managed Keys are still in public preview.*

If you have any questions or feedback on these features, you can open an issue in the [App Configuration GitHub repo](https://github.com/Azure/AppConfiguration/issues).