ソニーストア

【トラブルシューティング】Microsoft 365 の複数のサービスが利用できない場合がある SI(サービス インシデント)が発生【MO402741】【復旧済み】【PIR】

  • 2022/07/21
  • Masahiro

Microsoft Office
Microsoft Office

Microsoft が提供する Microsoft 365 のサービス正常性(MO402741)にて、複数のユーザーが Microsoft 365 サービスを利用できなくなる SI(サービス インシデント)が発生しています。

本事象の影響を受けているユーザーでは複数の Microsoft 365 サービスを利用できなくなる可能性があり、以下の問題のうち、1 つ以上で発生していた可能性があります。

また、その他の機能にも影響が発生していた可能性もあります。

  • ・Microsoft Teams(アクセス、チャット、通話、会議、および Microsoft Teams Room デバイスでの会議への参加に関する問題)
  • ・Exchange Online(メール送信の遅延)
  • ・Microsoft 365 管理センター(アクセスできない)
  • ・複数のサービス内の Microsoft Word(読み込みができない)
  • ・Microsoft Forms(Microsoft Teams 経由で使用できない)
  • ・Microsoft Graph API(この API に依存しているサービスは影響を受けている可能性があります)
  • ・Office for the web(Microsoft Word へのアクセスに関する問題)
  • ・SharePoint Online(Microsoft Word へのアクセスに関する問題)
  • ・Project Online(アクセスできない)
  • ・PowerPlatform および PowerAutomate(データベースを含む環境の作成ができない)
  • ・Microsoft Managed Desktop 内の Autopatches
  • ・Yammer(Yammer の実験への影響)
  • ・Windows 365(クラウド PC のプロビジョニングができない)

現在は、最初のサービス復旧後に影響する事例は確認されておらず、引き続き、米国内の営業時間内において、サービスの監視を行い、問題の解消を確認するとのことです。

最近のグローバル管理データベースの導入が、本事象発生時に実行されていたサービス インスタンスと互換性がありませんでした。

このため、Enterprise Configuration Service(ECS)がサービス要求に対して空の応答を返したことにより、一部の Microsoft 365 サービス側で構成のオーバーライドを失い、予期しないエラー メッセージやユーザーから報告された動作への影響が発生しました。

今後は同様の問題が発生しないように Microsoft 365 サービスを強化するためのサービス改善のための要因の特定する作業を行っています。

また、5 営業日以内に PIR(Post – Incident Report)を発行する予定です。

この問題は、上記の Microsoft 365 サービスのいずれかを利用しようとするユーザーに潜在的に影響を与える可能性があります。




PineApple では記事内リンクからアフィリエイト報酬を得ることで当サイトの運営および維持を行っておりますため、ご協力いただけますと幸いです。

目次

Users may be unable to use multiple Microsoft 365 services – MO402741

サービス:Microsoft 365 suite

状態:Service restored

ユーザーへの影響:Users may have been unable to use multiple Microsoft 365 services.

Microsoft 365 のサービス正常性(MO402741)にて、複数のユーザーが Microsoft 365 サービスを利用できなくなる SI(サービス インシデント)が発生しています。

本事象の影響を受けているユーザーでは複数の Microsoft 365 サービスを利用できなくなる可能性があり、以下の問題のうち、1 つ以上で発生していた可能性があります。

また、その他の機能にも影響が発生していた可能性もあります。

  • ・Microsoft Teams(アクセス、チャット、通話、会議、および Microsoft Teams Room デバイスでの会議への参加に関する問題)
  • ・Exchange Online(メール送信の遅延)
  • ・Microsoft 365 管理センター(アクセスできない)
  • ・複数のサービス内の Microsoft Word(読み込みができない)
  • ・Microsoft Forms(Microsoft Teams 経由で使用できない)
  • ・Microsoft Graph API(この API に依存しているサービスは影響を受けている可能性があります)
  • ・Office for the web(Microsoft Word へのアクセスに関する問題)
  • ・SharePoint Online(Microsoft Word へのアクセスに関する問題)
  • ・Project Online(アクセスできない)
  • ・PowerPlatform および PowerAutomate(データベースを含む環境の作成ができない)
  • ・Microsoft Managed Desktop 内の Autopatches
  • ・Yammer(Yammer の実験への影響)
  • ・Windows 365(クラウド PC のプロビジョニングができない)

