Study guide
5.6 Bastion and Key Vault for Administration and Secrets
Azure SC-900 Study Guide Exam
Track your progress as you read
Finished sections get a check mark.
1 Orientation: SC-900 Audience, Format, Scoring, Retakes, and Study Map
1.1 Credential Purpose and Audience 1.2 Exam Duration, Seat Duration, and Experience 1.3 Scoring, Scaled Score, and Pass-Rate Myths 1.4 Retake Policy and Certification Lifecycle 1.5 Scheduling, Price, and Delivery Options 1.6 Skills Measured and Study Map
2 Security, Compliance, and Identity Concepts: Zero Trust, Shared Responsibility, and GRC
2.1 Shared Responsibility Model 2.2 Defense in Depth and the CIA Triad 2.3 Zero Trust Model 2.4 Encryption, Hashing, and Data States 2.5 Governance, Risk, and Compliance 2.6 Identity Perimeter, Authentication, Authorization, and Federation
3 Microsoft Entra ID: Identities, Hybrid Identity, and Authentication
3.1 Microsoft Entra ID Foundations 3.2 Identity Types and Directory Objects 3.3 Hybrid Identity and Entra Connect Concepts 3.4 Authentication Methods and Sign-in Assurance 3.5 Multifactor Authentication 3.6 Password Protection, Self-Service Password Reset, and External Identities
4 Microsoft Entra Access Management, Governance, PIM, and Identity Protection
4.1 Conditional Access Purpose 4.2 Signals and Controls 4.3 Microsoft Entra Roles and Role-Based Access Control 4.4 Identity Governance, Entitlement Management, and Lifecycle Governance 4.5 Access Reviews and Privileged Identity Management 4.6 Microsoft Entra ID Protection and Risk
5 Azure Infrastructure Security: DDoS, Firewall, WAF, NSGs, Bastion, and Key Vault
5.1 Choose the Right Infrastructure Security Control 5.2 Azure DDoS Protection for Availability 5.3 Azure Firewall for Centralized Network Policy 5.4 Web Application Firewall for HTTP Workloads 5.5 Virtual Networks, Subnets, and Network Security Groups 5.6 Bastion and Key Vault for Administration and Secrets
6 Defender for Cloud: CSPM, Cloud Workload Protection, and Secure Score
6.1 Defender for Cloud Purpose and Exam Role 6.2 CSPM, Foundational Posture, and Defender CSPM 6.3 Policies, Standards, and Security Recommendations 6.4 Secure Score and Remediation Priority 6.5 Regulatory Compliance and Multicloud Posture 6.6 Cloud Workload Protection and Defender Plans
7 Microsoft Sentinel: SIEM, SOAR, Analytics, Hunting, Workbooks, and Playbooks
7.1 Sentinel as SIEM and SOAR 7.2 Data Connectors and Security Signals 7.3 Analytics Rules, Incidents, and Detection 7.4 Workbooks for Visual Review 7.5 Hunting, KQL Awareness, and Notebooks 7.6 Automation Rules and Logic Apps Playbooks
8 Microsoft Defender XDR: Office, Endpoint, Cloud Apps, Identity, Vulnerability, and Threat Intelligence
8.1 Defender XDR Suite and Microsoft Defender Portal 8.2 Defender for Office 365 8.3 Defender for Endpoint 8.4 Defender for Cloud Apps 8.5 Defender for Identity 8.6 Vulnerability Management and Threat Intelligence
9 Microsoft Purview, Service Trust, Privacy, Compliance Manager, and Compliance Score
9.1 Service Trust Portal and Assurance Resources 9.2 Privacy Principles and Microsoft Priva 9.3 Microsoft Purview Portal 9.4 Compliance Manager Assessments 9.5 Compliance Score and Improvement Actions 9.6 Scenario Selection for Trust, Privacy, and Compliance Manager
10 Microsoft Purview Data Classification, Labels, DLP, Retention, eDiscovery, and Audit
10.1 Data Classification Foundations 10.2 Content Explorer and Activity Explorer 10.3 Sensitivity Labels and Label Policies 10.4 Data Loss Prevention 10.5 Retention, Records Management, and Label Policies 10.6 eDiscovery, Audit, and Insider Risk Management
11 SC-900 Product Selection Playbooks and Common Microsoft Rebrand Traps
11.1 Read the Scenario Before Picking a Product 11.2 Entra Playbook for Identity, Access, and Governance 11.3 Defender Playbook for Protection, Detection, and Posture 11.4 Sentinel Playbook for SIEM, SOAR, and Hunting 11.5 Purview Playbook for Compliance, Data, and Risk 11.6 Renamed Products and Similar-Name Traps 11.7 Microsoft Learn Practice Assessment Review Loop
12 Final SC-900 Review, Timed Practice, Exam Day, and Next Certification Path
12.1 Domain-Weighted Final Review Plan 12.2 Timed Practice and Pacing 12.3 Exam Sandbox and Question Experience 12.4 Exam-Day Logistics and Boundaries 12.5 Scoring, Retakes, and After-Exam Decisions 12.6 Final Memory Check and Scenario Drills 12.7 Next Certification Path After SC-900
5.6 Bastion and Key Vault for Administration and Secrets
Key Takeaways Explain This Topic AI
Azure Bastion is a managed PaaS service that provides RDP/SSH to VMs over TLS (port 443) directly in the portal using the VM's private IP, so VMs need no public IP, agent, or special client.
Bastion SKUs scale capability: Developer (free, test, one VM), Basic, Standard (native client, IP-based connections, custom ports, file transfer), and Premium (session recording, private-only deployment).
Azure Key Vault centralizes three things: secrets (passwords, connection strings, API keys), keys (cryptographic keys for encryption), and certificates (TLS/SSL); access needs Microsoft Entra ID authentication plus Azure RBAC or vault access policies.
Key Vault Standard is software-protected (FIPS 140-2 Level 1); Premium is HSM-backed (FIPS 140-3 Level 3). Encryption at rest (Azure-managed or customer-managed keys) and in transit (TLS) are core to data protection.
Last updated: June 2026
Secure the Administration Path with Azure Bastion
Azure Bastion and Azure Key Vault are frequently tested as product-matching controls, and they solve different problems. Bastion is about how administrators connect to virtual machines . Key Vault is about where applications and administrators store sensitive values .
Azure Bastion is a fully managed platform-as-a-service (PaaS) service for RDP and SSH connectivity to virtual machines over TLS (port 443) . You deploy it into the VM's virtual network, and you connect to VMs directly in the Azure portal using the VM's private IP address . The headline exam points: the VMs do not need public IP addresses , no agent runs inside them, and (for portal access) no special client software is required — just a browser.
Because there is no public RDP/SSH port open to the internet, Bastion materially shrinks the attack surface that brute-force and port-scanning attacks target, supporting Zero Trust principles.
Bastion comes in tiers of increasing capability:
- SKU Positioned for Notable capabilities
- Developer Dev/test, no cost; one VM at a time; no VNet peering Basic browser RDP/SSH
- Basic Production, fixed dedicated capacity Portal-based RDP/SSH, no advanced features
Standard Production with advanced needs Native client, IP-based connections, custom ports, shareable links, file transfer
Premium Sensitive/regulated workloads Everything in Standard plus session recording and private-only deployment
For SC-900 you do not memorize SKU feature lists, but knowing Bastion = private-IP RDP/SSH over TLS without public VM IPs is essential.
Centralize Secret Material with Azure Key Vault
Azure Key Vault centralizes sensitive material so it is not scattered through source code or app settings that many people can read. Microsoft documents three problem areas Key Vault solves — and recognizing all three is a common exam point:
- Key Vault object What it stores Examples
- Secrets Arbitrary sensitive strings Passwords, database connection strings, API keys, tokens
- Keys Cryptographic keys RSA/EC keys used for encryption, signing, wrapping
Certificates TLS/SSL certificates Certificates for Azure and connected web resources, with lifecycle management
Access control is central. A caller must be authenticated and authorized before touching stored material. Authentication is always done through Microsoft Entra ID . Authorization can use either Azure role-based access control (RBAC) or legacy Key Vault access policies — RBAC is the recommended model. Tie this to Zero Trust and least privilege : store sensitive values centrally, grant only the access each identity needs, and audit access rather than distributing secrets freely.
Key Vault has two tiers that map to a frequently tested compliance distinction:
Standard — software-protected keys; validated to FIPS 140-2 Level 1 .
Premium — HSM (hardware security module) -backed keys in a hardware boundary; validated to FIPS 140-3 Level 3 .
For stricter single-tenant HSM isolation, Microsoft also offers Azure Key Vault Managed HSM , but Standard versus Premium is what SC-900 expects you to recognize.
Encryption at Rest and in Transit, and the Selection Trap
Key Vault underpins encryption , a CIA-triad confidentiality control. Encryption at rest protects stored data: Azure encrypts data at rest by default (for example, Azure Storage Service Encryption for blobs and files, and Transparent Data Encryption for Azure SQL). Customers can supply customer-managed keys (CMK) stored in Key Vault instead of using Microsoft-managed keys, giving control over the key lifecycle. Encryption in transit protects data moving across networks, primarily via TLS — the same protocol Bastion uses for its RDP/SSH sessions.
SC-900 expects you to know both states of data must be protected and that Key Vault is where customer-managed encryption keys and certificates live.
Bastion and Key Vault frequently combine with the chapter's network controls. A VM might sit in a private subnet protected by NSGs , be administered through Bastion , draw secrets from Key Vault , and route egress through Azure Firewall . A web app might use Key Vault for its TLS certificate while WAF inspects its HTTP requests.
Avoid the matching trap:
Do not choose Bastion when the prompt is about SQL injection (WAF), DDoS mitigation (DDoS Protection), or storing secrets (Key Vault).
Do not choose Key Vault when the prompt asks how admins can RDP/SSH to a VM without a public IP (Bastion).
Bastion protects the administrative access path ; Key Vault protects secret material .
Microsoft Entra ID authenticates Key Vault access; RBAC or access policies authorize it.
Both support defense in depth but neither replaces a firewall or an NSG.
Soft Delete, Purge Protection, and Managed Identities
Key Vault includes resilience features that protect against accidental or malicious loss. Soft delete retains deleted vaults and objects for a recoverable retention period (default 90 days) so they can be restored. Purge protection goes further: while enabled, even a soft-deleted vault or object cannot be permanently purged until the retention period elapses, blocking an attacker (or a mistake) from immediately erasing keys. These are commonly enabled together for production vaults and are worth recognizing as data-protection controls.
A related identity concept is the managed identity . Rather than storing a Key Vault credential inside the application (which would defeat the purpose), an Azure resource can be given a managed identity in Microsoft Entra ID and granted access to the vault via RBAC. The app then authenticates as itself with no secret in code — a clean illustration of Zero Trust and least privilege that the exam likes to pair with Key Vault.
- Key Vault feature Purpose
- Soft delete Recover deleted vaults/objects within a retention window
- Purge protection Prevent permanent deletion until retention elapses
- RBAC authorization Grant least-privilege access per identity
- Managed identity access Apps read secrets with no credential in code
- A Combined Worked Scenario
Consider a regulated web application. Its TLS certificate lives in Key Vault Premium (HSM-backed, FIPS 140-3 Level 3); its database password is a Key Vault secret retrieved at runtime via the app's managed identity . Administrators patch the backend VMs through Azure Bastion over TLS on the VMs' private IPs — no public RDP/SSH exposure. The VMs sit in NSG-filtered subnets, egress through Azure Firewall , and the public web tier is fronted by WAF .
Each control answers a different exam clue: certificate/secret storage → Key Vault; VM admin without public IP → Bastion; subnet filtering → NSG; central egress → Azure Firewall; web exploits → WAF. Mapping the clue to the control is the entire skill this chapter builds.