See your tenant the way an attacker or an auditor would.
- We review Entra ID, Intune, Defender and Purview setting by setting, and export what is there before we change anything.
- Every finding is ranked by risk and comes with evidence, a fix and an owner.
- We make the fixes with your IT team or MSP, tested on a small group first, and prove them with before and after exports.
One tenant moved from 28% to 68% Microsoft Secure Score in six weeks. Your starting point and timing will differ.
200+ Microsoft 365 and Azure tenants. 100+ engagements. A full Microsoft 365 incident response after an AiTM session token theft. 20+ years in regulated technology.
How a tenant review usually starts
Four questions that land on an IT lead’s desk, and what sits behind each one.
“Does MFA cover every admin account?”
Someone has to check before anyone signs. The answer is in your Conditional Access policies and their exceptions.
“How do you protect email and devices?”
The honest answer lives in tenant settings, and an auditor will ask to see them.
“We pay for security features. Which ones are on?”
Licensed and switched on are not the same thing. Since July 1, 2026, Microsoft 365 E3 includes Defender for Office 365 Plan 1, which still has to be set up.
“We think an account was taken over.”
Then containment comes first and the review comes after. The next section shows the order.
If you think an account was taken over
In an adversary in the middle (AiTM) attack, the attacker steals the signed in session after MFA, so the response has to end that session, not just change the password. This is the order we work in, following Microsoft’s token theft playbook.
-
Cut off the stolen session
Revoke the account’s sessions and reset its password, so the stolen tokens stop working.
-
Remove what the attacker added
Sign in methods, registered devices, inbox rules and forwarding that the account did not have before.
-
Find out what was touched
Search the audit log for what the account read, sent and changed. Audit (Standard) keeps 180 days of records, so this cannot wait.
-
Close the way in
Phishing resistant sign in for admins, Conditional Access that requires a managed device, and token protection for supported apps.
-
Then review the rest of the tenant
The same review this page describes, with the incident’s findings at the top.
We have run a full Microsoft 365 incident response after an AiTM session token theft.
If it is happening now, call rather than book: (786) 577-9743
Setting by setting, with an owner for every fix
Two formats from the assessment. Each one is a sample format with illustrative content, not a client’s tenant.
Tenant changes, before and after
What each setting was, what it is now and why it matters, backed by exports taken before and after.
Tenant changes, before and after
Sample format, illustrative content
| Setting | Before | After | Why it matters |
|---|---|---|---|
| MFA for admin accounts | Optional | Required for every admin role, with phishing resistant methods | Admin sign ins are the first target |
| Legacy authentication | Allowed | Blocked by Conditional Access | Older sign in methods skip MFA |
| Sending mail with a password (SMTP AUTH) | On for the whole tenant | Off, except one scanner until it moves to OAuth | Microsoft turns it off by default at the end of December 2026 |
| Laptop encryption | Not enforced | Required by Intune, with recovery keys kept in Entra ID | A lost laptop stays a hardware loss |
| Links in email | Not checked | Checked when clicked, by Safe Links | Phishing links stop at the click |
A finding card
One page per finding, so the person who owns the fix has everything on it.
F03 Email can forward automatically to outside addresses
Sample format, illustrative content
High
- Finding
- The outbound spam policy still uses the system controlled setting, which in this older tenant allows automatic forwarding. Three mailboxes forward outside the company today.
- Risk
- A taken over mailbox can quietly copy every message to an attacker.
- Evidence
- An export of the outbound spam policy and a list of mailboxes that forward.
- Fix
- Turn automatic external forwarding off. Allow named exceptions with approval.
- Owner
- Your IT lead, with sign off from leadership
Last checked
Where Microsoft 365 stands, November 2026
Three dated changes that decide what your tenant should look like now, and what the common fixes need from your licenses.
Scheduled
Sending mail with a password turns off by default
Exchange Online disables Basic authentication for SMTP AUTH by default in existing tenants. Admins can turn it back on for now, and Microsoft plans to announce a final removal date in the second half of 2027. Scanners, printers and apps that send mail with a password need another way.
In effect
E3 now includes Defender for Office 365 Plan 1
Office 365 E3 and Microsoft 365 E3 include Plan 1, with Safe Links, Safe Attachments and anti phishing. Microsoft 365 Business Premium already did. Having the license does not mean the policies are set the way you want them.
In effect
Microsoft requires MFA for admin tools
MFA has been required for the Azure portal and the Entra and Intune admin centers since late 2024, and has been rolling out to the Microsoft 365 admin center since February 2025. From October 1, 2025, it extended to Azure command line tools, PowerShell and APIs that change resources. Postponements ran out on July 1, 2026, so scripts that sign in as a person to change Azure resources now need MFA or a workload identity.
What the common fixes need from your licenses
We show what a fix needs before you decide. Business Premium covers most of them.
| Fix | Needs | In Business Premium |
|---|---|---|
| MFA and blocking legacy sign in through Conditional Access | Microsoft Entra ID P1 | Included |
| Only managed devices reach email and files | Intune Plan 1 and Entra ID P1 | Included |
| Safe Links and Safe Attachments | Defender for Office 365 Plan 1 | Included |
| Admin roles turned on only when needed | Entra ID P2 or Entra ID Governance | Not included |
| Sign in risk and user risk policies | Entra ID P2 | Not included |
| Audit records kept longer than 180 days | Audit (Premium) | Not included |
Read first. Change carefully. Prove it.
The same four steps in every assessment. None has a fixed length; this is what sets it for you.
-
Read
What sets the time The size of the tenant and how many policies it has
We start with read only access and export the current settings before touching anything. Emergency access accounts are checked first, because every later change depends on them.
-
Rank
What sets the time How many findings there are
Findings go in order of risk, each with evidence, a fix and an owner. Where a fix needs a license you do not have, the finding says so.
-
Stage
What sets the time How often you can approve changes, and the change windows you agree
New Conditional Access policies run in report only mode first, then reach a pilot group, then everyone. We make the changes with your IT team or MSP, so nobody is locked out.
-
Prove
What sets the time Nothing extra. It is built as each change lands.
A change log, fresh exports and a new Secure Score, so an auditor or insurer can see what changed and when.
What we need from your side
Read only admin roles to start, a person who can approve changes, your list of admins and licenses, and agreed change windows. If an incident is under way, we also need whoever can reset accounts at short notice. Your point of contact is a senior security and compliance lead who also directs the engineering in Microsoft 365 and Azure.
Ten questions we ask about every tenant
If the honest answer to any of them is “not sure”, treat it as a gap.
- Is MFA required for every user, including admins and shared accounts?
- Is legacy authentication blocked?
- Are admin roles granted only when needed, instead of held full time?
- If a policy locked admins out, is there a tested way back in?
- Must a device pass Intune checks before it opens company email and files?
- Are company laptops encrypted, and could you show it?
- Are links and attachments in email checked before people open them?
- Are SharePoint and OneDrive links limited to specific people by default?
- Does someone read sign in and admin alerts every week?
- Has anyone worked through your Secure Score recommendations this quarter?
Want a first read before a call? Take the Microsoft 365 security check
Work we have delivered
What we can say about past tenant work without naming clients.
-
Incident response
A full Microsoft 365 incident response after an adversary in the middle (AiTM) session token theft.
-
Independent assessment
A defense contractor we prepared passed its CMMC Level 2 C3PAO assessment with every requirement met.
-
Healthcare
HITRUST e1 and i1 work for healthcare clients.
Who this is for, and who it is not for
A good fit
- Microsoft 365 tenants facing an audit, a security questionnaire or an insurance renewal.
- Teams that think an account was taken over, or want to be ready if one is.
- IT teams and MSPs that want a second set of hands.
- Teams planning a Copilot rollout.
Not a fit
- You want a report and no changes.
- You need help desk or day to day IT support.
- Your organization runs on Google Workspace.
- You want a guaranteed result. Nobody can honestly promise one.
Questions before you book
Will you lock us out?
The approach is designed to avoid it. Emergency access accounts are checked first and kept out of policies that block sign in, as Microsoft recommends. New Conditional Access policies run in report only mode before they are enforced, and changes reach a small group before everyone.
Do you need global admin?
Usually not to start. A review can often begin with read only roles. When changes are needed, the aim is the narrowest admin access that does the job, for as long as the job takes.
What licenses do these fixes assume?
Most common fixes work with Microsoft 365 Business Premium. Admin roles turned on only when needed and risk based sign in policies need Entra ID P2, and keeping audit records past 180 days needs Audit (Premium). Each finding says what its fix needs before you decide.
Will this disrupt users during business hours?
Changes are staged: report only first, then a pilot group, then everyone, in windows you agree. Users notice the changes that ask them to do something, like registering a new sign in method, and we tell them before it happens.
How is this different from our MSP’s report?
Your MSP keeps the tenant running. We look at it the way an attacker or an auditor would: each finding comes with evidence, a fix and an owner, and we make the fixes alongside your MSP instead of handing over a list.
Is a higher Secure Score the goal?
No. Microsoft defines Secure Score as “a measurement of an organization’s security posture, with a higher number indicating more recommended actions taken.” Some recommendations need a higher license edition than you have. We use it as one input. A higher score is not the goal. Fewer ways in is.
How long does an assessment take?
It depends on the size of the tenant, how many findings there are and how often you can approve changes. We give you a plan after the read only review, not a guess on the first call.
We think an account was taken over. What now?
Call rather than book. Containment comes first: cut off the stolen session, remove what the attacker added and find out what was touched. The review comes after.
How is the work priced?
As a fixed scope project, or as a fractional security and compliance officer on retainer. We agree the scope in writing before work starts.
What happens after you book
- Pick a 30 minute time that suits you.
- We talk through what prompted the review and how your tenant is licensed.
- You leave knowing where to start and whether to go further.
Bring a Secure Score screenshot and your list of admins to a 30 minute call.
You leave knowing where your tenant stands and what to fix first.