現在は、最初のサービス復旧後に影響する事例は確認されておらず、引き続き、米国内の営業時間内において、サービスの監視を行い、問題の解消を確認するとのことです。

最近のグローバル管理データベースの導入が、本事象発生時に実行されていたサービス インスタンスと互換性がありませんでした。

このため、Enterprise Configuration Service(ECS)がサービス要求に対して空の応答を返したことにより、一部の Microsoft 365 サービス側で構成のオーバーライドを失い、予期しないエラー メッセージやユーザーから報告された動作への影響が発生しました。

今後は同様の問題が発生しないように Microsoft 365 サービスを強化するためのサービス改善のための要因の特定する作業を行っています。

また、5 営業日以内に PIR(Post – Incident Report)を発行する予定です。

この問題は、上記の Microsoft 365 サービスのいずれかを利用しようとするユーザーに潜在的に影響を与える可能性があります。

Post Incident Repot(PIR)

Incident Information

Important Note
  • This is a preliminary Post Incident Report (PIR) that is being delivered to provide early insight into details of the issue.
  • The information in this PIR is preliminary and subject to change.
  • A final PIR will be provided within five (5) business days from full event resolution and will supersede this document upon publication.
Incident ID
TM402718/MO402741
Incident Title
Users may be unable to use multiple Microsoft 365 services
Service(s) Impacted
Microsoft 365

Glossary

ECS – Enterprise Configuration Service

An internal central configuration repository that allows services to make dynamic changes across multiple services and features.

Additionally, ECS allows us to make changes at a much more targeted level, including specific configurations per tenant or even per user.

Overall summary

On Thursday, July 21, at 1:05 AM UTC, we began receiving reports that users were unable to access or leverage features within the Microsoft Teams service.

We determined this outage was due to a failure in the enterprise configuration service that manages product configuration changes.

Unfortunately, a recent code defect created an incompatible configuration which was not handled properly by downstream services.

This subsequently led to cascading failures and availability impact primarily affecting Microsoft Teams.

We began our mitigation efforts by redirecting traffic to compatible instances at 2:40 AM UTC, and completed this effort at 3:45 AM UTC.

Once complete, many services recovered automatically, however, to expedite recovery we were required to make targeted service side restarts.

Additionally, some users may have needed to restart their Teams client to reconnect.

The majority of impact was recovered by 6:00 AM UTC; however, some users may have continued to experience residual impact with a subset of features until approximately 1:14 PM UTC.

This issue impacted all downstream services that leverage ECS.

The extent of the impact depended on how the service clients behaved when they encountered the issue.

This ranged from services crashing to services that had limited impact.

User Impact

Users may have been unable to use multiple Microsoft 365 services or features.

Microsoft Teams

The majority of impact occurred to the Microsoft Teams service based on how it consumes ECS updates.

This issue affected the users’ ability to connect to the Microsoft Teams Desktop, Web and Mobile clients.

Users who were able to login may have experienced issues with Teams’ features.

PSTN services

Users may have been unable to make calls during the service outage.

Additionally, this impacted services which depended on PTSN calling including; Azure Communication Service (ACS), Direct Routing, Managed Carriers, Skype for Consumer and Operator Connect.

Additionally, services such as Skype MFA, Audio Conferencing, P2P, Call queues. Auto attendant and Emergency calling were also impacted in both directions.

Telemetry indicated that approximately 300k calls were impacted by this event.

The Asia Pacific (APAC) region was most affected due to business hours coinciding with the impact window.

Additionally, Direct Routing and Skype MFA were mostly impacted service.

Other services

