Using Microsoft Teams on macOS, including installation, features, and compatibility
That Teams 2.0 is currently for Teams for public users only. No plan for Teams for biz yet
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
I want to know about teams M1 support as teams through rosetta glitches and Touch Bar controls especially leave button doesn't work. When can we get an arm based M1 apple silicon optimized teams?
Using Microsoft Teams on macOS, including installation, features, and compatibility
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.
That Teams 2.0 is currently for Teams for public users only. No plan for Teams for biz yet
I agree with your response. Sadly, it has been 7 months since your reply, and still no movement from Microsoft...
I still don't understand why its not out yet. Its been almost 2 years since M1's roll out, and its not like it should be hard to make an ARM based version, since we already have one for IOS and IPadOS (both are ARM based)
Since OneDrive on Monterey, is broken for plenty of people from what I can tell from the app-store reviews - it would be great if Apple and Microsoft could get these business app working correctly and efficiently!
Since OneDrive on Monterey, is broken for plenty of people from what I can tell from the app-store reviews - it would be great if Apple and Microsoft could get these business app working correctly and efficiently!
Ah!, yesterday I just tried updating from the app-store version, to the standalone version downloaded from Microsoft's website, (and set to beta) to try and get the Apple Silicon 1drive working, but it keeps failing when logging in and trying to set the folder. For some reason it asks me to provide my account email twice, then tells me it cannot sync when I select my directory.
I've tried "resetting" 1drive, going back to the app-store version getting it all working as expected then overwriting the app with the web-download version but all with the same failed results.
So Judging by what you are saying, it's not just me with this issue ?