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

43 answers

Sort by: Newest
Most helpful Newest Oldest
  1. Anonymous
    2023-09-21T02:16:40+00:00

    This does not solve the problem... Not helpful...

    Was this answer helpful?

    0 comments
  2. Anonymous
    2023-09-20T14:21:48+00:00

    Thanks for the tip for the workaround for the flickering problem by first opening Teams and THEN click the Outlook reminder "Join" meeting button .

    Hopefully this bug is fixed soon by the engineers.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  3. Anonymous
    2023-09-20T11:23:58+00:00

    Uninstall > restart the machine > install again (search Teams for mac)

    Was this answer helpful?

    0 comments
  4. Anonymous
    2023-09-18T12:55:32+00:00

    Happens to me with High Sierra 10.13.6...

    Was this answer helpful?

    0 comments
  5. Anonymous
    2023-09-18T05:16:47+00:00

    I have just figured out that if you have Teams open when the user clicks the meeting link, Teams will not flicker. If Teams is not running when the meeting is launched, then the flickering occurs.

    The issue only started for these users when they upgraded to macOS Ventura 13.5.2

    Currently opening a ticket with Microsoft now but I am guessing it will be a lost cause.

    I hope this helps someone else to find a workaround!

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments