Connect with us

Blog

Microsoft 365 services fully recovered after multi-day outage

Microsoft has fully restored Microsoft 365 services after a multi-day outage that began November 12, confirming that previously affected environments have recovered and the email backlog has been cleared. The disruption, which stemmed from servers failing health checks and creating Exchange Online traffic imbalances, impacted Outlook, Teams calendar features, Copilot and other tools before ending on November 13.

Published

on

Microsoft has confirmed that services across the previously affected environments have fully recovered and that the backlog of email messages has been processed, bringing an end to a widespread Microsoft 365 outage that began on Thursday, November 12, 2026. The company stated that the issue is remediated. The incident, tracked under EX1550543 and MO1550821, started at 10:05 AM UTC on November 12 and ended at 4:10 PM UTC on Friday, November 13, 2026. This marks the final update for the event. On X, the Microsoft 365 Status account reported that efforts to address the underlying issue had been completed and that service had been restored to the remaining impacted customers and regions.

During the outage, users may have been unable to access or perform several actions in Microsoft 365 services. Features that interact with Exchange Online and email services were primarily affected, while elements that did not depend on them remained functional. Many users were unable to access their Exchange Online mailboxes through Outlook on the web, the Outlook desktop client via MAPI, Exchange ActiveSync, or REST-based connections, and email delivery was delayed. In Microsoft Teams, most core functionality including joining calls, meetings, group chats and channel messages continued to work, but scenarios that depended on Exchange Online such as calendar scheduling, invites, viewing and meeting edits failed for many users, as did the creation of Live or Virtual events, certain Copilot responses that rely on Outlook, calendar or Microsoft 365 files, and the ability to create or delete private or shared channels. Microsoft 365 Copilot users were often unable to load Copilot Chat or receive responses in web and desktop apps, and Copilot experiences could not access work data such as email, calendar and files. Other impacted areas included parts of the Microsoft 365 admin center, Microsoft Graph API requests that access Exchange Online data, Microsoft Defender for Office 365 features such as Safe Links and quarantine operations, Microsoft Defender XDR portal pages, Microsoft Purview services including labeling and data loss prevention, certain Intune device scenarios, Planner, To Do, Power BI and Microsoft Fabric exports involving sensitivity labels, Universal Print, and some Windows 365 Cloud PCs configured with Microsoft Purview Customer Key.

The elevated load and connectivity failures stemmed from Exchange Online traffic imbalances created when a large number of servers unexpectedly became unavailable after failing automated health checks. With fewer healthy backend servers able to accept and process requests, the remaining infrastructure was forced to handle a disproportionate share of the traffic. Microsoft stated that the elevated load was not driven by an increase in overall user traffic volume, but by the sudden loss of server capacity, which strained the systems still in service. Subsequent mitigation efforts, including traffic rebalancing and attempts to return servers to service, produced further imbalances: routing services generated surges in outbound calls when they could not properly direct requests to backend machines, and restored servers sometimes became unresponsive again once they began receiving traffic. These sustained traffic management imbalances complicated recovery as the company worked to identify the underlying cause of the original server failures, scale capacity, optimize routing and carefully repair affected infrastructure.

Microsoft has said it is not aware of any malicious activity that caused the incident. Administrators can find further details under MO1550821 in the Microsoft 365 admin center. With services restored and the email backlog cleared, normal operations have resumed across the previously affected environments.

Continue Reading
Click to comment

Leave a Reply

Your email address will not be published. Required fields are marked *

Business

Microsoft 365 outage continues as recovery efforts stall, disrupting Outlook, Teams, Copilot and more

Microsoft continues efforts to restore Microsoft 365 services after a widespread outage that began November 12, leaving many users unable to access Outlook and Exchange Online while also disrupting Teams calendar features, Copilot, and other tools that rely on email services. The company attributes the problems to servers unexpectedly becoming unavailable, which created sustained traffic management imbalances across its infrastructure, and says it has found no evidence of malicious activity.

Published

on

Microsoft is still working to restore full service after a major global Microsoft 365 outage that began on November 12, 2026. Users in multiple regions continue to face connectivity problems accessing email, collaboration tools, AI features and related services. The company says it has found no evidence of malicious activity and is pursuing multiple workstreams to recover backend servers and manage traffic imbalances.

