Since the Office 365 groups are now the center stage/focal point for the majority of the Office 365 products/services, it will be great to have the ability to send the customized welcome emails whenever we add someone to the group either via the user interface or using Microsoft Graph API.

This functionality can be set at Tenant level or at individual Office 365 group level. By default, it should be off.

The reason this functionality is important because the default welcome message does not contain enough information to let the users know what this group is about and what will be its usage. The customized welcome message will help organizations to communicate effectively the intended usage of the Group and other relevant information. The customized welcome emails are really helpful for non-technical users.

If Microsoft can not provide this functionality via User Interface at least this functionality should be available via Microsoft Graph API. Right now the only way to suppress the Group's welcome email messages is via Spam Filter (which is not a viable option) and send customized emails to avoid duplicate welcome email messages.

When I use my group email address this message appears at the bottom:

"You're receiving this message because you're a subscribed member of the XXXXX group.
View group conversations | View Group Files | Unsubscribe"

I want to be able to turn that off because I don't want other people who are cc'd, to want to attempt view or join the group. Just confusing to them and it's not something they need to think about. I often cc the group when I email to outside people and there is no need for them to know about the group and try to join it etc.

We have an increasing request about mage O365 group (most typicality Planner group in to other existing group that is more actively using for file share.

User start the group in mind that using some specific feature of O365 and later find out two or three slimier group exist and want to merge into.

I would like to have feature support ted at least by the tenant global administrator or better with group's own administrator, if the person has admin role in both group.

This will help tidy up the ever growing number of groups and better use by end user.

Thanks,

What’s really needed is an exclusion list, ex: Expire all groups EXCEPT for these 5 that I really really care about. All the others, let the owners decide if they want to keep them, but these 5, I keep important stuff in there, and I don’t want to sweat it about missing an email and potentially losing all that information.
Otherwise, due to the dynamic nature of groups, if I set a selected list of groups that I want to expire, I would have to keep coming back to this to keep it updated since any user can self create a group.

The changes are additive but if you remove an email address from UnifiedGroup.EmailAddresses, it is not reflected in MsolGroup.ProxyAddresses. This is important for organizations that host multiple domains in the same tenant.

To reproduce:

New-UnifiedGroup -DisplayName "myawesomegroup" -Notes "myawesomegroup" -Alias "myawesomegroup" -EmailAddress "myawesomeness@contoso.onmicrosoft.com" -owner "consultant@contoso.com" -AccessType Public -Verbose

Get-UnifiedGroup myawesomegroup | select *

Set-UnifiedGroup myawesomegroup -PrimarySmtpAddress "myawesomeness@contoso.com"

Set-UnifiedGroup myawesomegroup -PrimarySmtpAddress "yourawesomeness@contoso.onmicrosoft.com"

Set-UnifiedGroup myawesomegroup -EmailAddresses @{remove="SMTP:myawesomeness@contoso.onmicrosoft.com"}

Set-UnifiedGroup myawesomegroup -EmailAddresses @{remove="SMTP:myawesomeness@contoso.com"}

$msolGroup = Get-MsolGroup | Where-Object {$_.DisplayName -eq "myawesomegroup"}

$msolGroup.ProxyAddresses

This shows all the email addresses that have been added. Deleted email addresses still show up here.

These same values (including deleted email addresses) show up in the O365 Admin center:

Groups -> Groups -> myawesomegroup

Group Id : yourawesomeness@contoso.onmicrosoft.com
Aliases: myawesomeness@contoso.onmicrosoft.com, myawesomeness@contoso.com

When creating an Office 365 Group, a SharePoint site is automatically created. Neither the user nor the administrator, however, have any control of where that group lives or what template it uses.

Ideally, users would be able to alternatively associate an Office 365 Group with an EXISTING SharePoint site, thus allowing them to a) choose any location, b) choose any template, and c) associate with current SharePoint infrastructure (instead of potentially duplicating content).

Obviously, the site would need to a) meet some preconditions, b) be upgraded to satisfy requirements, or c) have limited integration support. For instance, the site would need to have, at minimum, a Document Library and a (OneNote) Notebook to take advantage of current integrations. My preference would be to automatically add those features if they aren't already enabled, although this may introduce permissions issues.

I love the integration between Office 365 Groups, Planner, Yammer, SharePoint, and Exchange, but wish it provided more control, especially on the SharePoint side.