Teams not working on MacOS Big Sur

Anonymous
2020-11-18T23:57:31+00:00

Hi all, 

I recently installer MacOS Big Sur in my Macbook Pro from scratch (not upgrading from previous installation). Once the system was working, I installed the Office 365 suite from App Store and MS Teams from microsoft.com (Teams does not exists in the App Store). All software is working properly EXCEPT Teams. After installation and launch, I keeps freezed in the "Loading Microsoft Teams" view.

I have uninstalled and reinstalled the package several times, restarted the machine, etc, but it still does not work.

Are there any procedures or fixed I should perform? Does Teams actually works on Big Sur?

Thanks.

Microsoft Teams | Microsoft Teams for business | Teams for Mac

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

107 answers

Sort by: Newest
Most helpful Newest Oldest
  1. Anonymous
    2021-03-31T16:25:34+00:00

    Hi Rodrigo,

    I'm Nik, an independent advisor here to assist you with this.

    1. Quit Microsoft Teams.
    2. Delete files in following folders.
      “~/Library/Application Support/Microsoft/Teams/Application Cache/Cache”
      “~/Library/Application Support/Microsoft/Teams/blob_storage”
      “~/Library/Application Support/Microsoft/Teams/Cache”
      “~/Library/Application Support/Microsoft/Teams/databases”
      “~/Library/Application Support/Microsoft/Teams/GPUCache”
      “~/Library/Application Support/Microsoft/Teams/IndexedDB”
      “~/Library/Application Support/Microsoft/Teams/Local Storage”
      “~/Library/Application Support/Microsoft/Teams/tmp”
    3. Restart Microsoft Teams.

    If it does not work, you may try clearing the cache of your app.
    Sign Out and Quit Microsoft Teams then
    to remove the cache credentials.
    See following steps：

    1. Go to Finder > Applications > Utilities.
    2. Select Keychain Access.
    3. Look for the login credential to MS teams, then delete it.

    Regards
    Nik

    THIS WORKS! This is the only method that works after trying all other methods. Especially the Keychain Access part is the one does the trick! Thank you!

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  2. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

    Comments have been turned off. Learn more

  3. Anonymous
    2021-03-25T02:24:46+00:00

    What works for me is to add Microsoft Teams under:

    System Preferences>Security & Privacy>Privacy tab>Screen Recording

    Was this answer helpful?

    3 people found this answer helpful.
    0 comments
  4. Anonymous
    2021-03-13T16:19:50+00:00

    I have the exact same issue that Rodrigo Zarate so clearly outlined. For now I'm going to use the website on a Chrome browser https://teams.microsoft.com/. But, would love to be able to have the full functionality of the app again.

    Was this answer helpful?

    0 comments
  5. Anonymous
    2021-03-04T21:18:12+00:00

    I just installed Teams on two computers running Big Sur, using essentially the same process. This is what worked for me, so I hope it helps others.

    1. Downloaded Teams to the two computers, but did not open the app.
    2. Created a Teams meeting from a system that had Teams running properly (ie: not in Big Sur).
    3. Emailed the invite to an address outside of the organization and then accessed the invite via webmail, not Outlook or any other mail program.
    4. Opened the invite, which launched the meeting.
    5. After launching the meeting, I clicked on the Teams app via the Teams icon and was able to open it and set up the actual Teams app with the applicable user names and passwords.

    All has worked well since then.

    Was this answer helpful?

    6 people found this answer helpful.
    0 comments