Use built in notifications for macOS
Notifications built into the OS (which all apps I've seen use other than Outlook and now Teams) are more functional and allow for more user control. Most importantly, they honor Do Not Disturb settings, which is critical.
Sergi Isasi
shared this idea
We are getting closer… the team is almost ready to rollout MacOS notification support internally for testing – we hope to have it to the public by the end of this quarter.
Thanks!
392 comments
-
Scott
commented
As a workaround, you can use an application called Rambox and set up Teams inside of it. Notifications that fire through Teams inside of Rambox display natively through Mac OS Notifications. It's not ideal but it works for now.
-
Ryan Pendleton
commented
Perhaps this has been mentioned before, but another reason to use the native notification center is to prevent notifications from overlapping. If I have notifications pinned to my screen, such as calendar events or reminders, Teams shows notifications underneath those for a few seconds. It makes it pretty much impossible to read the notifications without frantically dismissing the others on top of it.
-
Anonymous
commented
I present often sharing my screen and always set notifications in macOS to Do Not Disturb. However, Teams does not honor this and I'm sometimes sent private messages that are now shown to everyone who I am presenting to. This needs to be addressed.
-
Anonymous
commented
Any updates since April 8th?
-
Bob
commented
I guess if 387 other users have taken time out of their lives to comment and ask here I may be crazy to think you'll finally do something for the 388th but here I am adding my voice to the deafening chorus along with the 2677 other people who have voted for Microsoft to finally support such a simple and necessary aspect of being a good MacOS citizen.
-
Anonymous
commented
As incoming call not ringing / alerting with the integrated notification when the team windows is minimized, this function is even more important. Otherwise, the MS Team Call function is useless. Hope it can be implemented soon, as this is actually the only "workaround" from the microsoft support.
-
Ed
commented
Seriously Microsoft?! How many votes and comments does it take for someone internal to actually read this and provide a simple update? In April of 2019 "Alex" - from Microsoft Teams Engineering - stated it would be public by end of quarter yet here we are in January of 2020 without anything, not even an update. This is beyond ridiculous at this point. It's literally a 30 minute change tops. Stop embarrassing yourselves and do something about this.
-
Roy H
commented
I would love this as well!
-
Charlie Schliesser
commented
Ya just gotta get this rolled out.
-
Drew Covi
commented
Is this specific to Teams? Or can we expect this in Outlook as well?
-
Felipe Delgado
commented
Found out the hard way that notifications do not respect the Do Not Disturb setting. Glad it wasn't anything embarrassing.
And we are 3 months shy of a year for the internal rollout. Any updates?
-
Anonymous
commented
So we have read receipts now, but not native macOS notifications… something that would be far more useful than knowing if a colleague has seen a message… like obeying do not disturb and being able to see message notifications when I'm working in full screen…
-
GastonM
commented
We're over 2 weeks into 2020, and still no update from Microsoft. Do we really need to wait until 2021?
-
Matt Richards
commented
Bump. Bump Bump Bump Bump.
Bump.
-
Anonymous
commented
Like half the purpose of teams is getting notifications, the standard ones are a real drag. PLEASE, PLEASE fix this asap!
-
Anonymous
commented
is this feature launched yet?
-
Jan Denmark
commented
About time for a public release now, right? 6 months internal testing should be enough?
-
Ronald Jacobs
commented
Really want and need this. What is the status? The message saying "we hope to have it to the public by the end of this quarter" Was from 3 quarters ago. So that is 9 months later now!
-
Adam
commented
Hey team,
Last update was in April of 19.... Are we any closer to this being completed?
-
Peter Kasarda commented
from November 03, 2016 still not fixed, shame!