Additional Microsoft 365 services and features which experienced some impact included :

  • – Exchange Online (Delays sending mail)
  • – Microsoft 365 admin center (Inability to access)
  • – Microsoft Word within multiple services (Inability to load)
  • – Microsoft Forms (Inability to use via Teams)
  • – Microsoft Graph API (Any service relying on this API may have been affected)
  • – Office Online (Microsoft Word access issues)
  • – SharePoint Online (Microsoft Word access issues)
  • – Project Online (Inability to access)
  • – PowerPlatform and PowerAutomate (Inability to create an environment with a database)
  • – Autopatches within Microsoft Managed Desktop
  • – Yammer (Impact to Yammer flighting)
  • – Windows 365 (Unable to provision Cloud PCs)

Scope of Impact

This issue may have affected any user attempting to utilize the listed Microsoft 365 services.

Incident Start Date and Time

Thursday, July 21, 2022, at 1:05 AM UTC

Incident End Date and Time

The majority of impact was remediated by Thursday, July 21, 2022, at 6:00 AM UTC

There was some isolated residual impact which had recovered by Thursday, July 21, 2022, at 1:14 PM UTC

Preliminary Root Cause

A deployment in the ECS service contained a code defect that affected backward compatibility with services that leverage ECS.

The net result was that for services that utilize ECS it would return incorrect configurations to all its partners.

This resulted in downstream services getting a “200” status message (indicating the pull was successful), however, it actually contained a malformed JSON object.

The extent of the impact depended on how individual Microsoft services utilize the malformed configuration provided by ECS.

Impact ranged from services crashing such as Teams while other services experienced limited to no impact.

Actions Taken (All times UTC)

Thursday, July 21
  • ・12:55 AM – The impact change was deployed to the ECS service.
  • ・1:05 AM – Telemetry indicates this is when impact first occurred within Microsoft Teams, as the incorrect ECS configurations start to be gathered.
  • ・1:16 AM – Our engineering resources start to troubleshoot the issue.
  • ・1:31 AM – Support-based infrastructure which identify commonalities in support reports identified a potential issue with Microsoft Teams.
  • Our automated communication features published TM402718.
  • ・1:45 AM – We analyzed telemetry and diagnostic data from both Azure Blob Storage (more info) and the ECS platform to assist our investigation.
  • ・1:51 AM – TM402718 was expanded worldwide.
  • ・2:20 AM – We isolated log errors and determined that rerouting ECS traffic to alternate components would provide relief.
  • In parallel, we activated additional processing throughput.
  • ・2:30 AM – We rerouted ECS traffic in the East Asia region.
  • ・2:40 AM – After rerouting ECS traffic in East Asia provided relief, we started to reroute the remaining regions to healthy components.
  • ・3:00 AM – Telemetry indicated that the East Asia and Australia regions of the ECS service had recovered.
  • ・3:34 AM – We published MO402741 to communicate the impact to other Microsoft 365 services which were impacted outside of Microsoft Teams.
  • ・3:45 AM – Service monitoring indicated that the West US region for the ECS service had recovered.
  • ・4:00 AM – Asia Pacific (APAC), Japan, and India regions started to see recovery.
  • Work continued to redirect traffic in Europe, US West, and US East in parallel.
  • ・4:40 AM – Telemetry indicated that all ECS service had recovered.
  • ・5:25 AM – Availability for the Microsoft Teams service was showing improvement.
  • We continued to perform targeted restarts to accelerate resolution.
  • ・5:25 AM – Availability for the Microsoft Teams service was showing improvement.
  • ・6:00 AM – Telemetry indicated that the majority of the Microsoft Teams service had recovered, however, there was a subset of services still experiencing some residual impact.
  • We continued to perform targeted node restarts on the Teams Graph Service, allowing the components to gather the correct ECS configuration.
  • ・6:38 AM – We continued to perform targeted node restarts for the Teams Graph Service.
  • ・7:08 AM – Availability across the Microsoft Teams service remained at 99.9 %.
  • There was some residual impact within the Chat service and Bot API services and we continued to perform targeted restarts.
  • We started an extended period of monitoring through European business hours to confirm resolution.
  • ・7:30 AM – As an additional insurance, we recovered the inactive B side infrastructure by via a configuration change once the root cause was determined
  • ・7:47 AM – Telemetry indicated the residual impact to the Chat service had fully recovered, and we continued to work on mitigating the Bot service.
  • ・7:54 AM – Telemetry indicated Bots and forms API recovered.
  • ・8:44 AM – Our telemetry indicated all services are green across all regions with the exception to Desktop App launch in the UK region.
  • ・10:04 AM – Availability in the UK was improving.
  • ・1:14 PM – Telemetry indicated that the impact within the UK had recovered.
  • ・1:58 PM – We entered into a period of extended monitoring throughout the European and US business hours to ensure the issue had resolved.
  • ・6:51 PM – After a period of monitoring, we declared the incident resolved.

