Skip to content

Solutions

Microsoft Security

Subnet reviews and strengthens Microsoft 365 security for South Australian organisations, using the licences you already own before recommending anything new.

Since 2001

a Microsoft partner

420+

Microsoft 365 engagements

20+

Intune rollouts

15+

Defender deployments

WHAT WE DELIVER

Get the security you are already paying for

These are the parts Subnet delivers, and the technology we use for each.

Baseline

Microsoft 365 hardening

A review of tenant settings against Microsoft and ASD guidance, with the changes that matter applied and recorded.

What it solves

  • Default settings never revisited
  • Admin accounts with too much access
  • No record of why settings were chosen

How Subnet works with it

We agree a baseline, apply it in stages and keep it from drifting.

Intune and Defender device compliance and access controls

Access

Identity and device controls

Microsoft Entra sign-in policies and Intune device management decide who can reach what, and from which devices.

What it solves

  • Accounts without multi-factor authentication
  • Personal devices reaching company data
  • Leavers who keep access

How Subnet works with it

We design policies around how people work and pilot them before wider rollout.

Threats

Endpoint and email protection

Microsoft Defender protects computers, email and collaboration tools, with plans that differ by licence.

What it solves

  • Phishing reaching inboxes
  • No visibility of compromised devices
  • Uncertainty about which Defender plan you have

How Subnet works with it

We confirm entitlements, configure protection and route alerts to people who act on them.

Information

Information protection

Microsoft Purview labels and data loss prevention policies classify sensitive content and limit where it can go.

What it solves

  • Sensitive files shared too widely
  • No way to see where data is leaving
  • Copilot surfacing content people should not see

How Subnet works with it

We start with a small set of labels people understand and extend from there.

WORK WITH SUBNET

How a Microsoft security project runs

1. Assess

We review the tenant, licences and current controls.

2. Design

Changes, exceptions and owners are agreed.

3. Deploy

Controls are applied in stages with a pilot group first.

4. Manage

The tenant is monitored against the baseline.

5. Review

Settings are reviewed as Microsoft releases changes.

WORK WE HAVE COMPLETED

Microsoft Security work by sector

Education

Domain controllers moved to Microsoft Entra ID, Intune for classroom and lab devices, SharePoint modernisation and Copilot for staff.

Health and not-for-profit

Microsoft 365 migrations, SharePoint builds, Intune rollouts and Copilot readiness assessments.

Professional services

A full Azure migration, followed by a move to Azure Virtual Desktop with Intune device management.

CONNECTED EXPERTISE

FIND THE NEXT PART OF YOUR PLAN.

03

Azure infrastructure

Cloud assessment, virtual infrastructure, Azure Virtual Desktop and selected recovery work.

Explore Azure infrastructure

PROJECT DELIVERY

TURN THE REQUIREMENT INTO A DEFINED SCOPE.

Capabilities, licences, prerequisites and service responsibilities are agreed for your environment.

YOUR QUESTIONS

A LITTLE MORE CLARITY.

Who can review and harden Microsoft 365 security in Adelaide?

Subnet does. We are based in Forestville, Adelaide, and have been a Microsoft partner since 2001. We review your tenant against Microsoft and ASD guidance, confirm what your licences already include, apply the changes in stages with a pilot group, and monitor the tenant so settings do not drift.

What does a Microsoft 365 security review look at first?

Work starts by understanding your environment, existing licences and business priorities. The usual path is then to review the controls and agree the changes, exceptions and owners; pilot and implement the selected work, with change approval where needed; and validate the results and hand over. Findings should become implementation decisions with owners and testing, with the handover agreed in scope, not an unchecked list of settings. The users, devices and workloads covered should be agreed in scope.

Does a good Microsoft Secure Score mean we are secure?

No. Secure Score is a useful way to report on and improve your security posture, but it is not a certification. Microsoft says the score is not an absolute measure of how likely a breach is, and that it should not be read as a guarantee against one. Treat it as a progress indicator alongside a view of your business risk.

Will tighter sign-in and access rules disrupt our staff?

They can if they are switched on without testing. Low-impact changes should be separated from those that affect sign-in, access or user workflows. Higher-impact changes need a rollout plan, agreed exceptions and a recovery approach, and should be piloted with representative users and devices, including administrators and business-critical applications. Microsoft Entra Conditional Access also offers a report-only mode, which evaluates a policy and logs the result without enforcing it, so it can be tested before it is enabled.

How do Entra and Intune relate to our existing Active Directory?

Microsoft says organisations with an existing Windows Server Active Directory use Microsoft Entra Connect to sync identities to the cloud. Microsoft Intune can report whether a device is compliant, and Conditional Access can require a compliant device before granting access. Subnet treats an Active Directory assessment as distinct from cloud Entra configuration, so confirm which of the two is in scope for your work.

Do we need Defender for Business or Defender for Endpoint?

It depends on your organisation size, operating requirements and existing entitlements. Microsoft says Defender for Business is designed for small and medium-sized businesses with up to 300 users. It includes the features of Defender for Endpoint Plan 1, some features from Plan 2, and some unique features for small and medium-sized businesses. Microsoft also says protection for Windows and Linux servers needs extra licences, for example the Defender for Business servers add-on. Deployment work should establish which devices are covered, whether existing security tools conflict, how protection is validated and who responds to alerts. Server coverage and ongoing managed detection and response should be explicitly agreed in scope.

What does our Microsoft 365 licence already include for security?

Checking existing entitlements is part of understanding the environment first. As an example from Microsoft’s documentation, Microsoft 365 Business Premium, which Microsoft positions for small and medium-sized businesses of up to 300 users, includes Microsoft Entra ID P1, Microsoft Intune Plan 1, Microsoft Defender for Business, Microsoft Defender for Office 365 Plan 1, and Microsoft Purview Information Protection and data loss prevention. Microsoft also offers a separate add-on, Microsoft Defender Suite for Business Premium, whose components are Microsoft Entra ID P2, Defender for Identity, Defender for Endpoint Plan 2, Defender for Office 365 Plan 2 and Defender for Cloud Apps. Licences, prerequisites and service responsibilities are agreed for your environment.

How do sensitivity labels, DLP and retention differ in Microsoft Purview?

Sensitivity labels classify content and can enforce protection such as encryption and content markings. Data loss prevention policies identify and monitor sensitive items and can block inappropriate sharing, for example by email, across locations such as Exchange and SharePoint. Retention policies and labels retain content, delete it, or both, for a specified period. Each control needs a policy purpose, an owner and testing, and a security uplift should not be assumed to include Purview implementation, so confirm governance requirements, licensing and delivery scope separately.

Should we fix our permissions and data handling before turning on Copilot?

It is worth reviewing first. Microsoft says Copilot only surfaces organisational data that a user has at least view permissions to, so overly broad permissions on content in places such as SharePoint or Teams are worth reviewing before Copilot is turned on. Subnet’s AI, Copilot and data security readiness assessment reviews data security, identity, permissions, information protection, governance and Microsoft 365 readiness. Related Microsoft 365 project work can be discussed separately. Whether a readiness review fits your situation should be agreed in scope.

What do we receive at the end of Microsoft security work?

The path described ends with validating the results and handing over the configuration, outstanding actions and operational responsibilities, so it is clear who looks after each control afterwards. The format and contents of the handover should be agreed in scope. Server coverage, ongoing managed detection and response and any Purview implementation are not assumed and must be agreed explicitly. Capabilities, licences and prerequisites are agreed for your environment.

BEFORE WE TALK

A useful starting point.

You do not need a finished technical brief. Start with the outcome, what you know today and the questions you need answered.

  • What outcome matters to your organisation?
  • Which users, applications, systems and risks are involved?
  • What would a practical first step look like?
Discuss these priorities

LET’S TALK

WHAT WOULD YOU LIKE TO DO NEXT?

Tell us about your organisation and what you need. Start a conversation, discuss a project or request a meeting.

Prefer to talk?(08) 7127 9400Already a customer and need help? Go to Support.
PROPOSED FORM · PRIVATE PREVIEW ONLY

Preview only. Nothing is sent, stored or booked.

A live version will need final routing, consent and privacy review. Subnet privacy policy

Contact us