ISO 27001:2022 on Microsoft 365: Annex A, SoA and Evidence

SOC 2 and ISO 27001Published Last reviewed November 20268 min read

Short answer

ISO/IEC 27001:2022 is the only edition certification bodies audit against now; certificates based on the 2013 edition expired or were withdrawn when the transition ended on October 31, 2025. Its Annex A has 93 controls in four themes. Companies on Microsoft 365 can show most technical controls from Entra, Intune, Defender and Purview, but auditors also test the Statement of Applicability, risk assessment and management review.

Check where you stand: take the SOC 2 and ISO 27001 check. About two minutes, no email needed.

Update, November 2026

On October 28, 2026, the AICPA proposed revised SOC 2 Trust Services Criteria, with comments due January 15, 2027 and a proposed effective date for engagements beginning on or after December 31, 2027, so SOC 2 to ISO 27001 mappings like the one in this post will need a refresh if the changes are approved. ISO/IEC 27001:2022 with Amendment 1:2024 remains the current edition. Since this post, one Ethereum Tech client received its ISO/IEC 27001:2022 certificate from its certification body.

ISO/IEC 27001:2022 is now the only edition a certification body will audit you against. The transition from the 2013 edition ended on October 31, 2025, and certificates still based on the 2013 version expired or were withdrawn at that point. For a company that runs on Microsoft 365, the Annex A technical controls map well onto Microsoft Entra ID, Intune, Defender and Purview. The audit is usually decided somewhere else.

Our point of view, after more than 100 engagements across Microsoft 365 and Azure: the tenant evidence is the part most teams already have. The management system around it, meaning the risk assessment, the Statement of Applicability, the internal audit and the management review, is where first audits stumble.

What changed in Annex A between ISO 27001:2013 and ISO 27001:2022?

Annex A went from 114 controls in 14 clauses to 93 controls in four themes. The list now mirrors ISO/IEC 27002:2022, which groups controls as organizational, people, physical or technological and adds attributes you can use to sort them.

ThemeControlsCountExample controls
Organizational5.1 to 5.37375.15 Access control, 5.23 Information security for use of cloud services
People6.1 to 6.886.3 Information security awareness, education and training
Physical7.1 to 7.14147.4 Physical security monitoring
Technological8.1 to 8.34348.5 Secure authentication, 8.12 Data leakage prevention

Some 2013 controls were merged, a few were deleted and several are new. The new ones that matter most to a Microsoft 365 company are threat intelligence (5.7), information security for use of cloud services (5.23), ICT readiness for business continuity (5.30), configuration management (8.9), information deletion (8.10), data masking (8.11), data leakage prevention (8.12), monitoring activities (8.16), web filtering (8.23) and secure coding (8.28).

Clauses 4 through 10 were also realigned with the harmonized structure ISO uses for its management system standards. In February 2024 ISO published Amendment 1:2024, Climate action changes, which applies to ISO/IEC 27001:2022. Make sure the copy of the standard your team works from includes it.

What does the October 31, 2025 transition deadline mean now?

It means a certificate issued against ISO/IEC 27001:2013 is no longer valid. If a vendor sends you one, ask for the current certificate, and if your own transition slipped, talk to your certification body before planning anything else.

The rules came from IAF MD 26, the International Accreditation Forum’s mandatory document for this transition. It gave certification bodies 36 months from the last day of the publication month of ISO/IEC 27001:2022, which set the deadline at October 31, 2025. From April 30, 2024, initial certification and recertification audits had to use the 2022 edition. At the end of the transition, all certifications based on the 2013 edition were to expire or be withdrawn.

When you collect certificates from vendors, check the edition, the scope statement and the dates, and remember who stands behind them. ISO does not perform certification; certification bodies do, and accreditation bodies oversee them. The IAF ceased operations on January 1, 2026, and its work passed to the Global Accreditation Cooperation (Global ACI), so newer documents may cite that body instead.

What goes in an ISO 27001 Statement of Applicability?

The Statement of Applicability (SoA) lists the controls you need, why each is included, whether each is implemented, and why any Annex A control is excluded. Clause 6.1.3 d) requires all four.

Start from your risk treatment, not from Annex A. Clause 6.1.3 asks you to determine the controls your risk treatment needs, then compare them with Annex A to confirm nothing necessary was left out. The SoA records that comparison. An auditor reads it next to the risk register and expects each included control to trace back to a risk, a contract or a legal requirement.

For a company running on Microsoft 365, exclusions should be rare. Microsoft runs the data centers, but you still have offices, home workers and laptops, so most physical controls apply in some form. Secure coding (8.28) can be excluded if you truly develop no software, and that reason has to be written down.

One habit we ask of every client: add two columns the standard does not require, the control owner and where the evidence lives, such as a Purview policy name or an Entra access review. It turns each surveillance audit into a walk through the SoA instead of a scavenger hunt.

