Reading Your First CIS Microsoft 365 Scan: What to Fix First
A scan returns in 20–25 minutes, but a long failure list is not a plan. How to read the score, severity estimate, profiles and sections in order.
The first scan of a Microsoft 365 tenant against the CIS Microsoft 365 Foundations Benchmark v7.0.0 rarely comes back clean, and that is normal. The useful question is not "why did so much fail?" but "what do I read first, and what can I safely ignore until later?" This post walks through the results view of a ConfigCobra assessment in the order that saves the most time.
What you get when the scan finishes
An automated scan returns results in 20–25 minutes. The dashboard summarises the run as a compliance score, the number of passing and failing controls, and the most severe failures. That last element is the one to start with, but only if you know what "severe" means here.
Severity is an estimate, not a CIS rating
CIS publishes no severity for its controls. The severity shown next to each control in ConfigCobra is ConfigCobra's own estimate, used to prioritise remediation. Treat it as a sorting aid, not as a statement from the benchmark. A control that the estimate ranks lower can still be the one your auditor asks about, so keep the profile and section information in view alongside it.
Know the denominator: 160 controls, 143 automated
v7.0.0 contains 160 controls across 9 sections. Of those, 143 are Automated in the benchmark's own assessment status and 17 are Manual, meaning they require verification by a person. When you read a score, remember that the 17 manual controls are a separate piece of work: a tool reading your tenant configuration cannot settle them for you.
Read the failures in four passes
- Most severe failures first. Start from the dashboard's most severe list. These are the highest-priority items by ConfigCobra's estimate.
- Separate the profiles. Level 1 controls are the safe, minimal-impact ones (114 of the 160); Level 2 controls are stricter and security-focused (46 of the 160). Close Level 1 failures before debating Level 2.
- Look at the sections. Section 5, Microsoft Entra (Identity), holds 63 of the 160 controls — MFA, password protection, Conditional Access, authentication methods and Privileged Identity Management. If most of your failures cluster there, one identity workstream will clear many findings at once. The other sections are Microsoft 365 admin center (15), Defender (21), Purview (5), Intune (2), Exchange Online (13), SharePoint and OneDrive (12), Teams (17) and Fabric / Power BI (12).
- Keep the evidence. The PDF report carries the findings, the evidence and a timestamped tenant snapshot, so you can confirm what was read before you change anything.
Before you fix: check what changes
A failing control tells you what is wrong, not what will break when you correct it. For a failing control, remediation impact analysis shows what changes in your environment if you apply the fix: the affected users, groups, mailboxes, apps and policies, the effect on each (for example a sign-in being blocked or a user being prompted for MFA), a confidence level and a "prepare" step. Each fix carries an impact level of High, Medium, Low or None. Use it to decide which Level 1 fixes can go out this week and which need a heads-up first. See remediation impact analysis for the detail.
When you are ready to act, remediation scripts are generated per finding, as PowerShell or as admin portal steps you can copy and paste. ConfigCobra only reads your tenant through read-only Microsoft Graph permissions; you or your admin apply the change.
Turn the first scan into a baseline
The first result is a snapshot, not a verdict. Save it as the PDF report, which contains the findings, the evidence and a timestamped tenant snapshot, so you have something to compare against. Then set a scan schedule — daily, weekly or monthly — or start an ad hoc scan after a batch of fixes. If a control regresses later, you are alerted, and email notifications cover findings and drift. Scans run on the schedule you set or when you start them; there is no scanning outside that.
A simple first-week plan
- Day 1: run the scan, read the most severe failures, export the PDF baseline.
- Day 2–3: work through Level 1 failures, checking impact analysis before each change.
- Day 4: rescan ad hoc and compare against the baseline.
- Day 5: list the 17 manual controls and assign an owner to each; decide Level 2 controls one at a time.
Try it on your own tenant
The 14-day free trial gives full access to every available module and every control. The CIS Microsoft 365 benchmark page lists the sections and control counts, and the posture management overview explains how assessments work end to end.
ConfigCobra checks Microsoft 365, Azure, Google Cloud and AWS against the CIS benchmarks, read-only. 14-day free trial with full access.