Repository navigation
Support for Network Security Perimeter (NSP) #1050
Description
Activity
Network Security Perimeter (NSP) is the right path forward, and we’ll be adding NSP support on our side as well. You can find a good overview here:
https://learn.microsoft.com/en-us/azure/private-link/network-security-perimeter-concepts
- changed the title
[-][feature request] Define IP Whitelist Firewall Rules on App Configuration Services (Like Key Vault)[/-][+]Support for Network Security Perimeter (NSP)[/+]on May 14, 2025 Arjan Kohli (@arjankohli) I updated the title of this issue and use it to track our support for NSP in the roadmap.
When will this be available?
Reacted by Antoine Milochau, Bas Martin, Lucaskuster, Mike Zweers, Serhat Kepez, Yiğit Baylan and Jeffrey HaenBryan Schoot (@bryanschoot) we are progressing towards the public preview of our service's NSP integration. We expect this feature to be available June 2026 in public preview.
Any updates on when the public preview will be available?
Wouter Stinkens (@wstinkens) we are currently expecting public preview to be available by the end of August 2026.
Reacted by Bryan Schoot and Wouter Stinkens
I would love the ability to define an IP Whitelist firewall rule on my configuration services.
This would benefit customers that are running in hybrid multi-cloud + on-prem environments, where traffic to the configuration service needs to originate from outside Azure data-centers.
Azure Key Vault already supports this functionality, but protecting configuration services in the same manner creates defense in depth.
Many corporate environments have a strong desire to protect all configuration (not just vaulted secrets), because compromising and changing non-sensitive configuration can modify application behavior and create a denial of service.