About The IT Janitor
Every environment eventually becomes a little messy & someone has to clean it up.
Hi, I'm Sven.
I'm an IT Consultant with a strong focus on Microsoft 365, Azure, Security, Identity, Endpoints and Infrastructure.
Most days are spent helping organisations build, secure, troubleshoot and maintain their IT environments.
Some days are spent cleaning up things that should have been cleaned up years ago. Those are usually the interesting ones.
Why does this site exist?
The honest answer?
Over the years I've accumulated a ridiculous amount of notes, documentation, scripts, troubleshooting steps and discoveries. Some lived in OneNote, some in Markdown files, some in SharePoint, and some in places I've completely forgotten about.
At some point I realised I was spending more time searching for my own documentation than actually using it.
Instead of letting all that knowledge slowly fossilise inside a stale documentation repository, I decided to clean it up, organise it properly and share the useful bits publicly.
That's how The IT Janitor was born.
What's on the menu?
- Microsoft 365 field notes
- Azure documentation
- Security recommendations
- Troubleshooting guides
- PowerShell snippets
- Licensing information
- Useful calculators
- Small utilities that solve oddly specific problems
- Lessons learned the hard way
Why "The IT Janitor"?
Because most IT work isn't building shiny new systems.
It's cleaning up:
- Forgotten configurations
- Mystery permissions
- Legacy settings
- DNS records nobody remembers creating
- Mail flows powered by hope and luck
- Servers everyone is afraid to reboot
- Technical debt disguised as "temporary solutions"
In other words:
Somebody has to mop the tenant and server room.
Is this official documentation?
Not even remotely.
The goal of this site is different.
I just spent three hours figuring this out, so hopefully you don't have to.
Most content published here is based on real-world experience, troubleshooting sessions, customer environments and lessons learned in the field.
Can I trust everything here?
Reasonably.
Everything is based on my own experience and testing, but that differs for everyone and each environment is different.
Always validate changes before deploying them into production.
If you copy a PowerShell command from the internet or let an AI generate one, and immediately decide to run it against a production tenant on a Friday afternoon... That's between you and your change management process.
Why are there tools here as well?
Because documentation alone isn't always enough.
Some problems are easier to solve with a calculator, a generator or a simple tool than with a 2,000 word article.
If I build something that saves me time and I think others might find it useful too, there's a good chance it ends up here.
Found something useful?
That's awesome.
If a guide, tool or calculator saved you time, solved a problem, or prevented an unnecessarily long troubleshooting session, consider clicking:
Sponsor a Mop Upgrade
It helps keep the site running and funds one of the most critical dependencies in IT:
☕ Coffee.
Final note
If you've ever spent an absurd amount of time troubleshooting something only to discover a single checkbox was causing the problem...
You're among friends.