Troubleshooting: Microsoft sign-in suddenly stopped for the whole office

If everyone who signs in with Microsoft was working fine and then suddenly can’t get in — and the error mentions that the application is disabled — this is a different problem from the “Need admin approval” prompt new users hit during onboarding. This page is for the “it stopped working” case.

How to recognize this one

This is likely your issue if all of these are true:

You and your team could sign in with Microsoft before — this isn’t a brand-new account.
The error message mentions the application is disabled (it may also show a request ID and a timestamp).
It hit a group of people at once, not just one person.

If instead a first-time user sees “Need admin approval” with Teamio marked unverified, that’s the onboarding approval step, not this — see “Need admin approval” signing in with Microsoft.

Work around it right now

If any affected staff have a Google sign-in (a Gmail or Google Workspace address on file), they can sign in at https://prod.teamio.app using Sign in with Google instead of the Microsoft button. Teamio matches you by email address, so you land in the same account either way — this gets your team working while the Microsoft side is sorted out.

What causes it, and who fixes it

The Teamio app can be switched off in a few different places. Two of them are on Teamio’s side and only Teamio can re-enable them; one is inside your organization’s Microsoft 365 (Entra) tenant, which only your IT admin can fix.

Ask your IT admin to check your tenant

If only your office is affected (other practices still sign in fine), the switch is most likely in your own Microsoft 365. Ask whoever administers it — they’ll need a Global Administrator, Cloud Application Administrator, or Application Administrator role — to do this:

Sign in at entra.microsoft.com.
Go to Enterprise applications > All applications and open Teamio.
Open Properties and set “Enabled for users to sign-in?” to Yes, then select Save.
While there, also check:
- “Assignment required?” — if it’s set to Yes, the affected staff must be added under Users and groups.
- Conditional Access policies — a policy that targets Teamio can also block sign-in.
It’s worth asking why it got turned off (a manual security review or an automatic policy), so it doesn’t happen again.

When it’s on Teamio’s side

If the outage spans your whole office and you’ve heard other practices are affected too, the switch is on Teamio’s side and your admin won’t find anything to change in step 1 above. Contact Teamio support with a screenshot of the error (including the request ID and timestamp if shown) and roughly when it started, and we’ll re-enable it.

Still stuck?

Not sure who your Microsoft 365 admin is? It’s usually your IT support company, or whoever set up your @yourpractice.com email accounts.
Send a screenshot of the full error page and note whether it’s just you or the whole office — that tells us immediately which fix applies.
Your Teamio contact can hop on a short call with your IT admin to walk through it.