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.
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.
@Chris Thompson suggested the Time Zone could be fixed at 'SharePoint Admin centre > Settings > Site Creation > You can specify Default time zone and where to create the sites' - thanks for that.
But that does not take care of SPO Tenant locale setting. Our one has been set originally as US locale and any new SPO sites created, incl. OneDrive and Teams sites are created with US locale, which creates problems with date formats - US mm/ddd/yyyy (and others problems connected with locale format), when we are based in single UK zone.
@Microsoft - don't think about it - please provision a way to change that in SPO/MS365 admin centres - tenant wide and on SharePoint Admin centre > Settings > Site Creation page for a single site.
Chris Thompson commented
In your SharePoint Admin centre > Settings > Site Creation > You can specify Default time zone and where to create the sites
yes, for organisations which are in a single time zone, it's extremely tedious to have to set each site's time zone individually. please allow for tenant wide setting of time zone. the individual site time zone can still remain to be set to override any tenant wide setting.
I can see why each site collection can have the ability to change the time zone as they may exist in different countries.
We should, however, be able to set the tenancy default to English UK though.
It is very annoying that the standard default for English is English US.
Robert Park commented
This would be fantastic, thanks. :)
Completely agree with you. It would be a good product improvement ...
Javier Orts commented
We have created thousand of sites before we realized our time zone setting for site creation was wrong. Now we have to edit that setting in each site. A whole tenant directive for this would be great.
We are in 2020, you could do this on premises without issue.
My job is to support companies migration to the office 365 environment, it is not a good starting point to suggest they change the way they work with date and time or setup external scripts to convert new and current sites just to change a TZ and location.
We could do with some MS support on this. Cloud migrations are fast becoming a one way street for the modern generation of business. the very least MS could offer is a global setting for time and location.
Dave Webster commented
Just adding to the, "this still isn't fixed yet!"
It's just a massive cludge / cluster...k
Veronique Palmer commented
And ALL content on the sites must reflect our desired timezone and locale - ie : the date format on the modern pages....
Bassem Khalil commented
For the record, this has been actioned since 2018
Chris Copland commented
Re-iterating Chris O'Connor's comment of 05/03 (or 03/05 depending on your perspective...). Requirement is to set locale (and therefore date and time format) at a tenant level.
Sharing the link to new uservoice item covering this (needs more votes - maybe Microsoft think this has been completed and therefore closed it off).
We want to change the default time zone settings for Chile Country in our active sites; in addition, if a user creates a new sites, the same must have the time zone of this country as the default.
David Mounsey commented
We need there to be a single location within the O365 Admin whereby we can set the default timezone, language and region setting that ALL MS services pick up and use.
This includes Teams, Groups, OD4B, Sharepoint & Exchange.... and even the Admin Centre itself!!
I cant spend by day going and fixing this after users create (eg) a new Group and have to go in and change the site settings
Simon Hudson commented
Is this still not fixed?
That's crazy! So everyone who isn't in the US (so almost everyone) has to manually set it for every new site (including those created by Teams)
It's vital that this is sorted out
Setting the TZ in Sharepoint will only make it apply to new sites. Sites that have been made in the past will not copy or set the new timezone automatically, which means you'd still have to set all of those by manually. Very inconvenient.
Chris O'Connor commented
My 'fix' was to create an Azure Function that uses PowerShell to set the timezone + locale for every site collection in the tenant - and this runs on a schedule at 11pm every evening. *sigh*
Chris O'Connor commented
@Daniel (February 10, 2019) - this feature is HALF available. You can set the default timezone - but that's just TIME.
The 'locale' is missing. I can't believe Microsoft didn't do BOTH fields - when doing the Timezone.
Also - this is when creating a team site - and still have to set EVERY time.
There should be a GLOBAL tenant setting - for all sites & mailboxes - TIMEZONE + LOCALE.
Most countries use DMY format, not the old format of MDY (only in America)
Tony Sutton commented
Can MS make sure the Locale can also be set to a different default too please?
New Admin centre allows setting of default time-zone to UK (for example), but this is of little use when locale still defaults to U.S. and has to be manually reset on every site collection.
This feature IS available! Check out the following blog for more info: