Some Microsoft consumers were unable to access the business’s Azure and Microsoft 365services on Thursday due to a problem with Microsoft’s geolocation services.Just after 12 p.m. GMT, the Microsoft 365 Status Twitter account posted a tweet notifying clients to the reality that it was”investigating a concern where users with particular conditional access policies applied might be unable to access any Microsoft 365 service,”adding that Microsoft was trying to reverse a recent change in order to reduce the impact.As a result of the change, some users who had an IP-based conditional access policy experienced sign-in issues, as Microsoft’s geolocation service was unintentionally showing traffic was stemming from Tashkent, Uzbekistan, instead of the real native land.”Not cool. Sending out US-based traffic to Uzbekistan is inappropriate on lots of levels,”Twitter user @brianwilson said in a tweet, in addition to screenshots of traffic being routed to Toshkent(the
local name for Tashkent).”Second time this MONTH this has taken place. Earlier this month Azure advertisement was reporting a few of our users as remaining in India; today it’s reporting some are in Tashkent, Uzbekistan (myself included).
We are 100 %based in Canada! “Andy Matthews, an affected customer, said in a tweet. Although the problem was eventually dealt with about eight hours later on, a number of replies to Microsoft’s preliminary tweet suggested the problem had started lots of hours before the business first required to social networks to alert its customers. This is not the very first time this year Microsoft customers have actually been left unable to access the company’s services. At the end of January, Microsoft implemented a network change that saw consumers around the world not able to access its collaboration suite Groups and email service Outlook, as well as Microsoft Exchange Online
, SharePoint Online, and OneDrive for Business.Less than 2 weeks later on, consumers when again reported having concerns accessing Teams and Outlook. Copyright © 2023 IDG Communications, Inc. Source