Next Steps

Findings
Action
Completion Date
A change to ECS caused the underlying issue.
We’ve corrected the change which caused the incompatibility within the ECS service.
Complete
Our database and service update is packaged by design.
We’ve implemented a framework change to separate these updates.
Complete
The database and service changes being separated need to have sufficient Safe Deployment Time.
We’ve implemented a process change to ensure that database and service changes will be separated by 7 days.
Complete
Monitoring within the Pre-production environment was not tuned to detect this issue early in the deployment cycle.
We’re updating our monitoring thresholds to better identify this type of low-grade failure.
August 2022
The Microsoft Teams service does not fall back to a local version of ECS configurations in the event of an ECS failure.
We’re improving the resiliency of the Microsoft Teams service to fail back to a cached version
August 2022
The ECS service incorrectly returned a ‘200’ status message, which is considered valid.
We’re updating the error logic so that the service returns a ‘500’ error.
August 2022
Fault isolation did not sufficiently protect ECS from this failure.
We’re investing in further fault isolation to limit impact.
Quarter 1, 2023

July 22, 2022 2:45 PM – Service restored

A post-incident report has been published.

July 22, 2022 2:16 PM – Service restored

A post-incident report has been published.

July 22, 2022 4:09 AM – Service restored

  • ・Title : Users may be unable to use multiple Microsoft 365 services
  • ・User Impact : Users may have been unable to use multiple Microsoft 365 services.
  • ・More info : Users may have experienced one or more of the following issues. Additional features or functionality may have also been impacted.
  • – Microsoft Teams (Access, chat, meetings, and Microsoft Teams Room device issues joining meetings)
  • – Exchange Online (Delays sending mail)
  • – Microsoft 365 admin center (Inability to access)
  • – Microsoft Word within multiple services (Inability to load)
  • – Microsoft Forms (Inability to use via Teams)
  • – Microsoft Graph API (Any service relying on this API may have been affected)
  • – Office Online (Microsoft Word access issues)
  • – SharePoint Online (Microsoft Word access issues)
  • – Project Online (Inability to access)
  • – PowerPlatform and PowerAutomate (Inability to create an environment with a database)
  • – Autopatches within Microsoft Managed Desktop
  • – Yammer (Impact to Yammer experiments)
  • – Windows 365 (Unable to provision Cloud PCs)
  • ・Final status : We’ve observed no further instances of impact following the initial service recovery.
  • We’ll continue to monitor the service throughout the remainder of US business hours to further confirm that the issue is resolved.
  • ・Scope of impact : This issue may have potentially affected any user attempting to utilize any of the listed Microsoft 365 services.
  • ・Start time : Thursday, July 21, 2022, 10:07 AM (1:07 AM UTC)
  • ・End time : Thursday, July 21, 2022, 10:14 PM (1:14 PM UTC)
  • ・Preliminary root cause : A recent deployment to our global management database was incompatible with the service instance running at the time the problem occurred.
  • This caused the Enterprise Configuration Service (ECS) to provide empty responses to service requests, trigging some of the consuming services to lose their configuration overrides, resulting in unexpected error responses and the impacting behaviors reported by users.
  • ・Next steps : – We’re working to identify service improvements to strengthen Microsoft 365 against further issues of this nature.
  • We’ll publish a post-incident report within five business days.

