To secure Microsoft 365, turn on strong sign-in controls, restrict who can access what, and close the common paths used in email fraud. Then test the settings against the way your staff actually work, because security that stops a payroll officer sending an invoice is not a useful outcome.
For a business of 5 to 200 people, Microsoft 365 security is mostly a discipline problem, not a software problem. Licences get added as people join. Old accounts remain. Multi-factor authentication is switched on for some staff but not others. A shared mailbox becomes the finance team's main inbox. That is where exposure builds.
What is the first step to secure Microsoft 365?
Start with an account and access review. List every user, administrator, shared mailbox, Microsoft 365 group, external guest and app with access to your tenant. Compare that list with your current staff list and remove anything that has no clear owner.
Pay particular attention to administrator roles. Global Administrator access can change users, licences, domains and security settings. Most staff, including many office managers, do not need it for daily work. Give people the least privilege needed to do their job, and use narrower roles such as Exchange Administrator or User Administrator where appropriate.
Keep two emergency administrator accounts that are not used for normal work. Store their credentials securely, document who can access them, and review them after a staffing change. These accounts are a recovery option if a conditional access rule or identity problem locks out your normal administrators. They need careful handling, not casual sharing.
Also turn off legacy authentication where it is still permitted. Older mail protocols can bypass modern sign-in controls and remain a common target for password-spraying attacks. Before blocking them, confirm whether a scanner, accounting package or older application is still using SMTP or another legacy method. Fix the integration first, then block the weaker method.
How should you set up multi-factor authentication?
Require multi-factor authentication for every user. Start with administrators, finance staff and anyone with access to sensitive client files, then apply it across the business. A password alone is not enough when staff use email on mobiles, home internet and customer sites.
Use the Microsoft Authenticator app or a security key where practical. SMS codes are better than no MFA, but they can be exposed through SIM-swap fraud and social engineering. Avoid approving unexpected prompts. Number matching in the authenticator app gives users a clearer signal that they are signing into a real request.
Conditional Access is where Microsoft 365 becomes more specific about risk. Depending on your Microsoft licensing, you can require MFA outside trusted locations, block sign-ins from countries where you have no business activity, and require a compliant device for higher-risk work. Do not copy a complex policy from the internet and apply it to everyone at once. Run it in report-only mode first, check the sign-in logs, then move to enforcement.
The trade-off is straightforward. Tighter rules reduce unnecessary access but can interrupt a staff member travelling, replacing a mobile or using a line-of-business app. Document an approval path so exceptions are deliberate, time-limited and reviewed.
How do you stop Microsoft 365 email fraud?
Email remains the main route into small and mid-sized businesses. A compromised mailbox can send believable payment-change requests, access shared files and create inbox rules that hide warning emails.
Set up SPF, DKIM and DMARC for every domain you send mail from. SPF states which services can send on your behalf. DKIM signs outgoing messages. DMARC tells receiving systems what to do when those checks fail and gives you reporting visibility. Start DMARC in monitoring mode if you are unsure which systems send mail for your business, then move towards quarantine or rejection once legitimate senders are accounted for.
Review Microsoft Defender for Office 365 settings if your licence includes it. Enable protection against impersonation, unsafe links and malicious attachments. Set policies for high-risk targets such as directors, accounts payable and payroll. These controls reduce obvious threats, but they do not replace a payment verification process.
For bank-detail changes, urgent invoice requests and new supplier payment instructions, require an independent check using a known phone number or established contact. Do not reply to the email thread or trust the number in the message. This is a process control, and it matters even when email filtering is working as intended.
How do you secure files, Teams and shared mailboxes?
Check how your team shares files before applying restrictions. Many businesses have years of OneDrive links, Teams channels and SharePoint folders with unclear ownership. Some are open to anyone in the organisation. Others allow external guests long after a project finished.
Assign an owner to each Team and SharePoint site. Remove abandoned sites, review guest access at a set interval, and use expiry dates for external sharing where the feature is available. For documents containing client records, payroll information or commercial terms, limit access to named people rather than sending broad links.
Shared mailboxes need the same attention. Confirm who has Full Access and Send As permissions, especially for accounts, reception and executive inboxes. A shared mailbox should not become a workaround for avoiding individual accountability. Where several people need to process a queue, keep individual sign-ins and grant delegated access.
Sensitivity labels and data loss prevention can help classify and control sensitive information, but they need planning. If labels are too complex, staff will work around them. Start with a small number of clear categories, such as public, internal and confidential, and apply them to the documents that create the most risk if misdirected.
Do managed devices matter for Microsoft 365 security?
Yes. MFA confirms a person at sign-in, but it does not fix an unpatched laptop, a stolen mobile or a browser full of saved passwords. Require screen locks, operating system updates and device encryption on business devices. Remove local administrator rights unless there is a real operational reason to keep them.
Microsoft Intune can manage Windows, macOS, iOS and Android devices when your licensing and device mix suit it. It can check for basics such as encryption, supported operating systems and screen-lock settings before allowing access to business data. A sole trader with one well-managed laptop may not need a full device-management project. A practice with staff using personal mobiles, shared laptops and client files usually needs clearer controls.
Bring-your-own-device arrangements need a written rule. Decide whether staff can access email only, whether files can be downloaded, and what happens when they leave. Without that agreement, offboarding becomes an argument about personal phones rather than a controlled business process.
Is Microsoft 365 backup already included?
Microsoft 365 has retention and recovery features, but that is not the same as a separate backup plan. Retention can help recover deleted or changed information for a defined period. It may not meet your recovery needs after accidental deletion, a compromised account, a misconfigured retention policy or a dispute about historical records.
Decide what must be recoverable, how far back, and how quickly. Include Exchange email, OneDrive, SharePoint and Teams data. Then test a recovery. A backup that has never restored a mailbox, folder or file is an assumption, not evidence.
Your records obligations will vary by industry and contract. Ask your legal, compliance or insurance adviser what retention periods and evidence they require. Technology settings should support that decision rather than inventing it.
How often should you review Microsoft 365 security?
Review key settings quarterly and after any major change, such as a merger, a new finance system, a new office, or a large intake of staff. Each month, check failed sign-ins, unfamiliar inbox rules, administrator role changes, external sharing and devices that have stopped checking in.
Train staff in short, regular sessions using examples relevant to their work. A restaurant manager needs to recognise a fake supplier invoice. An accounting practice needs to recognise a client email account takeover. An NDIS provider needs to know when a file-sharing request is unusual. Training should include a simple reporting path, not just a quiz.
If your insurer, a tender panel or a larger customer has asked for security evidence, keep a short record of your policies, user access reviews, MFA coverage, staff training and incident process. Do not claim compliance because a checklist has been ticked. Show what is configured, who reviewed it and when.
Sharktech can scope Microsoft 365 hardening and email fraud controls around your actual licences, staff workflows and data. The work should be scoped and priced up front, with no dashboard promises until we've seen your data.
The useful next step is not buying another security tool. Pick one owner, review your administrator accounts and MFA coverage this week, and write down the first gap you find. That gives you a concrete starting point rather than another security document nobody uses.






