Microsoft が提供する Microsoft 365 のサービス正常性（TM402718）にて、ユーザーが Microsft Teams にアクセスできない SI（サービス インシデント）が発生していました。

本事象は、Microsft Teams 上でのメッセージの送受信や通話、会議の開始が行えないといった様々な影響を受けるものになります。

また、Microsoft Teams Room（MTR）デバイスが Microsft Teams の会議に参加できない可能性があるという事象も報告されていましたが、これらのデバイスでは再起動を行うと正常に動作することが確認されています。

なお、Microsft Teams デスクトップ クライアントに正常にサインインが行えても、すべての機能が停止し、以下のエラー メッセージが表示される可能性があります。

“問題が発生しました。再接続…”

また、Microsft Teams ブラウザー版を利用しているユーザーでは、”予期せぬエラーで操作に失敗しました。” というエラー メッセージが表示される場合があります。

現在、サービス復旧後に本事象の影響は確認されていません。

引き続き、米国内の営業時間中にサービスの監視を行い、問題が解決したことを確認する予定となっています。

本事象は、最近のグローバル管理データベースの導入が、事象発生時に実行されていたサービス インスタンスと互換性がなく、実験的構成サービス（ECS）がサービス要求に対して空の応答を返したことで、Microsft Teams 側の構成でオーバーライドを失い、予期しないエラー メッセージやユーザーから報告された動作のような影響を与えるものになります。

今後は同様の問題が発生しないように Microsft Teams を強化するためのサービス改善を検討しており、5 営業日以内に PIR（Post – Incident Report）を発行する予定です。

この問題は、Microsft Teams を利用しようとするすべてのユーザーに影響する可能性のある事象になります。

目次

Users can’t access Microsoft Teams – TM402718

サービス：Microsoft Teams

状態：Service restored

ユーザーへの影響：Users may be unable to access Microsoft Teams.

Microsoft 365 のサービス正常性（TM402718）にて、ユーザーが Microsft Teams にアクセスできない SI（サービス インシデント）が発生していました。

本事象は、Microsft Teams 上でのメッセージの送受信や通話、会議の開始が行えないといった様々な影響を受けるものになります。

また、Microsoft Teams Room（MTR）デバイスが Microsft Teams の会議に参加できない可能性があるという事象も報告されていましたが、これらのデバイスでは再起動を行うと正常に動作することが確認されています。

なお、Microsft Teams デスクトップ クライアントに正常にサインインが行えても、すべての機能が停止し、以下のエラー メッセージが表示される可能性があります。

“問題が発生しました。再接続…”

また、Microsft Teams ブラウザー版を利用しているユーザーでは、”予期せぬエラーで操作に失敗しました。” というエラー メッセージが表示される場合があります。

現在、サービス復旧後に本事象の影響は確認されていません。

引き続き、米国内の営業時間中にサービスの監視を行い、問題が解決したことを確認する予定となっています。

本事象は、最近のグローバル管理データベースの導入が、事象発生時に実行されていたサービス インスタンスと互換性がなく、実験的構成サービス（ECS）がサービス要求に対して空の応答を返したことで、Microsft Teams 側の構成でオーバーライドを失い、予期しないエラー メッセージやユーザーから報告された動作のような影響を与えるものになります。

今後は同様の問題が発生しないように Microsft Teams を強化するためのサービス改善を検討しており、5 営業日以内に PIR（Post – Incident Report）を発行する予定です。

この問題は、Microsft Teams を利用しようとするすべてのユーザーに影響する可能性のある事象になります。

Post Incident Repot（PIR）

Incident Information

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

July 22, 2022 2:45 PM – Service restored

A post-incident report has been published.

July 22, 2022 2:15 PM – Service restored

A post-incident report has been published.

July 22, 2022 4:05 AM – Service restored

• ・Title : Users can’t access Microsoft Teams
• ・User Impact : Users may have been unable to access Microsoft Teams.
• ・More info : Reported impact scenarios included, but may have not been limited to, the inability to access to the service, initiate messaging, calling, and meetings.
• Additionally, we received reports that Microsoft Teams Room (MTR) devices may have been unable to join Teams meetings; although, we confirmed that restarting these devices successfully restored this functionality.
• The desktop app may have allowed successful sign in; though, without any standard functionality.
• Users may have also seen the following message : “We ran into a problem. Reconnecting…”
• Users leveraging the web client may have seen a message stating “Operation failed with unexpected error.”
• ・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 the Microsoft Teams service.
• ・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 Experimental Configuration Service (ECS) to provide empty responses to service requests, in-turn triggering Microsoft Teams – a consumer of this service – to lose its’ 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 Teams against further issues of this nature.
• We’ll publish a post-incident report within five business days.

July 21, 2022 11:50 PM – Service restored

