Bookings stopped syncing with the calendar
Rooms that synced for months quietly stop. The cause is almost always a lapsed sign-in on the account Offision borrows, and the console now says so on its own home page.
A calendar connection does not go red when it breaks. The integration still reports as configured, the rooms are still listed, and bookings simply stop crossing over — which is why this is usually noticed days later, by somebody asking why a meeting is missing from Outlook.
The reason is almost always the same. Offision does not hold your calendar permanently; it borrows the sign-in of an account you nominated, and that sign-in can lapse on its own.
Start at the home page
Open the console’s home page. If any connection needs attention, an Action required card sits at the top of it, with a red count.
The card lists each affected integration as numbered steps: the account that has stopped, why, and how many rooms are out of date because of it. It ends with a Resync rooms step that stays Waiting until the sign-in above it is fixed.
No card at all means no connection is broken. It renders nothing while everything is healthy, so an empty home page is the good answer, not a missing feature.
What the red chip is telling you
Two different accounts can fail, and they break different things:
| Account | What stops working |
|---|---|
| Resource delegate | Room calendars stop syncing in both directions |
| Booking representative | Booking on somebody else’s behalf is blocked |
The chip beside it names the cause, and that is what decides your next move:
| Chip | What happened | What to do |
|---|---|---|
| Sign-in expired | The stored sign-in aged out, usually after a spell of disuse | Sign in again as the same account |
| Access revoked | Consent was withdrawn, or an administrator removed the app | Sign in and accept the permission request again |
| Verification required | The account now demands multi-factor verification | Sign in and complete the challenge |
| Account unavailable | The account is disabled or deleted in the provider | Re-enable it, or sign in as a different account |
| Access denied | The account no longer has rights to those calendars | Restore its access in the provider first |
| Sign-in required | The provider refused without saying why | Try Sign in; if it fails again, collect the details below |
Sign in again from the card
Most commonPress Sign in on the failing step and complete the provider’s sign-in.
Use the same account that was there before — the address is printed on the step for exactly this reason. Signing in as yourself instead is the common mistake: it succeeds, the chip turns green, and the rooms still do not sync, because your account cannot open those mailboxes.
Once the sign-in succeeds, the Resync rooms step turns from Waiting to Ready. Press Resync and the rooms named in the count are brought back up to date. Nothing catches up on its own before you do.
The account itself is gone or locked out
CommonAccount unavailable and Access denied cannot be fixed from Offision. The account has been disabled, deleted, or stripped of its access to the room mailboxes, and signing in will keep failing until that is put right where it was changed.
Fix it in Microsoft 365 or Google Workspace, then come back and sign in.
If the account is gone for good, sign in as a replacement instead. Swapping the account does not disconnect your rooms — they keep syncing on the new account’s permission. The same Renew and Sign in actions sit on the provider’s own tile, if you would rather work from there than from the card.
Open IntegrationsIt keeps lapsing every few months
Less commonA borrowed sign-in is refreshed as long as it is used, and lapses when it is not. An account kept only for this, with a password rotation policy on it, will break on the same schedule as that policy.
Two ways out:
- Exempt the account from password rotation, if your provider allows it for a service account.
- Move the connection to application access, where Offision holds the tenant’s own permission instead of a person’s sign-in and there is nothing to expire. See How Offision connects to Microsoft 365.