Skip to content
Back to overview Illustration: dated evidence and logs are filed in an archive, a magnifying glass examines one entry
NIS2 Evidence Microsoft 365

NIS2 evidence from Microsoft 365: which logs and reports auditors want to see

By , Founder & Managing Director 8 min read

Key takeaways

  • Section 30(1) of the German BSI Act (BSIG) requires entities in scope to document compliance with their risk management measures. Evidence shows what is configured, since when it has been in effect and how deviations were handled.
  • Microsoft 365 keeps much of this evidence only briefly: Entra sign-in logs for 30 days with P1, Secure Score data for 90 days, the audit log in Audit (Standard) for 180 days, Defender incidents for 180 days.
  • You build a reliable history with diagnostic settings that feed a Log Analytics workspace, regular configuration exports and a defined retention period.
  • Screenshots document a moment. Auditors ask about the period before and after.

After implementation comes the question management most often underestimates: how do we prove it? Whether the request comes from the supervisory authority, a customer audit or the cyber insurer, nobody asks about your intentions; they ask for evidence. Section 30(1) BSIG puts it briefly: the entity must document its compliance. Which measures NIS2 requires is covered in our article on NIS2 basics. This article shows which evidence Microsoft 365 provides, how long it is available and how to turn it into documentation that still holds up months later.

What makes evidence reliable?

Reliable evidence meets four conditions. It is time-stamped, it comes from the system itself rather than from a description written afterwards, it can be produced again, and it covers a period of time. The last condition is the hardest. A Conditional Access policy that is active today says nothing about whether it was active three months ago, when the suspicious sign-in attempt took place.

For management, this means the question to IT is not “Do we have MFA?” but “Can we show since when MFA has applied to whom, and which exceptions there were?”

Which evidence do auditors expect from Microsoft 365?

The table maps typical evidence to its source in Microsoft 365. The “Default retention” column shows how long Microsoft keeps the data without additional setup.

EvidenceSourceDefault retentionRecommendation
Conditional Access policiesMicrosoft Entra admin center, Microsoft GraphCurrent state only; changes in the Entra audit log for 30 days (P1)Regular JSON export, changes via diagnostic setting to Log Analytics
Intune compliance policies and compliance statusMicrosoft Intune admin centerCurrent state; Intune audit events via Graph API for two yearsDiagnostic setting for Audit Logs and Device Compliance Org
Sign-in logs (MFA coverage, blocked sign-ins)Microsoft Entra ID30 days (P1/P2)Diagnostic setting to Log Analytics
User and admin activity in Exchange, SharePoint, TeamsUnified audit log in Microsoft Purview180 days (Audit Standard)Audit (Premium) or forwarding to Microsoft Sentinel
Secure Score and historyMicrosoft Defender portal90 daysMonthly export, for example via the Graph endpoint security/secureScores
Security incidents with handling historyMicrosoft Defender portal180 daysMicrosoft Sentinel or an incident report per event
Access reviewsMicrosoft Entra ID GovernanceResults per reviewRequires Entra ID P2 or Entra ID Governance; otherwise a documented manual review
Configuration changesEntra and Intune audit logs, ticketing systemsee aboveLink each logged change to a ticket and approval

Two things stand out. First, the most important logs disappear after 30 days. Second, Microsoft only shows the current state of policies. History exists only once you record it yourself.

How do you keep the history?

Route logs to a Log Analytics workspace

In the Microsoft Entra admin center, under Entra ID > Monitoring & health > Diagnostic settings, you define which logs flow into a Log Analytics workspace. For evidence purposes, select at least the AuditLogs and SigninLogs categories. Routing sign-in logs requires Entra ID P1 or P2, which Business Premium includes. For Intune, you set up the same thing in the Intune admin center under Reports > Diagnostic settings.

In the workspace, you set retention per table. Data remains queryable for up to two years and can be kept in long-term retention for up to twelve years. One point is often overlooked: retention is not retroactive. Whatever had already expired before you set it up cannot be recovered.

Microsoft Sentinel on the same workspace adds analytics rules and incident management. Office 365 audit logs and Defender security alerts are free data sources in Sentinel. Entra sign-in logs are billed by volume.

Export configuration regularly

