Zero Trust and Secure Architecture on Azure: Defense in Depth, Landing Zone Security, Threat Modeling and Review Checklist

Microsoft Azure Architect Technologies AZ 300 55 min min read Updated: Nov 17, 2026 Advanced
Zero Trust and Secure Architecture on Azure: Defense in Depth, Landing Zone Security, Threat Modeling and Review Checklist
Advanced Topic 3 of 3

Zero Trust Principles

PrincipleMeaningAzure examples
Verify explicitlyAuthenticate and authorize using all signalsMFA, Conditional Access, device compliance
Use least privilegeJust enough and just-in-time accessRBAC, PIM, JIT VM access, managed identities
Assume breachLimit blast radius, monitor and encryptSegmentation, Defender, Sentinel, encryption

Defense in Depth: Layers

LayerControls
PhysicalMicrosoft datacenter security
IdentityEntra ID, MFA, Conditional Access, PIM, passwordless
PerimeterDDoS Protection, Front Door + WAF, Azure Firewall
NetworkSegmentation, NSGs, private endpoints, no public IPs, Bastion
ComputePatching, Defender for Servers, trusted launch, JIT
ApplicationSecure coding, secrets in Key Vault, WAF, dependency scanning
DataEncryption, classification, Purview, backups, immutability
OperationsMonitor, Sentinel, Policy, incident response

Shared Responsibility

On-premIaaSPaaSSaaS
Data and identitiesYouYouYouYou
AppsYouYouSharedMicrosoft
OSYouYouMicrosoftMicrosoft
Network controlsYouSharedSharedMicrosoft
PhysicalYouMicrosoftMicrosoftMicrosoft

You are always responsible for your data, identities and access.

Threat Modeling with STRIDE

ThreatQuestionTypical control
SpoofingCan someone pretend to be a user or service?Strong auth, managed identity
TamperingCan data be changed?Signing, integrity checks, immutability
RepudiationCan an action be denied?Audit logs
Information disclosureCan data leak?Encryption, private endpoints, RBAC
Denial of serviceCan it be overloaded?DDoS, autoscale, rate limits
Elevation of privilegeCan a user gain more rights?Least privilege, PIM

Secure Reference Design

  1. Users sign in with Entra ID + MFA + Conditional Access and reach the app through Front Door with WAF
  2. The app runs in a spoke VNet, with no public IPs on VMs. Admins use Bastion and PIM
  3. The app accesses SQL, Storage and Key Vault with managed identities over private endpoints
  4. All traffic to the internet goes through Azure Firewall in the hub
  5. Policy enforces tags, allowed regions, encryption and diagnostics
  6. Logs flow to Log Analytics and Sentinel. Defender for Cloud monitors posture
  7. Backups are immutable and replicated. IaC and pipelines use OIDC with least privilege

Architecture Review Checklist

  • Is MFA enforced for everyone, and are break-glass accounts protected and monitored?
  • Are standing Owner/Contributor assignments minimized and replaced with PIM?
  • Do any resources have public endpoints? Can private endpoints replace them?
  • Are secrets in Key Vault and managed identities used instead of passwords?
  • Is data encrypted at rest and in transit, and who controls the keys?
  • Are NSG/firewall rules specific, with no any-any rules and no open management ports?
  • Is logging enabled, centralized, retained and alerting?
  • Are backups tested, protected from deletion and meeting RPO/RTO?
  • Do Policy and Defender show non-compliance, and who fixes it?
  • Is there an incident response plan and regular exercises?

Practice

  1. Run STRIDE on a simple web app with a database and write one control per threat
  2. Review a sample design with the checklist and list five findings
  3. Explain Zero Trust to a manager in three sentences

Conclusion

Secure designs combine identity, network, compute, application, data and operations controls following Zero Trust: verify explicitly, use least privilege and assume breach. Use STRIDE and a checklist during every design review.

Quick Summary: Zero Trust; layers; shared responsibility; STRIDE; reference design; checklist.

Get Newsletter

Subscibe to our newsletter and we will notify you about the newest updates on Edugators