"We couldn't complete that action" when creating a new Team

Anonymous
2024-06-24T13:46:15+00:00

I have a user that is getting this error when trying to create a new Team in the Teams beta version. I was having it as well until I cleared my cache. Unfortunately, the same fix did not work for them. Any ideas?

Microsoft Teams | Microsoft Teams for business | Teams and channels | Create a new team or channel

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

83 answers

Sort by: Newest
Most helpful Newest Oldest
  1. Anonymous
    2024-07-03T01:14:41+00:00

    TM807389 says its specifically about admins, but between it and TM801268 i'd say lies the problem

    Signing out and quitting teams is not helping my users, but hitting up the web version on https://teams.microsoft.com/v2/ is working, and is more convenient then the phone app for most users, so thats what we are pushing.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2024-07-02T23:06:59+00:00

    Just wait until they force the "New" Outlook down our throats. The olny thing that works for me is the mobile app in Teams to create a new project. I'm glad for these posts so I don't spend ours of frustration going after something I can't fix as an admin.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  3. Anonymous
    2024-07-02T17:52:47+00:00

    Hi Pat. This didn't work for me, just an FYI.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2024-07-02T17:49:04+00:00

    Signing out of Teams freezes it, then giving MS Teams the three finger salute (Ctrl+Alt+Del) and ending the frozen Teams instance from the Task Manager seems to resolve the issue.

    Was this answer helpful?

    0 comments
  5. Anonymous
    2024-07-02T17:46:41+00:00

    Signing out of Teams freezes it, then giving MS Teams the three finger salute (Ctrl+Alt+Del) and ending the frozen Teams instance from the Task Manager seems to resolve the issue.

    Was this answer helpful?

    0 comments