SECURITY. WITH A STANDARD.
Repeatable Microsoft 365 security configuration, with room for the way each customer actually works.
Simplified workflow illustration · no live systems connected
THE PROBLEM.
Configuring tenants one setting at a time creates opportunities for drift. At the same time, applying one rigid baseline without understanding users can interrupt legitimate work.
MY ROLE.
After completing Jonathan Edwards’ Secure & Manage Microsoft 365 Business Premium training, I applied its principles to repeatable MSP security baselines using SkyKick, Entra ID and Intune.
HOW IT WORKED.
Define the scope
Create security groups and distinguish managed devices, BYOD users and customer-specific exceptions.
Build a repeatable baseline
Cover MFA, legacy authentication, Conditional Access, app protection, BitLocker and device-management configuration.
Review before enforcing
Assess Conditional Access in report-only mode, review expected impact and introduce changes in stages.
MAKE IT TRUSTWORTHY.
Potentially disruptive Conditional Access changes were reviewed and staged. Report-only assessment helped check the effect before enforcement. Recovery access, exclusions and reversal of an individual policy belong in the deployment plan.
Controls that matter
- Report-only policy assessment
- Staged enforcement
- Customer-specific exceptions
- Managed-device and BYOD separation
- Review of disruptive changes
WHY IT MATTERS.
A repeatable starting point makes differences visible and easier to explain. Engineers can review intentional exceptions instead of rediscovering each tenant’s configuration from scratch.
CONSISTENT DOESN’T HAVE TO MEAN INFLEXIBLE.
Cyber Essentials Plus delivery
GOT SOMETHING
WORTH AUTOMATING?
Tell me where your RMM is creating work.
Let’s look at what could run better —
and how to get there.