Study guide
3.7 Azure Compliance, Privacy, and Trust
Microsoft Azure Fundamentals AZ-900
Track your progress as you read
Finished sections get a check mark.
1 Introduction
About the Microsoft Azure Fundamentals (AZ-900) Exam Study Strategies and Exam Tips
2 Domain 1: Cloud Concepts (25-30%)
1.1 What Is Cloud Computing? 1.2 Cloud Service Models (IaaS, PaaS, SaaS) 1.3 Cloud Deployment Models (Public, Private, Hybrid) 1.4 The Consumption-Based Model
3 Domain 2A: Azure Architecture Components
2.1 Azure Regions and Availability Zones 2.2 Azure Resource Hierarchy (Management Groups, Subscriptions, Resource Groups) 2.3 Azure Resource Manager (ARM) Overview
4 Domain 2B: Azure Compute Services
2.3 Azure Virtual Machines 2.4 Azure App Service, Containers, and Serverless 2.5 Azure Virtual Desktop
5 Domain 2C: Azure Networking Services
2.6 Azure Virtual Networks (VNet) 2.7 Azure VPN Gateway and ExpressRoute 2.8 Azure Load Balancing and Content Delivery
6 Domain 2D: Azure Storage Services
2.9 Azure Storage Accounts and Services 2.10 Azure Database Services 2.11 Azure Data Services and Analytics
7 Domain 2E: Azure Identity, Access, and Security
2.11 Microsoft Entra ID (Azure Active Directory) 2.12 Azure RBAC, Zero Trust, and Defense in Depth 2.13 Azure Security Services
8 Domain 3A: Azure Cost Management
3.1 Factors That Affect Azure Costs 3.2 Azure Pricing Calculator and Cost Management 3.3 Using Tags for Cost Management and Organization
9 Domain 3B: Azure Governance and Compliance
3.3 Azure Policy 3.4 Resource Locks and Tags 3.5 Azure Blueprints, ARM Templates, and Bicep 3.6 Azure Governance Features: Putting It All Together
10 Domain 3C: Azure Monitoring and Management Tools
3.6 Azure Monitor and Service Health 3.7 Azure Compliance, Privacy, and Trust 3.8 Azure Activity Log, Diagnostics, and Resource Health
11 Additional Azure Services and Exam Review
Azure AI and Machine Learning Services Azure IoT and DevOps Services AZ-900 Exam Review: Key Concepts Summary Common AZ-900 Exam Scenarios and Practice
12 Advanced Azure Topics and Service Deep Dives
Azure Migration Services and Tools High Availability and Disaster Recovery in Azure Azure Networking: Private Link, Service Endpoints, and Bastion Azure Management Tools: Portal, CLI, PowerShell, and Cloud Shell Azure SLAs, Service Lifecycle, and Support Plans
3.7 Azure Compliance, Privacy, and Trust
Key Takeaways Explain This Topic AI
The Microsoft Trust Center is the single public hub for security, privacy, and compliance information across Azure, Microsoft 365, and Dynamics 365.
Azure holds 100+ compliance offerings (GDPR, HIPAA, ISO 27001, SOC 1/2/3, FedRAMP, PCI DSS); the Service Trust Portal hosts the actual downloadable audit reports.
Microsoft Purview delivers unified data governance — data catalog, data map, lineage, classification, and compliance scoring — across multi-cloud and SaaS estates.
Data residency = WHERE data physically lives; data sovereignty = WHICH laws govern it; data-location commitments are service-specific, so check each service's terms.
Composite SLAs multiply (99.9% x 99.9% ≈ 99.80%), so chaining dependent services lowers availability while adding redundancy raises it; free-tier services carry no SLA.
Last updated: October 2026
Quick Answer: Trust Center = the public marketing/info hub for trust topics. Service Trust Portal = where the downloadable audit reports live. Microsoft Purview = data governance and classification. Composite SLA = multiply the percentages (so it always goes down ). Free services have no SLA.
Microsoft Trust Center vs Service Trust Portal
The Microsoft Trust Center is the central, public-facing resource describing how Microsoft handles security, privacy, and compliance across Azure, Microsoft 365, and Dynamics 365. It hosts overviews, white papers, regional compliance summaries, and the privacy principles.
A closely related distractor is the Service Trust Portal (STP) — this is where you actually download the audit artifacts (ISO certificates, SOC 1/2/3 reports, FedRAMP packages). On the exam: "where do I read about Microsoft's practices?" → Trust Center; "where do I download the SOC 2 report for my auditor?" → Service Trust Portal.
Azure compliance offerings (100+)
Azure advertises more than 100 compliance offerings . You do not memorize all of them — you recognize what each acronym governs.
Global standards
- Standard What it covers
- ISO 27001 Information security management system (ISMS)
- ISO 27018 Protecting personally identifiable information in the cloud
- ISO 27701 Privacy information management
- SOC 1 / 2 / 3 Service Organization Controls — financial (1) and security/availability (2/3) audits
- CSA STAR Cloud Security Alliance security assessment
- Regional and industry standards
- Standard Region / Industry Plain-English purpose
- GDPR European Union General Data Protection Regulation — personal-data rights
- HIPAA US Healthcare Protects patient health information
- FedRAMP US Government Authorizes cloud services for federal agencies
- PCI DSS Global Finance Securing payment-card data
- NIST 800-53 US Federal Security and privacy controls baseline
- CJIS US Law Enforcement Criminal Justice Information Services
Scenario shortcut: a US hospital → HIPAA; a payment processor → PCI DSS; a US federal agency → FedRAMP; an EU citizen's personal data → GDPR.
Microsoft Purview: unified data governance
Microsoft Purview is the answer whenever a question mentions discovering, classifying, or governing data across an entire estate — on-premises, multi-cloud, and SaaS.
- Data catalog — searchable inventory of all data assets
- Data map — automated scanning and classification of sources
- Data lineage — traces how data flows and transforms end to end
- Compliance Manager — a compliance score with prioritized improvement actions
- Data Loss Prevention (DLP) and Information Protection — sensitivity labels that stop data leaving
Trap: do not confuse Purview with Azure Policy (enforces resource configuration rules) or Microsoft Defender for Cloud (threat protection). Purview = data governance.
The six privacy principles
- Principle Meaning
- Control You own and control your data
- Transparency Microsoft is open about how data is used
- Security Data is protected with encryption and strong controls
- Strong legal protections Microsoft defends your privacy rights legally
- No content-based targeting Your content is never mined for ads
- Benefits to you Data use improves your own experience
- Data residency vs data sovereignty
Data residency = the physical location where data is stored. Choosing West Europe keeps a resource's stored data in that region for most services, but data-location commitments are service-specific, and a few region pairs cross geographies (Brazil South is paired with South Central US).
Data sovereignty = the laws and jurisdiction that apply based on that location. Data in Germany is subject to German law. Sovereign/specialized regions (for example, Azure Government for US agencies) provide physically isolated environments for the strictest requirements.
Service Level Agreements (SLA) math
An SLA is Microsoft's financially-backed uptime guarantee for a paid service.
- SLA Nickname Approx. monthly downtime
- 99.9% three nines ~43 minutes
- 99.95% ~22 minutes
- 99.99% four nines ~4.3 minutes
- 99.999% five nines ~26 seconds
Composite SLA = multiply dependent services: 99.9% x 99.9% = 99.8001%, about 99.80% (lower than either part).
Adding redundancy (availability zones, paired regions) raises the effective SLA.
Free-tier services have no SLA at all.
Missing an SLA earns service credits — a discount, never a cash refund.
Worked SLA example
Suppose an application uses App Service (99.95%) in front of Azure SQL Database (99.99%) , and both must be up for the app to function. The composite SLA is 0.9995 x 0.9999 = 0.99940 , i.e. 99.94% — lower than either component. Add a second region behind Traffic Manager and the math flips: the failure probabilities multiply instead, so two 99.95% regions in parallel push the combined availability toward 99.9999%. The takeaway the exam wants: serial dependencies drag the SLA down; parallel redundancy pulls it up.
Common AZ-900 traps in this section
Trust Center vs Service Trust Portal — read about practices on the Trust Center; download the SOC/ISO reports from the Service Trust Portal.
Purview vs Policy vs Defender — Purview governs data ; Azure Policy governs resource configuration ; Defender for Cloud handles threats . The word "governance over a data estate" is your Purview signal.
Residency vs sovereignty — residency is the place ; sovereignty is the law . They are often offered as two options in the same question.
"No content-based targeting" is one of the six privacy principles — Microsoft does not mine your content for advertising.
Region choice — the chosen region drives where most services store data, but check each service's data-location terms before making a residency claim.
On the Exam: Two facts help with SLA questions — dependent services multiply (so the composite is always smaller), and free tiers have zero SLA. Each service has its own SLA terms; there is no global blanket SLA covering every Azure product at once.