Keep priority customer work moving with a documented outage plan that assigns staff roles, approved alternatives and clear limits on what can continue. Make the instructions accessible without Microsoft 365, test the arrangements beforehand, and include a controlled return to normal work so temporary records aren't missed or entered twice.
What does an outage plan actually cover?
Your Microsoft 365 outage plan should explain how staff will serve customers without their usual email, chat or shared documents. Keep those instructions separate from the technical work needed to restore access.
Microsoft's guidance for app developers distinguishes business continuity planning from disaster recovery, which restores an app's functions and data. It isn't an office outage checklist, but its planning questions are useful here. Which customer tasks matter most, what do they rely on, and what alternatives will work?
I'd build your plan around customer tasks rather than application names. For example, receiving a booking needs a way to speak to the customer and record their request. Confirming that booking might also need access to the current schedule. Give each task its own instructions and stopping point.
Which customer work needs to keep moving?
Prioritise customer tasks according to the effect of delaying them, then identify the information and systems each task needs. Set separate limits for acceptable downtime and missing data, as Microsoft's planning guidance recommends.
Take an appointment-based business as a planning example. You could allow staff to record callback requests while the shared calendar is unavailable. Require them to check availability through an approved alternative before confirming appointments. Write that boundary into the instructions, rather than asking staff to judge it during a busy call.
For each priority task, record the responsible role, required information, approved alternative and point where work must pause. Being willing to delay a booking confirmation doesn't mean you're willing to lose the customer's request. Ask whoever owns that task to agree on those limits with your IT provider.
Who does what while Microsoft 365 is unavailable?
Assign someone to coordinate the outage response, communicate with customers and manage temporary records. Someone may cover several roles, but name a replacement who can activate the plan if the usual coordinator is away.
Microsoft's app-planning guidance calls for defined responsibilities and instructions to activate, carry out and end the contingency plan. For your office, I'd write that sequence around the customer work you've prioritised:
- Have the coordinator check which work is affected with your IT contact, activate the relevant alternative and tell staff where updates will appear.
- Give customer-facing staff an agreed message explaining what can proceed and what needs confirmation later. Don't promise a restoration time your IT contact hasn't confirmed.
- Ask the records owner to log outstanding requests using the approved temporary method. Specify the customer details and follow-up information staff should record.
- Once access returns, have the coordinator check with your IT contact before ending the temporary arrangements. Assign someone to check temporary records against the live system and resolve duplicates or conflicting changes.
Keep the instructions and contact details somewhere staff can access without the affected Microsoft 365 services. Specify the communication channels and record-keeping methods they should use. Don't leave staff to choose personal accounts or devices during a customer call.
What shouldn't we assume about recovery?
Don't treat a backup arrangement as your customer-service plan, or use another product's recovery targets for Microsoft 365. Ask your IT provider to document what your recovery arrangements cover and which tasks still need temporary alternatives.
The supplied Microsoft recovery guidance covers production environments in Power Platform and Dynamics 365. It doesn't establish how quickly Outlook, Teams or your shared files will return. Don't use its recovery figures to promise customers when you'll confirm their bookings.
Test the assumptions behind each alternative too. If your plan relies on another network connection, check that staff can complete the intended task through it. For a separate coverage issue, see why Wi-Fi can be slow in some rooms. Ask your IT contact to establish what's affected before activating an office-wide workaround.
How do we test the plan before we need it?
Run a practice customer request without using its normal Microsoft 365 services, then fix anything that prevents staff completing it. Microsoft's planning guidance recommends regular exercises and updates when functions, systems or requirements change.
- Choose a pretend customer request and make the normal email, chat and shared-file routes off limits for the exercise. Don't disconnect live systems.
- Ask staff to find the instructions, contact the coordinator and record the request using the approved alternative.
- Walk through the return to normal access and transfer the temporary record. Check who verifies it and closes the outstanding request.
- Update unclear instructions, missing contacts or unusable alternatives, then repeat the affected part of the exercise.
If you're unsure which systems a booking or customer request needs, I can help map those dependencies through Microsoft 365 support. Bring the customer tasks you can't leave waiting, and we can work out what staff need to handle each without their usual tools.
For help at home, see our Check a separate Wi-Fi coverage problem.
Sources
Need help with this?
If you'd rather hand it over, Peninsula IT Solutions supports small businesses across Frankston and the Mornington Peninsula, onsite or remotely.
View Microsoft 365 support →Send an enquiry →