How can we improve the tenant admin features O365?

Tenant-wide time zone setting for SharePoint (at least)

It doesn't make any sense to me to have to set the time zone per Site Collection. For an organization that sits in one time zone, having to change every Site Collection from PST to the local time zone is tedious. If there were a single overarching setting that Site Collections could inherit from, it would make things a lot easier.

309 votes
Vote
Sign in
Check!
(thinking…)
Reset
or sign in with
  • facebook
  • google
    Password icon
    I agree to the terms of service
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Marc D AndersonMarc D Anderson shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →
    thinking about it  ·  O365 Feedback TeamO365 Feedback Team responded  · 

    Thanks for your feedback! We’re reviewing your suggestion. Remember, the more votes a suggestion gets, the more likely it is that we’ll do it. You can see what’s happening with Office 365 on the Office 365 Roadmap.

    18 comments

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      I agree to the terms of service
      Signed in as (Sign out)
      Submitting...
      • EricaErica commented  ·   ·  Flag as inappropriate

        Don't want the tenant setting to control all the site collections. But when the end users creating site collections, the default time zone is the same with tenant or current windows time zone, it's good. If someone wants to change the time zone, they can change at site collection level by themselves. ^_^

      • ShirleyShirley commented  ·   ·  Flag as inappropriate

        When the end user create site collection, it's better to set the default time zone the same with the tenant time zone,not US.

      • Anonymous commented  ·   ·  Flag as inappropriate

        This shouldn't be a case of and I quote "the more votes a suggestion gets, the more likely it is that we’ll do it". This is not a popularity contest like on trash TV, this is a real issue affecting every user who is not in your timezone. Please try to think of people who are not American as we are paying customers too.

      • Rick de VriesRick de Vries commented  ·   ·  Flag as inappropriate

        Please do something about this! Just because it's your timezone in Redmond does not magically make the impact less.

      • AdamAdam commented  ·   ·  Flag as inappropriate

        You are thinking about it. Wonderful. Such customer service. Let's pretend that instead of being a US based software developer, you are attempting to gain user uptake in new technologies and you don't happen to live in the US (crazy, I know).

        Now, you are introducing one of your (older/non-technical) users to all things Office 365 & OneDrive. Do you realise how much confusion is caused, when these people are reviewing their files, with wrong date & time stamps?

        How to you think they share their experiences with their co-workers & manger.

        Just. Fix. It.

      • Eric LEric L commented  ·   ·  Flag as inappropriate

        What complete garbage to not have this already implemented, It should take the tenant settings and propagate instead of having each user go set it with a procedure. everything available from a business standpoint should be optimezed for time zones and regional settings, we've been with 365 for more than 2 years and still asking for this "feature" to be done. Really not impressed MS.

      • JustinJustin commented  ·   ·  Flag as inappropriate

        Time zones across o365 need to be looked at. Skype for Business missed conversations emails come through with the wrong timezone, I believe these are set to mountain time. Message trace in Exchange, despite having a timezone selector, outputs in UTC.

      • Alex OAlex O commented  ·   ·  Flag as inappropriate

        This is a great idea. Shame it has not been implemented after more than 2 years.

      • WimWim commented  ·   ·  Flag as inappropriate

        Fully agree. This is not an issues with SharePoint, also with Exchange the same happens for each mailbox. Currently only (personal) mailboxes can be configured, meaning any shared mailbox is still hooked to some time/zone settings. It should be someway hooked to an organization "template" or policy, better to allow regions hooked to for example organization groups, or zone settings on the device. Today for Exchange mailboxes we need to run separate PowerShell command's once people are created through the Admin portal.

      • LauraLaura commented  ·   ·  Flag as inappropriate

        Other portals - Video for example - can't be individually changed, so we are now stuck with US date format. This is such a basic requirement for enterprises in a single time zone, why has this not happened yet? Have the O365 Feedback Team really been "Thinking about it" for 14 months??

      • Thaddeus BrownThaddeus Brown commented  ·   ·  Flag as inappropriate

        To add on to this, having one place for a user to set their time/region would be great or have it set everywhere once the user sets it. As an admin, I have to send users to different places to make sure the time zone is set properly (Email, OneDrive ). Once a user sets their time zone they shouldn't have to do it in every service and they are using email in one time zone and onedrive in another.

      • AnonymousAnonymous commented  ·   ·  Flag as inappropriate

        allow admins to set default time zone for all mailboxes tenant wide. There are user that don't have access to OWA to set their time zone. When time zone for mailbox is null, it defaults to UTC for voicemail. This is causing confusion among end users. changing time zone mailbox by mailbox is time consuming and tedious. every time new mailbox is provisioned, we have to remember to set appropriate time zone.

      • Anonymous commented  ·   ·  Flag as inappropriate

        I would agree that the UTC needs to be set globally, then be able to override based on group or individual needs. 99% of our staff is in PST. The other 1% is in EST. We should be able to set the UTC for the bulk of our staff and admins (including mail trace) to PST and the for the few people who are in another time zone change their group or individual status. This should be for everything not just OWA or then separately SharePoint, Message Tracking etc.....

      • Ruth JennawayRuth Jennaway commented  ·   ·  Flag as inappropriate

        Timezones, Regional date formats, Language settings all should inherit from the Tenancy. And they should be updatable there, from the UI and an SPO-cmdlet, for those smaller clients who rushed through the set-up screens too quickly when they first signed up.

      • Dean GrossDean Gross commented  ·   ·  Flag as inappropriate

        O365 time information is somewhat of a mystery to me. I'm in the EST, set sites to EST, yet get error message from the PST, and reports seem to show UDT. The lack of ability to set a time zone for a tenant that applies to everything is annoying. It is just another example of MS failing to understand the needs of an enterprise.

        Their should be the ability to set Default values for many attributes and then have the ability to override them when appropriate at lower levels (service/site/user etc)

      Feedback and Knowledge Base