Any suggestions for making the group email in a Teams group more visible / intuitive / accessible in Outlook?
Posted by ZippyDan@reddit | sysadmin | View on Reddit | 9 comments
I made a Teams group, where I want users to be able to share files and chat, but I also want them to be able to email the group.
But in Outlook, the place where Teams group emails gets relegated is so obscure, and it feels like it adds to the user workload for remembering to check for emails, in a non-intuitive way.
My users are already used to checking for new email in their main email box and in shared email boxes. But now they have to also check the inconsistently organized "Groups" folder in their main account mailbox?
As an IT admin, I understand why Teams group emails are slightly different from shared mailboxes, but why does that difference need to be communicated to the user in such a drastically different UI organization? They don't understand why some shared mailboxes appear in "Groups" under their username, but all the others appear as separate mailboxes - and frankly neither do I understand that UI design choice.
Even more frustratingly, there doesn't seem to be a default notification that you've received an email in one of your groups: I can't even see a message count from the main "homepage" in New Outlook.
In MacOS under New Outlook, I can only see that I've received new messages if I expand the "Groups" subfolder. But it's worse in Windows. At least on macOS, expanding the "Groups" subfolder is relatively easy and I can access the group emails directly from the "homepage" (but it's still a non-intuitive process compared to shared mailboxes).
But in Windows under New Outlook it instead shows a "Go to Groups" link, which takes me away from the normal Outlook "homepage", and which then doesn't seem to have a "back button" to return me to the normal homepage (I end up clicking the mail category on the left navigation pane to return to the "homepage"). Not only is this more clunky and unintuitive: it means I can't interact with group emails while also interacting with the rest of my corporate mailbox. I can only look at group emails in isolation.
Is there a better way to handle this?
General_Opening_7739@reddit
What I did was set up custom notifications through Atera so they always know when a group email lands, no matter where it is. It also lets me consolidate group messages with regular email, which cuts down on missed stuff and keeps everyone focused.
General_Opening_7739@reddit
What i did was set up custom notifications through Atera so they always know when a group email lands, no matter where it is. It also lets me consolidate group messages with regular email, which cuts down on missed stuff and keeps everyone focused.
CeC-P@reddit
I saw one company ensure they were all in the global address list and then prefix them all "GRP-groupname" so people knew, if you were emailing someone from Outlook you just type GRP- and let autosuggest find it for you. That separated it from interesting incoming customer/vendor email From line titles that they accumulate over years.
Master-IT-All@reddit
I would setup a Shared Mailbox to be the end point for the email, and then have users work from there.
There's details to it, so you'd want to actually do some more research. But that's how I think I'd work around it.
hihcadore@reddit
U can configure them so the user gets the email in their mailbox if that helps.
Silent_Villan@reddit
This. Owners can "subscribe" all members. Or each member can "follow" the team mailbox. They will get a copy of all mail sent like a dist group.
enterprisedatalead@reddit
we ran into something similar when managing group emails across teams
it usually starts as a simple config thing, but turns into an ownership and access problem pretty fast. over time nobody really knows who owns the group or who still needs access
what helped for us was treating it less like email and more like access governance. once we defined ownership and cleaned up access, things became much easier to manage
we also realized a lot of the mess comes from lack of clear policies around who can create and manage these groups
this was actually helpful when we were thinking through governance side of it:
https://www.solix.com/resources/ebooks/what-should-you-consider-for-effective-data-governance-policy-management/
are you trying to standardize this org-wide or just fix a few problematic groups?
St0nywall@reddit
Have a staff pizza party themed with the name of the Teams group to promote it.
Everyone likes pizza parties, am I right?
Now if you have a few hundred Teams groups... this may get expensive.
NiiWiiCamo@reddit
Enable that MS365 group to also be a distribution group.