3.7 Azure Compliance, Privacy, and Trust
Key Takeaways
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.
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.
An auditor asks your team to provide Microsoft's signed SOC 2 audit report to satisfy a compliance review. Where do you download the actual report?
The Service Trust Portal
The Azure portal Activity Log
Azure Advisor
The Microsoft Trust Center marketing pages
An application depends on two Azure services, each with a 99.9% SLA, and both must be available for the app to work. What is the composite SLA?
99.9%
99.95%
99.99%
99.80%
A data team needs to discover, classify, and trace the lineage of data spread across on-premises databases, multiple clouds, and SaaS apps. Which service fits?
Microsoft Purview
Azure Policy
Microsoft Defender for Cloud
Azure Key Vault
Which statement about Azure Service Level Agreements is correct?
All Azure services, including free tiers, carry an SLA
Free-tier services do not carry an SLA
Missing an SLA entitles you to a full cash refund
Adding redundant zones lowers your composite SLA
Sections you finish are checked off in the contents.