Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
However, the Office team ported the Windows version of the apps from x64 Windows to ARM64 Windows over a decade ago. They also maintained 32bit and 64bit Windows versions of the apps for years and iOS versions of the apps.

If you are talking about the Surface RT, that work was built on 32-bit ARMv7. Keep in mind Apple was the first to deliver an ARM64 chip to market (in 2013, while Surface RT shipped a year prior). Apple moved quickly enough on ARMv8 that other OEMs were caught off guard.

That said, Win 10-based WoA supports both ARMv7 and v8, but I’m not sure what state the WoA port at the time, and if it had been fully ported to ARMv8. Anything not ported to ARMv8 wouldn’t benefit the AS port.

As Erik Schwiebert mentioned in an interview, parts of Office are dependent on the .NET runtime, which also needed to be ported (and is one of those complex dependencies you mention since it includes a JIT engine). And don’t forget that VBA is another JIT engine. And as iPad version doesn’t support VBA, you couldn’t depend on the iPad version to catch all the stuff Mac/Windows did. Erik also mentioned in the interview that they were brought into the Apple labs back in March under NDA, so months prior to WWDC.

That said, all the previous work certainly cut down the cost of the work for sure. But Office in particular is a rather old beast with lots of nooks and crannies for work to hide. The thing still supports COM and OLE on Apple Silicon.
 
  • Like
Reactions: MiniApple
If you are talking about the Surface RT, that work was built on 32-bit ARMv7. Keep in mind Apple was the first to deliver an ARM64 chip to market (in 2013, while Surface RT shipped a year prior). Apple moved quickly enough on ARMv8 that other OEMs were caught off guard.

That said, Win 10-based WoA supports both ARMv7 and v8, but I’m not sure what state the WoA port at the time, and if it had been fully ported to ARMv8. Anything not ported to ARMv8 wouldn’t benefit the AS port.

As Erik Schwiebert mentioned in an interview, parts of Office are dependent on the .NET runtime, which also needed to be ported (and is one of those complex dependencies you mention since it includes a JIT engine). And don’t forget that VBA is another JIT engine. And as iPad version doesn’t support VBA, you couldn’t depend on the iPad version to catch all the stuff Mac/Windows did. Erik also mentioned in the interview that they were brought into the Apple labs back in March under NDA, so months prior to WWDC.

That said, all the previous work certainly cut down the cost of the work for sure. But Office in particular is a rather old beast with lots of nooks and crannies for work to hide. The thing still supports COM and OLE on Apple Silicon.

Yes, I was referring the Surface RT but MS has continued supporting ARM versions on Windows and in some ways ARMv8 is simpler. Supporting Windows technologies like COM (still a core part of the Windows tech stack) on MacOS at all is a challenge. Like compiler backends JIT engines obviously have to be written for the target architecture but that work already had to be done for Windows. I seem to recall that Apple announced MS Office support at WWDC so I am sure they were talking to MS for a while.

MS Office is certainly a large, old and complex code base (like Photoshop for example). It is much more complex than Teams but has full native support for Apple Silcon. Teams, a much simpler and newer app built on web tech does not. That suggests to me that the delay in AS support is because it has not been a priority for that team.
 
Having been forced to use MS Teams on Windows via a poorly executed VMWare Horizon VDI in my hospital, I LOVE LOVE LOVE both the beta M1 Mac version of Teams and/or the iOS version compared to the native Windows version. Fast, reliable on Mac/iOS vs Windows 10 via VDI.
 
Yes, I was referring the Surface RT but MS has continued supporting ARM versions on Windows and in some ways ARMv8 is simpler. Supporting Windows technologies like COM (still a core part of the Windows tech stack) on MacOS at all is a challenge. Like compiler backends JIT engines obviously have to be written for the target architecture but that work already had to be done for Windows. I seem to recall that Apple announced MS Office support at WWDC so I am sure they were talking to MS for a while.

