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.

Like you can with an Exchange account.

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!

I have a need to convert a number of distribution groups to mail-enabled security groups. Right now I have to record DG members, delete the DG, create the SG and populate the SG.

we have an office 365 groups which needs auto-response but unfortunately this feature is not supported. it would be nice if we have this feature the same as the mailbox behaves.

Similar to Distribution Group aliases.

Please add a Groups button in the App Launcher. I thought this was a planned release.

I understand the reasoning behind Groups and modern teams and using Delve. However, my clients don't care and want a button. Thanks

Please all Office 365 Groups calendars to be added to the native iOS calendar app. It's a deal breaker for my team to totally abandon our google calendar. We can add it to the native app so several of us won't let go of it. As an Office 365 admin, one of my tasks is encourage our clients to use Office 365 more! this would be huge!

Currently an Owner of a group can delete that group - I'm aware soft-deletion is coming, but ideally we want to be able to stop users from deleting groups entirely. An Azure policy to specify who can delete groups would put power back with the IT Dept. This will allow us to empower users, but without the risk of them deleting groups and the content getting past the retention period and being permanently lost.

Not able to nest an Office 365 group inside other Office 365 group make the task of managing groups much harder. This is a normal concept for all of us working in this field for a long time.

For large deployment we need some option to control user settings globally via group policy or similar admin control options

When contributing to a Group. Enable feature to move documents directly from Onedrive to a specific map within a Group. (now done by downloading / uploading). But documents are already in Office 365

Users, by default, should get a personal, private, Planner just like their personal OneDrive. The problem is that if a user wants to use Planner, just for themselves, it creates an entire O365 Group which becomes visible in the GAL and the entire organization. It also creates mail, sharepoint site, etc... which is completely unnecessary and wastes resources (because the user already has mail and onedrive) just for a personal planner.

To ensure consistent Groups across the organization, be able to create a new group from an existing group, keeping the structure (Navigation/sub-sites, Library folders, Notebook sections, Planner buckets..) without the content/documents

Ability to add an Office 365 Group email address to Distribution Lists

In Microsoft's April update for Office 365 groups they mention the Azure AD naming policy is coming but only for Azure Premium customers. This should not be the case. Proper management of Office 365 groups should include naming policies. Without naming policies, there is a large potential for namespace collisions for folks who do not use the Azure AD premium service. This is something that should be available to all not just Azure AD premium customers.