Correct settings to allow New Teams ("admin has restricted access")

Chris J 61 Reputation points
2023-08-16T18:49:47.8966667+00:00

I have been using New Teams for some time. A couple of weeks ago, it started returning the message "Your admin has restricted access to the new Teams" (in black text on a dark background, no less).

An image of a door with a red rope across the front, and the error message (in black on dark grey) "Your admin has restricted access to the new Teams"

I have set the following update policy for the tenant, but still get the message two days later:

Teams update policy Global: Teams preview features "On for everyone" and client setting "New teams as default"

I was previously signed into multiple tenants, so I am not sure whether or not it is attempting to connect to the correct tenant.

  • Where might I begin to investigate this?
  • Is there a debug log somewhere?
  • How can I find out which tenant it is trying and failing to access?
  • How can I force it to connect to a specific tenant?
Microsoft Teams
Microsoft Teams
A Microsoft customizable chat-based workspace.
9,393 questions
{count} votes

Accepted answer
  1. JimmyYang-MSFT 49,886 Reputation points Microsoft Vendor
    2023-08-17T09:25:33.43+00:00

    @Chris J

    According to your error message, it looks like your admin has set the permission for users to access new Teams client. To check if you could access this tenant, you could firstly try to switch to Classic Teams to see if you could login with no issue.

    Meanwhile, if you have set the update policy to users but it is not working, please try to remove new Teams for all users then start again.


    If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.


    3 people found this answer helpful.

14 additional answers

Sort by: Most helpful
  1. Carl Karawani 35 Reputation points
    2023-09-17T03:50:42.5966667+00:00

    Clear the cache on Mac fixed this for me:

    (Cache for Teams v2 is a different location)

    How to clear cache

    1. Command + Space and enter Terminal.
    2. rm -rf ~/Library/Group Containers/UBF8T346G9.com.microsoft.teams
    3. rm -rf ~/Library/Containers/com.microsoft.teams2

    Ref. https://learn.microsoft.com/en-us/microsoftteams/new-teams-mac-install-prerequisites#how-to-clear-cache

    7 people found this answer helpful.

  2. Łukasz Weiss 30 Reputation points
    2023-09-07T13:21:07.3233333+00:00

    Hi,

    I've also been struggling with this and was missing the switch button to enable MS Teams Preview...

    These are the steps that solved the issue for me:

    1. Remove Teams for AllUsers
      Get-AppxPackage MSTeams -AllUsers |Remove-AppxPackage -AllUsers
    2. Download the .exe installer
    3. Open the Command Prompt as an Admin.
    4. At the prompt enter: ./teamsbootstrapper.exe -pnew-teams-direct-reploy-cmd-feedback
    5. A success or fail status displays. If you receive an error, learn more at Common HRESULT values.
    5 people found this answer helpful.

  3. Opaque 20 Reputation points
    2023-10-11T07:57:33.08+00:00

    What the absolute f...? What is MS doing with the applications? Always a problem! I want to use the New (Desktop) MS Team for my Education purposes but then this bs comes in and throws error. Now what I seeing is I need to follow some solutions that are meaningless? NO! Enough is enough, I have no time for this issues, I'm busy with work and study, I'm tired. Please, solve this issue yourselves, I'm tired of always MS and MW making so much update that most of my Applications are even working anymore and then I have to find solutions that could be meaningless and waste of time. So annoying! Now I have to restart my whole PC from the very begining and hope that it will work. Thanks a lot.

    4 people found this answer helpful.

  4. js2010 186 Reputation points
    2023-11-28T19:12:44.5666667+00:00

    If you use the -o option, you must have the full path to the msix, or will get error 0x80070057, E_INVALIDARG. For example:

    teamsbootstrapper.exe -p -o %cd%\MSTeams-x64.msix

    If you try a second time, it will just say error 0x80004000 E_ABORT. You can start over with teamsbootstrapper -x. It never sets the errorlevel, just outputs some json with the result.

    2 people found this answer helpful.