Microsoft 365 security hardening
Microsoft 365 and Entra ID security hardening
Close the gaps in your Microsoft 365 tenant, with a runbook and rollback step for every change.
BlueRadius hardens Microsoft 365 and Entra ID tenants for mid-market companies as a fixed-scope project. We review how your tenant is set up today, agree what will change, then make the changes in planned windows and leave you with a record of every setting.
Most Microsoft 365 tenants were set up to get people working, not to stop attackers. Accounts that can still sign in without multi-factor authentication, old protocols that skip it entirely, too many global administrators and wide-open external sharing are common findings in assessments and audits. This project fixes them.
When companies ask for this
- A pen test or assessment listed Microsoft 365 findings and nobody has had time to fix them.
- A cyber insurance renewal asks about MFA on email, admin accounts and remote access.
- A SOC 2, ISO 27001 or CMMC audit needs evidence that access controls are configured, not just written down.
- An account was taken over through phishing or a fake sign-in page, and you want to stop it happening again.
What is in scope
Sign-in security
Multi-factor authentication for every user, Conditional Access policies, blocking legacy authentication, phishing-resistant methods for administrators, and two emergency access accounts set up the way Microsoft recommends.
Administrator accounts
Fewer global administrators, separate admin accounts from day-to-day accounts, and roles that give people only the access their job needs.
Email protection
Anti-phishing and impersonation protection, safe links and attachments where licensed, SPF, DKIM and DMARC for your domains, and rules that flag external senders.
Sharing and data
External sharing settings in SharePoint, OneDrive and Teams, guest access, and the third-party apps that users have allowed to read your mail and files.
Logging
Unified audit logging turned on and kept long enough to investigate an incident, with alerts for the sign-in and mailbox events that matter.
How the project runs
- Baseline. We export your current settings and agree the target state with you.
- Runbooks. Each change is written up with the exact settings, a check that it worked and a rollback step. You approve them before anything changes.
- Report-only first. Sign-in policies run in report-only mode so we can see who would be affected.
- Change windows. We make the changes in agreed windows, stop at each checkpoint and confirm before moving on.
- Handover. You get the before-and-after record, the runbooks and the evidence for your auditor or insurer.
Related work
Hardening often follows a penetration test or comes before a SOC 2 audit. If you also need help with on-premises networks or cloud accounts, see firewall and network segmentation and vulnerability remediation.
Frequently asked questions
What does a Microsoft 365 security hardening project cover?
Sign-in security in Entra ID (multi-factor authentication, Conditional Access, legacy authentication), administrator accounts and roles, email protection in Exchange Online and Defender for Office 365, external sharing in SharePoint, OneDrive and Teams, audit logging, and the app consents that give third-party apps access to your data. The exact list is agreed in the statement of work before we start.
Will this lock people out?
Not if it is done in order. Every change has a written runbook with the exact settings, who approved it, how we check it worked and how to roll it back. Sign-in policies start in report-only mode so we can see who would be affected before anything is enforced, and we keep two emergency access accounts outside the policies.
What licenses do we need?
Most of the work can be done with Microsoft 365 Business Premium or E3. Some controls, such as risk-based sign-in policies and Privileged Identity Management, need Entra ID P2 or E5. We tell you up front which recommendations depend on licenses you do not have, so you can decide whether they are worth it.
Can you work alongside our MSP?
Yes. Many clients have an MSP that runs day-to-day IT. We agree the change windows with them, hand over the runbooks, and leave them able to maintain the settings after we finish.
How long does it take?
Most projects take two to four weeks, depending on the number of users, how much needs to change and how many change windows your team can support. The schedule is set in the statement of work.
What do we get at the end?
A before-and-after record of every setting we changed, the runbooks, the evidence an auditor or insurer will ask for, and a short list of anything we recommended but did not change, with the reason.
Scope your Microsoft 365 hardening project
Tell us how many users you have, which Microsoft 365 licenses you hold and what prompted the work: an audit, an insurance renewal, a pen test or an incident. Book a 30-minute scoping call and we will send a fixed-scope statement of work. If you want an independent view of your security first, start with a risk assessment.