Too Many Notifications When Creating Managing Teams & Membership

[John Benak]

My company is rolling out Teams and are struggling with too MANY notifications.  

Specifically, whenever a new Team is created or a user is added to a team there are 2 notifications sent out - 1 from Teams, and one from (I guess) O365/EOL.  We are trying to drive everyone to use Teams and these Outlook notifications take away from that.   

I frankly had never really noticed this before and initially thought this was a bug in AvePoint, which we're using as a self-service provisioning tool. We would immediately get both emails, which is why this stood out.

I created some new Teams in the desktop client and the members I added immediately got the notification from Teams.  I as the Team creator got nothing.  HOWEVER - a couple of hours later they received the O365/Outlook 'you've joined the XXX group' notification.

Has anyone else seen this, and is there ANY way to selectively manage the group provisioning service (or whatever controls this) to NOT send the groups-sourced notifications?

 

[#2]

You can hide the group notification email via powershell:

Set-UnifiedGroup -Identity <O365groupalias> -UnifiedGroupWelcomeMessageEnabled:$false

[#3]

Thanks @David Christensen.  I'm aware of that CMDLET, but will that suppress ALL notifications, or just the ones from the O365 Groups workload?  We want to keep the Teams notifications, and suppress just the Outlook/O365 notifications.  We'd like to do this at a global level if possible, and other than a PS loop this only works at the individual group level.  These are sent out right after the Team/Group is created and/or when a user is added to a team.

We're using a 3rd party product (AvePoint) that performs the Team provisioning via a user-initiated workflow request.  

[#4]

That cmdlet will only stop the O365 group notification email. It will not affect the Teams email a new member receives.
Our Teams workflow isnt fully automated yet. For now...after I run the New-UnifiedGroup cmdlet and then run Set-UnifiedGroup to stop the welcome message and hide the group from exchange clients and address lists. Once that is done...I run Add-UnifiedGroupLinks to add an owner to the group. Then I provision a Team and let the Team owner add members via the client. Adding the additional members this way ensures each will receive a Teams notification.