Most organisations assume their Microsoft 365 environment is secure because MFA is enabled, mail filtering is turned on, or because “Microsoft takes care of the security”. But after running hundreds of Microsoft 365 Security Assessment engagements, I can tell you this: the gaps are almost always deeper, more systemic, and more avoidable than leaders expect.
Every week, I sit down with Australian IT teams who are confident they’ve covered the basics—yet the assessment uncovers issues that put identity, data and availability at risk. This article explains the five gaps I see most often, what a good M365 security review looks for, and why Secure Score alone isn’t enough.
What a Microsoft 365 Security Assessment Actually Covers
A proper assessment goes far beyond clicking through a Secure Score dashboard. Secure Score is a useful indicator, but it cannot replace structured examination across identity, device, data, threat protection and governance. A comprehensive review evaluates your configuration against Microsoft’s Zero Trust principles, assesses how well controls are implemented—not just enabled—and determines how likely a real-world attack would succeed.
In Microsoft 365, security posture is defined by the relationship between identity policies, device compliance, Conditional Access decisions, Defender threat signals and Purview data governance. If even one of these pillars is misaligned, the entire defence model weakens. This is why Microsoft recommends organisations deploy Zero Trust across identities, devices, apps, data and networks as a unified operating model not in isolation.
The Five Gaps I See in Almost Every Microsoft 365 Environment
- Conditional Access configured—but not enforced
Most organisations have Conditional Access policies in place. Very few have them structured correctly. The most common findings include overly broad exclusions, unenforced baseline protection, and risky “allow” paths left open for legacy apps.
Microsoft’s guidance is extremely clear: Conditional Access should verify explicitly, enforce least privilege and apply real-time signals from user, device and session risk. Weak or untested policies undermine the entire identity layer—still the number one target for attackers.
- MFA enabled, but not phishing resistant
While MFA adoption is high, the type of MFA matters. Too many organisations rely on SMS or mobile prompts without number matching. Microsoft now recommends phishing resistant MFA methods (such as FIDO2 keys), and assessments often reveal inconsistent enforcement across admin accounts, service accounts and privileged groups.
- Misconfigured or incomplete device compliance
This is one of the biggest surprises for CIOs. Conditional Access may require a “compliant device”, but Intune baselines are often outdated, misaligned or not deployed consistently. The result: users access sensitive workloads from unmanaged or partially secured devices.
- Purview data protection barely used
Purview sensitivity labels, DLP rules and encryption capabilities are widely available—but rarely implemented beyond test groups. This leaves organisations exposed to accidental data leaks via email, Teams, SharePoint and third-party apps. A good assessment maps actual data flows and identifies where labels and rules should be applied automatically.
- Defender XDR signals not integrated
Most organisations run Defender for Endpoint but limit themselves to “AV mode”. They miss the advanced correlation, automated investigation and response capabilities that come from Defender XDR and integrated incident workflows. Without this, incident response is slower, visibility is fragmented, and threats take longer to contain.
Why Secure Score Isn’t a Security Strategy
Secure Score is a helpful snapshot, but it doesn’t reflect risk in context. High scores can mask serious configuration gaps—particularly if an organisation aggressively checks off recommended actions without understanding the operational impact.
A Microsoft 365 security assessment looks at why your Secure Score is high or low, what the score doesn’t measure, and where real-world exploitable gaps still exist. This is especially important for regulated industries or organisations preparing for ISO, SOC2 or Essential Eight alignment.
What a Good M365 Security Posture Actually Looks Like
A secure Microsoft 365 environment doesn’t depend on a single feature—it’s the orchestration of consistently applied, mutually reinforcing controls. The strongest environments share these characteristics:
Identity as the control plane. Every access decision validated through Conditional Access with user risk, device posture and session context.
Phishing resistant authentication. FIDO2 or certificate-based authentication for admins and high privilege roles.
Intune baselines fully deployed. Devices receiving the latest configuration profiles, patching and compliance policies.
Data governed at the source. Labels, DLP and insider risk policies enforced across Microsoft 365 workloads.
Unified threat detection. Defender XDR correlating identity, endpoint, email and cloud signals for faster response.
If these elements aren’t in place and aligned, risk increases exponentially.
Why This Matters Now
Attackers are exploiting cloud misconfiguration far more than software vulnerabilities. Weak Conditional Access design, overprivileged accounts and inactive data loss prevention policies are among the biggest causes of Microsoft 365 breaches. And with AI driven attack automation ramping up, the gaps I see in midmarket environments are becoming more exploitable, more quickly.
This is why our team is hosting an upcoming webinar specifically for IT leaders wanting clarity on Microsoft 365 security best practices and what a real assessment should surface. (We’ll add the registration link here once confirmed.)
How A1 Technologies Conducts a Microsoft 365 Security Assessment
Our approach is methodical and aligned with Microsoft’s Zero Trust framework. The assessment includes:
Architecture & identity analysis — Conditional Access, MFA configuration, privileged access, identity risk.
Device posture review — Intune baselines, compliance policies, OS patching, access patterns.
Data governance review — Purview labels, DLP rules, retention policies, sharing behaviour.
Threat detection & response — Defender XDR configuration, incident workflow, SOC readiness.
Secure Score analysis — Interpreting score in context, not at face value.
Remediation roadmap — Prioritised recommendations with business impact and sequencing.
This isn’t a box ticking exercise. It’s a deep review that shows you where attackers get in—and how to close those doors permanently. Talk to A1 Technologies today to help.
Read and download our Microsoft 365 Security Assessment ebook.
Subscribe to our newsletter
Enter your email and stay in touch with the latest updates from A1.
You might also like…
- Software Defined Wide Area Networks are an intrinsic element of many companies networking infrastructure. Think your business may need an SD-WAN, or looking...
- Uncontrolled Azure growth what many teams call “cloud sprawl” shows up first in the bill and later in risk. In decentralised environments, subscriptions...
- Modern cyber threats are no longer isolated incidents. They evolve rapidly across cloud, hybrid, and on‑prem environments. For Australian IT leaders, Zero Trust...