Quick answer
What changed?
The business moved from a Microsoft 365 setup that worked but had unclear risk, to a cleaner environment with better user control, stronger sign-in protection, improved email authentication, reduced admin exposure, and a practical roadmap for endpoint security and Copilot readiness.
Overview
The client was a Cape Town professional services business using Microsoft 365 for email, Teams, OneDrive, and Office apps. The platform was important to daily work, but it had grown over time without a proper security review.
That is common in SMEs. Microsoft 365 starts as email and Office apps, then becomes the place where documents, identities, meetings, shared mailboxes, permissions, devices, and security settings all meet. If no one reviews the setup, small gaps accumulate.
The business wanted to understand whether its Microsoft 365 environment was safe enough for current operations and ready for stronger endpoint protection and future AI adoption.
The challenge
The tenant had become difficult to manage. Some settings were inherited from earlier decisions, some were never documented, and some had not been reviewed since the business grew.
The main concerns were weak sign-in protection, inconsistent MFA coverage, too many admin permissions, old user accounts, email authentication records that needed review, limited visibility into risky sign-ins, and no clear Microsoft 365 security baseline.
The risk was not one dramatic failure. The risk was the combination of unclear access, unclear email protection, unclear sharing controls, and unclear ownership.
What ITried reviewed
ITried started with a Microsoft 365 tenant review. The review covered user accounts, admin roles, licensing, Exchange Online, Teams, SharePoint, OneDrive, Entra ID, Defender settings, and DNS records.
- Microsoft 365 licences and user assignments
- Old users, shared mailboxes, aliases, and unused accounts
- Admin roles and unnecessary privilege
- MFA coverage and Entra ID security settings
- Exchange Online mail flow and sender protection
- SPF, DKIM, and DMARC records
- SharePoint and OneDrive external sharing
- Teams access, guest settings, and collaboration controls
- Defender recommendations and next security steps
Where settings needed change, ITried explained the risk in plain language before applying changes. That helped the business understand why the cleanup mattered instead of treating it as invisible technical work.
The outcome
The client gained a cleaner and safer Microsoft 365 setup. User access became easier to manage, admin permissions were reduced, risky account settings were identified, and email authentication improved.
The business also gained a clearer roadmap for Microsoft 365 security, endpoint protection, and future Copilot readiness. That roadmap mattered because it turned a vague concern about security into a practical list of improvements.
The result was a Microsoft 365 tenant that better matched the needs of a growing SME: safer, easier to understand, and easier to support.
Why this mattered
Microsoft 365 is often treated as email and Office apps. For SMEs, it is also the front door to business data. A weak setup can increase the risk of account compromise, email spoofing, data exposure, and poor access control.
This project reduced risk without making daily work harder. That balance is important. Security controls only work when the business can keep operating normally.
FAQ
What should be checked first?
Start with MFA, admin roles, old users, risky sign-ins, email authentication, external sharing, Defender settings, and DNS records.
Does ITried help with SPF, DKIM, and DMARC?
Yes. ITried checks and improves SPF, DKIM, and DMARC records to help protect your domain from spoofing and improve email trust.
Can this help with Copilot?
Yes. Copilot readiness depends on identity, access, permissions, data control, and security foundations.
Can this be done on an existing tenant?
Yes. The review is designed for existing Microsoft 365 environments that need a cleaner baseline.