On-premises Exchange had Email Address Policies which allowed administrators to define the email addresses (SMTP:alias@domain1.com,smtp:firstname@domain2.com) that would automatically be added to mailboxes.

Office 365 desperately needs this functionality so we don't have to resort to over complicated PowerShell scripts.

Outlook 365 for Windows needs a unified Inbox similar to ALL other Outlook apps. For those of us with multiple email accounts. It would be very convenient to have all emails arrive in one inbox instead of clicking the whole time through all Inboxes, which consumes a lot of time.

Enable option to subscribe by email Office 365 Health Service Incidents and Advisories.

Get a new user role to read only the entire configuration of O365 admin portal.

The option should be there to assign specific domain permission to Administrators.

Proposal: Have the option through GUI to disable automapping for inboxes, and/or certain individuals that have permission to that inbox.

Explanation: When you assign permissions for someone to a particular inbox (including shared) it automatically adds the mailbox to their Outlook profile - this has caused us issues. While it can be disabled through PowerShell, it's very tedious to go through and remove each user and then add each user to every inbox with automapping disabled.

Today you have to use the regkey DelegateWastebasketStyle to control the behaviour when deleting items in a shard mailbox.

This should have a PowerShell command, just like for sent items (set-mailbox shared@contoso.com -MessageCopyForSentAsEnabled $True)

One of the companys i manage Office365 for has, no AD which means no GPO's to use with regkeys, no consistensy in Office versions and thus this gets unmanageble.

Please add a way for me to control this centrally in Exchange Online.

We have around 75 meeting rooms. We would really appreciate if we could have some sort of report on how often the rooms are used (frequency), how many are using them etc. Our needs are in the context of "how should we shape the meeting rooms in the future, should we build more in one location, and close down some in another location and so on".

Outlook email APP in windows 365 should have a delayed delivery option so we can send emails out at a time we desire. Old outlook had it so the web APP should also have this feature. Otherwise it is a step backwards.

Allow the creation of new remote mailboxes that are 'shared' mailboxes. At present, you have to create a regular user mailbox and then after you have synchronized this to Office 365, you then have to login to the 365 admin portal and convert it to shared. The problem with this method is that the user object on premises will always be shown as an office 365 mailbox and not an office 365 shared mailbox. Just a bit messy.

Over the last month or so case sensitive searches have been added into the shared mailbox and permissions sections on the Office 365 admin page. Could these be reverted back or was there a reason for case sensitive searches being added?

I had weeks of no results coming back until I spoke to Microsoft Support who also have the issue and they noticed it is now case sensitive.

Bring back the ability to have custom domains on O365 Home Premium. I have a family domain and want to set it up as a domain on my O365 account.

Currently message trace timezone is set to UTC 0. This is really annoying. We should be able to change the timezone for this. There are posts on the forums going back to 2012 requesting this feature... please implement it.

Currently there is an issue with permissions if you use the partner delegated admin to convert a user to a shared mailbox. You must log into the tenant as a global admin in order to accomplish this.

As a delegated admin we should be able to manipulate mailboxes as needed to ensure an enjoyable client experience.

I would like to get an uptime graph for an specific tenant, instead of an uptime report for the whole datacenter.
Right now we can only get the Regional uptime graph and a tenant-level availability report will be much more helpful.

The one-time-bypass feature is only available for Azure MFA with server/sdk implementations.

We use Azure MFA in a cloud-only setup. We don't have any server/sdk running. We would like to use the one-time-bypass feature.