The disruption is tracked under incident IDs EX1550543 for Exchange Online and MO1550821 for the broader Microsoft 365 suite. Features that interact with Exchange Online and email services are primarily affected, while elements that do not depend on them remain functional. Users may be unable to access their Exchange Online mailboxes through Outlook on the web, the Outlook desktop client via MAPI, Exchange ActiveSync, or REST-based connections, and email delivery may be delayed. In Microsoft Teams, most core functionality including joining calls, meetings, group chats and channel messages continues to work, but scenarios that depend on Exchange Online such as calendar scheduling, invites, viewing and meeting edits can fail, as can the creation of Live or Virtual events, certain Copilot responses that rely on Outlook, calendar or Microsoft 365 files, and the ability to create or delete private or shared channels. Microsoft 365 Copilot users may be unable to load Copilot Chat or receive responses in web and desktop apps, and Copilot experiences may be unable to access work data such as email, calendar and files. Other impacted areas include parts of the Microsoft 365 admin center, Microsoft Graph API requests that access Exchange Online data, Microsoft Defender for Office 365 features such as Safe Links and quarantine operations, Microsoft Defender XDR portal pages, Microsoft Purview services including labeling and data loss prevention, certain Intune device scenarios, Planner, To Do, Power BI and Microsoft Fabric exports involving sensitivity labels, Universal Print, and some Windows 365 Cloud PCs configured with Microsoft Purview Customer Key.

The elevated load and connectivity failures stem from Exchange Online traffic imbalances created when a large number of servers unexpectedly became unavailable after failing automated health checks. With fewer healthy backend servers able to accept and process requests, the remaining infrastructure was forced to handle a disproportionate share of the traffic. Microsoft has stated that the elevated load was not driven by an increase in overall user traffic volume, but by the sudden loss of server capacity, which strained the systems still in service. Subsequent mitigation efforts, including traffic rebalancing and attempts to return servers to service, produced further imbalances: routing services generated surges in outbound calls when they could not properly direct requests to backend machines, and restored servers sometimes became unresponsive again once they began receiving traffic. These sustained traffic management imbalances have complicated recovery, as the company works to identify the underlying cause of the original server failures, scale capacity, optimize routing and carefully repair affected infrastructure without triggering additional instability.

As of early November 13, Microsoft reported that changes applied to improve serviceability were not taking effect as expected. The company is identifying alternate workstreams to increase capacity amid the sustained traffic management imbalances and is continuing work on recovering frontend servers while implementing further traffic optimization actions. It is taking a measured approach to identify and repair affected infrastructure and is tracking results to confirm recovery and performance. Microsoft has emphasized that it is treating the incident with urgency and priority until full resolution and has confirmed it is not aware of any malicious activity. A full post-incident report covering root cause and defense-in-depth repairs is expected once the incident is mitigated.

Administrators can check the latest details in the Microsoft 365 admin center under EX1550543 and MO1550821, or through Microsoft’s public status resources if the admin center is unavailable. This is a service-side incident, and users are generally advised not to reset passwords, reinstall clients or make local configuration changes in an attempt to resolve it. Core functionality that does not depend on Exchange Online interaction may still work in some applications. The outage has affected businesses, schools, government services and individual users worldwide as Microsoft continues efforts to stabilize the infrastructure and restore normal capacity. Further updates are expected as recovery progresses.

Continue Reading

Opinions

Before You Write Off Uganda, Ask What You Have Contributed

Singapore’s transformation offers lessons in leadership, policy, and institutional reform. Rather than simply admiring successful countries, Ugandans should study their journeys and identify what can work at home.

Published

on

They say travelling is one of the few things you will never regret spending money on. But why do some of us travel? Why do I travel?

I travel to learn, to experience, and to see what the world has to offer in terms of economic progress, infrastructure, governance, and development. I travel to benchmark. We study what has worked elsewhere, identify the lessons worth learning, and explore how to adapt them to our own circumstances and the needs of our people.

It is our responsibility to contribute to the development of our country.

And then there are people like Dj City Gal, in an engagement with renowned Ugandan rapper Big Tril. Watch here: Everything she said may be true, but what was the purpose of this? Beyond pointing out what is wrong, what has she done that can be counted as a contribution to Uganda’s development?

She referenced Singapore. But does she understand where Singapore came from and what it took to become the country it is today?

Does she know the circumstances surrounding Singapore’s separation from Malaysia in 1965? Does she understand the challenges Lee Kuan Yew and his government faced, the policies they pursued, and the difficult decisions and institutional reforms that helped transform Singapore?

China has also studied and drawn lessons from Singapore’s economic development experience. But who did Singapore itself learn from? What countries, systems, and ideas influenced the people who built the Singapore we admire today?

These are the questions people with a development mindset ask. We do not simply admire successful countries; we investigate their journeys. We look at the people who inspired them, the systems they adopted, the mistakes they made, and the lessons we can apply to our own circumstances.

Uganda will still be here long after we are gone. The question is: What will your contribution have been?

It is perfectly fine to criticise individual Ugandans. You can love them, dislike them, agree with them, or disagree with them. But do not confuse the actions of particular individuals or those in positions of responsibility with the entire country.

Uganda is not one person. It is all of us.

Lumping an entire nation together in criticism because of the actions of a few is neither fair nor constructive. Direct your criticism at the people responsible, the decisions they make, and the systems that enable them. Do not make every Ugandan a defendant in a case they had no part in creating.