What will an ISO 27001 auditor ask to see from Microsoft 365, Entra and Purview?

Expect requests for configuration exports and records showing the controls in your SoA actually running in the tenant. Initial certification happens in two stages, a documentation and readiness review followed by an implementation audit, and surveillance audits then come at least once a calendar year across a three year cycle.

EvidenceWhere it livesISO 27001 Annex ASOC 2 criteria
Access review decisions and removalsMicrosoft Entra access reviews5.15, 5.18CC6.2, CC6.3
Privileged role assignments and activationsPrivileged Identity Management8.2CC6.3
MFA policy and registration statusConditional Access, authentication methods registration details8.5CC6.1
Label taxonomy and publishing policiesMicrosoft Purview sensitivity labels5.12, 5.13C1.1
DLP policies and alert handlingMicrosoft Purview Data Loss Prevention8.12CC6.7
Audit logging, retention and incident ticketsMicrosoft Purview Audit, Microsoft Defender XDR8.15, 8.16CC7.2
Retention and deletion policiesMicrosoft Purview Data Lifecycle Management8.10C1.2
Device compliance and configuration baselinesMicrosoft Intune8.1, 8.9CC6.8
Review of Microsoft as a supplierMicrosoft certificates and SoA from the Service Trust Portal5.19, 5.23CC9.2

Two Microsoft tools help you prepare. Microsoft Purview Compliance Manager offers an ISO/IEC 27001:2022 assessment as a premium regulation template, and A5, E5 and G5 subscriptions include three premium templates. For Azure workloads, Microsoft Defender for Cloud can add ISO IEC 27001:2022 to its regulatory compliance dashboard. Both show configuration gaps. Neither is evidence on its own, and Microsoft itself says compliance in Azure Policy is only a partial view of your overall status. An auditor wants records and decisions, not a score.

Microsoft’s own ISO/IEC 27001 certificate covers its services, and you can use it when you assess Microsoft as a supplier. Microsoft is clear that you remain responsible for engaging an assessor for the controls and processes inside your own organization. Our Microsoft 365 compliance work usually starts by comparing the SoA with what the tenant actually enforces.

How much does SOC 2 and ISO 27001 evidence overlap?

Most of the technical evidence is shared. The same access review, Conditional Access export or Purview policy can support an Annex A control and a Trust Services Criterion at once, as the table above shows.

The difference is what each one judges. ISO 27001 ends in a certificate from a certification body stating that your management system meets clauses 4 through 10, with Annex A controls selected through risk treatment. SOC 2 is an attestation report from a CPA firm on whether your controls met the Trust Services Criteria, and a Type 2 tests them across a defined period.

That changes where the effort goes. A SOC 2 Type 2 needs operating evidence from every part of the period. An ISO auditor samples records too, but spends more time on whether the ISMS itself works: the internal audit (9.2), the management review (9.3) and how you handle nonconformities and corrective action.

If you hold one and are adding the other, build one control set and map it both ways instead of running two programs side by side. Our GRC advisory and planning work often begins with exactly that mapping.

If you are preparing for a first ISO 27001 audit on Microsoft 365, or need to bring an older SoA in line with the 2022 Annex A, book a 30 minute call and we can walk through where you stand.

Frequently asked questions

Do we need our own copy of the ISO 27001 standard?

Yes. Work from a licensed copy of ISO/IEC 27001:2022 with Amendment 1:2024, and keep ISO/IEC 27002:2022 nearby for control guidance. Both are sold by ISO and national standards bodies. Auditors expect your ISMS to follow the actual requirement text, not a summary found online.

Can Microsoft’s ISO 27001 certificate cover our company?

No. Microsoft’s certificate covers Microsoft’s own services and operations. Your certificate covers your ISMS and the scope you define. You can use Microsoft’s certificate and Statement of Applicability as evidence that you assessed a key cloud supplier, which supports Annex A controls 5.19 and 5.23.

How long does an ISO 27001 certificate last?

Certification runs on a three year cycle that begins with the certification decision. Surveillance audits happen at least once a calendar year in between, and the first must take place within 12 months of initial certification. A recertification audit before the cycle ends starts the next one.

Do we have to implement all 93 Annex A controls?

No. Annex A is a reference list you compare against. You include the controls your risk treatment needs and justify any exclusions in the Statement of Applicability. Clause 6.1.3 also notes that Annex A is not exhaustive, so you can add controls of your own.

Is a high Compliance Manager score enough to pass?

No. Compliance Manager is useful for tracking improvement actions against the ISO/IEC 27001:2022 template, but the score is not audit evidence. Auditors want policy exports, records, tickets and minutes that show controls working, plus the management system clauses that no tenant setting can satisfy.

Keep reading

Related guides

Have a question this raised?

Bring it to a 30 minute call and leave knowing where you stand and what comes next.

Book a 30 minute call

(786) 577-9743sales@ethereumtech.ai

Or take the two minute starting point check