unable to see secrets in keyvault because of firewall issue

Nawaz Shaik (LTIMINDTREE LIMITED) 5 Reputation points Microsoft External Staff
2026-07-20T10:15:55.5766667+00:00

unable to see secrets in keyvault because of firewall issue.Firewall is turned on and your client IP address is not authorized to access this key vault. 

Azure Key Vault
Azure Key Vault

An Azure service that is used to manage and protect cryptographic keys and other secrets used by cloud apps and services.

0 comments No comments

2 answers

Sort by: Most helpful
  1. Saravana Kumar D 5 Reputation points Microsoft External Staff Moderator
    2026-07-29T10:41:05.5866667+00:00

    Hello Nawaz,

    Greetings!

    The error indicates that the request to access the Key Vault secrets is being blocked by the vault's network access restrictions. Azure Key Vault management permissions are separate from data-plane permissions, so being able to view the Key Vault resource in the Azure portal does not automatically allow access to its secrets.

    If the Key Vault is configured to allow access from selected networks, verify that the client's current public IPv4 address is added to the firewall allowlist under Key Vault → Networking. If the client is connected through a VPN or corporate proxy, ensure that the public IP seen by Azure is allowlisted rather than the local/private IP address. After updating the firewall rules, save the changes and refresh the Secrets blade.

    If Public Network Access is disabled, IP allowlisting will not be effective. In this scenario, access must be performed through an approved Virtual Network using a configured Private Endpoint or an allowed subnet with the Microsoft.KeyVault service endpoint enabled. Additionally, confirm that the Key Vault FQDN resolves to the private endpoint IP address.

    Once network connectivity is validated, verify that the account has the required data-plane permissions. For vaults using Azure RBAC, the Key Vault Secrets User role is required to read secret values, whereas the Key Vault Contributor role does not grant access to secret contents. For vaults using the Access Policy permission model, ensure that Get and List permissions are assigned for secrets.

    In summary, the issue is typically caused by Key Vault firewall/network restrictions or insufficient data-plane permissions. Reviewing the Key Vault networking configuration, Private Endpoint connectivity (if applicable), and RBAC/Access Policy assignments should help restore access to the secrets.

    Configure network security for Azure Key Vault -- https://learn.microsoft.com/en-us/azure/key-vault/general/network-security?tabs=azure-portal

    Access Key Vault behind a firewall -- https://learn.microsoft.com/en-us/azure/key-vault/general/access-behind-firewall

    I hope this helps clarify the cause of the issue and the required remediation steps. Please let us know if you continue to experience the problem after validating the network configuration and permissions, or if you need further assistance reviewing the Key Vault settings

    Was this answer helpful?

    0 comments No comments

  2. Christos Panagiotidis 3,546 Reputation points
    2026-07-20T11:25:57.87+00:00

    The error means your browser’s Key Vault data-plane request is blocked by network rules; vault-management permission is separate. If public access allows selected networks, open Networking, add the workstation’s current public IPv4 address, save, and refresh Secrets. Use the public address after any corporate proxy or VPN, not a private address.

    If public access is disabled, an IP rule cannot help. Connect from the VNet through an approved private endpoint and confirm the vault name resolves to its private IP. An allowed subnet with a Microsoft.KeyVault service endpoint is another supported design.

    Then verify data-plane authorization. Under Azure RBAC, Key Vault Secrets User can read secret values; Key Vault Contributor cannot. With legacy access policies, grant secret Get and List. Avoid enabling unrestricted public access merely to use the portal. The trusted-services bypass applies only to listed services; it does not make your browser trusted.

    Was this answer helpful?

    0 comments No comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.