Teams Flickering when joining from Outlook calendar

Anonymous
2023-07-25T17:35:39+00:00

macOS

Teams version 1.6.00.19303-E (updated 7/21/2023)

Outlook version 16.75.1 (23071400)

Many users experiencing an issue where Teams will flicker non-stop when joining a meeting from the Outlook calendar if Teams is not already open.

Will have to force quit Teams application, then reopen Teams separately.

Clearing MS Teams cache doesn't fix the issue.

Only work around is to either join directly from Teams calendar, or open Teams first, then join from Outlook calendar.

Microsoft Teams | Microsoft Teams for business | Meetings and calls | Other

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

43 answers

Sort by: Newest
  1. Anonymous
    2023-09-26T23:22:55+00:00

    same problem and it is September 26th. The response you gave is a non-answer.

    Should my office switch to zoom or google meeting?

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2023-09-26T19:29:33+00:00

    Mac OS 13.5.2

    Outlook 16.77.1

    Yes, my IT department opened a ticket.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2023-09-26T19:22:45+00:00

    What Mac OS are you running and Outlook? Have you opened a ticket with MS yet?

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2023-09-26T16:23:59+00:00

    I'm running 1.6.00.24065 and it is definitely not fixed for me!

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2023-09-26T16:16:33+00:00

    This issue has been fixed by MS if you are running at least 1.6.00.2215 - 1.6.00.24065. Our ticket with them was escalated to the Product team which we received a request to quit Teams and relaunch then test again. As of yesterday I ran all successful tests on the 4 laptops that were running different Teams version and it was resolved.

    I am not sure what they did to fix it, but I am glad its working for our users now. :)

    Was this answer helpful?

    0 comments No comments