Share via

How to bypass Microsoft Teams desktop client sign-in loop using the Progressive Web App (PWA)

Vedish Achadoo 0 Reputation points
2026-06-02T21:36:27.87+00:00

If the desktop client is stuck in a sign-in loop, you can deploy Microsoft Teams as a Progressive Web App (PWA) via Google Chrome. This completely bypasses the local desktop authentication issues while maintaining standard app behavior.

__Step-by-step workaround:
__Open Google Chrome and sign into Teams via the web using this direct link, you can use Microsoft Edge if you want.
https://go.microsoft.com/fwlink/?linkid=873020&clcid=0x409&culture=en-us&country=us

Once signed in, look for the Install icon on the far right side of your Chrome address/search bar and click it.
If you cannot see the icon in the address bar:
Click the three dots menu in the top right corner of Chrome (the menu used to open a new window).
Navigate down to Cast, save and share and hover over it.
Select Install page as app.
This will launch Teams in a standalone PWA window that behaves just like the desktop client.

Note: This solution has been rigorously tested and verified as a successful workaround across 45 production devices.

Microsoft Teams | Microsoft Teams for business | Sign up and Sign in | Sign in

Locked Question. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Sophie N 15,145 Reputation points Microsoft External Staff Moderator
    2026-06-02T23:49:49.57+00:00

    Dear @Vedish Achadoo,

    Thank you for sharing this helpful workaround.

    I have reviewed your solution, and it is correct. Using Microsoft Teams via a Progressive Web App (PWA) through Google Chrome or Microsoft Edge is a reliable method to bypass desktop client sign-in loop issues while maintaining full functionality similar to the desktop application. Your detailed steps are clear and very useful.

    I appreciate you taking the time to document and validate this approach across multiple devices.

    At this time, since the thread does not contain a specific question or request for further assistance, we will proceed with closing (blocking) this case. If you have any additional questions or require further support in the future, please don’t hesitate to reach out.

    Thank you again for your contribution.

    Was this answer helpful?

    0 comments

  2. AI answer

    2026-06-02T21:36:46.16+00:00

    Using the Microsoft Teams Progressive Web App (PWA) in Google Chrome or Microsoft Edge is a valid way to work around issues with the desktop client, including sign-in problems, while still providing an app-like experience.

    To bypass desktop client sign-in issues by using the Teams PWA in Chrome:

    1. Open Google Chrome.
    2. Go to the Teams web experience (for example, via the Microsoft 365 portal) and sign in.
    3. Once Teams on the web is loaded, install it as a PWA:
      • If the Install icon appears at the right side of the address bar, select it to install Teams as an app.
      • If the icon is not visible, open the Chrome menu (three dots in the upper-right corner), go to Cast, save and share, and select Install page as app.
    4. Teams will open in its own window and behave similarly to the desktop client, but it runs as a browser-hosted PWA.

    For managed environments, administrators can also deploy Teams on the web as a PWA via group policies in Edge or Chrome using the WebAppInstallForceList and WebAppSettings policies. This lets admins force-install the Teams PWA for users who are having desktop client issues.

    To ensure a smooth experience for PWA users and avoid common permission or loading issues, administrators should additionally configure these recommended policies for Teams on the web:

    • SleepingTabsBlockedForUrls – Prevents Teams tabs from going to sleep.
    • NotificationsAllowedForURLs – Automatically allows notifications.
    • ScreenCaptureAllowedByOrigins – Allows screen sharing.
    • AudioCaptureAllowedUrls – Allows microphone access.
    • VideoCaptureAllowedUrls – Allows camera access.
    • CookiesAllowedForUrls – Explicitly allows required cookies, including third-party cookies used by Teams and line-of-business apps.

    If the sign-in issue occurs only in the Teams web client (including the PWA), follow the browser-specific guidance in the Teams sign-in loop article. For Google Chrome, this includes explicitly allowing cookies for key Microsoft and Teams domains under Privacy and security → Cookies and other site data → Sites that can always use cookies.

    If sign-in errors persist across both the desktop client and the PWA/web client, use the documented sign-in troubleshooting steps, which include checking for broader Office sign-in issues and, if needed, reinstalling Teams and clearing the local Teams data folder.

    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?