First, confirm whether it is a wider outage

Check the Microsoft 365 Service health dashboard or Microsoft's public status page and compare reports from several users, devices and internet connections. If many people cannot reach Outlook, Teams or related services at the same time, record the symptoms and avoid treating every computer as a separate fault. Microsoft may restore different services or regions gradually, so intermittent access does not necessarily mean the issue is inside your business.

Do not change working DNS settings during a provider incident

DNS records control how your domain, website and email are located. Changing known-good mail records, nameservers or authentication records will not repair Microsoft's unavailable infrastructure and may create a second problem that remains after the provider outage is resolved. Preserve the current configuration unless a qualified administrator has confirmed a separate DNS fault and has a documented rollback plan.

Use an agreed alternative communication channel

Your continuity plan should name a backup method that does not depend on the affected Microsoft 365 service. This may be a phone tree, SMS group, separate status page or another approved messaging platform. Keep an offline copy of essential staff, supplier and customer contact details, and tell people in advance which channel will be used. Avoid moving confidential information into personal accounts or unapproved apps simply because the normal service is unavailable.

Decide which work must continue

Identify the few activities that cannot wait: receiving urgent customer calls, confirming bookings, processing time-sensitive orders, coordinating field staff or accessing critical operating instructions. Give each activity an owner, an alternative process and a clear record of what must be entered back into the normal system after recovery. A short, rehearsed checklist is more useful during an outage than a long plan nobody can find.

Document recovery and the return to normal

Record who checks provider status, who communicates with staff and customers, and who decides when normal systems are reliable again. Once service returns, confirm that delayed messages, calendars, Teams activity and connected applications have synchronised before assuming everything has completed. Note any manual work performed during the outage and reconcile it so requests, approvals or customer records are not missed.

Where backup fits—and where it does not

Microsoft 365 backup can help recover deleted, corrupted or compromised business data, but backup alone does not make Outlook or Teams available while Microsoft's live platform is experiencing an outage. Continuity planning addresses the period without the service; backup and tested recovery address data loss. Small businesses usually need both, with realistic expectations about what each control can and cannot do.

Prepare before the next disruption

Maintain current emergency contacts, export the small amount of information needed to operate safely offline, document key dependencies and test an outage scenario with the team. Review which workflows depend on Microsoft 365 sign-in, email, Teams, SharePoint or connected applications. The aim is not to duplicate every cloud service—it is to keep essential communication and decisions moving until normal service returns.

Build a more resilient support plan

Explore Avant IT’s Managed IT Service, Microsoft 365 & Cloud support, and Backup & Continuity service. For the latest provider status during an incident, check Microsoft’s public service health page

Building something useful together

Did this guide help?

If an Avant IT article helped you solve a problem or better understand your technology, you can make an optional $5 contribution towards creating more practical guides. Help keep us awake and typing by shouting the team a coffee! Every guide is created in-house by our passionate team, often in our own time, to share our knowledge and give back to the community.

Your support is completely optional but always appreciated.
$5,000 community goal

Help us build a free guided troubleshooting centre for common email, Wi-Fi, internet, computer and browser problems.

Support the free tools