03-24-2017 09:44 AM
03-24-2017 09:44 AM
We are moving from an on-premise Exchange 2013 environment (using Hybrid) and we have to move our DLs to the cloud. I can create them through powershell as a distribution group, but that does not write back to our local AD (using AADConnect). So using the Unified Group commands, I can create them and they write back.
The problem is the welcome message. We are not ready for users to use the extra features of the groups, plus we have users that are a part of several hundred DLs, based on what customers they take care of.
I see the attribute WelcomeMessageEnabled, but am unable to change that to $False. I have also tried using mail rules to delete the message based on content in subject or body, but again no go.
Does anyone have any way of turning these off? This will create a huge helpdesk and support nightmare if I can not turn these off.
03-24-2017 12:12 PM
I'm not aware of any method to bypass the message. @Christophe Fiessinger might be able to help or take some feedback on this.
03-28-2017 03:41 AMSolution
You can use the following command to suppress the welcome message for any new users added to the group as a member. The default value will be set to true for this parameter. So you will need to pass "false" as the value to suppress the welcome message.
Set-UnifiedGroup <groupname> -UnifiedGroupWelcomeMessageEnabled:$<true/false>
03-28-2017 06:29 AM
Thank you so much Siva. That worked great. This will help tremedously.
03-28-2017 08:03 PM
Great update! Did this parameter just get released? It is not currently listed on the supporting technet page for Set-UnifiedGroup.
03-29-2017 02:25 AM
Seems it's a recent addition indeed. I checked all the parameters available for Set-UnifiedGroup in my PowerShell session before posting the other day. Anyway, great news indeed!
03-30-2017 04:41 AM
We are in the process of updating the technet documentation. You will have the documentation updated soon.
07-26-2017 07:30 AM
This is exactly what I am looking for, just to confirm, this is a Cmdlet run at Windows PowerShell - correct?
Actually, I did add the "Identify" parameter and tried the following command, but it was not recognized under PowerShell, any ideas where I need to correct this?
PS C:\> Set-UnifiedGroup -Identify "MyGroupName" -UnifiedGroupWelcomeMEssageEnable:$false
Set-UnifiedGroup : The term 'Set-UnifiedGroup' is not recognized as the name of a cmdlet, function, script file, or
operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try
At line:1 char:1
+ Set-UnifiedGroup -Identify "MyGroupName" - ...
+ CategoryInfo : ObjectNotFound: (Set-UnifiedGroup:String) , CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException
07-26-2017 10:31 AM
You need to connect to ExO PowerShell first: https://technet.microsoft.com/en-us/library/jj984289(v=exchg.160).aspx
08-06-2017 11:33 PM
Suppose -UnifiedGroupWelcomeMessageEnabled switch is not available in our environment and we cannot disable it.
What could be the solution ?
08-07-2017 04:27 AM
Here is how I did switch off/on the new group member welcome message.
First of all, you need to connect to the O365 Exchange Server Online.
1. Open Windows PowerShell command window as Administrator
2. Run the command: $UserCredential = Get-Credential
3. Run the command: $Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri https://outlook.office365.com/powershell-liveid/ -Credential $UserCredential -Authentication Basic -AllowRedirection
4. Run the command: Import-PSSession $Session
5. Set-UnifiedGroup "MyGropuName" -UnifiedGroupWelcomeMessageEnabled:$false
(For switching on the Welcome message, the same command but "$true" in the end.)
Hi Brian, actually I am not sure if you can do multi-groups in one command. From my experience, you need to set it for each. However, this is a one-time setup, you can connect to your Exchange account and need just change the command for the setup each time by entering one after the other group name and run.
Maybe somebody else from the community could accomplish this in a one-step command.