Study guide

3.2 Access Control and Firewall for Key Vault

Microsoft Certified: Cloud and AI Security Engineer Associate SC-500

Track your progress as you read

Finished sections get a check mark.

1 Introduction & Exam Overview

1.1 Current Exam Facts 1.2 Skills Measured & Weightings 1.3 Study Path, Prerequisites & Exam Strategy

2 Microsoft Entra ID Secure Access

2.1 Privileged Identity Management (PIM) 2.2 Conditional Access Policies 2.3 MFA and Passwordless Authentication 2.4 Application Identities, OAuth Consent & Managed Identities

3 Azure Key Vault Secrets and Keys

3.1 Deploy and Configure Key Vault 3.2 Access Control and Firewall for Key Vault 3.3 Keys, Secrets, Certificates & Defender for Key Vault

4 Governance, Policy & RBAC

4.1 Azure Policy for Security Controls 4.2 Defender for Cloud Compliance & Security Standards 4.3 Resource Locks and Azure RBAC 4.4 Custom Roles, Overprivileged Access, Backup & IaC Security

5 Secure Storage Accounts

5.1 Storage Account Security Fundamentals 5.2 Storage Firewalls and Access Policies 5.3 Defender for Storage

6 Secure Databases

6.1 Azure SQL Platform Security 6.2 Database Auditing 6.3 Defender for Databases

7 Network Security Groups & Virtual Network Manager

7.1 Network Security Groups and Application Security Groups 7.2 Azure Virtual Network Manager Security Admin Rules 7.3 Virtual WAN and VPN Security

8 Private Access, Private Link & Azure Firewall

8.1 Microsoft Entra Private Access 8.2 Private Endpoints and Private Link 8.3 Azure Firewall 8.4 Network Watcher Diagnostics and Effective Rules

9 Security for AI Workloads

9.1 Purview DSPM for AI and Data Overexposure 9.2 Copilot Studio Protection and Agent Management 9.3 Microsoft Entra Agent ID Security 9.4 Defender for AI, Foundry Guardrails & AI Gateway

10 Secure Servers and Virtual Machines

10.1 Disk Encryption 10.2 Azure Bastion and JIT VM Access 10.3 Azure Arc and Defender for Servers 10.4 Trusted Launch, VM Security Features & Machine Configuration

11 Application Platform Security

11.1 Containers: AKS, ACR, ACI, Container Apps & Defender for Containers 11.2 Azure Functions and Logic Apps Security 11.3 Azure App Service Security 11.4 Web Application Firewall and API Management Protection

12 Defender for Cloud Security Posture

12.1 Defender CSPM and Secure Score 12.2 Workload Protection Plans and Multicloud Connectors 12.3 Vulnerability Management and Defender EASM

13 Microsoft Sentinel Activity and Event Collection

13.1 Workspaces, Roles & Content Hub 13.2 Data Connectors, Syslog/CEF & Windows Event Collection 13.3 Custom Tables, Retention & Purview Audit 13.4 Automation Rules and Playbooks

14 Microsoft Security Copilot & Final Review

14.1 Microsoft Security Copilot Workspaces and Roles 14.2 Plugins and Security Agents 14.3 Final Review and Exam-Day Strategy

3.2 Access Control and Firewall for Key Vault

Key Takeaways Explain This Topic AI

Control plane manages the vault resource with Azure RBAC; data plane manages keys, secrets, and certificates via Azure RBAC (preferred) or legacy access policies.

Key Vault Contributor can manage the vault and may escalate into data access via access policies—tightly restrict Contributors and use least-privilege data roles.

Private endpoints plus disabled public access provide the strongest network isolation; service endpoints and IP rules are intermediate controls.

Trusted Microsoft services can bypass the firewall when allowed, but still need Entra authentication and data-plane permissions; not every Azure service is on the list (for example Azure DevOps is not).

Apps should use managed identities with Key Vault Secrets User or Crypto User roles rather than embedding client secrets in configuration.

Last updated: July 2026

Two Planes, Two Authorization Stories

Every SC-500 scenario about Key Vault access starts with this split:

Plane Endpoint (global) What you do Authorization

Control plane management.azure.com Create/delete vault, set networking, tags, permission model, access policies Azure RBAC on the vault / RG / subscription

Data plane <vault-name>.vault.azure.net Get/set secrets, crypto ops, cert lifecycle Azure RBAC for Key Vault (preferred) or vault access policies (legacy)

Authentication for both planes is Microsoft Entra ID. Having a valid Entra token is never enough—you still need the right role or policy and an allowed network path for data-plane calls when the firewall is on.

  • Access Policies vs Azure RBAC Data Plane
  • Legacy access policies

An access policy is a vault-level entry that grants a specific security principal (user, group, service principal, or managed identity) a set of key, secret, and/or certificate permissions ( get , list , set , delete , purge , crypto ops, and so on). Policies live on the vault resource . They do not manage who can create the vault or change its firewall—that remains Azure RBAC on the control plane.

Limits of access policies:

  • Vault-wide grants; poor fit for centralized identity governance across many vaults
  • Harder to audit consistently with Azure Activity Log role assignment history
  • Mixing models is confusing; switching to RBAC clears policy-based data access
  • Azure RBAC for Key Vault data plane

RBAC assigns built-in (or custom) roles at management group, subscription, resource group, vault, or even individual key/secret/certificate scope. Microsoft recommends one vault per application per environment with roles at vault scope , not per-object assignments, except for rare sharing cases.

Built-in data-plane role Capability summary