• ・Title : Users can’t access Microsoft Teams
• ・User Impact : Users may be unable to access Microsoft Teams.
• ・More info : Reported impact scenarios include, but may not be limited to, the inability to access to the service, initiate messaging, calling, and meetings.
• The desktop app may sign in successfully, though all functionalities may be down, and users may see the following message: “We ran into a problem. Reconnecting…”
• Users leveraging the web client may see a message stating “Operation failed with unexpected error.”
• ・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 the Microsoft Teams service.
• ・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 Microsoft Teams or utilize any functions within the service.
• ・Next update by : Friday, July 22, 2022, 4:00 AM (7/21/2022, 7:00 PM UTC)

July 21, 2022 8:57 PM – Service restored

• ・Title : Users can’t access Microsoft Teams
• ・User Impact : Users may be unable to access Microsoft Teams.
• ・More info : Reported impact scenarios include, but may not be limited to, the inability to access to the service, initiate messaging, calling, and meetings.
• The desktop app may sign in successfully, though all functionalities may be down, and users may see the following message : “We ran into a problem. Reconnecting…”
• Users leveraging the web client may see a message stating “Operation failed with unexpected error.”
• ・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 the Microsoft Teams service.
• ・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 Microsoft Teams or utilize any functions within the service.
• ・Next update by : Friday, July 22, 2022, 12:00 AM (7/21/2022, 3:00 PM UTC)

July 21, 2022 6:34 PM – Service restored

• ・Title : Users can’t access Microsoft Teams
• ・User Impact : Users may be unable to access Microsoft Teams.
• ・More info : Reported impact scenarios include, but may not be limited to, the inability to access to the service, initiate messaging, calling, and meetings.
• The desktop app may sign in successfully, though all functionalities may be down, and users may see the following message : “We ran into a problem. Reconnecting…”
• Users leveraging the web client may see a message stating “Operation failed with unexpected error.”
• We’ve performed targeted restarts and recommend that users restart their client if they are experiencing failures when attempting to create or join calls, meetings, or send chats.
• ・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 the Microsoft Teams service.
• ・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 Microsoft Teams or utilize any functions within the service.
• ・Next update by : Thursday, July 21, 2022, 9:00 PM (12:00 PM UTC)

July 21, 2022 4:29 PM – Service restored

• ・Title : Users can’t access Microsoft Teams
• ・User Impact : Users may be unable to access Microsoft Teams.
• ・More info : Reported impact scenarios include, but may not be limited to, the inability to access to the service, initiate messaging, calling, and meetings.
• The desktop app may sign in successfully, though all functionalities may be down, and users may see the following message : “We ran into a problem. Reconnecting…”
• Users leveraging the web client may see a message stating “Operation failed with unexpected error.”
• We’ve performed targeted restarts and recommend that users restart their client if they are experiencing failures when attempting to create or join calls, meetings, or send chats.
• ・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 the Microsoft Teams service.
• ・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 Microsoft Teams or utilize any functions within the service.
• ・Next update by : Thursday, July 21, 2022, 6:30 PM (9:30 AM UTC)

July 21, 2022 3:31 PM – Service restored

• ・Title : Users can’t access Microsoft Teams
• ・User Impact : Users may be unable to access Microsoft Teams.
• ・More info : Reported impact scenarios include, but may not be limited to, the inability to access to the service, initiate messaging, calling, and meetings.
• The desktop app may sign in successfully, though all functionalities may be down, and users may see the following message : “We ran into a problem. Reconnecting…”
• Users leveraging the web client may see a message stating “Operation failed with unexpected error.”
• We’ve performed targeted restarts and recommend that users that are experiencing failures when attempting to create or join calls, meetings, or send chats, restart their client.
• ・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 the Microsoft Teams service.
• ・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 Microsoft Teams or utilize any functions within the service.
• ・Next update by : Thursday, July 21, 2022, 4:30 PM (7:30 AM UTC)

July 21, 2022 2:43 PM – クイック更新 – Service restored

• We’ve performed targeted restarts and recommend that users that are experiencing failures when attempting to create or join calls, meetings, or send chats, restart their client.
• This quick update is designed to give the latest information on this issue.

July 21, 2022 2:14 PM – Service restored

• ・Title : Users can’t access Microsoft Teams
• ・User Impact : Users may be unable to access Microsoft Teams.
• ・More info : Reported impact scenarios include, but may not be limited to, the inability to access to the service, initiate messaging, calling, and meetings.
• The desktop app may sign in successfully, though all functionalities may be down, and users may see the following message : “We ran into a problem. Reconnecting…”
• Users leveraging the web client may see a message stating “Operation failed with unexpected error.”
• ・Current status : A large portion of the Microsoft Teams service has 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 the Microsoft Teams service.
• ・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 Microsoft Teams or utilize any functions within the service.
• ・Next update by : Thursday, July 21, 2022, 3:30 PM (6:30 AM UTC)

July 21, 2022 1:29 PM – Service restored

