Home › Blog
Writing
No listicles and no predictions about the future of work. These are write-ups of things that happened on real projects, published because the useful detail is usually the part nobody else prints.
Guides
Written against the threads that recur for years in Microsoft’s own forums, verified against current documentation, with the exact order and the traps.
Seven days, then the term is binding. What the three terms commit you to, how seat reductions work, what happens at expiry, and the two mistakes that cost real money.
Read it →Microsoft now requires a second factor for its admin portals. The five things that break — starting with the six-year-old script running as a user — and the order to fix them.
Read it →The standard advice stops working at 50 GB, exactly where the mailboxes you most want to keep already are. Four options, what each costs, and which fits which situation.
Read it →Free, built in, higher fidelity than copying items, and with prerequisites that stall most first attempts. What has to exist before the batch runs, and what it leaves for other tools.
Read it →Whether the mailbox comes back depends on which state it is in and how many days have passed. How to tell, the commands for each, and the OneDrive clock that runs separately.
Read it →Three reports Microsoft already gives you, an afternoon, and the same three findings every time. How to run it, and how to turn it into money at renewal.
Read it →Nothing bounces and everything goes to junk. The DKIM records are tenant-specific and still describe the tenant you left. What each record does, the fix in order, and the five-minute test.
Read it →A licensed mailbox with a password everyone knows and MFA off is a licensing breach and the softest target in the tenant. The fix is free and takes twenty minutes.
Read it →The files are all there and nobody can find them. What Known Folder Move does, how to deploy it weeks ahead, and the cutover sequence for OneDrive.
Read it →A group is an identity, a mailbox, a site, a membership and whatever sits on top, each with its own route or none. The sequence that works, and the five mistakes.
Read it →Remove the licence and wait thirty days and the mailbox is gone. Three ways to keep it, the exact order, and the traps that catch people every week in Microsoft’s own forums.
Read it →When no administrator can sign in there is one supported path back, and it is slow. What to try first, how to reach Microsoft, and the emergency accounts every tenant should have.
Read it →Your data lives in your tenant and the tenant is yours. Six steps, the one that costs money if you time it wrong, and what to check before you accept.
Read it →A custom domain lives in one tenant at a time. What has to be true before the weekend, ten steps in order, and the DNS mistake that sends everything to spam.
Read it →A team is four services in one, each with its own migration path or none. What actually arrives when tools migrate chat, and the decision that saves most of the cost.
Read it →Write-ups
Every partner uses one of these five. What each does well, where each stops, and the honest pick for five situations — from a partner that resells none of them.
Read it →Nine questions that separate people who have done this from people who have read about it — with the answers you should expect, and the things to ignore.
Read it →The tool vendors say no professional services required. Sometimes they are right. The honest test, the cases where it fails, and the middle option nobody advertises.
Read it →The comparison without the reseller in the room. Where an EA still wins, the four things CSP does that an EA cannot, and the one question that actually decides it.
Read it →The schedule is set by concurrency limits, mailbox size distribution and throttling — not by budget. The arithmetic behind real timelines, and the two things that genuinely shorten them.
Read it →A relocation, 24 TB, no downtime allowed — and a failed virtual machine that put duplicate mail into live mailboxes. What broke, how it was fixed, and why the same fix would not work today.
Read it →Endpoint management falls under co-determination in Germany. Projects that treat approval as a formality get halted after deployment. What is in scope, how long it takes, and how to sequence around it.
Read it →Something you would like written up? Ask — almak@itpartnerhq.com. We would rather write about the question people actually have.
One email a month, at most
Postmortems, timelines, licensing changes that cost people money. No newsletter cadence, no digest of other people’s news. If a month has nothing worth your time, you hear nothing.
Please enter a work email address.
Done. Unsubscribe by replying to any email; we will not argue.