Key Vault Administrator Full data-plane ops on all object types; cannot manage vault resource or role assignments

  • Key Vault Reader Metadata only—not secret values or key material
  • Key Vault Secrets User Read secret contents (typical app runtime role)
  • Key Vault Secrets Officer Manage secrets (set/delete/etc.), not permission management
  • Key Vault Crypto User Perform crypto operations with keys
  • Key Vault Crypto Officer Manage keys (including rotation policy)
  • Key Vault Certificates Officer / Certificate User Manage or consume certificates
  • Key Vault Purge Operator Permanently purge soft-deleted vaults/objects when purge protection allows

Key Vault Data Access Administrator Assign/remove a constrained set of Key Vault data roles (with ABAC conditions)

Exam trap: Key Vault Contributor is a control-plane role. It lets someone manage vault properties. With the access-policy model, a Contributor can often grant themselves data-plane access by editing policies. Treat Contributor as privileged. Prefer RBAC data plane so management of the resource and use of secrets stay cleanly separated.

Who Typical roles

Platform / vault owners Limited Owner/User Access Administrator + Key Vault Contributor only for those who must change networking/SKU; Key Vault Data Access Administrator for granting app access

  • Security officers managing objects Secrets Officer / Crypto Officer / Certificates Officer
  • Applications (managed identity) Secrets User and/or Crypto User—never Officer/Administrator by default
  • Auditors Key Vault Reader + Log Analytics reader on diagnostics
  • Who Can Manage the Vault vs Use Secrets

Think in least privilege :

Manage vault (networking, diagnostics, locks, delete): control-plane RBAC such as Contributor or custom roles with Microsoft.KeyVault/vaults/* write actions.

Use secrets (read at runtime): data-plane Secrets User (or access-policy get / list on secrets only).

Rotate / write secrets : Secrets Officer—not every app identity.

Purge : separate Purge Operator or highly restricted Administrator path; combine with purge protection.

Scenario: DevOps engineers deploy App Service slots. Give the deployment pipeline identity Secrets Officer (or scoped set) only on the non-prod vault. Give the App Service managed identity Secrets User only. Do not put human Contributors on production vaults without PIM and justification.

  • Firewall, Service Endpoints, and Private Endpoints
  • Firewall modes (conceptual)
  • Mode Behavior
  • Firewall disabled (default) Data plane reachable from any network; Entra + authz still required

Allow specific VNets / IPs Default action Deny; only listed subnets (with service endpoint) and public IPv4 ranges

  • Trusted services exception Listed Microsoft services may bypass network rules when the bypass is enabled
  • Public access disabled Only private endpoints (plus trusted services bypass behavior as documented)

Constraints to memorize:

  • Max 200 virtual network rules and 1000 IPv4 rules
  • IP rules accept public IPv4 only—not RFC1918 private ranges
  • Service endpoint: enable Microsoft.KeyVault on the subnet, then add the subnet to the vault network rules

After rules apply, portal users may open the vault blade but fail to list secrets if their client IP is not allowed

Private endpoints (Private Link)

Private endpoints map the vault’s data-plane FQDN into a private IP in your VNet via Private Link DNS ( privatelink.vaultcore.azure.net ). Best practice for sensitive workloads:

  • Create private endpoint + private DNS zone links for all consuming VNets/hubs
  • Set public network access to Disabled
  • Confirm apps use the vault URI and resolve privately

Public DNS may still resolve the vault name to a public ingress that refuses traffic when public access is disabled—that is expected and does not expose private IP or secrets.

Service endpoints vs private endpoints: Service endpoints keep traffic on the Azure backbone to the public data-plane VIP but restrict source VNets. Private endpoints bring the service into your private address space and support full public disablement. SC-500 “most secure network isolation” answers usually prefer private endpoint + public access disabled .

Trusted Microsoft Services

When the firewall is on, you may allow trusted Microsoft services to bypass network rules. Important nuances:

Bypass covers a documented list (Storage CMK, SQL TDE BYOK, Disk Encryption, Backup, Resource Manager template deployment of secure values, and many others).

Services not on the list (classically Azure DevOps custom pipelines) do not get blanket bypass—use private endpoints, self-hosted agents on allowed VNets, or IP rules.

Bypass does not skip authentication or authorization; the service still needs a valid identity and data-plane rights.

With Network Security Perimeter in enforced mode, trusted bypass can be overridden—perimeter rules govern access.

Managed Identity Access Patterns

Preferred application pattern:

Enable system-assigned or user-assigned managed identity on App Service, Function, VM, AKS workload identity, Logic Apps, and so on.

Assign Key Vault Secrets User (and Crypto User if needed) on the vault or secret scope.

Application retrieves secrets via SDK/REST using Entra token for that identity— no client secret in app settings .

Combine with Key Vault references in App Service configuration where supported, still backed by the app’s managed identity.

Optionally constrain with ABAC conditions on secret names (preview capabilities for secret data actions).

Anti-pattern (exam wrong answer): Store a service principal password in App Service application settings that is also used to call Key Vault. Prefer managed identity end-to-end.

User-assigned identity shines when multiple resources share one identity lifecycle or when blue/green slots need a stable identity across restarts.

SC-500 Exam Traps (Access & Network)

Contributor on the vault ≠ ability to read secrets under pure RBAC without a data role—but with access policies, Contributor can self-elevate.

Key Vault Reader cannot read secret values .

Firewall does not secure control plane; private endpoint is about data plane connectivity.

Trusted services list is not “all of Azure.”

Apps need Secrets User , not Key Vault Administrator.