July 21, 2022 11:56 PM – Service restored

  • ・Title : Users may be unable to use multiple Microsoft 365 services
  • ・User Impact : Users may be unable to use multiple Microsoft 365 services.
  • ・More info : Users may be experiencing one or more of the following issues. Additional features or functionality may also be impacted.
  • – Microsoft Teams (Access, chat, and meetings)
  • – Exchange Online (Delays sending mail)
  • – Microsoft 365 Admin center (Inability to access)
  • – Microsoft Word within multiple services (Inability to load)
  • – Microsoft Forms (Inability to use via Teams)
  • – Microsoft Graph API (Any service relying on this API may be affected)
  • – Office Online (Microsoft Word access issues)
  • – SharePoint Online (Microsoft Word access issues)
  • – Project Online (Inability to access)
  • – PowerPlatform and PowerAutomate (Inability to create an environment with a database)
  • – Autopatches within Microsoft Managed Desktop
  • – Yammer (Impact to Yammer experiments)
  • – Windows 365 (Unable to provision Cloud PCs)
  • ・Current status: The issue with the Teams Desktop app launch has recovered and the service availability across all the regions is above 99.9 %.
  • We’ll continue to monitor the service through the morning hours in the North American region to ensure this issue doesn’t reoccur.
  • ・Scope of impact : This issue may potentially affect any user attempting to utilize any of the listed Microsoft 365 services.
  • ・Start time : Thursday, July 21, 2022, 10:14 AM (1:14 AM UTC)
  • ・Preliminary root cause : A recent deployment contained a broken connection to an internal storage service, which is causing an issue in which users may be unable to access or use various Microsoft 365 apps or functions.
  • ・Next update by: Friday, July 22, 2022, 4:00 AM (7/21/2022, 7:00 PM UTC)

July 21, 2022 9:06 PM – Service restored

  • ・Title : Users may be unable to use multiple Microsoft 365 services
  • ・User Impact : Users may be unable to use multiple Microsoft 365 services.
  • ・More info : Users may be experiencing one or more of the following issues.
  • Additional features or functionality may also be impacted.
  • – Microsoft Teams (Access, chat, and meetings)
  • – Exchange Online (Delays sending mail)
  • – Microsoft 365 Admin center (Inability to access)
  • – Microsoft Word within multiple services (Inability to load)
  • – Microsoft Forms (Inability to use via Teams)
  • – Microsoft Graph API (Any service relying on this API may be affected)
  • – Office Online (Microsoft Word access issues)
  • – SharePoint Online (Microsoft Word access issues)
  • – Project Online (Inability to access)
  • – PowerPlatform and PowerAutomate (Inability to create an environment with a database)
  • – Autopatches within Microsoft Managed Desktop
  • – Yammer (Impact to Yammer experiments)
  • – Windows 365 (Unable to provision Cloud PCs)
  • ・Current status: We’re investigating the underlying cause of an issue that is affecting the launch of the Teams Desktop app for some users in the UK region. Service availability across all the other regions has stayed above 99 %.
  • We’ll continue to monitor the service to ensure full recovery and apply targeted mitigations for any residual impact.
  • ・Scope of impact : This issue may potentially affect any user attempting to utilize any of the listed Microsoft 365 services.
  • ・Start time : Thursday, July 21, 2022, 10:14 AM (1:14 AM UTC)
  • ・Preliminary root cause : A recent deployment contained a broken connection to an internal storage service, which is causing an issue in which users may be unable to access or use various Microsoft 365 apps or functions.
  • ・Next update by: Friday, July 22, 2022, 12:00 AM (7/21/2022, 3:00 PM UTC)

