Additional meeting and call-related features and issues within Microsoft Teams for business
same issue here on mac.
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
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.
Additional meeting and call-related features and issues within Microsoft Teams for business
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.
same issue here on mac.
So I just took the bait on the "New Teams", downloaded it on both my mac and iphone, and whalla, the problem is gone.
New Teams / pre release preview version installed easily and looks kinda the same, but I now have the weekend to play with it. Lets see what I fix, and what I break:>
Version 23231.406.2360.4907 (23231.406.2360.4907)
Started running into this a couple days ago.
I don't know if New Teams is part of New Outlook but if it is, that's definitely not a solution. New Outlook has to be the worst 'update' I have ever loaded. Thankfully the option to revert back is there but I do wonder how long that is going to be the case.
Joe
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!
Happens to me with High Sierra 10.13.6...