Finally, development begins at home. To everyone in that video, I have a few questions. What meaningful development have you contributed to your home? What have you done for your neighbourhood? Your village? Your parish? Your district? Your region? And beyond all that, what have you contributed to Uganda as a whole?

These questions are not meant to suggest that individual effort alone can solve every national problem. Government has a responsibility to provide leadership, build infrastructure, deliver public services, and create an environment in which citizens can thrive. Holding leaders accountable is necessary. But so is recognising that we, as citizens, also have a role to play.

Before writing off an entire country, consider what you can do to make your own corner of it better. Nobody has stopped you from contributing to the development of your home, your community, or your country.

And if you genuinely believe that your future lies elsewhere, you are free to seek opportunities beyond Uganda’s borders. But leaving should not be confused with contributing, just as staying should not automatically be mistaken for patriotism.

The real question is not simply what Uganda has failed to do for you, but also what you are doing, within your means and responsibilities, to make Uganda better.

Continue Reading

Business

Standard Chartered Uganda Retail Banking Migration to Absa Set for November 2026

Standard Chartered Uganda’s retail banking migration to Absa is set for November 2026. Here’s what customers need to know about account transfers, digital banking registration, debit cards, recurring payments, and customer support.

Published

on

Standard Chartered Bank Uganda’s Wealth and Retail Banking (WRB) business is scheduled to migrate to Absa Bank Uganda on November 13, 2026. Customers can access their Absa accounts, services, and digital banking channels starting November 16, 2026.

In separate communications to customers, both banks outlined the transition timelines and arrangements, which will involve transferring customers’ existing banking relationships to Absa.

On October 13, 2026, Standard Chartered confirmed that the migration would be completed on November 13. The bank assured customers that their existing account terms and conditions, banking facilities, and services would remain unchanged until the migration is fully completed.

Absa Bank Uganda has indicated that final migration and integration activities will occur over the weekend of November 13-15, 2026. Access to Absa accounts and banking channels will commence on November 16.

Absa has assured customers that their current banking arrangements will remain unchanged after the transfer. This includes current and savings accounts, term deposits, loans, insurance policies, wealth products, and other banking facilities such as overdrafts.

The bank has confirmed that existing loan terms and repayment arrangements, as well as the terms, conditions, and benefits associated with other banking products, will remain the same.

As part of the transition, customers will receive separate communications containing their new Absa account details. These details may be required when registering for Absa digital banking services.

Customers will need to set up their digital banking profiles using the Absa Uganda mobile application after receiving confirmation that digital access has been enabled.

The registration process involves downloading the official Absa Uganda app, selecting the “Standard Chartered Customer” option, and providing the required identification details, date of birth, and new Absa account number. Customers will then complete facial verification, create a new password, and register their primary device before setting up a four-digit passcode.

Customers’ existing Standard Chartered usernames will remain unchanged; however, they will need their new passwords and passcodes to access their profiles from November 16, 2026, onwards.

Absa has also confirmed that debit cards are currently being processed, and customers will receive further information on delivery arrangements through the bank’s approved service providers. Existing cheque books will be replaced and delivered alongside the new debit cards, with collection available from the Standard Chartered Bank Speke Road Branch as an alternative.

Customers are encouraged to monitor official SMS and email communications from Absa to obtain their new account details. Once received, these details should be shared with employers, service providers, and other organizations that make payments to or collect payments from their accounts.

Customers should also review standing orders, direct debits, subscriptions, and other recurring payment arrangements linked to their accounts, following Absa’s instructions for any necessary updates.

To prepare for digital banking registration, customers should download the official Absa Uganda mobile application when instructed and have their National Identification Number (NIN) or passport number (for non-Ugandan nationals), date of birth, and new Absa account number ready. Registration should only be completed once the bank confirms that digital access is enabled.

Customers are also advised to monitor official communications regarding the delivery or collection of their new debit cards and replacement cheque books. With final integration activities scheduled for November 13-15, customers should plan accordingly and follow official instructions from both banks regarding changes to their accounts and services. Until the migration is complete, they should continue using the existing banking channels of Standard Chartered.

Until the migration is complete, Standard Chartered customers may continue to access banking services through the bank’s existing branches, ATMs, contact centers, and Relationship Managers.

For assistance before the migration, customers can reach Standard Chartered at ug.service@sc.com or through its 24-hour helplines at +256 313 294 100 and +256 200 524 100.

After the transition, customers can contact Absa through the relevant customer support channels. Personal banking customers can email Absa.Uganda@absa.africa, Prestige customers can reach out at PrestigeBanking.Uganda@absa.africa, Premier customers can contact PremierBanking.Uganda@absa.africa, and SME customers can use BusinessBanking.Uganda@absa.africa.

Customers can also call Absa’s toll-free line at 0800 222 333 or use +256 312 218 348 for assistance.

Continue Reading

Trending