OWA with Office 365 Cannot Change Time Zone
-
In the continuing saga of "nothing on Office 365 works for me", found this today: can't change my time zone for my own account. So my calendar shows everything eight hours off when it should be, which means that I don't get calendar notifications for anything and I have to remember to calculate the right time skew all the time. This is super annoying.
-
It was an easy fix the country needs to be changed from the admin panel.
-
That fixes the changing of the time zone. Doesn't fix why that error message was given instead of information about how to change it and doesn't explain why my existing country, which has valid locations in this time zone, doesn't work here. What if I wasn't in a foreign country but was on US territory but in this time zone? Changing the country to an arbitrary one is not intuitive or "correct".
-
@scottalanmiller said:
That fixes the changing of the time zone. Doesn't fix why that error message was given instead of information about how to change it and doesn't explain why my existing country, which has valid locations in this time zone, doesn't work here. What if I wasn't in a foreign country but was on US territory but in this time zone? Changing the country to an arbitrary one is not intuitive or "correct".
Have MS errors EVER been helpful?
-
@scottalanmiller said:
That fixes the changing of the time zone. Doesn't fix why that error message was given instead of information about how to change it and doesn't explain why my existing country, which has valid locations in this time zone, doesn't work here. What if I wasn't in a foreign country but was on US territory but in this time zone? Changing the country to an arbitrary one is not intuitive or "correct".
It's a line of reasoning to create a feature on a product. Correct isn't part of the equation. That's how it works. And it's obviously not all-inclusive. A lot of things are like that.
-
@art_of_shred said:
It's a line of reasoning to create a feature on a product. Correct isn't part of the equation. That's how it works. And it's obviously not all-inclusive. A lot of things are like that.
It's considered incorrect, an error or a bug if you are forced to lie to a product to get it to work as described.
-
In my case, you can easily say that travelling to another country warrants telling MS that you are in that country and that just makes the product annoying and poor. That's fine.
But it does not know "where" I am, it simply incorrectly associates country with timezone - it's an association that does not exist in the real world.
This is the same problem that causes Windows to have no working timezone for the Falkland Islands. They simply don't have working time there on Windows.
-
There's an apt phrase that I picked up while in Africa that applies well to this. It's not broken, it's just cheap.
