M1 optimized teams

Anonymous
2021-03-24T11:30:10+00:00

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?

Microsoft Teams | Microsoft Teams for business | Teams for Mac

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

110 answers

Sort by: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2022-07-01T07:26:23+00:00

    The last update, Build 18112 (released on June 30th), broke telephony for me :-(

    Could I please get a link of a version or two before? Thanks!

    Was this answer helpful?

    0 comments
  2. Anonymous
    2022-07-01T07:30:34+00:00

    Found this: https://github.com/ItzLevvie/MicrosoftTeams-msinternal/commits/master/defconfig. Going through "History" now to get an earlier link :-)

    Was this answer helpful?

    0 comments
  3. Anonymous
    2022-07-01T12:43:34+00:00

    Since c. 2 days, the exploration builds no longer function correctly on a Mac with M1: The devices (audio, video) are no longer recognized and do not show up in the settings - devices section, so you cannot select them. MS Teams also says that no calls are possible and that the admin did disable video.

    None of that is the case.

    Last working version for me was 1.5.00.18014 (maybe there was one later version that worked). All current versions show the above behaviour.

    Running on macOS 12.4 on a MacBook Pro 16" (2021) with M1 Max

    Was this answer helpful?

    0 comments
  4. Anonymous
    2022-07-01T13:04:37+00:00

    I ended up going back to build 1.5.00.18011, published on Wednesday June 29th. So far, nothing seems broken and calls work as they should.

    https://statics.teams.cdn.office.net/production-osx/1.5.00.18011/Teams_osx.pkg

    Was this answer helpful?

    0 comments
  5. Anonymous
    2022-07-06T12:58:56+00:00

    Have you found a subsequent release that resolves your issue?

    I'm still on 1.5.00.16809

    Edit: I've just bumped this up to 1.5.00.18011 now...

    Was this answer helpful?

    0 comments