Microsoft Office 365 · Security review
Microsoft 365 Security Health Check
Our Microsoft 365 security health check gives your business a practical starting point for reviewing account access, email settings and everyday security. Speak to Symstar Technology about the setup your team uses and the concerns you want to address.
£149Microsoft 365 Security Health Check
Book an engineerUse our contact form to request the £149 health check. We will confirm the scope and appointment arrangements before work starts.
A clear starting point
What the Microsoft 365 security health check reviews
Security settings need to suit your users and the way they work. The review focuses on these five areas, with the available checks agreed around your Microsoft 365 licences, access and business requirements.
Sign-in protection
Review how users sign in, their multi-factor authentication arrangements and the approach to protecting important accounts.
Privileged accounts
Discuss who has administrator access and whether their permissions still match their responsibilities.
Mailbox settings
Review relevant email security settings, forwarding arrangements and mailbox rules that need attention.
File and guest access
Discuss how your team shares business information and whether external access needs a closer look.
Practical priorities
Identify security improvements to consider and discuss the work needed to address the findings.
Who is this review for?
The Microsoft 365 security health check is a useful first step for small businesses that want a clearer picture of their current setup. It can also help when users have joined or left, administrator responsibilities have changed, or your team is unsure which protections are in place.
You do not need to know every technical setting before contacting us. Tell us about your business email, the number of users and any specific worries. We can discuss whether the health check is suitable for your requirements.
For wider help with users, migration and cloud tools, explore our Microsoft 365 support services.
How to book an engineer
- Send your enquiry. Open the contact form and mention the £149 Microsoft 365 security health check. Include your business name, approximate user count and a brief description of your concerns.
- Discuss your setup. Symstar will confirm what can be reviewed, the access arrangements and appointment availability.
- Agree the next step. Review the findings with an engineer and discuss any follow-up work your business needs.
Do not send passwords or authentication codes in your enquiry. Access arrangements should be discussed with the engineer through an appropriate process.
Microsoft 365 security health check FAQs
Does this cover Microsoft Office 365?
Yes. Businesses often use the name Office 365 for their Microsoft cloud email and productivity services. Tell us which plan and services you use so we can confirm the relevant review scope.
Will settings be changed automatically?
The health check starts with a review. Any proposed changes and additional work should be discussed and agreed before implementation.
What if we think an email account has already been compromised?
Contact your IT administrator promptly and explain the suspicious activity. Tell Symstar that you need help with an active security concern when you enquire, so the response can be discussed separately from a routine health check.
Can you help with the improvements afterwards?
Symstar provides Microsoft 365 security support. We can discuss the findings, priorities and scope of any follow-up assistance.
For further background, read the NCSC guidance on recovering a hacked account or service. Recovery processes vary between providers and account types.
Book your £149 health check
Request a Microsoft 365 security health check and take the next step towards understanding your business email and account security.
Book an engineerOn this page
Microsoft 365 security health check preparation guide
Preparing for a Microsoft 365 security health check

Begin with a description of how your team uses business email, shared documents and collaboration tools. Identify the person responsible for administering the environment and any existing support provider. A Microsoft 365 security health check should have an agreed scope, with the accounts and areas for review clear before access is arranged. Explain the concerns you want to understand and any recent incidents or changes. You do not need to send private mailbox content or administrative credentials in the initial enquiry. A practical starting point helps the review focus on your organisation’s priorities.
Clarifying the review and follow-up work
A review helps you understand the agreed areas and discuss findings; it does not mean that every change is automatically authorised or included. Ask what the proposed appointment covers, what information is needed and how recommendations will be explained. A Microsoft 365 security health check can lead to follow-up priorities, but implementation should have its own agreed scope where required. The advertised £149 offer remains the starting point shown on this page. Confirm suitability, availability and the service details before booking, including any work or requirements that need to be considered separately.
Identify an authorised business contact
Choose a contact who can explain how the organisation uses the service and obtain approval for the agreed review. They may need to coordinate with the current administrator or another provider. A Microsoft 365 security health check should not rely on credentials passed through an ordinary enquiry form. Establish who owns the tenant and who can authorise any necessary access. Discuss the review method and access requirements before the appointment. Clear ownership helps avoid conflicting changes, makes it easier to ask follow-up questions and keeps responsibility for business decisions with the appropriate person.
Account ownership and administrator roles
An account review begins with understanding who uses the service and who administers it. Identify staff accounts, shared responsibilities and any access retained by suppliers. The relevance of particular settings depends on your environment and the scope agreed for the appointment. A Microsoft 365 security health check can help discuss whether account ownership and roles are clear, without assuming that every administrator arrangement needs the same change. Any recommendation should explain its purpose and the people or systems it may affect. Changes need separate approval and coordination with the responsible business administrator.
Understanding the current authentication arrangements

