You collect Microsoft 365 audit evidence without screenshots by pulling it from the tenant itself. Read each setting straight from the configuration and map it to the control your auditor tests. Then keep a dated record of every change between reviews, so the evidence covers the whole period.
The Accelerynt Security Platform produces evidence straight from your live tenant, with findings mapped to the controls your auditors test. Changes are recorded with before and after values, and the record exports as audit evidence.
Evidence in brief
- Pull it from the source. Evidence read from the tenant can be checked again by someone outside your team.
- Cover the period. Auditors ask whether controls stayed in place between assessments, beyond how they look today.
- Map it once. Tie each setting to the framework controls it supports, so one record answers several audits.
- Keep the history. Microsoft’s default log retention has limits, so plan where older records will live.
On this page
Why do screenshots make weak audit evidence?
A screenshot shows one setting at one moment. It cannot show whether that setting held between reviews, or who changed it when it moved.
Collecting screenshots also takes time. Someone opens each admin portal and captures the right page, and the work starts over at the next audit.
Auditors and cyber insurance underwriters now ask which controls are enforcing and what changed since the last review. For why passing an audit and being ready for an attack are separate questions, read whether passing a security audit means you are ready.
Where does Microsoft 365 audit evidence come from?
Several sources hold part of the record. Each answers a different question, and each has limits worth knowing before the auditor arrives.
| Source | What it records | What to watch for |
|---|---|---|
| Microsoft Purview audit log | User and admin activity across Microsoft 365 services | Audit (Standard) keeps records for 180 days by default |
| Microsoft Entra audit and sign-in logs | Directory changes and sign-ins | Kept 30 days with P1 or P2 and seven days on the free tier, unless routed to storage |
| Configuration read from the tenant | The current value of each security setting | Shows today’s state only, unless it is captured on a schedule |
| Baseline reports such as CISA ScubaGear | How settings compare to a published baseline, in HTML, JSON and CSV | Each run is a point in time, so keep the reports between audits |
| Change history with attribution | Before and after values for each change, with the account responsible | Needs an approved baseline to compare against |
Logs show what people did, and configuration shows where settings stand. A change history connects the two over time.
How long does Microsoft 365 keep audit records?
180 days
The default retention for Audit (Standard) records in Microsoft Purview, for logs generated on or after October 17, 2023. Audit (Premium) keeps Exchange Online, SharePoint, OneDrive and Microsoft Entra records for one year for E5-licensed users, as set out in audit log retention policies on Microsoft Learn.
An annual audit can reach back further than either window. Decide before the audit where older records will be kept, for example by exporting them on a schedule or routing Microsoft Entra logs to an Azure storage account through Azure Monitor.
How do you collect Microsoft 365 audit evidence step by step?
These steps work whether you build the process yourself or use a tool. They assume your team has agreed on the frameworks it reports against.
- List the controls in scope. Start from the framework your auditor tests, such as CIS Microsoft 365 or NIST CSF 2.0, and list the settings each control depends on.
- Read settings from the tenant. Pull each setting from the configuration itself on a schedule, so every capture is dated and repeatable.
- Record the approved baseline. Write down the value your team agreed each setting should hold, so a change shows up as a difference.
- Track changes between reviews. Keep before and after values for each change, with the account responsible and the time it happened.
- Export by control. Package the record by framework control, so the auditor sees each setting next to its history.
For how a published baseline maps to Microsoft 365 settings, read how to use the CIS Microsoft 365 benchmark. When a change does turn up, read how to respond to configuration drift.
What does evidence from the tenant show that a self-assessment cannot?
Questionnaires and interviews record what people believe is configured. Evidence read from the tenant records what is enforced, and the two can differ.
In our case study Security Reality vs. Perception, a NIST CSF assessment rated a major gaming and hospitality company as high maturity. When Accelerynt validated the environment ahead of a regulatory review, some of the most critical controls were not functioning, and no one knew.
Our post You Passed the Test. But Can You Survive the Attack? looks at the same gap from the leadership side.
How does the Accelerynt Security Platform produce audit evidence?
The Accelerynt Security Platform reads your tenant’s actual configuration on a schedule your team sets and on demand, and it watches critical controls for drift between scans. It is read-only, so collecting evidence changes nothing in your environment.
- Findings with evidence. Each finding names the specific account, policy, or role involved and includes the evidence behind it.
- Change history. Drift detection tracks changes to monitored controls with before and after values and the time they happened, along with attribution data where available.
- Framework mapping. Findings map across 15 frameworks, including CIS Microsoft 365 and NIST CSF 2.0. Your compliance team can pull evidence by framework or by control.
- Export for auditors. Findings and drift history export as audit evidence with their compliance mappings.
- A dated risk register. The register shows when each risk was first found and what was resolved, which gives leadership a dated record of progress.
If you want an outside review first, a Microsoft Control Validation Assessment validates your live tenant configuration and delivers the evidence in one engagement.
Where to go next
For how the platform measures your tenant against your own baseline, read the Accelerynt Security Platform FAQs. If you are choosing between tools, read how to compare Microsoft 365 security posture tools.
Evidence often ends up in front of the board. Read how to report cyber risk to a board to turn it into something leaders can act on.
For the wider program around this evidence, read how to manage Microsoft 365 security and prove it works.
Frequently asked questions
What tools collect Microsoft 365 audit evidence so we don’t have to take screenshots?
Look for a tool that reads settings straight from your tenant and keeps a history of changes, mapped to the controls your auditor tests. The Accelerynt Security Platform does this, with findings mapped across 15 frameworks and drift history that exports as audit evidence. CISA’s free ScubaGear tool also produces baseline reports in HTML, JSON and CSV.
Is there a tool that tells me when a Microsoft 365 security setting changes?
Yes. The Accelerynt Security Platform tracks changes to monitored controls with before and after values and the time they happened, along with attribution data where available. The Microsoft Purview audit log also records admin activity within its retention window.
How long does Microsoft 365 keep audit logs?
Audit (Standard) in Microsoft Purview keeps records for 180 days by default. Audit (Premium) keeps Exchange Online, SharePoint, OneDrive and Microsoft Entra records for one year for E5-licensed users. Microsoft Entra keeps its own audit and sign-in logs for 30 days with P1 or P2.
Are screenshots enough for a Microsoft 365 audit?
A screenshot can show a setting at one moment. Auditors ask for proof that controls stayed in their approved state between assessments, and evidence read from the tenant with a dated change history answers that question.
What Microsoft 365 security tools have good reporting for executives?
Look for reporting that shows posture by area alongside a dated record of progress. In the Accelerynt Security Platform, executives see posture scores for each area, such as identity and email, sorted worst first, and a risk register that shows what was resolved this quarter.