July 21, 2022 6:49 PM – Service restored

  • ・Title : Users may be unable to use multiple Microsoft 365 services
  • ・User Impact : Users may be unable to use multiple Microsoft 365 services.
  • ・More info : Users may be experiencing one or more of the following issues.
  • Additional features or functionality may also be impacted.
  • – Microsoft Teams (Access, chat, and meetings)
  • – Exchange Online (Delays sending mail)
  • – Microsoft 365 Admin center (Inability to access)
  • – Microsoft Word within multiple services (Inability to load)
  • – Microsoft Forms (Inability to use via Teams)
  • – Microsoft Graph API (Any service relying on this API may be affected)
  • – Office Online (Microsoft Word access issues)
  • – SharePoint Online (Microsoft Word access issues)
  • – Project Online (Inability to access)
  • – PowerPlatform and PowerAutomate (Inability to create an environment with a database)
  • – Autopatches within Microsoft Managed Desktop
  • – Yammer (Impact to Yammer experiments)
  • – Windows 365 (Unable to provision Cloud PCs)
  • ・Current status : Our telemetry indicates that service availability continues to be above 99% across the majority of regions.
  • Some users in the UK region may experience residual impact with certain features in Microsoft Teams.
  • We’re continuing to monitor the service to ensure full recovery and apply targeted mitigations for any residual impact.
  • ・Scope of impact : This issue may potentially affect any user attempting to utilize any of the listed Microsoft 365 services.
  • ・Start time : Thursday, July 21, 2022, 10:14 AM (1:14 AM UTC)
  • ・Preliminary root cause : A recent deployment contained a broken connection to an internal storage service, which is causing an issue in which users may be unable to access or use various Microsoft 365 apps or functions.
  • ・Next update by : Thursday, July 21, 2022, 9:30 PM (12:30 PM UTC)

July 21, 2022 5:04 PM – Service restored

  • ・Title : Users may be unable to use multiple Microsoft 365 services
  • ・User Impact : Users may be unable to use multiple Microsoft 365 services.
  • ・More info : Users may be experiencing one or more of the following issues.
  • Additional features or functionality may also be impacted.
  • – Microsoft Teams (Access, chat, and meetings)
  • – Exchange Online (Delays sending mail)
  • – Microsoft 365 Admin center (Inability to access)
  • – Microsoft Word within multiple services (Inability to load)
  • – Microsoft Forms (Inability to use via Teams)
  • – Microsoft Graph API (Any service relying on this API may be affected)
  • – Office Online (Microsoft Word access issues)
  • – SharePoint Online (Microsoft Word access issues)
  • – Project Online (Inability to access)
  • – PowerPlatform and PowerAutomate (Inability to create an environment with a database)
  • – Autopatches within Microsoft Managed Desktop
  • – Yammer (Impact to Yammer experiments)
  • – Windows 365 (Unable to provision Cloud PCs)
  • ・Current status : Service availability has mostly recovered with only a few service features still requiring attention.
  • We’ll continue to monitor the service as new regions enter business hours to ensure the service health does not fluctuate while the remaining actions are completed.
  • ・Scope of impact : This issue may potentially affect any user attempting to utilize any of the listed Microsoft 365 services.
  • ・Start time : Thursday, July 21, 2022, 10:14 AM (1:14 AM UTC)
  • ・Preliminary root cause : A recent deployment contained a broken connection to an internal storage service, which is causing an issue in which users may be unable to access or use various Microsoft 365 apps or functions.
  • ・Next update by: Thursday, July 21, 2022, 7:30 PM (10:30 AM UTC)

July 21, 2022 3:20 PM – Service restored

  • ・Title : Users may be unable to use multiple Microsoft 365 services
  • ・User Impact : Users may be unable to use multiple Microsoft 365 services.
  • ・More info : Users may be experiencing one or more of the following issues.
  • Additional features or functionality may also be impacted.
  • – Microsoft Teams (Access, chat, and meetings)
  • – Exchange Online (Delays sending mail)
  • – Microsoft 365 Admin center (Inability to access)
  • – Microsoft Word within multiple services (Inability to load)
  • – Microsoft Forms (Inability to use via Teams)
  • – Microsoft Graph API (Any service relying on this API may be affected)
  • – Office Online (Microsoft Word access issues)
  • – SharePoint Online (Microsoft Word access issues)
  • – Project Online (Inability to access)
  • – PowerPlatform and PowerAutomate (Inability to create an environment with a database)
  • – Autopatches within Microsoft Managed Desktop
  • – Yammer (Impact to Yammer experiments)
  • – Windows 365 (Unable to provision Cloud PCs)
  • ・Current status : We’re addressing any residual impact related to this event. In parallel, we are adding additional infrastructure to ensure the stability of the service as traffic returns to normal levels.
  • Additionally, we are monitoring for any signs of failure until we’re confident that all functions of the service are fully recovered.
  • ・Scope of impact : This issue may potentially affect any user attempting to utilize any of the listed Microsoft 365 services.
  • ・Start time : Thursday, July 21, 2022, 10:14 AM (1:14 AM UTC)
  • ・Root cause : A recent deployment contained a broken connection to an internal storage service, which is causing an issue in which users may be unable to access or use various Microsoft 365 apps or functions.
  • ・Next update by: Thursday, July 21, 2022, 5:30 PM (8:30 AM UTC)

