"Based on our research, the behavior is a result of Teams' design and there is currently no way to change it."
"Many features of our current products are designed and upgraded based on customers’ feedback. With requirements like this increase, the problem may well be released in the future."
- This is not a feature-related issue.
- This is something Microsoft Support and the dev team should be responding to directly and escalating to the dev team to fix within a month at latest. Especially given that everyone will be forced to upgrade to New teams after March 31.
- Useability is more important than features and if you read the initial post this is a glitch and may cause people to miss meetings.
- It could potentially cost someone money if they schedule a meeting with an important client and miss that meeting because they set the wrong time zone
- "if there is a will, there is a way" ... Microsoft can fix this if they make it a priority
Microsoft needs to address actual glitches and useability different from feedback or product features. "Many features of our current products are designed and upgraded based on customers’ feedback" ...
This is a glitch (it's not a feature) and Microsoft Support should be escalating this to the dev team, not asking people to vote for it. Would Outlook users be okay if they always had to manually switch the time zone? Of course, not.