replacing close/min/max buttons when screen sharing on macos?

Thanks for the details. I was surprised by this feature/bug. The big question is why? The same features, but hidden one more click away. Typically how I experience a lot of Microsoft software, starting with the office suite and windows.
I filed a bug report. I hope that they will revert this mistake. Why do you want to bully the macos Teams users that much? To draw them to Windows? I think the result is the opposite. Or maybe it is a start to force people, because the macos version becomes unusable over time.
Just like Teams is the only application on the that seams to have it own audio drivers, because it is the only application that causes my music to change sound quality when starting a teams conversation. It seems like they to not use de default OS audio and device capabilities, which are working fine.
But it is just frustration after frustration with ms software. But I think it is mainly UI and UX related. As far as I know, Microsoft can build very good frameworks, but yeah. UX? sadly not in my experience.

I found it. Thanks for letting me know where the option is :)

And, the give feedback doesn't exists in Teams for Mac, BTW.

It took some hunting, but I found the "feedback" feature in teams. It **was not** where De Paul said it was... not even close (maybe that's where it is in the windows version of the application).

It is however, at least for the next few minutes until they push out a new update changing where this is located...

there is an ellipsis next to your profile picture in the upper right corner of the main window. if you click it, there is a menu (why they could not add this menu to the macOS menu is beyond me... they can never integrate into any native application probably)...

under that menu there is a "Feedback" menu, with a "Report a problem" CMD + Opt + Shift + R apparently also brings up this dialog... (lol i tried it, and though its shown as a shortcut... ya... it doesn't do anything... surprise, surprise).

I submitted a bug report about this there... I'd recommend others do the same.

How is it possible to make such a frustraiting UI feature enabled by default and then not even have any option of turning it off? Don't dare to touch another OS design and think you know better :P

But, seriously.. disable it by default. And if ju MUST have it then it should be a feature you must turn on. Personally I think most people did not wish for this to ever have existed..

we and our parent company work with MS. from my experience, very few ppl are actually "employed (as in proper non-contractor employees)" with for the company, most people are contractors of some sort, and projects are some sort of contract. My guess is how the state of mediocrity happens: projects and features get proposed; approvals get issued all in a vacuum outside of necessity, user experience (or in things like crowdstrike), or safety nets... contracts get assigned, software gets end of life'd and replaced by identical apps or platforms (skype/teams/xamarin-maui) and things get changed without anyone ever stopping to think whether it should or how it impacts the quality of life of any user... all for the sake of the a few more months of a contract for people working for microsoft. another release is kicked out the door, and more buzz is published out the microsoft PR engine, and life continues on. unless enough people complain about it, in which case.... another contract is issued, more people get to work longer changing whatever anybody didn't like, and (original scenario continues).

How is it possible to make such a frustraiting UI feature enabled by default and then not even have any option of turning it off? Don't dare to touch another OS design and think you know better :P

But, seriously.. disable it by default. And if ju MUST have it then it should be a feature you must turn on. Personally I think most people did not wish for this to ever have existed..