At the end of August I spent a session with two related small businesses, a clinic and a sister business. They're separate companies, and each has its own Microsoft 365 tenant (a tenant is just your business's own space inside Microsoft, with its users, email and settings). Neither had a break-glass account, and that's where this story starts.

Both tenants were run from one admin account. That account's two-factor codes came from an authenticator app on one phone.

If that phone went in a dam or got stolen, nobody could get into either admin panel. Their DNS was managed inside Microsoft too, so a lockout would have taken the domain with it, and the website and email addresses along with it.

That's a pretty common setup in small businesses.

The fix starts with a break-glass account

Microsoft recommends every tenant has emergency access accounts, sometimes called break-glass accounts. They're admin accounts kept for the day the normal admin can't sign in. The details are stored somewhere safe, they aren't used day to day, and they don't rely on the same phone as everything else.

Neither tenant had one. One lost phone was all it would've taken.

Two-factor that blocked the admin

One tenant had two-factor turned on, but no default sign-in method set. In practice the admin account couldn't finish signing in, which is the opposite of what two-factor is meant to do.

We added the authenticator app by scanning the QR code and set it as the default method. After that, admin sign-in worked the way it should.

Office 2016 and the endless sign-in prompts

Staff kept getting asked to sign in, over and over. The cause was Office 2016, which Microsoft no longer supports and which doesn't cope well with the way sign-in works now. We replaced it with the current Microsoft 365 apps.

Word also had some old orphaned accounts attached to it, so we cleared those out.

Keeping the two businesses apart

On paper it would've been tidier to merge everything into one tenant. We kept them separate because they're separate legal entities, and I'd want each business to own its own accounts, email and files.

A login for each person

Staff were all using the one admin login. We moved everyone to their own named account, so every sign-in and every change can be traced back to a person.

For addresses several people need to read, like admin@ and billing@, we set up shared mailboxes. A shared mailbox doesn't need its own licence, and staff open it right alongside their own inbox. Nobody has to share a password to read it.

Our guide to choosing a Microsoft 365 plan explains which accounts need a licence and which don't.

What to take from it

Sign in to your Microsoft 365 admin centre and have a look at the list of admins. If there's only one, and it lives on one phone, you're in the same spot these two businesses were.

What I'd do is add a second admin account, keep its details somewhere safe away from that phone, and check where your domain's DNS is managed. None of it takes long.

This kind of check is part of what we do under managed IT, and the setup side sits under Microsoft 365.