Skip to content

Technology

inforcer Microsoft policy baselines

Subnet uses inforcer to keep Microsoft 365 security settings consistent for South Australian organisations, and to know the moment a setting changes.

inforcer logo

Microsoft 365 policy management

built for IT service providers

Baselines and drift detection

so settings stay as agreed

Run by Subnet

across Intune, Entra ID and Microsoft security policies

WHAT INFORCER OFFERS

An agreed Microsoft 365 baseline that stays in place

inforcer is a Microsoft 365 management and security platform used by IT service providers to manage policies across tenancies. These are the capabilities Subnet works with most.

Consistency

Policy baselines

inforcer applies a shared, tested set of Microsoft 365 policies, covering devices, identity and security settings, so a tenancy is configured to a known standard instead of one setting at a time.

What it solves

  • Microsoft 365 set up years ago and never reviewed
  • Security settings that differ from what was intended
  • Slow, manual policy changes

How Subnet works with it

We agree a baseline that fits your organisation, apply it in stages and explain what each policy changes for staff.

inforcer tenant policy alignment and deviations

Assurance

Drift detection and correction

inforcer tracks configuration against the baseline and flags when a setting changes, whether by accident, by an administrator or by an attacker, so it can be corrected.

What it solves

  • Settings quietly changed after an audit
  • No alert when a security policy is switched off
  • Not knowing who changed what

How Subnet works with it

We review every drift alert, restore the setting or update the baseline if the change was intended, and keep a record.

Recovery

Policy backup and restore

inforcer keeps a backup of Microsoft 365 policies so a known-good configuration can be restored.

What it solves

  • A change that breaks sign-in or device enrolment
  • No copy of how things were configured before
  • Rebuilding policies from memory

How Subnet works with it

Before any significant change we take a backup, so rolling back takes minutes.

Readiness

Assessments and reporting

inforcer provides tenancy assessments, including Copilot readiness, and reports on security posture for audit and compliance.

What it solves

  • Not knowing how your tenancy compares with good practice
  • Preparing for Copilot
  • Evidence for boards, auditors and insurers

How Subnet works with it

We run an assessment at the start, turn the findings into a plan and re-run it to show progress.

WORK WITH SUBNET

How Subnet works with inforcer

1. Assess

We assess your Microsoft 365 tenancy against a tested baseline.

2. Design

The baseline is adjusted to your needs and the changes are explained before they are made.

3. Deploy

Policies are applied in stages, with a backup taken first.

4. Operate

Drift is monitored and corrected. inforcer is one of the technologies behind Subnet’s managed services.

5. Review

Posture is reported regularly and the baseline updated as Microsoft’s recommendations change.

POLICY WITH PURPOSE

CONSISTENCY ACROSS THE ENVIRONMENT.

Microsoft policy settings need to reflect the organisation’s users, devices and working practices. A useful baseline makes the intended configuration clear and helps the people responsible understand changes and exceptions.

Subnet uses inforcer to apply agreed Intune configuration profiles and security baselines. The platform supports Microsoft policy standardisation and configuration-drift management. The tools, licences and ongoing responsibilities are confirmed for each engagement.

AGREE THE DELIVERY MODEL

A TOOL IS PART OF THE APPROACH.

01

Define the baseline

Agree applicable settings, user impact and exceptions before applying policy changes.

02

Confirm the method

The tools used depend on the delivery model. Some separately scoped policy work may be performed manually rather than through inforcer.

03

Keep ownership visible

Agree who reviews changes, approves exceptions and handles follow-up work. Do not infer ongoing monitoring or a service level from tool capability alone.

CONNECTED EXPERTISE

CONNECT THE POLICY WITH ITS PURPOSE.

Availability and licensing are agreed for the engagement. This page describes supporting technology, not a standalone licence offer or automatic +Security entitlement.

YOUR QUESTIONS

A LITTLE MORE CLARITY.

Who manages Microsoft 365 security baselines in Adelaide?

