Where are we now - Microsoft 363? Cloud suite hit with yet another outage
- Reference: 1682342954
- News link: https://www.theregister.co.uk/2023/04/24/microsoft_365_search_outage/
- Source link:
The services affected reportedly include Teams, SharePoint Online, and Outlook. The problem is ongoing and Microsoft isn't saying much more than that. It's unclear how far reaching the outage is.
The Register has contacted Microsoft to get more information.
[2]
DownDetector this morning [3]reported a spike in complaints about a Microsoft 365 outage just before 0800 ET (1200 UTC).
[4]
[5]
"Here we go again, our daily wake up call from M365," one user wrote, with another saying that the software giant is "making my case to move to Exchange Online difficult."
One user said their site was down because of the problem. Another said the outage was causing some confusion around SharePoint.
[6]
"Why is site usage data showing views, whereas hub usage is zero?" they asked.
One user in Ireland wrote on [7]Reddit that the problem had been going on since 1000 local time.
The outage is only the latest to hit Microsoft this year and comes [8]just days after a problem causing high CPU utilization rates in some of its infrastructure tanked the use of various services for many users who were unable to sign into their Microsoft 365 accounts.
[9]
For many, once they finally did get into their accounts, they were unable to see online services like SharePoint Online, Planner, Yammer, and Outlook on the web. Those impacted by the outage were served by the affected infrastructure, with most of the cases being in North and South America.
[10]Microsoft not a Teams player as admin center, 365 service suffer partial outage
[11]Azure blunder left Bing results editable, MS 365 accounts potentially exposed
[12]Microsoft breaks geolocation, locking users out of Azure and M365
[13]Microsoft's Outlook: Cloudy with a chance of junk-mail-stuffed inboxes
It took Microsoft much of the day to clear up that issue. The caching infrastructure was not performing at expected thresholds, which caused timeout exceptions in the Azure Active Directory infrastructure.
In March, Microsoft spent four hours dealing with an [14]outage of Azure Resource Manager in Europe caused by a code change. In February, users saw Outlook [15]crash for a while, and in January, a network change involving a route IP address change in its WAN [16]affected a range of online apps, including Exchange Online, Outlook, Teams, and OneDrive for business.
We will update as more information becomes available. ®
Updated to add
"We've developed a fix to address the impact to the search feature, which we're currently validating internally to ensure it is efficient before deploying," Microsoft said in [17]a tweet
"Additionally, we're exploring if an ECS configuration change may provide quicker relief."
Get our [18]Tech Resources
[1] https://twitter.com/MSFT365Status/status/1650458920786247681
[2] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_offprem/saas&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=2&c=2ZEanqKFeXhCobLZubbug0AAAAJc&t=ct%3Dns%26unitnum%3D2%26raptor%3Dcondor%26pos%3Dtop%26test%3D0
[3] https://downdetector.com/status/microsoft-365/
[4] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_offprem/saas&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=4&c=44ZEanqKFeXhCobLZubbug0AAAAJc&t=ct%3Dns%26unitnum%3D4%26raptor%3Dfalcon%26pos%3Dmid%26test%3D0
[5] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_offprem/saas&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=3&c=33ZEanqKFeXhCobLZubbug0AAAAJc&t=ct%3Dns%26unitnum%3D3%26raptor%3Deagle%26pos%3Dmid%26test%3D0
[6] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_offprem/saas&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=4&c=44ZEanqKFeXhCobLZubbug0AAAAJc&t=ct%3Dns%26unitnum%3D4%26raptor%3Dfalcon%26pos%3Dmid%26test%3D0
[7] https://www.reddit.com/r/sysadmin/comments/12xeayd/m365_issues_this_morning/
[8] https://www.theregister.com/2023/04/20/microsoft_365_services_outage/
[9] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_offprem/saas&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=3&c=33ZEanqKFeXhCobLZubbug0AAAAJc&t=ct%3Dns%26unitnum%3D3%26raptor%3Deagle%26pos%3Dmid%26test%3D0
[10] https://www.theregister.com/2023/04/20/microsoft_365_services_outage/
[11] https://www.theregister.com/2023/03/30/wiz_bing_takeover/
[12] https://www.theregister.com/2023/03/24/microsoft_geolocation_fail_uzbekistan/
[13] https://www.theregister.com/2023/02/21/microsoft_outlook_spam/
[14] https://www.theregister.com/2023/03/23/microsoft_admits_azure_resource_manager/
[15] https://www.theregister.com/2023/02/07/outlook_down/
[16] https://www.theregister.com/2023/01/25/network_issues_causing_outage_in/
[17] https://twitter.com/MSFT365Status/status/1650496203342086145
[18] https://whitepapers.theregister.com/
Re: Single points
Now, if you want to dump your production workloads in the "Cloud", then that's your choice. Personally, I like to touch and feel my servers. That said, I wouldn't lump someone like AWS in the same bucket as Microsoft which just keep on seeming to have issues - normally it seems to be around Azure AD
Re: Single points
"Active Directory"? If this keeps happening, I feel like we should start calling it "Active Defectory" instead...
Re: Single points
Its why I'd like to get out of IT now. I'm getting to the point I've had enough but can't do anything else so have to stick it out until I die or win the lottery. Some cloud stuff is useful the rest is marketing bollocks. When you constantly are ignored that its marketing bollocks it just makes you fed up of it all.
Soon we'll be fully cloud and I've warned it will be more expensive but what do I know. Mark my words, the cost will increase and it won't be any cheaper than onsite kit with engineers to support that onsite kit.
Making on-prem more expensive is a feature, not a bug
The cloud is a self fulfilling prophecy. If it is not more expensive than on-prem, Microsoft will just make it more expensive until it is.
Its a great scheme: Microsoft control the pricing of both on-prem and cloud, so they can raise the prices of both almost at will to get the most profitable outcome for each.
Cloud providers are also in love with the fine-grained level of visibility they get into a customers operations. Meetings, calendars, emails, files, etc. - that will all prove very helpful when the cloud provider launches competing services. See "Amazon Basics" for a comparable strategy. Amazon is letting other companies take the risks and spend the money to create a market, and when it is established they launch a competing product which they advertise first.
[I also believe companies use the cloud to reduce/eliminate technical competency and knowledge in a customer. Then they *have* to buy cloud and other management services as they have no-one who can manage local systems.]
Re: Making on-prem more expensive is a feature, not a bug
"Its a great scheme: Microsoft control the pricing of both on-prem and cloud, so they can raise the prices of both almost at will to get the most profitable outcome for each."
Only for their own products. If you don't like that situation you can go elsewhere. If you're totally sold on the idea that there are no alternatives, maybe you should review the market.
Re: Single points
Are you my secret "brother from another mother".....in another country? LOL
I feel almost exactly the same way as you.
"Cloud suite hit with yet another outage"
...which is why the customer should always have the option of standalone software on their own computer(s).
Some customers are unable to use the search function for online services like Teams and Outlook
So you win a a prize if you can tell the difference between broken search and allegedly working search in Teams?
still having issues with shared calendars not being available for some O365 users
We were having issues all last with O365, a couple of people were dead in the water and couldn't sign into office 365 at all so they couldn't work. Another annoying side effect for all the problems was shared calendars were not showing up for people. I assumed this was sorted out over the weekend, but I have already had two people complaining about the calendars again today.
Me explaining that It's an ongoing issue that is only affecting some users is getting old, folks want me to fix the problem for them.
My Boss is talking about needing to move our support guy into an office to work because he's too loud out in his cubicle and folks are complaining about him. One of the discussed solutions is to move me into the server room since we have a desk setup there. I did work as a Data Center Administrator for a managed hosting company for years, so I am used to the noise levels around running servers, switches, and firewalls. It might not be such a bad thing if I move in there, people will certainly leave me alone and let me do the network administrator duties I am supposed to be working on.
Microsoft, if you want folks to pay for and use Microsoft 365 / Office 365 how about doing what is necessary to keep things running smoothly please.
Single points
We used to tell people to avoid single point problems. Then the cloud came along and a new single point was created... the cloud. Only this time the point is more of a stain-sized dot that blinds all who looked at it.
Well, we never learn, do we?