Explain how staff currently sign in and how account access is managed when a user needs help. The products, licences and configuration in place can affect the available controls. A Microsoft 365 security health check should consider the actual environment rather than a generic list of settings assumed to apply to every business. Tell the reviewer about any access difficulties, remote users or specialist applications that may be relevant. Do not share authentication codes in an enquiry. If an improvement is proposed, discuss its purpose, dependencies and user impact before implementation is agreed.
New starters and leavers
Describe the process for creating accounts, approving access and removing permissions when staff leave. Identify who requests the changes and who checks that they have been completed. A Microsoft 365 security health check can help surface questions about account lifecycle management within the agreed review scope. Business information and ownership also need consideration when a colleague changes role. Avoid informal password sharing as a handover method. Any proposed changes should be coordinated with the people responsible for staff processes and the existing administrator, with a clear record of approval and tasks that need separate follow-up work.
Business email and mailbox configuration
Tell the reviewer how your organisation uses business email, including shared addresses and any specialist applications that send messages. Explain the concern you want to investigate, such as unfamiliar mailbox behaviour or uncertainty about access. A Microsoft 365 security health check is a review of agreed areas, so clarify the particular accounts and settings in scope. Private message contents should not be sent unnecessarily in an initial enquiry. If a finding suggests a configuration change, discuss the reason, expected impact and approval required before work is carried out on the live environment.
Recognising suspicious mailbox activity
Examples of concerns worth reporting include unexpected messages, unfamiliar forwarding behaviour or sign-in activity you do not recognise. Describe what you have observed without assuming a diagnosis. If you suspect an active compromise, contact the responsible administrator promptly and explain that the issue is urgent. A Microsoft 365 security health check is separate from a response to an active incident, and the appropriate help needs to be discussed accordingly. Keep potentially useful details and follow the business’s agreed reporting route. Do not include passwords or private customer records in an ordinary enquiry message.
Reviewing access to shared documents