Subnet does. We are based in Forestville, Adelaide, and use inforcer to apply and maintain an agreed Microsoft 365 policy baseline for South Australian organisations, covering Intune, Entra ID and Microsoft security settings. We assess your tenancy, apply the baseline in stages and tell you when a setting drifts from what was agreed.

What does Subnet use inforcer for?

Subnet uses inforcer as supporting delivery technology for applicable Intune and security-baseline work: applying agreed Intune configuration profiles and security baselines, and helping manage configuration drift. inforcer describes itself as a multi-tenant platform for managed service providers to manage Microsoft 365, and it lists several Microsoft workloads beyond Intune. Subnet’s use of it is limited to what is agreed for your engagement, and some policy work is performed manually instead.

Can we buy inforcer through Subnet, or is it part of +Security?

inforcer is described as supporting delivery technology, not a standalone licence offer and not an automatic +Security entitlement. Whether any licensing, tooling or access is involved, and who holds it, is agreed for each engagement. If you want to understand your options, start with the outcome you need and the Microsoft environment you have today.

What is a policy baseline, and who decides what goes in it?

A baseline is the agreed set of Microsoft policy settings your organisation expects to be in place, reflecting your users, devices and working practices. The settings, the user impact and any exceptions are agreed with you before policy changes are applied. A tool does not decide this: inforcer’s own guidance says it does not decide what your baseline should be, though its templates can be a starting point.

How is an Intune security baseline different from our own policy settings?

Microsoft describes an Intune security baseline as a group of preconfigured Windows security settings, based on recommendations from Microsoft’s security teams and deployed as device configuration profiles. The defaults are mostly the most restrictive values, and Microsoft says Intune cannot know which configuration fits your environment, so it advises understanding the defaults and customising the baseline. Microsoft also notes the baselines are not strictly CIS or NIST compliant. A baseline is a starting point, and the agreed settings should reflect your business.

What is configuration drift, and why does it happen?

Drift is the gap that opens when an environment’s actual settings diverge from its intended baseline. inforcer’s guidance names two common causes: help desk exceptions that are never reverted, and Microsoft platform updates that change defaults. Seeing when a configuration changes is what lets the people responsible decide whether the change was intended, needs an exception or should be corrected.

If a setting changes, is it put back automatically?

Not necessarily. inforcer can compare tenants with a chosen baseline and alert on deviations, and its own guidance recommends automated detection with human review rather than automatic rollback, because emergency changes and legitimate variations should not be reversed unseen. Who reviews a change, who approves exceptions and who follows up are agreed in scope. A tool’s alerting capability does not by itself mean continuous monitoring or a service level.

If a policy is switched on, does that mean everyone is covered?

No. inforcer’s guidance on this makes the point that a policy being configured is different from it protecting the intended users and devices. Gaps it lists include partial scope, legacy sign-in paths, temporary exclusions that become permanent and service accounts that were overlooked. For that reason, exceptions and exclusions should be agreed, recorded and revisited rather than left in place by default.

How do you avoid a baseline change disrupting staff?

Test before wide rollout. Microsoft notes that a new Intune baseline profile deploys to its assigned groups immediately, so its guidance is to duplicate a profile, assign the copy to a test group, validate the result and then roll out. Duplicates do not carry assignments, so they deploy nowhere until assigned. Microsoft also says changes can take from immediately to a few hours to reach devices, and offline devices update at their next sync, so allow for that when planning and checking.

What happens when Microsoft releases a new baseline version?

Microsoft says existing Intune baseline profiles do not upgrade by themselves. Once a newer version is available, the older profile’s settings become read-only, though names, descriptions and assignments can still be edited. Updating is a choice between keeping your customisations or discarding them. The update creates a side-by-side copy whose assignments must be set again, and settings Microsoft removes keep their last value on devices until something else changes them. Agree who reviews each new version and when.

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 capability are you looking for?
  • How would it work with your current environment?
  • Who will own licensing, implementation and ongoing operation?
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