Anonymous

My feedback

  1. 1,036 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    189 comments  ·  Public » Calendar  ·  Flag idea as inappropriate…  ·  Admin →

    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”

    An error occurred while saving the comment
    Anonymous commented  · 

    It should be enough for Teams to use OS-level settings for regional options (date and time formats, start of week etc.) and not to derive them from application-level language setting. Or make it even more configurable like "use system settings" or "use this display language" and "use these regional formats". Windows settings for language and regional formats are separated and it proved as a good concept since NT 4.0. Mixing display language and regional formats into single option (like in Android) is step backward. There are many companies intentionally using English display language due to clear terminology and different regional format to match local habits.

  2. 230 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    207 comments  ·  Public » Bugs  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Anonymous commented  · 

    Simply said - crapware. Idle renderer process starts to eat one CPU core on daily basis, requiring to restart the app. Sometimes quitting the app restarts it instead since some kind of autorecovery mechanism believes that the app crashed in previous run. Unusable diagnostic data readable only for MS support... I can continue almost infinitely.

  3. 5 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Public » Guest Access  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Anonymous commented  · 

    The problem still persists as of January 2021 and even enabling aliased email address for sign-in and signing in with that address is not sufficient for Teams to recognize intended user. It seems that Teams relies on primary alias only (this however can be caused by authentication server and not the Teams service itself).

    Anonymous supported this idea  · 

Feedback and Knowledge Base