Forum Discussion
Organization with more than 1 time zone and SharePoint calendars
Another solution for the product team: Match the Office365 time zone setting of users with what is already set for the users in Outlook online. The two settings are different. In Outlook online, the time zone value gets set when the user first logs on (there is a first time wizard experience). That setting in Outlook online is connected with and understood by an Outlook 2016 client as well (if they change that setting in the 2016 client, the Outlook online setting is changed as well). So there are links and connections. The odd one out seems to be the main Office 365 time zone setting, which should probably be the authoritative one, I would think. Can this be fixed or set?
- Well, SharePoint calendars are just lists that allow to store events and provide a calendar view but they are very limited and does not support the scenario you have just described
We could add all sorts of extra metadata fields to help organized and properly tag the events to the correct time zone, but the modern views for events do not respect or surface that data. Surely we are not the only customer that spans time zones and surely there is a solution (at least on a roadmap) for this. Either there needs to be an effort to unify the back end of all calendars across O365, or an effort to expand the modern views of SharePoint calendar events to allow for the surfacing of additional metadata.
- Indeed. In fact we can now support three time zones in Outlook. Incredibly useful. I’m on BST (GMT+1). So accessing ET and PT in calendar is brilliant. Frequently SharePoint defaults to PT giving me some ‘strange’ time stamps. Yes, you can change this at a site collection level but I agree the authoritative timezone should be at tenant level.