• ・Title : Users can’t access Microsoft Teams
• ・User Impact : Users may be unable to access Microsoft Teams.
• ・More info : Reported impact scenarios include, but may not be limited to, the inability to access to the service, initiate messaging, calling, and meetings.
• The desktop app may sign in successfully, though all functionalities may be down, and users may see the following message : “We ran into a problem. Reconnecting…”
• Users leveraging the web client may see a message stating “Operation failed with unexpected error.”
• ・Current status : We’re observing continued improvement for a majority of the functions within Microsoft Teams.
• 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 the Microsoft Teams service.
• ・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 Microsoft Teams or utilize any functions within the service.
• ・Next update by : Thursday, July 21, 2022, 3:00 PM (6:00 AM UTC)

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

• We’re receiving many reports that users are able to access Microsoft Teams, 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:49 PM – Service restored

• ・Title : Users can’t access Microsoft Teams
• ・User Impact : Users may be unable to access Microsoft Teams.
• ・More info : Reported impact scenarios include, but may not be limited to, the inability to access to the service, initiate messaging, calling, and meetings.
• The desktop app may sign in successfully, though all functionalities may be down, and users may see the following message : “We ran into a problem. Reconnecting…”
• Users leveraging the web client may see a message stating “Operation failed with unexpected error.”
• ・Current status : We understand the impact that this issue has caused to your organization and are treating this issue with the highest priority.
• We’ve taken action to reroute a portion of traffic in an effort to provide some relief within the environment.
• We anticipate that some users may be able to access some features of Microsoft Teams shortly.
• ・Scope of impact : This issue may potentially affect any user attempting to utilize the Microsoft Teams service.
• ・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 Microsoft Teams or utilize any functions within the service.
• ・Next update by : Thursday, July 21, 2022, 2:00 PM (5:00 AM UTC)

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

• We’re rerouting Microsoft Teams 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:11 PM – Service restored

• ・Title : Users can’t access Microsoft Teams
• ・User Impact : Users may be unable to access Microsoft Teams.
• ・More info : Reported impact scenarios include, but may not be limited to, the inability to access to the service, initiate messaging, calling, and meetings.
• The desktop app may sign in successfully, though all functionalities may be down, and users may see the following message : “We ran into a problem. Reconnecting…”
• Users leveraging the web client may see a message stating “Operation failed with unexpected error.”
• ・Current status : 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 to Teams.
• 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 the Microsoft Teams service.
• ・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 Microsoft Teams, or utilize any functions within the service.
• ・Next update by : Thursday, July 21, 2022, 1:00 PM (4:00 AM UTC)

July 21, 2022 11:05 AM – Service restored

• ・Title : Users can’t access Microsoft Teams
• ・User Impact : Users may be unable to access Microsoft Teams.
• ・More info : Reported impact scenarios include, but may not be limited to, access to the service, messaging, calling, and meetings.
• The desktop app may sign in successfully, though all functionalities may be down and users may see a “We ran into a problem. Reconnecting…” message.
• Users leveraging the web client may see a message stating “Operation failed with unexpected error.”.
• ・Current status : We’ve received reports that users are experiencing issues with the Microsoft Teams service.
• We’re analyzing service telemetry to help identify the source of the issue and determine our next steps to restoring the service.
• ・Scope of impact : This issue may potentially affect any user attempting to utilize the Microsoft Teams service.
• ・Next update by : Thursday, July 21, 2022, 12:00 PM (3:00 AM UTC)

July 21, 2022 10:31 AM – クイック更新 – Service restored

• ・Title : Possible delays or problems when accessing Microsoft Teams
• ・User impact : Some customers have reported issues with accessing the service, or using features in Microsoft Teams.
• ・Current status : We’re looking into your reported issue and checking for impact to your organization.
• We’ll provide an update within one hour.

Microsoft Teams とは？

Microsoft Teams は、Microsoft の提供するコラボレーション ツールになります。

Microsoft Teams 関連記事一覧

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

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

関連リンク

• ・Microsoft Teams｜リモート ワークのためのコラボレーション ツール：https://www.microsoft.com/ja-jp/microsoft-365/microsoft-teams/group-chat-software
• ・日本マイクロソフト – Official Home Page：https://www.microsoft.com/ja-jp

Microsoft Teams 目指せ達人 基本&活用術

created by Rinker

• Amazon
• 楽天市場
• Yahooショッピング

マイクロソフト Surface Pro 8 / Office H&B 2021 搭載 / 13インチ /第11世代 Core-i5 /8GB/256GB / プラチナ 8PQ-00010

created by Rinker

マイクロソフト

• Amazon
• 楽天市場
• Yahooショッピング

【Microsoft ストア限定】3点セット: Surface Laptop 4 13.5インチ(Core i7 / 16GB / 512GB / プラチナ) + Surface Arc Mouse グレー + Surface ペン プラチナ

created by Rinker

マイクロソフト

• Amazon
• 楽天市場
• Yahooショッピング

マイクロソフト Surface Pro X / Microsoft SQ1 / Office H&B 2019 搭載 / 13インチ / SQ1 / 8GB / 128GB / LTE / ブラック MJX-00011

created by Rinker

マイクロソフト

• Amazon
• 楽天市場
• Yahooショッピング