Translate an Office 365 audit request into the right workload scope
Office 365 remains a common name for the productivity workloads now reviewed within Microsoft 365. Specify whether you need Exchange Online, SharePoint, Teams, identity or device controls assessed. The name alone does not define coverage, and the features available depend on your tenant and licences.
- Email: forwarding, delegated access and relevant protection settings.
- Collaboration: external sharing, permissions and ownership.
- Identity: the access controls supporting those workloads.
See the broader Microsoft 365 engagement · Discuss the workloads you need reviewed
Know who can access your email and business information
An Office 365 security audit examines the configuration and operating evidence behind your organisation’s email, accounts and collaboration services. Atlant Security helps your team identify gaps, understand their business impact and decide what to fix first.
This assessment focuses on the questions behind everyday operations: who can administer the environment, where messages can be forwarded, how external people gain access to files, and whether the records needed to investigate suspicious activity are available.
Define your Office 365 audit
Tell us your tenant count, approximate user count, licence mix and priorities. Use the audit planner or send an enquiry with your NDA or RFP.
What the audit can cover
| Area | Assessment questions | Useful output |
|---|---|---|
| Accounts and administration | Who holds privileged roles? How are joiners, leavers, guests and emergency access handled? | An access and ownership register with prioritised exceptions. |
| Email security | Which forwarding rules, connectors and policy exceptions affect your recipients? How are sending domains authenticated? | Mail-flow observations, protection coverage and remediation priorities. |
| SharePoint and OneDrive | Who can share externally? Which sampled sites and files have broad access or unclear ownership? | A sampled sharing and permissions review with agreed limitations. |
| Teams collaboration | How are guests and external collaboration governed, including connected document storage? | Collaboration boundaries and ownership actions. |
| Connected applications | Which applications have access to business data, and who owns or approves that access? | Application-permission questions and a review of selected consent records. |
| Investigation readiness | Which audit and sign-in records are available for the agreed period, and who reviews them? | Evidence gaps and an investigation-readiness action list. |
We agree the actual scope before starting. Review methods and available controls depend on your subscriptions, assigned licences, integrations and evidence retention. An unavailable feature is recorded as a dependency rather than treated as a configuration failure.
Review email protection in context
A useful email review follows the real routes messages take. We examine agreed mail-flow settings, forwarding arrangements, accepted and sending domains, protection-policy coverage and exceptions. Public DNS records provide only part of that picture; they do not reveal the configuration inside your tenant.
Microsoft explains how SPF, DKIM and DMARC work together in its email-authentication guidance. Our assessment connects those records to your approved sending services and operational needs.
For a focused engagement, see our Exchange Online security audit. Mailbox content collection and live incident investigation are not included by default.
Include account access and phishing exposure
Email and collaboration depend on account security. Include administrative access, authentication settings, selected sign-in evidence and policy exclusions in the discussion. Where relevant, examine how your environment handles device code phishing exposure and the dependencies behind any exceptions.
The Entra ID audit and Conditional Access review offer deeper identity coverage. Active phishing exercises, password attacks and attempts to compromise the tenant require separate written scope and authorisation.
Receive findings your team can act on
- Executive summary explaining the material observations and decisions.
- Technical findings tied to dated evidence, affected populations and assessment limitations.
- Prioritised remediation actions with proposed owners, licence dependencies and validation criteria.
- A findings discussion so your team can clarify observations and plan implementation.
For example, a forwarding-related finding should identify the observed setting or rule, its owner and business justification, the affected scope and a safe validation step. It should distinguish a confirmed observation from a question requiring further evidence.
View the illustrative audit report to see the reporting approach. Implementation and subsequent verification are scoped separately.
A controlled assessment process
- Agree the objectives, tenants, workloads, criteria, evidence period and exclusions.
- Confirm access arrangements, confidentiality and evidence handling.
- Review approved configuration evidence and representative operating records.
- Discuss observations with the relevant owners and document uncertainties.
- Present the findings and an ordered action plan.
Your team can provide approved exports or lead supervised sessions. Do not send passwords or grant tenant access through the website. Read our access and data-handling approach and assessment methodology.
Office 365 or Microsoft 365: which audit scope do you need?
If your brief says “Office 365 security audit”, start by naming the services you actually use. Email and collaboration may be the priority, while identity, devices, data protection and connected applications may need additional coverage. The product label alone does not define your assessment boundary.
Our broader Microsoft 365 security audit brings those additional workloads into one agreed scope. We confirm entitlements and dependencies before making recommendations, rather than assuming every tenant has the same features.
Prepare your audit request
Useful starting details include tenant and user counts, your licence mix, domains, current IT provider, key workloads and the event driving the assessment. Mention any acquisition, handover, customer requirement or security concern that affects the timing.
Use the audit brief builder to organise the request, or contact Atlant Security directly. You can attach your NDA or RFP before discussing the engagement. See audit pricing factors for what influences the proposal.
Atlant Security is an independent provider and is not affiliated with or endorsed by Microsoft.

