A 35-staff Australian wholesale business — referred to in this case study as Hartwell Trading Pty Ltd — engaged Evisent in May 2026 to run a read-only Microsoft 365 audit. The brief was cost optimisation. The brief was met. But the audit also surfaced seven high-severity security findings the client didn't know they had — including an admin account with no MFA that was signed into 17 staff workstations.
Hartwell Trading is a 35-staff Australian wholesale business with a Microsoft 365 Business Premium tenant, a third-party email gateway, and an incumbent IT provider that had been in place for several years. The leadership team came to Evisent with a specific question: "is there money we're paying Microsoft that we shouldn't be?"
The answer turned out to be yes — about $4,070 a year in unused or over-assigned licences, recoverable inside a four-week window before the next annual renewal. That was the immediately quantifiable answer. The harder answer came alongside it.
Engagement type: Read-only M365 audit, similar in shape to an AI Readiness Sprint
Duration: Two weeks
Scope: Identity & access, Conditional Access, endpoint & email security, data sharing, licensing, operational hygiene
Output: 27-page audit report, board-ready summary, prioritised remediation roadmap
Microsoft Secure Score (at audit): 66.8%
The full report contains thirteen findings across security, licensing, and operational hygiene. Below are the six that most shaped the conversation with Hartwell's leadership team. Headline numbers preserved; identifying detail anonymised.
The most material finding of the audit. The incumbent IT provider held a shared administrative account that was excluded from the tenant's "Require MFA for all users" policy, held permanent Global Administrator role (the highest privilege level Microsoft 365 offers), and was configured as the Windows sign-in identity on approximately seventeen staff workstations.
External sharing was configured at the most permissive setting Microsoft offers. Anonymous "Anyone" links — which work without sign-in — never expired. Folders shared anonymously permitted upload back into them. Twenty-nine of thirty-five SharePoint sites had external sharing enabled at the site level.
The domain's DMARC policy was set to p=none — a monitoring-only configuration that allows receiving mail servers to report on unauthenticated mail but does not block it. In practical terms: a scammer in another country could send a perfectly legitimate-looking invoice or HR email from anyone@<Hartwell's domain> to Hartwell's customers, suppliers, or staff — and major email providers (Gmail, Outlook) would deliver it normally.
Hartwell's Microsoft 365 Business Premium subscription included Microsoft Defender preset security policies — protections specifically designed to block the malware patterns used in over 90% of real-world attacks against businesses this size. None had been enabled. No Attack Surface Reduction rules had been deployed.
Fourteen user accounts held paid Microsoft 365 licences but were not active users. They included disabled ex-staff accounts (some inactive for 1-4 years), accounts that had never been signed in (including one new-starter account with two stacked licences worth $533/yr that had never been used), and Teams Phone service accounts using paid user licences rather than free resource-account licences. The tenant was also over-assigned (35 users, 33 paid Business Premium licences) — Microsoft had already flagged this for billing at the next renewal.
Microsoft Intune — included in Business Premium licences — had zero mobile devices enrolled. Every iPhone or Android device staff used to read company email was completely unmanaged: no enforced screen lock, no remote-wipe capability when a device was lost, no separation of work data from personal data, no audit trail of which devices held company information.
We weren't asked to investigate whether a prior compromise had occurred. We were asked to assess the current state. But the current state read like the inheritance from one: a shared admin account exempt from MFA, the same identity active on seventeen workstations, a domain that could be spoofed without programmatic protection, anonymous file-sharing links that never expired, and twelve security controls that had been previously implemented and silently drifted out of compliance.
Each finding individually is a configuration weakness. Taken together, they describe the exact pattern of conditions a well-prepared attacker would want left behind — persistent administrative access, an exfiltration channel, an impersonation channel, and detection controls that had been quietly disabled. Whether the configuration was the inheritance of a prior compromise, the residue of a former provider's habits, or simply the cumulative drift of a tenant nobody had audited in several years — the operational risk was the same.
The findings were ranked, reported plainly, and walked through with Hartwell's leadership team. The remediation roadmap was sequenced against the four-week renewal window so that the cost recovery could fund the security uplift. The work is ongoing.
The complete 27-page audit report — anonymised at the same level as this case study, with all client-identifying detail removed — is available on request as a sample of the deliverable shape. Useful if you're evaluating Evisent against another provider and want to see what an audit output actually looks like, end to end.
Email info@evisent.com.au with "sample audit" in the subject line — we respond same business day.
The AI Readiness Quiz scores your environment in three minutes against three readiness axes — Governance, Build, Operations — and routes you to the right SKU. Or book a Sprint directly if you'd rather skip the quiz.