Secure servers and virtual machines
Disk encryption, Azure Bastion, just-in-time access, Azure Arc, Defender for Servers onboarding, settings and agentless scanning, Trusted launch features, and Machine Configuration.
- 22 min
- 9 concepts
- Try it yourself
- 4-question check
Learn
Servers are still the most attacked part of most estates. Harden them from boot (Trusted launch), close management ports (Bastion and JIT), encrypt their disks, extend controls to servers outside Azure with Arc, and protect them with Defender for Servers.
- 1
Implement and configure disk encryption
All managed disks have server-side encryption (platform or customer-managed keys via a disk encryption set). Encryption at host also encrypts temp disks and caches and is Microsoft's recommended option. Azure Disk Encryption (BitLocker/DM-Crypt in the guest) is scheduled to retire in September 2028. Confidential disk encryption is for confidential VMs.
Remember: New VMs: encryption at host.
- 2
Plan and implement Azure Bastion
Bastion provides RDP and SSH over TLS without public IPs on VMs, in a dedicated
AzureBastionSubnet(/26 or larger). Standard and Premium add native client, IP-based connection, shareable links and (Premium) session recording and private-only deployment. Use NSG rules on VM subnets to allow RDP/SSH only from the Bastion subnet.Remember: Only allow 3389/22 from AzureBastionSubnet.
- 3
Enable and enforce use of just-in-time (JIT) VM access
JIT (Defender for Servers Plan 2) locks management ports with NSG or Azure Firewall rules and opens them only on request, for an approved IP and a limited time. Requests are logged and need Azure RBAC permissions. Recommendations flag VMs with open management ports.
Remember: JIT = management ports closed until requested.
- 4
Extend security controls to hybrid and multicloud servers by using Azure Arc
Azure Arc-enabled servers project on-premises and other-cloud machines into Azure, so you can apply Azure Policy and Machine Configuration, RBAC, tags, Update Manager, Azure Monitor Agent, Defender for Servers and managed identity to them.
Remember: Arc brings Azure governance to every server.
- 5
Onboard servers to Defender for Servers in Defender for Cloud, including hybrid and multicloud scenarios
Enable Defender for Servers Plan 1 or Plan 2 at subscription (or resource) level. Azure VMs are covered automatically; on-premises servers connect through Azure Arc; AWS and GCP servers via multicloud connectors (which can auto-provision Arc). Plan 2 adds JIT, agentless scanning, file integrity monitoring and more.
Remember: Non-Azure servers: Arc or multicloud connectors.
- 6
Configure Defender for Servers settings, including vulnerability scanning, and endpoint detection and response (EDR)
Defender for Servers integrates Defender for Endpoint (EDR, antivirus) with automatic onboarding, and Defender Vulnerability Management for vulnerability assessment. Configure the integration, EDR settings, and review recommendations such as 'EDR solution should be installed'.
Remember: EDR comes from Defender for Endpoint integration.
- 7
Implement and manage agentless scanning for VMs in Defender for Servers
Agentless scanning takes disk snapshots and analyses them out-of-band for vulnerabilities, software inventory, secrets and malware, with no agent and no performance impact. Enable it in Defender for Servers Plan 2 or Defender CSPM settings; exclude VMs by tag if needed.
Remember: Vulnerabilities without an agent: snapshot scanning.
- 8
Configure security features on a VM, including secure boot, virtual Trusted Platform Module (vTPM), integrity monitoring, and security type
Trusted launch (default security type for Gen2 VMs) gives Secure Boot (only signed boot components), vTPM (measured boot, BitLocker keys, attestation) and boot integrity monitoring via the Guest Attestation extension reported to Defender for Cloud. Confidential VMs add hardware-based memory encryption.
Remember: Trusted launch = Secure Boot + vTPM + boot integrity.
- 9
Enforce security configuration of Azure-managed servers by using Azure Machine Configuration
Azure Machine Configuration (formerly guest configuration) audits and enforces settings inside the OS (for example password policy, installed software, Windows security baselines) through Azure Policy, on Azure VMs and Arc-enabled servers, with audit or audit and auto-correct modes.
Remember: Settings inside the OS: Machine Configuration.
Defender for Servers plans (key differences)
| Feature | Plan 1 | Plan 2 |
|---|---|---|
| Defender for Endpoint integration | Yes | Yes |
| Vulnerability management | Basic | Premium add-on features |
| Just-in-time VM access | No | Yes |
| Agentless scanning | No | Yes |
| File integrity monitoring | No | Yes |
Try it
Which control fits?
This interactive part needs JavaScript.
In the portal
- JITAzure portal: Microsoft Defender for Cloud > Workload protections > Just-in-time VM access
- BastionAzure portal: Bastions > Create
- Arc serversAzure portal: Azure Arc > Machines
- Defender for Servers settingsAzure portal: Microsoft Defender for Cloud > Environment settings > your subscription > Defender plans > Servers > Settings
Key terms
Click a card to see the definition.
Check your understanding
4 questions. Score 80% or more and these skills are marked as confident in your SC-500 study plan.
Which Defender for Servers plan includes JIT VM access?
JIT is a Plan 2 feature.
What must the Bastion subnet be called?
Exact name required.
Which audits settings inside the guest OS through Azure Policy?
Formerly guest configuration.
How are on-premises servers onboarded to Defender for Servers?
Arc projects them into Azure.
Sources
- Microsoft Learn: Overview of managed disk encryption options
- Microsoft Learn: Just-in-time machine access
- Microsoft Learn: Trusted launch for Azure VMs
- Microsoft Learn: Defender for Servers overview
- Microsoft Learn: Agentless machine scanning
- Microsoft Learn: Azure Machine Configuration
Facts in this lesson are from Microsoft Learn. This site isn't affiliated with Microsoft.