I bring it up in part because Apple’s ARM chips don’t have a 32-bit mode, which has created some issues with Linux for example. So ARMv7 support isn’t sufficient to be the foundation, it also needs to be fully 64-bit clean on ARMv8.

As Erik also points out one of the bits of work was also disabusing code of the notion that you could assume the platform from the architecture.

MS Office is certainly a large, old and complex code base (like Photoshop for example). It is much more complex than Teams but has full native support for Apple Silcon. Teams, a much simpler and newer app built on web tech does not. That suggests to me that the delay in AS support is because it has not been a priority for that team.

I don’t disagree it is because of priority. On that front all I’ll really point out is that with the explosion of WFH due to the pandemic in 2020, it doesn’t surprise me too much that Apple Silicon wasn’t exactly a priority.
 
Uninstalling now as the camera issues are too frustrating. Can somebody that is sticking with the experimental builds please advise when the black/white camera problem is fixed? Thanks
 
I got to say it works quite well for me, but always updates itself to the Intel version overnight. How did you guys stop that? I did configure the AutoUpdate app to manual, but still no joy...
 
I got to say it works quite well for me, but always updates itself to the Intel version overnight. How did you guys stop that? I did configure the AutoUpdate app to manual, but still no joy...

Doesn't happen to me either. Did you fully un-installed Teams before installing the beta?
 
We should see more daily builds coming this week...

New one

1.5.00.13003 (osx-x64 + osx-arm64) - published on Tuesday, May 10, 2022 at 5:14 AM with 203 MB: https://statics.teams.cdn.office.net/production-osx/1.5.00.13003/Teams_osx.pkg


It doesn't happen to me...
Where are you finding the new releases at? I have looked at every article posted about the native Apple Silicon version of Teams and none of them say exactly where they find the releases at - just that they were noticed on some Microsoft site.

Edit: I see the comments on previous pages here with the GitHub link that shows the various builds. Sweet. Thanks.
 
Last edited:
Where are you finding the new releases at? I have looked at every article posted about the native Apple Silicon version of Teams and none of them say exactly where they find the releases at - just that they were noticed on some Microsoft site.

Edit: I see the comments on previous pages here with the GitHub link that shows the various builds. Sweet. Thanks.
Yeah it's the best place to get them, there's a new one every day.. sometimes even more than one
 
If someone sees the Intel audio driver dependency change please post/reply. I'll start testing at that point but until it's 100% AS it's not worth it. Sticking with Chrome version.
Thanks!
 
I am using a MBA M1

Before the beta, I was using the webapp version of Teams (installing Microsoft Edge, go teams.microsoft.com, then installing the webapp). It was already much better than using it through Chrome

This beta does improve my global experience, except for the black&white webcam but it is worth it
 
  • Like
Reactions: michalm
Finally, this version of Teams v1.5.00.13102 has now fixed the strange colors we saw in the screen share.
 
Is the webcam issue fixed as well?
Unfortunately not fixed yet :(

Actually, I can accurately see in color the person sharing a webcam with me but not as good as Skype. They see me as the weird grayscale.
 
Last edited:
I had a Finder window open with a 3 GB .mp4 file in it. I wanted to drag this to my media player app in the Dock. I pick up the icon, start dragging, and contact the open Teams window, which promptly crashes.

To quote the title of this thread, "MS Teams....very depressing".
 
New build out

1.5.00.13219 (osx-x64 + osx-arm64) - published on Friday, May 13, 2022 at 2:11 AM with 204 MB: https://statics.teams.cdn.office.net/production-osx/1.5.00.13219/Teams_osx.pkg

I had a Finder window open with a 3 GB .mp4 file in it. I wanted to drag this to my media player app in the Dock. I pick up the icon, start dragging, and contact the open Teams window, which promptly crashes.

To quote the title of this thread, "MS Teams....very depressing".
1652430884953.png


This is the ARM64 version and I'm doing a call with screen share... And the difference is by half, in the Intel Binaries I would hit 4GB sometimes.
 
Last edited:
How does it run for just general text chat? I do not use it for video calling at my work
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.