Document access can involve team folders, individual accounts, external recipients and inherited permissions. Explain which information the business needs to protect and who should be able to use it. A Microsoft 365 security health check may raise questions about sharing and access where those areas are included in the agreed scope. Broad access is not automatically the correct solution to a single user’s difficulty opening a file. Identify the business owner of important material and discuss how permissions are reviewed. Any changes should be authorised and tested against the way colleagues actually work.
External sharing and business ownership
External collaboration should have a clear purpose and an authorised owner. Tell the reviewer whether the business shares documents with customers, suppliers or other parties and what access is intended. A Microsoft 365 security health check can help you discuss relevant settings and review questions within the scope agreed for your environment. Consider how access is removed when a relationship or task ends. Do not widen sharing permissions simply to remove an inconvenience without understanding the consequences. Recommendations should explain the business requirement, the proposed control and any impact on legitimate collaboration.
Connected applications and permissions
Business accounts may be connected to applications or services used by staff and suppliers. Identify the important integrations and who owns them before a review is arranged. A Microsoft 365 security health check should recognise that changes can affect workflows outside the obvious email or document interface. Ask how a proposed recommendation relates to those dependencies. Unfamiliar access needs investigation rather than an assumption that every connection is malicious or unnecessary. Any removal or permission change should be authorised and coordinated with the responsible administrator, particularly where business applications rely on the existing setup.
Devices and access requirements
Tell the reviewer whether staff use business-managed devices, personal equipment or both. Include broad working arrangements such as office and remote access, without sending unnecessary private information. A Microsoft 365 security health check depends on the services and configuration involved; device-related controls may require separate scope, licences or technical work. Discuss the actual requirement and the users affected before changes are proposed. Clear boundaries help distinguish a cloud account review from a wider device-management project. If follow-up work is needed, agree the tasks and responsibilities separately from the initial assessment.
Reviewing alerts and reporting routes
Staff should know how to report unfamiliar account behaviour or a suspicious message. Explain who currently receives reports and who can investigate issues in the service. A Microsoft 365 security health check can help discuss the relevant monitoring and reporting questions within its agreed scope. Available information and controls depend on the environment, so confirm what is actually configured. Useful findings should identify who needs to act and how the business obtains further assistance. A routine review does not replace a response arrangement for an active incident or guarantee that every security issue will be detected.
Interpreting findings in business terms
A useful finding explains what was observed, why it matters and what needs further consideration. Ask for priorities to be related to the way your organisation works, rather than treating every recommendation as equally urgent. A Microsoft 365 security health check should help you understand the agreed review areas and discuss practical next steps. Some findings may require more investigation or input from another supplier. Keep those dependencies clear. The business can then decide which changes to approve, with implementation scope, costs and user impact confirmed before the proposed follow-up work begins.
Prioritising proposed improvements
Review recommendations with the business owner and the responsible administrator. Consider the risk addressed, the systems affected and whether licences, application dependencies or user training are involved. A Microsoft 365 security health check can provide a starting point for this discussion, but it does not automatically authorise changes. Separate immediate concerns from planned improvements and work that requires another provider. Agree who owns each action and how completion will be checked. A practical order of work helps the organisation make informed decisions without assuming that every item can be implemented during the same appointment.
Plan testing before changing settings
An approved configuration change should have a way to confirm that the intended business task still works. Identify representative users and relevant applications before implementation is arranged. A Microsoft 365 security health check is a review, while testing and remediation tasks should be defined in any follow-up scope. Explain important deadlines or service dependencies that could be affected by a change. Record remaining issues and the route for obtaining help. Checking the actual workflow can reveal consequences that are not visible from a setting alone, particularly where several locations or suppliers are involved.
Supporting staff with agreed changes
Colleagues may need instructions when sign-in, sharing or account processes change. Identify who will communicate the change and how users can obtain help. A Microsoft 365 security health check can lead to recommendations with a user impact, so include that impact in the planning discussion. Keep guidance relevant to the tasks staff perform and avoid putting passwords or recovery codes into ordinary documents. Any training or wider rollout work should be identified in the agreed follow-up scope. Clear communication can reduce confusion and helps the business keep responsibility for approvals and ongoing support visible.
Keep a record of responsibilities
Record the areas reviewed, the responsible business contact and any recommendations that need separate action. Include other suppliers where they own a relevant service or integration. A Microsoft 365 security health check is easier to follow up when findings have clear ownership and unresolved questions remain visible. Store the record appropriately and keep administrative credentials separate from ordinary review notes. Revisit responsibilities when staff, suppliers or business systems change. The record should help the organisation understand what was assessed and what still needs investigation, without implying that a routine review is a compliance certificate or a guarantee.
Review after significant business changes
New users, different applications or changes to document sharing can affect the questions a business needs to ask about its environment. Discuss whether a further review is useful after a significant change. A Microsoft 365 security health check should be scoped to the current organisation rather than treated as a permanent assessment of every future configuration. Keep previous findings available so that the next discussion can distinguish completed actions from new requirements. The timing and depth of any additional work should be agreed separately, with the responsible administrator involved where access or implementation decisions are needed.
Book a Microsoft 365 security health check
Use the contact page to describe your organisation, approximate user count and the concerns you want to review. Identify any existing provider and a suitable business contact. A Microsoft 365 security health check enquiry should not include private mailbox exports, passwords or sign-in codes. If you believe an incident is currently in progress, explain that clearly so that the appropriate response can be discussed separately. Symstar can confirm the advertised offer’s scope, suitability and appointment availability before the work is arranged, with any additional changes or services agreed separately.
