MicrosoftIn Manitoba, we are considering changing to "Bogota, Colombia" which is UTC-5 and does not observe daylight savings. Would that not work in the interim?
This same timezone is where I am leaning as well.
If you run the below in powershell, it seems to be the best candidate (DST unsupported and UTC-05):
> Get-TimeZone -ListAvailable | ? -Property BaseUtcOffset -eq "-05:00" | ? -Property SupportsDaylightSavingTime -eq $false
Id : SA Pacific Standard Time
DisplayName : (UTC-05:00) Bogota, Lima, Quito, Rio Branco
StandardName : SA Pacific Standard Time
DaylightName : SA Pacific Daylight Time
BaseUtcOffset : -05:00:00
SupportsDaylightSavingTime : False
Official guidance from MS is to use EST with DST disabled....which is fine for Windows, but I don't know many admins who only have to worry about windows. Most of our SaaS tools are like "What's a Manitoba?" so we're going with Bogatime pretty much everywhere that isn't user facing now......
Caution against using it in Windows - I had mine set to Bogota and when I was trying to schedule a meeting on one of those "pick your time slot" scheduling apps, it flashed the "BOGOTA, JAMAICA, LIMA TIME" and even though I was half-expecting it, I think the Jamaica part threw me, since it's not part of the Windows display name..... I think our users will be less terrified by setting it to EST and disable DST.....
But there is definitely some mismatches, too....when set to Bogatime on one of our SaaS tools and on my local workstation, I was still seeing an hour offset between the two.....with the same setting....