July 21, 2022 2:36 PM – Service restored

  • ・Title : Users may be unable to use multiple Microsoft 365 services
  • ・User Impact : Users may be unable to use multiple Microsoft 365 services.
  • ・More info : Users may be experiencing one or more of the following issues.
  • Additional features or functionality may also be impacted.
  • – Microsoft Teams (Access, chat, and meetings)
  • – Exchange Online (Delays sending mail)
  • – Microsoft 365 Admin center (Inability to access)
  • – Microsoft Word within multiple services (Inability to load)
  • – Microsoft Forms (Inability to use via Teams)
  • – Microsoft Graph API (Any service relying on this API may be affected)
  • – Office Online (Microsoft Word access issues)
  • – SharePoint Online (Microsoft Word access issues)
  • – Project Online (Inability to access)
  • – PowerPlatform and PowerAutomate (Inability to create an environment with a database)
  • – Autopatches within Microsoft Managed Desktop
  • – Yammer (Impact to Yammer experiments)
  • – Windows 365 (Unable to provision Cloud PCs)
  • ・Current status : A large portion of the affected services have recovered; however, our telemetry indicates that a portion of users may continue to experience issues utilizing some features.
  • We’re performing targeted actions to address the impact that persists.
  • ・Scope of impact: This issue may potentially affect any user attempting to utilize any of the listed Microsoft 365 services.
  • ・Start time : Thursday, July 21, 2022, 10:14 AM (1:14 AM UTC)
  • ・Root cause : A recent deployment contained a broken connection to an internal storage service, which is causing an issue in which users may be unable to access or use various Microsoft 365 apps or functions.
  • ・Next update by : Thursday, July 21, 2022, 3:30 PM (6:30 AM UTC)

July 21, 2022 1:32 PM – Service restored

  • ・Title: Users may be unable to use multiple Microsoft 365 services
  • ・User Impact: Users may be unable to use multiple Microsoft 365 services.
  • ・More info: Users may be experiencing one or more of the following issues.
  • Additional features or functionality may also be impacted.
  • – Microsoft Teams (Access, chat, and meetings)
  • – Exchange Online (Delays sending mail)
  • – Microsoft 365 Admin center (Inability to access)
  • – Microsoft Word within multiple services (Inability to load)
  • – Microsoft Forms (Inability to use via Teams)
  • – Microsoft Graph API (Any service relying on this API may be affected)
  • – Office Online (Microsoft Word access issues)
  • – SharePoint Online (Microsoft Word access issues)
  • – Project Online (Inability to access)
  • – PowerPlatform and PowerAutomate (Inability to create an environment with a database)
  • – Autopatches within Microsoft Managed Desktop
  • – Yammer (Impact to Yammer experiments)
  • – Windows 365 (Unable to provision Cloud PCs)
  • ・Current status: We’re observing continued improvement for a majority of the functions within the Microsoft 365 apps.
  • We’re focused on the areas that have not recovered and are taking action to restore service at the highest priority.
  • ・Scope of impact : This issue may potentially affect any user attempting to utilize any of the listed Microsoft 365 services.
  • ・Root cause : A recent deployment contained a broken connection to an internal storage service, which is causing an issue in which users may be unable to access or use various Microsoft 365 apps or functions.
  • ・Next update by : Thursday, July 21, 2022, 3:00 PM (6:00 AM UTC)

