Feedback by UserVoice

Office 365 Admin

We have partnered with UserVoice, a third-party service and your use of the portal and your submission is subject to the UserVoice Terms of Service & Privacy Policy. Please do not send any novel or patentable ideas, copyrighted materials, samples or demos for which you do not want to grant a license to Microsoft.

Welcome to the Office365 Admin UserVoice forum. If you’ve got ideas on how to improve the tenant admin features in the service, such as the Admin Console, Service Health Dashboard, and Message Center, you’ve come to the right place.

If you have feedback for SharePoint admin features, please submit your ideas here SharePoint Administration

Thanks for joining our community and helping improve the tenant admininistration features in Office 365!

Need Tech Support? Please see the Manage Office365 forum in the O365 Community.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. Make it possible to change the tenant name in Office365

    Iv realized that there is no option to change the tenant name in Office365.

    This would be a great tool for businesses that change their name and want to keep their current solution in Office365.

    A simple task like changing the tenant name for Office365 would save businesses allot of time.

    10,553 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    384 comments  ·  Flag idea as inappropriate…  ·  Admin →
  2. Delegate permissions for managing MFA

    To be able to delegate the permission of administering user account MFA setting like enable/disabled forcing reset of MFA code etc.

    Currently the Global Admin permission is needed. It would be able very useful to delegate this to a service desk function without having to provide full admin access to the tenant.

    3,762 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    156 comments  ·  Flag idea as inappropriate…  ·  Admin →
  3. Require TLS Fallback Automatically to OME

    When sending e-mails out with sensitive content, we can currently use a Transport Rule to detect said content (Sensitive Info Types) and take an action. Would like to be able to create a transport rule that first does "Require TLS." However, if TLS is not supported by the receiving server, have Office 365 automatically fail back over to OME and send out the e-mail securely that way. With Require TLS, if the receiving server doesn't support TLS, the user has to wait to find out that their e-mail did not go through. They also have to resend the e-mail manually.…

    171 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    9 comments  ·  Flag idea as inappropriate…  ·  Admin →
  4. mail flow to use alias

    Currently in mail flow i see no way to add an alias to mail flow rule. When you add a user it only adds the primary email address and not the aliases associated with that person. Adding the alias explicitly also redirects to the primary email address. The only way i have found to add and alias is to add it if the recipient address matches the word - email alias. Potentially this way will allow for abuse if other email addresses are created matching this pattern,

    86 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  Exchange Admin  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

Feedback and Knowledge Base