Currently it is not possible to switch the AD tenant in portal.office.com like you can in portal.azure.com.
Without that is is not possible to Access the O365 Admin Panel as an B2B guest account that has Global Admin or EXO/SPO permissions.
Login always takes me to my home tenant with my mailbox.

It is also not possible to do this by PowerShell.

So please make it possible to use portal.office.com Admin Section as an B2B guest otherwise it makes no sense that I can for example assign Exchange Admin permissions to an B2B user.

Once again, OWA has new 'features' added which are causing problems - particularly in a School environment such as ours. Likes and @mentions are flying about the system - teachers email a group of students who click the 'like' button and the teacher then gets loads of pings back which they have to deal with! Obviously, this could be useful but PLEASE release an admin UI for the control panel when you add these features so we can CHOOSE whether to let users have these features!

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.

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

In large environments (mine is 80,000 users!) it is necessary to have a the various admin roles split across several teams and personnel. To control this easier it would be great if I could use security groups from AD sync'd to AAD then assign the admin role(s) to the group instead of individually to users.

Change or customize start page for all users on same time.

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.

Auto mapping to a shared mailbox should be allowed even if the user doesn't have Full permissions. Many times I have to manually add in Outlook and on a large organization of over 3000 users is time consuming.

It would be very beneficial to have the Conversation View show sent emails in a shared mailbox. It appears that the conversation view does not show emails from sent or any other folders in the INBOX.

There should be option to provide external user access to shared mailbox.
Currently only internal user with license have access to shared mailbox. But there should be option such that external users can be added as member of shared mailbox created inside the organization since shared mailbox have feasibility to co-ordinate with external domain.

I'd like to run the exchange online powershell with a service principal. The use case is easy - we're running a background service setting some specific configuration on user mailboxes and don't want to use an admin account for that. It's sad this is not on the graph directly possible but at least make SPNs available for use with Exchange Powershell.

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.

Please allow companies to disable the "Request to reset user's password" notification's if password resets are disabled in Office 365. We have internal processes in place for employee password resets and our Office 365 administrators are not typically involved.

The best solution would be a custom message that companies could display to employees who attempt to reset their passwords in O365 - this way the employee would be notified about the correct reset process.

Actually it is not possible to obtain a free Exchange Server 2019 activation with a hybrid key. For earlier Exchange Versions this works trough HCW, but not with Exchange 2019: "Please note that HCW does not provide a 'hybrid key' for Exchange Server 2019. If you need a hybrid key, the latest version that it is available for is Exchange Server 2016."

This is not customer friendly at all - so please add Exchange 2019 to this feature.

https://techcommunity.microsoft.com/t5/Exchange-Team-Blog/Hybrid-Configuration-Wizard-and-licensing-of-your-on-premises/ba-p/608106

It is very frustrating to see messages that have been lying there for weeks - who has time or remembers to go into the admin panel every day? Email notifications to the tenant owner should be standard on this. We get notified by email for everything else, why not messages?

In case the big file is deleted (i.e. 1TB) from all recycle bins, it still takes this much space in the Preservation Hold Library folder. It would be great to be able to delete such file/folder at least by Global Admin. Otherwise, when the Retention Policy is set up for several years or never delete, even if the file is deleted there might be no room for the new files on user's OneDrive.

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.

Phishing emails are on the rise where Sender's name is used to lure recipients into trusting spam. We would like to prepend a disclaimer for emails originating outside the domain and add the sender's real email address to it. We have programmed the disclaimer but have been told by Microsoft tech. support that it is by design that sender's info is not available to be added to disclaimers.

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.