July 21, 2022 1:14 PM – クイック更新 – Service restored

  • We’re receiving many reports that users are able to access various Microsoft 365 services, and many functions are beginning to recover.
  • We’re continuing work to fully restore the service at our highest priority.
  • This quick update is designed to give the latest information on this issue.

July 21, 2022 12:46 PM – Service restored

  • ・Title : Users may be unable to use multiple Microsoft 365 services
  • ・User Impact : Users may be unable to use multiple Microsoft 365 services.
  • ・More info : Users may experience issues accessing or using features within the following Microsoft 365 services :
  • – Microsoft Teams
  • – Microsoft 365 Admin center
  • – Microsoft Word within multiple services
  • – Office Online
  • – SharePoint Online
  • – Project Online
  • – PowerPlatform and PowerAutomate
  • – Autopatches within Microsoft Managed Desktop
  • – Yammer
  • – Windows 365
  • ・Current status : We’ve taken action to reroute a portion of traffic in an effort to provide some relief.
  • We anticipate that some users may be able to utilize various Microsoft 365 apps or functions.
  • ・Scope of impact : This issue may potentially affect any user attempting to utilize any of the listed Microsoft 365 services.
  • ・Root cause : A recent deployment contained a broken connection to an internal storage service, which is causing an issue in which users may be unable to access or use various Microsoft 365 apps or functions.
  • ・Next update by : Thursday, July 21, 2022, 2:00 PM (5:00 AM UTC)

July 21, 2022 12:39 PM – クイック更新 – Service restored

  • We’re rerouting Microsoft 365 service traffic to an alternate region in an effort to provide some relief and potentially restore some functionality to the service.
  • This quick update is designed to give the latest information on this issue.

July 21, 2022 12:34 PM – Service restored

  • ・Title : Users may be unable to use multiple Microsoft 365 services
  • ・User Impact : Users may be unable to use multiple Microsoft 365 services.
  • ・More info : Users may experience issues accessing or using features within the following Microsoft 365 services :
  • – Microsoft Teams
  • – Microsoft 365 Admin center
  • – Microsoft Word within multiple services
  • – Office Online
  • – SharePoint Online
  • – Microsoft Managed Desktop
  • ・Current status : This post is related to an ongoing Microsoft Teams issue under TM402718, that we believe may have downstream impact on the service listed above.
  • We’re currently investigating the full scope of impact.
  • Our investigation has determined that a recent deployment contained a broken connection to an internal storage service.
  • We’re working to direct traffic to a healthy service to remediate the impact.
  • In parallel, we’re exploring other options to mitigate impact as quickly as possible.
  • ・Scope of impact : This issue may potentially affect any user attempting to utilize any of the listed Microsoft 365 services.
  • ・Root cause : A recent deployment contained a broken connection to an internal storage service, which is causing an issue in which users may be unable to access or use various Microsoft 365 apps or functions.
  • ・Next update by : Thursday, July 21, 2022, 1:30 PM (4:30 AM UTC)

デル株式会社

Microsoft 365 suite 関連記事一覧

Microsoft 365 suite のメッセージ センター関連情報一覧

Microsoft 365 suite のメッセージ センター関連記事一覧

デル株式会社

Microsoft 365 suite サービス正常性 関連記事一覧

関連リンク

  • ・Microsoft 365 – サブスクリプションで Office アプリを使用|Microsoft 365:
  • ・日本マイクロソフト – Official Home Page:https://www.microsoft.com/ja-jp




ナノ・ユニバース公式通販サイト

コメントを残す

メールアドレスが公開されることはありません。 が付いている欄は必須項目です

このサイトはスパムを低減するために Akismet を使っています。コメントデータの処理方法の詳細はこちらをご覧ください

カテゴリー

  • Apple
  • Windows
  • オーディオ
  • カメラ
  • スマートフォン
  • Hobby
  • 旅行

デル株式会社

ゴールデン ウィーク 新しいパソコンで GW を楽しもう

  • PR by DELL Technologies

  • PR by final

  • PR by e ☆ イヤホン