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.

725 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 Anderson shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →
    thinking about it  ·  O365 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.

    36 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...
      • Hamish Barry commented  ·   ·  Flag as inappropriate

        I would like to see this put in, ideally across all 365 products in the tenant.
        Its a looming task that we need to take care of, and its not straight forward to implement either, especially on all the one drives.

      • Paul Ewert commented  ·   ·  Flag as inappropriate

        Two and a half years, and still "THINKING ABOUT IT." We have nearly 10,000 site collections in our tenancy and nearly every one of them is going to have the wrong time zone for our corporation, by default. Brilliant, and oh so much fun to correct. Stop thinking about it and fix this already!

      • Rebecca Nevard commented  ·   ·  Flag as inappropriate

        assumed this was already a part of Office 365. Come on Microsoft not all your clients are based on the West coast of USA. A global product needs a Global solution that works for all

      • Hiten Lad commented  ·   ·  Flag as inappropriate

        you would of thought that this was a must.... this would make life so much better

      • Anonymous commented  ·   ·  Flag as inappropriate

        What on earth is there to think about? Having a US timestamp on a work file when we are not in the US is causing users to overwrite their data. This is a serious failure, not a desired feature to maybe plan in.

      • Simon Whitfield commented  ·   ·  Flag as inappropriate

        Just had a support request in about this issue. Being in the UK, it is a pain that everytime you create a new SharePoint site that you have to remember to go back and change the regional settings. This is more a nuisance with Microsoft Teams, as you create the team in the Teams GUI, which then creates the underlying SharePoint site automatically for you, so you never really interact with SharePoint.

      • Anonymous commented  ·   ·  Flag as inappropriate

        Even if we set user outlook timezones for outlook in o365 when you create an o365 group the SharePoint libraries do not pick up this user setting.

        This is a fundamental requirement for any organisation with a wildly different timezone than where the tenant is hosted - eg New Zealand - we are a day ahead of the USA... please resolve.

      • Jacqueline Sirmon commented  ·   ·  Flag as inappropriate

        We need Tenant-wide time zone set for users as we provision them so that they aren't prompted to select a time zone (which they just click past and are then late to all their appointments)!

      • Lance Moonshower commented  ·   ·  Flag as inappropriate

        How about an update on this? Seems like a lot of responses from customers but no update since July 2015 from MS. This seems so fundamental that it's crazy it hasn't already been addressed.

      • Jay H commented  ·   ·  Flag as inappropriate

        I can't fathom why Office 365 was ever released not using UTC adjusted to the local account timezone. Given that Microsoft is a global corporation with customers all over the world outside their headquarters's PST timezone, one would think this would be a super high priority to get this implemented. How has Microsoft been "thinking" about something this fundamentally wrong for over two years.

      • Anonymous commented  ·   ·  Flag as inappropriate

        The sites zone should not have a time zone. Store everything in UTC (as I'm sure it is anyway) and have the UI apply the user's timezone to the times accordingly....

      • Matthew commented  ·   ·  Flag as inappropriate

        I disagree -- Microsoft should get out of the entire time zone by site business altogether. Being in a global organization with global teams, setting a site time zone does not make any sense. Have a tenant time zone to default for external and anonymous users, and for licensed users -- use the regional settings in delve to drive time zone and format for all services.

      • Erica 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. ^_^

      • Shirley 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.

      ← Previous 1

      Feedback and Knowledge Base