Microsoft Outage: What Dallas–Fort Worth Small Businesses Should Do Next

When Microsoft services go down, a normal workday in Dallas–Fort Worth can turn into missed email, canceled meetings, and files nobody can open. The Microsoft outage that started Thursday, November 12, 2026, is still active as of Friday afternoon, November 13, 2026. Outlook, Teams, and Exchange Online are the services small businesses are feeling first.

For offices in Dallas, Fort Worth, Southlake, and the rest of DFW, a short disruption is enough to stall customer replies and the work that brings in revenue. If your business is affected, the priority is to confirm what Microsoft has actually reported, tell your team in a channel that still works, and keep essential operations moving without weakening security.

At 323 Technologies, we help Dallas–Fort Worth small businesses get through IT disruptions with practical guidance, troubleshooting, and a plan that shortens the next outage.

Microsoft outage update for November 13, 2026

Current outage update — Friday afternoon, November 13, 2026, Central Time. Microsoft’s public service-health page at status.cloud.microsoft still shows service degradation for Microsoft 365 business and enterprise accounts, and for Microsoft consumer products. The impact on that page is specific: users may be unable to connect to multiple Microsoft 365 services. Microsoft Azure shows no issues in this incident.

The disruption began Thursday, November 12. Microsoft is tracking it in the Microsoft 365 admin center under two incident IDs:

• EX1550543 — Exchange Online mailbox connectivity
• MO1550821 — the wider Microsoft 365 impact, including features that depend on Exchange Online and email

Your IT administrator can open Health → Service health in the Microsoft 365 admin center. If the admin center will not load, use status.cloud.microsoft.

Microsoft has described the cause as a technical issue introduced during an earlier network capacity upgrade that surfaced after a recent network change. The company has said the incident is not related to a cyberattack or to AI agents, and that it has no evidence of malicious activity. A Microsoft spokesperson said the company is “deeply sorry,” that the underlying issue has been addressed, and that Microsoft is still restoring service to remaining customers and regions because of the scale of demand. A full post-incident report is planned after that review. The BBC reported those statements on November 13.

By Friday afternoon, Microsoft was reporting encouraging recovery, including broader improvement in North America, and email queues moving toward normal levels. People who can open Outlook again may still see intermittent access problems or delayed email. Microsoft has not published a clock time for full restoration. Recheck the official status page before you change anything in your tenant. This section records what was confirmed at publication, and the incident is still moving.

Which Microsoft services are affected

People searching “Outlook down,” “Teams down,” “Microsoft 365 down,” or “Exchange Online outage” are looking at one event. Microsoft’s advisory for this outage has named services whose features depend on Exchange Online and email:

• Exchange Online and Outlook, including Outlook on the web, desktop Outlook (MAPI), mobile mail through Exchange ActiveSync, and the REST API. Mail flow between an on-premises email system and Exchange Online can be affected too.
• Microsoft Teams, including calendar and meeting features that depend on Exchange.
• SharePoint Online
• Microsoft 365 Copilot
• Microsoft Defender XDR

Microsoft’s consumer status is in degradation as well. That has included Outlook.com and other personal Microsoft 365 services such as OneDrive and Teams. A web app can respond when the desktop app does not, or the reverse. Several connection methods were impaired together, so a workaround that works for one person can fail for the next.

First, confirm whether the problem is Microsoft or your local IT

An unavailable inbox or a failed login can look exactly like a down office network, a bad password, or a broken computer. This Microsoft 365 outage produces those symptoms even when your internet and your firewall are fine.

Before anyone restarts equipment or changes settings:

• Check Microsoft’s service health. Compare the incident IDs above, EX1550543 and MO1550821, with what your users are seeing. The public status page is status.cloud.microsoft.
• Identify the scope. One employee, one department, or everyone? Which applications are failing: Outlook, Teams, SharePoint, Copilot, or the whole Microsoft 365 sign-in?
• Record the symptoms. Write down the error message, when it started, and which business tasks are blocked. Delayed email is part of this incident even after the inbox starts to open.
• Contact your IT provider. A provider who already knows your tenant can separate this Microsoft incident from a local outage, a failed laptop, or an account problem that still needs a human.

Hold broad configuration changes until the cause is clear. A licensing change, a DNS edit, or a new mail-flow rule made in the middle of MO1550821 can outlast the outage and make recovery harder.

What your business can do during the Microsoft outage

1. Give employees a clear update

Tell your team which services are affected, what they should do in the next hour, and when you will update them again. Say so even if Microsoft has not given a restoration time.

Use a communication path that does not depend on the affected service. A phone call, a text, or an established emergency contact process will reach people who cannot open Outlook or Teams. Do not send the only copy of the update by email.

2. Prioritize customer-critical work

Focus first on work that affects customers and revenue:

• Urgent customer requests
• Orders and payments
• Schedules and appointment information that staff can still see
• Deadlines that cannot move

Tell customers about a delay when they are waiting on you. Leave tenant details, incident IDs, and account information out of that message. A sentence is enough: email is delayed because of a Microsoft outage, and here is the phone number that works.

3. Use approved workarounds carefully

