@BrutusTheCat You can do a Bing search for TM221283. This is a known problem that was reported in the O365 Admin Center.
Impact
| Users who are given control by a presenter during a Microsoft Teams meeting are unable to control the screen. |
Depending on how impact is presenting itself for your organization, there are workarounds available. If no mouse or keyboard actions are working, users may click on one of the side rail items (such as Chat, Teams or Calendar) and then return to the meeting screen to mitigate impact. If a user has issues controlling the top of the screen, the sharer needs to move the shared app (such as a web browser or the Outlook client) down 40 pixels to mitigate the impact. Current status: We've determined that a recent service update is causing the problem. We're developing a fix, which is expected to take an extended period of time to complete as we need to make sure that it doesn't negatively impact any additional aspects of the Microsoft Teams service. We're expecting for the validation of the fix to complete by Tuesday, September 15, 2020, at which time we're aiming to provide an ETA for the deployment of the fix and the remediation of impact. Scope of impact: This issue could impact any of your users that are given control during a meeting. Our telemetry suggests that approximately three percent of meetings may experience impact. Root cause: A recent service update is preventing users who are given control by a presenter during a Microsoft Teams meeting from controlling the screen. Next update by: Tuesday, September 15, 2020, at 9:00 PMUTC; PublishedTime=2020-09-03T20:07:05.213Z
Status: We've received reports of an issue in which some users that are given control by a presenter during a meeting are unable to control the screen as expected. We've determined that a recent update may have introduced a code issue which could be causing the impact. We're developing a fix for this potential issue, which will help us confirm the underlying cause of the problem during the testing and validation phase. Next update by: Tuesday, September 1, 2020, at 9:00 PMUTC; PublishedTime=2020-09-01T19:10:39.74Z
Status: We're testing a fix directly with some affected users to confirm that we fully understand the underlying problem and validate that it effectively resolves the issue. Next update by: Tuesday, September 1, 2020, at 11:00 PMUTC; PublishedTime=2020-09-01T20:56:38.25Z
Status: We were unable to validate the fix with the users who we were testing with as they couldn't reproduce the issue prior to the process. We're working to set up additional testing as well as pursuing internal validation options and will update once we have a deployment timeline in place. Next update by: Wednesday, September 2, 2020, at 11:00 AMUTC; PublishedTime=2020-09-01T22:33:49.497Z
Status: We've developed a fix, which we anticipate will mitigate impact for this issue. We're organizing the deployment of this change, and will monitor the affected environments to ensure it provides the expected relief. Next update by: Thursday, September 3, 2020, at 9:00 PM UTC; PublishedTime=2020-09-02T10:17:40.19Z
Status: We've determined that a recent service update is causing the problem. We're developing a fix, which is expected to take an extended period of time to complete as we need to make sure that it doesn't negatively impact any additional aspects of the Microsoft Teams service. We're expecting for the validation of the fix to complete by Tuesday, September 15, 2020, at which time we're aiming to provide an ETA for the deployment of the fix and the remediation of impact. Next update by: Tuesday, September 15, 2020, at 9:00 PMUTC; PublishedTime=2020-09-03T20:07:05.213Z
