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. Please Allow Admin can change InfoPath Resources on SharePoint Online

    Please allow Admin can change InfoPath resources on SharePoint online.

    It's not good if your InfoPath forms on SharePoint without enough resources and then error message will show up and then system force closed InfoPath form.

    Users don't want this critical error message "This session has exceeded the amount of allowable resources" happen again.

    SharePoint onsite can change InfoPath resources by Admin, Why SharePoint online can't?

    9 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    8 comments  ·  SharePoint Admin  ·  Flag idea as inappropriate…  ·  Admin →
    declined  ·  O365 Feedback Team responded

    Thanks for your feedback! Although we appreciate your time and effort to give us this feedback, it’s not something we’re planning to do right now. But who knows – if enough customers ask for it, we’ll definitely reconsider. You can see what’s happening with Office 365 on the Office 365 Roadmap.

  2. Disable the cloud storage

    You should be able to use the office programs without having to store things in the cloud. We have strict policy against storing things in the cloud so we can not use this software. We should be able to store documents and files on the device.

    6 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    11 comments  ·  SharePoint Admin  ·  Flag idea as inappropriate…  ·  Admin →
    declined  ·  O365 Feedback Team responded

    Thanks for your feedback! Although we appreciate your time and effort to give us this feedback, it’s not something we’re planning to do right now. But who knows – if enough customers ask for it, we’ll definitely reconsider. You can see what’s happening with Office 365 on the Office 365 Roadmap.

  3. SMTP Relay in office 365

    We've been using the Office 365 SMTP service from our server for a few months now.
    We started using option 1 (SMTP client submission) in the How to set up a multifunction device or application to send email using Office 365
    This option works, but does not perform well.

    https://support.office.com/en-us/article/How-to-set-up-a-multifunction-device-or-application-to-send-email-using-Office-365-69f58e99-c550-4274-ad18-c805d654b4c4?ui=en-US&rs=en-US&ad=US

    It takes 15-20 seconds to send each e-mail.
    We need to send e-mails to addresses outside the organisation, so option 2 (direct send) was not an option, so we tried option 3 (Office 365 SMTP relay). I followed the instructions in the article, setting up a connector in our office…

    4 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Exchange Admin  ·  Flag idea as inappropriate…  ·  Admin →

    That was By Design behaviour. Your endpoint points to Office 365 IP addresses shared by other customers. You were not in fact relaying by sending directly to those customers as the messages could be delivered by us for the mailboxes hosted in Office 365. For the external mailboxes, it failed like you saw because the connector was not working.

  4. Allow ability to visually organize or group SharePoint site collections in SharePoint admin

    Allow ability to visually organize or group SharePoint site collections in SharePoint admin. Maybe in a folder structure or some other grouping structure. Would be useful for grouping Production vs. test vs. in development site collections. Or to group by function.

    5 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  SharePoint Admin  ·  Flag idea as inappropriate…  ·  Admin →
    declined  ·  O365 Feedback Team responded

    Thanks for your feedback! Although we appreciate your time and effort to give us this feedback, it’s not something we’re planning to do right now. But who knows – if enough customers ask for it, we’ll definitely reconsider. You can see what’s happening with Office 365 on the Office 365 Roadmap.

  5. Clear all user metadata from SharePoint Online after a user is deleted from Office 365

    I recently had a situation come up where a user's name was typed in incorrectly when their Office 365 account was provisioned. The error was propagated to SharePoint, and even though I corrected the error in Azure Active Directory and Office 365, the mistyped name persisted in SharePoint Online. In fact, I deleted the users account entirely from AD and Office 365 and recreated it with the same alias and the mistyped name persisted in SharePoint Online. There is no way, even using PowerShell to clear that metadata store or force an update. Please provide a way to force an…

    5 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  SharePoint Admin  ·  Flag idea as inappropriate…  ·  Admin →
    declined  ·  O365 Feedback Team responded

    The root cause is fixed. We had a bug. Changes to AAD are background synced to SPO cache. We had an issue where it took far too long. It should happen in 24 hours. This is why you did not see the typo corrected in SPO.

    Unfortunately the new user you created is a different object, even though the alias is the same. The AAD user associated with the name that has a typo is gone, so the SPO cached version will not be updated.

    We understand that this is a problem in your case but it was caused by a bug and we don’t expect it to be so common for us to build a tool that would allow editing the SPO cache.

  • Don't see your idea?

Feedback and Knowledge Base