An Azure service that is used to manage and protect cryptographic keys and other secrets used by cloud apps and services.
Yes, this is by design.
For Azure Key Vault, the Allow trusted Microsoft services to bypass this firewall option is a firewall setting. During creation, if public access is disabled, there is no public firewall configuration to edit in that create experience, so that checkbox is not shown there.
After the vault is created, when public network access is set to Disabled, trusted services bypass can still apply. Microsoft documents that:
- when public access is disabled, trusted services continue to reach the vault and do not require a private endpoint
- services not on the trusted services list are still blocked
- if the vault is associated with a Network Security Perimeter and public access is set to Secure by perimeter, that perimeter overrides the bypass unless an explicit perimeter rule allows access
So the behavior shown is consistent with the product model:
- At creation time: disabling public access hides the firewall exception option in that UI flow.
- After creation: disabling public access can still coexist with trusted Microsoft services bypass.
There is also a Microsoft Q&A example showing that if the portal blocks saving both changes together, the working sequence is:
- Set Public network access to Disable and save.
- Reopen Networking.
- Enable Allow trusted Microsoft services to access this resource and save.
That matches the behavior shown in the screenshots.