SOC 2 and ISO 27001Published Last reviewed November 20269 min read
Short answer
A SOC 2 Type 1 report shows your controls were suitably designed on one date. A Type 2 shows they operated effectively over a period, commonly three to twelve months, with the CPA firm’s test results. Most enterprise buyers want the Type 2. SaaS companies on Microsoft 365 and Azure should scope Security first, add Availability or Confidentiality when contracts require them, and keep logs for the full period.
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 released exposure drafts of 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; reports today still use the 2017 criteria with the 2022 revised points of focus. Since this post, one Ethereum Tech client moved from a SOC 2 Type 1 report to a clean Type 2 report issued by its CPA firm.
A SOC 2 Type 1 report shows a customer your controls were designed properly on one date. A Type 2 shows those controls actually operated across a period of months, with the auditor’s test results attached. Most enterprise security teams reviewing a SaaS vendor want the Type 2. On Microsoft 365 and Azure, much of the evidence already sits in your tenant. The work is keeping it for the whole period.
Our view, from work across more than 200 Microsoft 365 and Azure tenants: use a Type 1 only when a deal needs a report soon. Otherwise go straight to a Type 2 with a short first window, because the observation clock is the one part you cannot speed up later. That planning step is where our SOC 2 compliance work usually starts.
What is the difference between a SOC 2 Type 1 and a Type 2 report?
A Type 1 covers your system description and the design of your controls at a point in time. A Type 2 adds whether those controls operated effectively throughout a period, with the auditor’s tests and results included.
Both are examinations by an independent CPA firm under the AICPA attestation standards (SSAE No. 18), using the AICPA SOC 2 guide and the 2017 Trust Services Criteria. In a Type 1, the auditor checks that your system description is fair and that the controls in it are suitably designed as of a specific date. In a Type 2, the auditor also tests samples from the first day of the period to the last. Microsoft’s own SOC 2 documentation puts it plainly: Type 1 audits do not look back over a period of performance.
| Question | Type 1 | Type 2 |
|---|---|---|
| What it covers | System description and control design | Description, design and operating effectiveness |
| Timing | A single date | A period, commonly three to twelve months |
| Auditor work | Inquiry and inspection of design | Sampling and testing across the whole period |
| What a buyer learns | Controls exist on paper and in configuration | Controls ran, plus any exceptions found |
| Best fit | A deal needs a report soon | Most enterprise security reviews |
A Type 1 answers a smaller question; it is not a weaker grade of the same report. Some procurement teams accept one for a first contract if you commit to a Type 2 date. Ask first.
How long should a SOC 2 Type 2 observation period be?
The AICPA guide sets no minimum. Management chooses the period, and in practice CPA firms work with windows between three and twelve months.
A first Type 2 often uses three to six months so a report reaches buyers sooner. After that, most companies move to twelve month periods that run back to back. Microsoft examines Office 365 from October 1 to September 30 each year with no gaps, and issues quarterly bridge letters in between. A bridge letter is management’s own statement, not an auditor’s opinion.
Plan the window around your slowest control. If access reviews run quarterly, a three month window gives the auditor exactly one review to test, and if it is late you have nothing else to show.
Check log retention before day one. Microsoft Entra keeps audit and sign in logs for 30 days with P1 or P2 licensing. The Azure activity log keeps 90 days. Microsoft Purview Audit (Standard) keeps 180 days, and Audit (Premium) keeps Entra, Exchange, OneDrive and SharePoint records for one year. If you start exporting logs in month five of a six month period, the auditor’s sample can land on records that no longer exist.
Which Trust Services Criteria should a SaaS company include?
Security is always in scope. Add other categories only when your contracts and customers rely on those commitments.
The security criteria are the common criteria, CC1 through CC9, covering everything from the control environment and risk assessment to logical access, system operations and change management. On their own they make a complete security report. Each extra category adds its own criteria and more samples for the auditor to pull.
- Availability (A1): add it if you publish an uptime commitment. It brings capacity monitoring, backups and recovery testing into the report.
- Confidentiality (C1): add it if contracts spell out how you protect and dispose of customer confidential information.
- Processing integrity (PI1): rarely needed unless customers rely on you to process transactions completely and accurately, such as billing.
- Privacy (P1 through P8): only if you make specific commitments to individuals about their personal information. It is the heaviest category to support.
For most B2B SaaS companies on Microsoft 365 and Azure, security plus availability is a sensible first scope, with confidentiality added when enterprise contracts call for it. The report should match what you actually promise, not what looks thorough.
What evidence do Microsoft 365 and Azure produce for SOC 2 controls?
Microsoft Entra ID, Purview, Defender XDR and Azure Monitor produce most of the system records an auditor samples. They do not prove that a person reviewed anything, so pair each record with a ticket or a written sign off.
| Control | Criteria | Where it lives | What to keep |
|---|---|---|---|
| Access reviews | CC6.2, CC6.3 | Microsoft Entra access reviews (Entra ID P2 or Entra ID Governance) | Completed reviews, decisions and resulting removals. History reports stay downloadable for 30 days, so save them. |
| Multifactor authentication | CC6.1 | Conditional Access policies, authentication methods registration details, sign in logs | Policy exports with scope and exclusions, plus registration status per user |
| Privileged access | CC6.3 | Privileged Identity Management (PIM) assignments and activation history | Activations with justification, exported before the 30 day audit history rolls off |
| Change management | CC8.1 | Pull request approvals in Azure DevOps or GitHub, Azure activity log | Ticket, approval, test and deployment record for each sampled change |
| Logging and monitoring | CC7.2 | Purview Audit, Defender XDR incidents, Log Analytics or Microsoft Sentinel | Triage tickets and retention settings covering the full period |
| Backups and recovery | A1.2, A1.3 | Azure Backup jobs and Backup Reports | Job history and at least one documented restore test |
Microsoft’s own SOC 2 Type 2 report covers the platform, and your auditor will usually carve Microsoft out as a subservice organization. You still have work on that side. The user entity responsibilities at the end of Microsoft’s report list the controls Microsoft expects you to run, and your auditor will look for them.
If you are not sure what your tenant would show an auditor today, a Microsoft 365 security assessment before the window opens is a practical way to find out.
What mistakes turn a SOC 2 Type 2 into an exception list?
Most exceptions come from missed cadence and missing records, not from weak technology. These are the ones we see most often.
- Opening the window too early. Policies approved partway through leave the first weeks with nothing to test.
- Letting logs expire. Route Entra and Azure activity logs to a Log Analytics workspace or storage account before the period starts.
- Late or rubber stamped access reviews. A quarterly review finished two weeks late is an exception, and so is a reviewer who approved people who had already left.
- Slow offboarding. Auditors compare HR termination dates with the date each sampled account was disabled in Entra.
- Unwatched exclusions. Break glass and service accounts left out of Conditional Access need a written reason and sign in monitoring.
- Unapproved emergency changes. A hotfix pushed straight to production still needs a ticket and a review, even after the fact.
- Backups never restored. Successful jobs do not show you can recover, and A1.3 asks for recovery testing.
- Skipped vendor reviews. CC9.2 covers vendor risk, including a yearly read of Microsoft’s SOC 2 report.
An exception does not automatically mean a qualified opinion, and Microsoft notes that most examinations have some observations. Customers still read that section closely. Our starting point check covers most of these items if you want a read on where you stand.
Should you start with a SOC 2 Type 1 or go straight to a Type 2?
Go straight to a Type 2 with a short first window unless a specific deal needs a report soon. A Type 1 does not shorten the Type 2 period or count as tested evidence for it.
A Type 1 makes sense when controls are new and a deal is waiting. It also works as a rehearsal, since the auditor reviews your control design and you fix gaps before testing begins. The tradeoff is two audits in the first year instead of one.
If nothing is waiting, open a three to six month Type 2 window once your controls have run a full cycle. Your second period can then start the day the first one ends.
If you are weighing a Type 1 against a Type 2, or wondering whether your Microsoft 365 and Azure setup will hold up for a full period, book a 30 minute call and bring your current scope and target dates.
Frequently asked questions
Can a SOC 2 Type 2 cover less than three months?
The AICPA guide does not set a minimum, so a shorter period is possible. Very short windows contain few control cycles, though, and many buyers and CPA firms treat them with caution. Ask your CPA firm and your largest customers what they will accept before you choose the dates.
Does Microsoft’s SOC 2 report cover my company?
No. Microsoft’s report covers Microsoft’s controls over Azure and Microsoft 365. Your report covers your system and the controls you operate, including the user entity responsibilities Microsoft lists. Your auditor typically relies on Microsoft’s report for the platform layer and tests your own controls directly.
How long is a SOC 2 report considered current?
There is no formal expiration date, but most customers treat a report as current for roughly a year after its period ends. That is why companies run consecutive annual periods and hand out a bridge letter covering the months between the end of one period and the next report.
Which Microsoft licenses matter for SOC 2 evidence?
Conditional Access needs Microsoft Entra ID P1, which is included in Microsoft 365 Business Premium and E3. Access reviews and Privileged Identity Management need Entra ID P2 or Entra ID Governance for the users involved. One year Purview audit retention comes with Audit (Premium), part of E5 plans.
Can SOC 2 evidence be reused for ISO 27001?
Much of it can. Access reviews, Conditional Access exports, change records and restore tests support both. ISO 27001 adds management system requirements, such as a Statement of Applicability, an internal audit and a management review, that a SOC 2 examination does not ask for.