During this incident, Outlook on the web, the desktop app, and mobile mail have not failed in lockstep. If one method fails, try another approved Microsoft 365 sign-in before you invent a new tool. Neither path is guaranteed while status.cloud.microsoft still shows service degradation.

Files already on the computer, and apps that work offline, can cover a limited amount of work. Keep a list of what was edited offline so the team can resolve sync conflicts after Exchange Online and OneDrive catch up.

Keep business data in the company tenant. Personal email accounts, unapproved file-sharing sites, and unfamiliar chat apps are a poor substitute for Outlook, and they are a common place for data to leak while everyone is trying to keep working. Scam texts and emails that pose as “Microsoft support” are already a known follow-on risk during an outage this visible. Keep multifactor authentication on. Do not share passwords. Do not approve a sign-in prompt you were not expecting. Use the official status page and your known support channel, not a link in an unsolicited message.

4. Keep security controls in place

Microsoft has said this outage is a technical failure in its own network changes, and that it has no evidence of malicious activity. That is a reason to leave your security settings where they are. Turning off multifactor authentication, forwarding company mail to a personal inbox, or clicking a “restore your mailbox” link will not bring Exchange Online back, and it can create a second incident that is yours to clean up.

How 323 Technologies helps small businesses during a Microsoft outage

A managed IT provider cannot repair Microsoft’s infrastructure or promise when MO1550821 will be fully mitigated. What we can do is help a Dallas–Fort Worth business respond while that work is Microsoft’s.

For local small businesses, 323 Technologies can help:

• Assess the impact. Which users, which Microsoft 365 services, and which business processes are actually blocked.
• Troubleshoot local issues. Find the problems that are separate from the Microsoft incident, so a bad laptop or a local network fault is not left sitting under the outage.
• Explain the situation. Turn the service-health wording into the next step for the owner and the staff.
• Evaluate safe workarounds. Use what is still available inside your Microsoft 365 tenant without moving data into unapproved tools.
• Support recovery. After Microsoft reports restoration, check sign-in, Outlook send and receive, Teams meetings, SharePoint and OneDrive sync, and mail that was queued during the outage.

The goal is less confusion, fewer unnecessary changes, and a faster return to normal work once Microsoft’s recovery reaches your tenant.

Prepare now for the next Microsoft 365 disruption

Microsoft 365 is how most Dallas–Fort Worth offices send mail, meet, and store files. This week showed what happens when that dependency stalls for the better part of a day. A practical continuity plan includes:

• An employee communication path that is not Outlook or Teams
• A written list of critical apps and what each one depends on, including Exchange Online
• A short procedure for orders, scheduling, and customer calls during downtime
• Backups that have been restored in a test, not only installed
• Named owners for status updates, support calls, and the recovery check

Backups protect you from data loss. They do not make Outlook available while Exchange Online is degraded. Data protection and continuity have to be in place together. A security review and a tested restore belong in the same plan as the outage phone tree.

Microsoft outage questions from DFW businesses

Is Microsoft down right now?

As of Friday afternoon, November 13, 2026, Central Time, Microsoft’s public status page still listed service degradation for Microsoft 365 business, enterprise, and consumer services. Recovery was underway, especially in North America, and some users could work again. Others still had intermittent access or delayed email. Check status.cloud.microsoft for the live state.

What caused the November 13 Microsoft outage?

Microsoft said the incident was introduced by an issue during an earlier network capacity upgrade and surfaced after a recent network change. The underlying issue has been addressed, and remaining customers are being restored gradually because of the scale of demand. A post-incident report is expected after mitigation is complete.

Is the Microsoft 365 outage a cyberattack?

Microsoft has said it is a technical issue, not related to a cyberattack or to AI agents, and that it has no evidence of malicious activity. Treat unexpected “support” messages as suspicious anyway. Attackers use outages like this one as cover for password theft.

Why is Outlook down when Teams still opens?

This incident hits features that depend on Exchange Online and email. Teams chat can look healthy while the calendar, meeting invites, or mailbox access still fail. Outlook on the web, desktop Outlook, and mobile mail were all listed as connection methods that could fail, and they have not recovered at the same moment for every tenant.

What should a Dallas–Fort Worth small business do during the outage?

Confirm the incident IDs, tell staff by phone or text, protect customer-critical work, and leave security settings in place. Avoid new mail rules, personal email forwarding, and unsolicited recovery links. If you want a local team to sort Microsoft’s incident from your own network, contact 323 Technologies.

When will Microsoft 365 be fully restored?

Microsoft has not given a full-restoration time. Its Friday updates described encouraging recovery, residual impact, intermittent access, and delayed email, with a post-incident report to follow. Plan the rest of the business day as if mail may still arrive late.

Need IT support in Dallas–Fort Worth?

You can get through this outage with a clear status check and a short list of what still has to happen today. If you want help reading the incident, checking your tenant, or building the plan for the next disruption, 323 Technologies works with small businesses across Dallas–Fort Worth.

Contact the team about managed IT support, or call and email directly.

323 Technologies
1560 E. Southlake Blvd. Ste. 100, Southlake, TX 76092
(817) 674-7037
info@323techs.com