Be able to Nest Groups like Distribution Groups. I decided to convert a lot of our team DGs to O365 groups without realizing I wouldn't be able to nest them

To really replace Shared Mailboxes our users need to be able to quickly categorize incoming emails and show that actions have been completed by dragging and dropping emails to a named folder in outlook.

For example accounts payable shared mailbox allows any member of the accounts team to drag an invoice email to another folder to show that it has been entered for processing

There should be an option to convert a shared mailbox to an office 365 group especially since the Office 365 Group is the newer better version of the Shared mailbox and there is no way to convert.

I need a way of making security groups part of an Office 365 group. I want to be able to add users to a security group and then they are automatically a member of a Office 365 group.

Dynamic group membership only appears to work for user attribute values and not their group membership.

Today when you create a group, it is created under the "/sites" managed path. Please change this so we always can have complete governance over the /sites-path. So when we want to create new site-collections you won't get URL-conflicts.

When you rename an Office 365 group, only the display name changes. It is not possible to edit the email address or the name of the OneDrive associated to the group. This is confusing, especially for OneDrive.

It should be possible to change all names associated with the group when renaming.

When creating groups, or after the fact with a PowerShell command, all the ability to set a hide=True attribute so that the group is not visible when viewing all. Several other elements such as distribution lists and security groups can be hidden so why not allow the ability to hide Groups. This will allow groups to exist that are truly "private". This would be very helpful for groups that need a bit more privacy in order to operate using the Groups functionality beyond the invite only capability.

It would be nice if the Tasks created in the planner using O365 groups would appear under the 'task' section of outlook.

Also provide "drag and drop" functionality within Outlook. Sometimes a conversion will take place outside of the Group, but that conversation may be important to the Group. Have the function to "drag and drop" an email into the Group Inbox would be a great tool.

(This is already available if the Group Shared Mailbox is added to Outlook, but a few design changes will make this feature for user-friendly and available in the desktop client.)

Love the ability to add task to a group with Planner but please have task that have an expiration date automatically add themselves to the Group calendar and the Assigned resource's calendar automatically.

As soon as someone creates a private group, this should by default be hidden from GAL.

There are PowerShell CmdLets which allow administrators to hide/show the groups from the GAL. However this is a post-facto activity. With many users and groups this is very tedious and many times we don't even come know that a group has been created by someone somwhere.

Please make it possible to set Calendar permissions to read only so that it's possible to have a group calendar that can only be edited by selected members of the group.

For an admin adding people as members to various groups, provide a way of disabling the email notifications. Use case:
- people in my org don't even know what O365 groups are and this will create confusion and potential calls to the help desk when I don't want it to.
- don't want to bug people with things they likely don't care about (at least for now).

Currently there is no option to prevent users from unsubscribing to an O365 group. This can cause undesired behavior for communications to specfic groups or manditory groups such as ALL@company.com.

To have an Office 365 group for our team is a great idea. However, the team I'm on has multiple projects ongoing, and having to create a new group for each plan and then to assign permissions for each plan and manage documents, conversations, etc all in separate plans is an excess.
Better to be able to label documents, conversations, emails with each plan and to allow multiple plans than to have to manage all the plans separately and create groups that will be needless after the project is complete.

Email alias does not support many characters that are common in email addresses (e.g. "dot"), and cannot be changed after initial configuration. Additionally, alias creates an email address using the tenancy's "default" domain--doesn't allow you to select a domain if a tenancy has multiple domains. Finally, can't be changed after creation. All three of these are painful!