Your staff cannot send email, open a shared file, or join a Teams meeting. It looks like Microsoft 365 is down, but the service may be working normally. Your office may have lost the internet connection it needs to reach it.
In UTS’s experience serving Vero Beach and the surrounding Treasure Coast, a local internet interruption is a more common concern than a Microsoft 365 service outage, especially when a business uses an internet connection without a service-level agreement (SLA). Your continuity planning should give that local connection the attention it deserves.
Microsoft 365 can also have outages. Email could be delayed while files still work, or a sign-in problem could prevent access to several applications. Whether the interruption is local or at Microsoft, your plan should answer three questions: who will communicate, what work can continue, and what will you check when service returns?
Is Microsoft 365 down, or is the problem closer to home?
The symptoms can look similar, but the response depends on the cause. Give your IT provider specific observations: which application or action fails, when it started, what error appears, and whether it affects one person, one office, or people in several locations.
- A device or account problem: One employee cannot connect while coworkers can. That points toward an individual issue, although your provider still needs to investigate.
- An office internet problem: Several unrelated online services fail at the same location. Your connection or local network may need attention.
- A Microsoft service problem: Your provider can compare staff reports with the service-health information available to your Microsoft 365 administrator. Microsoft publishes incident information through the Microsoft 365 service-health dashboard.
A working website or an empty status dashboard does not rule out every problem. Let your IT provider assess the evidence rather than having everyone reset passwords or reinstall applications at once. A Microsoft-side outage must be resolved by Microsoft; your provider can help you understand its impact and use your fallback arrangements.
An approved mobile hotspot or alternate internet connection may help when your office connection fails. It cannot restore a Microsoft service that is unavailable. Similarly, a power outage may affect your computers, network equipment, and local internet equipment together, so an alternate connection alone is not a complete plan.
What does your internet agreement actually promise?
An SLA sets out contractual service commitments and the remedies available when the provider fails to meet them. Depending on the service, it may cover availability, performance, response, or restoration targets, with conditions and exclusions. Check your actual agreement; a plan marketed as “business internet” does not, by its name alone, tell you what commitments apply.
If your connection has no SLA covering availability or restoration, do not build your plan around a contractual uptime or repair commitment that you do not have. Fast download speeds are useful, but they do not tell you how an outage will be handled. Ask your provider how you report a failure, how it is escalated, and what repair expectations apply to your service.
An SLA also does not prevent outages or guarantee that your business will keep working. A remedy may be a service credit subject to the agreement’s terms. That credit does not recover your staff’s lost working time or finish a missed customer deadline. Your fallback plan still matters whether or not your primary connection has an SLA.
Plan an alternate connection before your primary one fails
If losing internet stops most of your office, discuss a secondary connection with your IT provider. Decide whether it should support the whole office or only critical work, whether switching is automatic or manual, and who will check that it has happened.
A phone hotspot may be enough for a few urgent tasks. It may not have the capacity, coverage, or configuration needed for your normal workload. A planned backup connection gives you an opportunity to test email, cloud applications, video calls, and business phones rather than discovering its limits during an outage.
Ask how independent the backup really is. Two services can share infrastructure or depend on the same local power. A different provider name alone does not prove that both connections cannot fail together. Wireless backup also depends on coverage, capacity, and power, so test it at your location.
Review what needs backup power in your office, including the modem or internet terminal, firewall, switches, and wireless access points. For a longer power interruption, decide which work can move to another approved location and how staff will get there safely. A short battery runtime should not be treated as a plan for an extended outage.
Finally, test both the switch to backup and the return to the primary connection. Check the critical applications, any data limits or added charges, and who receives an alert. Your IT provider can help you judge the options against the cost of interrupted work.
Before an outage: decide what your business needs to keep moving
Start with the work that cannot wait. Which customer commitments, deadlines, contacts, or documents would you need if email or shared files were unavailable for the rest of the day? Give each critical task an owner and an approved fallback.
For example, if staff normally record customer requests in a shared system, decide how they will capture those requests temporarily and who will enter them afterward. The fallback should preserve enough information to finish the work without encouraging staff to copy sensitive records into personal email or an unapproved app.
Name a decision-maker and a backup who can authorize temporary changes. Decide which work can continue, which work must wait, and when customers need an update. This avoids each employee inventing a different process during the same incident.
Check what is actually available offline
Seeing a file in a OneDrive folder does not prove it is stored on that computer. Cloud-only files need a connection to download. Files marked Always keep on this device are downloaded for offline use once the download completes. Microsoft explains these file states.
Choose essential files in advance and test them on the devices your staff would use. Confirm that the application needed to open or edit them is available too; downloading a document does not make a browser-based application work offline. Check when those copies last synchronized rather than assuming they contain the latest changes.
In classic Outlook for Windows, Cached Exchange Mode can provide access to previously downloaded mailbox items. New Outlook has different offline settings and limitations. What is available depends on your Outlook version, configuration, and what has already downloaded. Sending or receiving still requires the necessary service and connectivity. Ask your provider to check the actual setup your staff uses; do not assume every mailbox or attachment is available offline.
Keep offline information on approved devices or in another approved location, with appropriate access protection. Assign someone to keep essential contact details and procedures current. Avoid creating unnecessary copies of customer records, and decide how temporary documents or paper records will be secured and handled after the incident.
Offline access helps you continue some work. It does not restore Microsoft 365, guarantee current information, or replace a tested backup and recovery plan.
Keep a communication method outside Microsoft 365
If email or Teams is affected, your staff needs another approved way to coordinate. Record key phone numbers and the alternate channel somewhere accessible without signing into the affected service. Check whether that channel depends on the same Microsoft sign-in; another application is not necessarily an independent fallback.
Choose who sends staff and customer updates. A useful message identifies the affected work, the temporary contact method, and when you will provide another update. Avoid promising a restoration time unless it is supported by current information, and distinguish a provider’s estimate from a confirmed recovery.
Unified Technology Solutions (UTS) monitors incidents and shares relevant information through the UTS status page, website notices, and email to key personnel when that channel is available. Bookmark the status page before an incident. It does not require receiving a Microsoft 365 email to read it, although you still need a working internet connection. The channels UnifiedTechs uses can vary by incident.
Keep a short fallback checklist where staff can find it
Your working checklist can be one page, with links to fuller procedures where needed. Include:
- People: The decision-maker, backup, IT contact, and person responsible for customer updates.
- Critical work: Tasks that cannot wait, their owners, and the approved temporary process for each.
- Communication and connectivity: The alternate channel, essential contact numbers, relevant status pages, and instructions for using the approved backup connection.
- Offline resources: Where essential information is stored, who maintains it, and which device can open it.
- Incident record: Where to log blocked work, temporary actions, deadlines, and follow-up owners.
- Recovery checks: What each owner must verify before normal work resumes.
Keep an accessible copy outside the affected system. Review it when responsibilities, applications, or contact information change. A checklist stored only in the SharePoint site you cannot open will not help your team during that outage.
During the outage: follow the plan and record what changes
Follow your organization’s continuity policy. Keep a dated log of affected people, blocked tasks, customer commitments, and temporary work. Record who owns each follow-up so important requests do not disappear between a phone call, a paper note, and the normal system.
For example, a customer request taken by phone should have enough detail for the responsible employee to complete it and record it later. Keep the log in an approved place and avoid putting more sensitive information in it than the task requires.
After service returns: reconcile before closing the incident
A green status indicator is the beginning of recovery for your business. Check that the affected tasks work, email and files are synchronizing, and important messages have been delivered. Review queued email before sending it again so you do not create duplicate instructions or requests.
Enter work captured through temporary processes and check offline edits for conflicts. If two employees changed separate copies of a document, decide which information belongs in the final version. Have each follow-up owner confirm completion before closing the incident.
Then review what caused the most disruption. Was it a missing contact number, a file that had never downloaded, or uncertainty about who could authorize a workaround? Update the plan based on those findings. Your backup may help with data recovery, but it cannot bring Microsoft’s unavailable service back online.
Test the fallback before you need it
Run a short exercise with your team: “Our office internet is down this morning. How do we handle our most urgent customer request?” Walk through the backup connection, contact method, essential information, temporary record, and eventual handoff. Then consider a second scenario in which the connection works but Microsoft 365 does not, so everyone understands when an alternate connection will help.
With your IT provider’s guidance, verify offline access on a suitable test device without disrupting normal operations. Check that the backup decision-maker can find the plan and use it. Record the gaps and assign someone to fix them. The exercise is useful when it reveals a dependency you had overlooked.
If your business in Vero Beach or elsewhere on the Treasure Coast needs help preparing for an internet or Microsoft 365 outage, contact Unified Technology Solutions. We can discuss your dependencies, communication plan, and backup and recovery options in the context of your business.