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

Anonymous
2024-09-20T19:16:59+00:00

why does teams now replace the normal close / min / max buttons on macos:

with:

when sharing your desktop (or window).

this is the same icon that is shown in the notification bar when screen sharing, but annoyingly replaces the window chrome... and teams is the only application to do this.

OBS studio (which records / captures the desktop) does not do this.

Zoom does not do this...

only microsoft.

why?

please remove this annoyance.

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 No comments

60 answers

Sort by: Most helpful
  1. Anonymous
    2025-06-03T12:28:19+00:00

    Thank you - that's great news :)

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2025-06-03T05:45:35+00:00

    Hi @Oliver Scholz2

    can you tell the version in which this issue has been resolved?

    With every teams update I get, I'm in big hope that the issue is resolved, but no luck so far :(

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2025-04-28T09:16:54+00:00

    Hello @Alex,

    Could you confirm which version you have downgraded to ? I am willing to go down to get rid of this.

    Hi,

    I am using the last version from July from last year, 2024 - so far it works great, just like before 👍🏼

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2025-04-28T07:50:01+00:00

    Hello @Alex,

    Could you confirm which version you have downgraded to ? I am willing to go down to get rid of this.

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2025-04-25T07:10:56+00:00

    If it helps, I installed the old version of Teams and it works just like before. Just for the meantime, waiting for Microsoft's mess to be fixed.

    Was this answer helpful?

    0 comments No comments