Conditional Access, Intune and other settings have no built-in version history. Two approaches work well: a scheduled export via Microsoft Graph, or the open-source tool Microsoft365DSC, which Microsoft also references in its DORA guidance. It represents the tenant state as a configuration file and detects drift. Microsoft now also offers an official interface for snapshots and drift detection, the Tenant Configuration Management APIs in Microsoft Graph. Store the exports with versioning, for example in a repository or a protected SharePoint library. That way you can answer which policy applied on a given day.

Two queries auditors often ask for

Who changed Conditional Access policies, and when?

AuditLogs
| where TimeGenerated > ago(365d)
| where OperationName has "Conditional Access policy"
| project TimeGenerated, OperationName,
          InitiatedBy = tostring(InitiatedBy.user.userPrincipalName),
          Policy = tostring(TargetResources[0].displayName)
| order by TimeGenerated desc

What share of successful sign-ins used MFA?

SigninLogs
| where TimeGenerated > ago(90d)
| where ResultType == "0"
| summarize SignIns = count() by AuthenticationRequirement, bin(TimeGenerated, 7d)
| order by TimeGenerated asc

Link the first query to your change process: every change should have a ticket with a justification and an approval. The second shows, week by week, whether single-factor sign-ins are actually declining.

Why are screenshots not enough?

Screenshots are not worthless; as an illustration they have their place. As the only evidence they have three weaknesses. They show a moment, not a period. They cannot be reproduced when the auditor wants a different filter. And they are easy to alter, which reduces their value as proof.

In assessments we often see evidence folders consisting of screenshots taken in the single week before the audit. That becomes obvious as soon as someone asks about the state three months earlier. A fixed rhythm works better: a monthly export of Secure Score, the compliance report and policies, continuous log forwarding and a short monthly report that records deviations and actions.

Which evidence does not come from the tenant?

Part of the documentation is created outside Microsoft 365 but belongs in the same evidence folder:

  • Risk analysis with assessment, owners and the date of the last review.
  • Incident reports with the time of becoming aware, the classification, the decision on reporting and the actions taken. The technical timestamps from Defender or Sentinel are the basis; you write the assessment yourself. How an incident plan is structured is described in our article on the incident response plan.
  • Restore tests with date, scope and result.
  • Training records, including for management under Section 38(3) BSIG.

Next step

Our NIS2 with Microsoft 365 service sets up log forwarding, configuration exports and an evidence structure so that your tenant produces the evidence continuously. If you prefer to hand over operations, our Managed Security service runs Sentinel, Defender and the monthly report.

Book an introductory call

Frequently asked questions

How long do we need to keep logs for NIS2?

Section 30 BSIG does not specify a retention period. Set the period based on your risk analysis and document the decision. Because sign-in logs contain personal data, involve your data protection officer and, where one exists, the works council.

Is the compliance score in Purview evidence for NIS2?

It measures progress on implemented improvement actions; it does not confirm legal compliance. It is useful as part of the documentation if you file the underlying settings and your own documents alongside it.

Can our IT provider deliver the evidence?

Yes, if the contract specifies it: which reports, how often and with which retention. Make sure the workspace and exports sit in your tenant or your Azure subscription, not the provider’s. Otherwise you lose the evidence when you change provider.

Where should we start?

With the diagnostic setting for Entra logs. It takes little effort, and every day without it is a day for which you will later lack sign-in data, because retention is not retroactive. Next come the monthly export of policies and Secure Score, and finally analytics rules in a SIEM.

Is Audit (Standard) enough if we export the data?

For many companies, yes. Through the Office 365 Management Activity API or the Sentinel connector you can keep events longer than 180 days. Audit (Premium) adds one year of default retention for Entra, Exchange, SharePoint and OneDrive events of licensed users, custom retention policies and additional events for forensic analysis.

Let's talk about your IT security

In the introductory call (30 minutes, no obligation) we clarify:

  • where your company stands today and what concerns you most
  • which next step makes sense for your organisation
  • what effort and price range to expect
Bastian Wenske

Bastian Wenske

Founder & Managing Director

Heidelberger Straße 15
12059 Berlin
Germany

Prefer to reach out directly? Send us an email at [email protected].