Why It Started Inside Heron IT
Working at Heron IT, I kept running into the same problem during Microsoft 365 MFA onboarding. The technical process itself was not the hard part. The hard part was finding something I could send to a client that looked professional, stayed current, and actually helped them finish setup without another support call.
So the first version of the guide was built for our own client use. The aim was simple: one clean link, one clear flow, and fewer tickets caused by confusion rather than genuine technical faults.
Why PDFs, Word Docs, and Video Links Were Not Enough
I found it surprisingly difficult to locate an up-to-date guide that felt safe to hand to end users. A lot of available resources were too broad, too outdated, or too dependent on interface screenshots that no longer matched what people were seeing on screen.
Random YouTube links were never a great answer either. Even when the information was roughly correct, it did not feel especially professional to send clients off to third-party videos with different branding, old phone screens, or unnecessary noise around the actual task.
PDFs and Word documents were not much better in practice. They age quickly, screenshots go stale, and users often stop reading the moment they hit one screen that does not look exactly the same as the file in front of them.
Why I Turned It Into a Public MSP Edition
Once I redesigned the guide properly, it felt wasteful to keep the idea locked to a single internal use case. The public edition at m365guide.korbies.uk is the same underlying approach, rebuilt as a cleaner and more public-safe resource for the wider MSP community.
The point was not to build another marketing page. It was to create a reliable, professional URL that a technician can send with confidence when an end user needs MFA help right now.
What I needed as a technician
One professional link that works better than a stale document or a random video
How the Public Guide Is Built
- Separate iPhone and Android starting points so users are not guessing which route applies to them.
- Real screenshot-led steps from both the computer and the phone, rather than abstract diagrams or generic mockups.
- Built-in narration with replay controls for users who follow spoken guidance better than blocks of text.
- Inline help for common sticking points plus an optional app-password route for the accounts that still surface that extra step.
- Responsive slide layouts that still read clearly during a live desktop support session or on a smaller browser window.
Why Narration and Real Screens Matter
A lot of users are switching between a computer and a phone while already feeling unsure about what MFA is asking them to do. That is why I cared about more than just clean wording. The guide needed real screenshots, one-step-at-a-time pacing, and optional narration for people who follow spoken instructions more comfortably than a wall of text.
In the public stack, each route is split by device, each slide has its own focused instruction, and the extra help states are there for the places users usually hesitate. That is the difference between documentation that is technically correct and guidance that is actually usable under pressure.
What Other MSPs Can Take From This
If you support Microsoft 365 across multiple clients, I think there is real value in having a public-safe onboarding guide for recurring tasks like MFA setup. It reduces repetition for technicians and makes the client experience feel much more deliberate.
My main takeaway is simple: one trustworthy guide usually beats a long email, an attached document, or a scramble to find a tutorial every single time. Keep it current, keep it calm, and make it easy to share.

