Anonymous
My feedback
-
979 votes
Currently, start day for the week and the work-week are set based on your language in Settings in Microsoft Teams. The Calendar team has work on the backlog to address the case where users may want a different week/work-week start day than is usual for their language setting.
Until then, the team wanted to share this workaround for setting the work-week start day via OWA, while leaving your language settings as-is.
- Open Outlook Web Access (“OWA”), and go to the Settings panel, as described in this article: https://support.microsoft.com/office/calendar-settings-in-outlook-web-app-84544ef2-d5cf-4696-bcb3-cc87719a3e07.
- In the OWA Settings, click “View all Outlook Settings”
- Use the settings under “Show work week as” to choose your work-week days.
- Click “Save”
- Return to Teams, click on your photo/initials at the top right and choose “Sign Out”Anonymous supported this idea ·
-
273 votes
Anonymous supported this idea ·
-
15 votes
Anonymous supported this idea ·
-
5,670 votes
We are getting closer, and are still working thru some bugs, but hope to release this as part of a Public Preview pack in early 2021! (Windows 10 released with the December 2020 pack this week)
You can learn more about the new Microsoft Teams Public Preview program here: https://aka.ms/TeamsPublicPreview, and Teams administrators can find documentation to manage which users will see the Public Preview option here: https://aka.ms/TeamsPublicPreviewAdmin
Anonymous supported this idea ·
-
17 votes
An error occurred while saving the comment Anonymous supported this idea ·
-
1,876 votes
Thank you for your feedback! We are happy to share that users who write different messages in different languages, will now see spellchecking relevant to the language they are actively using when typing a message while using the Microsoft Teams Desktop App on Windows.
Please see details here – https://support.microsoft.com/office/check-your-spelling-in-multiple-languages-0e269374-0cac-4a22-a377-53f01e05a6d4
Anonymous supported this idea ·
I have the same issue on version 1.3.00.362.