Shifts app issue

Satram Likhitha 0 Reputation points
2026-05-21T08:17:29.1033333+00:00

Shifts app is not working inside the virtual desktop in both the Teams application and in web browser. While I opened the app in web it is showing the error msg "flw.teams.cloud.microsoft closed the connection" and while I try to open in teams application it is showing infinite blank page. tried in the incognite and also with different network same issue is happening.

Microsoft Teams | Microsoft Teams for business | Teams and channels | Manage a team or channel
0 comments

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Daniel-Vo 6,175 Reputation points Microsoft External Staff Moderator
    2026-05-21T09:25:31.41+00:00

    Dear @Satram Likhitha,

    I understand that the Shifts app isn’t working inside your virtual desktop, both in the Teams app and in the browser. In the browser you see “flw.teams.cloud.microsoft closed the connection,” and in the Teams client you see an infinite blank page, even after trying Incognito and a different network.

    To better assist, could you please confirm following information:

    • Which virtual desktop platform are you using: Azure Virtual Desktop, Windows 365, Citrix, or VMware?
    • Does Shifts work outside the virtual desktop (on a normal PC/laptop using the same account)?
    • What is your tenant cloud type (Commercial, GCC, GCC High, DoD)?
    • Is the affected account a guest user or a member user?
    • Is this happening for all users in the virtual desktop, or only specific users?
    • Can you confirm whether Shifts is allowed in your environment (Teams Admin Center > Teams apps > Manage apps > Shifts = Unblocked)?

    In the meantime, I recommend some quick checks below:

    1/ Confirm Shifts is allowed in Teams Admin Center

    Go to Teams apps > Manage apps > Search Shifts

    Then check the Status is unblocked

    2/ Quick isolation test (VDI vs non-VDI)

    Sign in with the same account on a non-VDI device and open Shifts in Teams (desktop or web). If it works outside VDI, the issue is likely specific to the virtual desktop configuration/restrictions. I recommend checking the OS and try to restart the system.

    3/ Quick validation inside VDI: check if other Teams apps load

    Try opening another Teams app (for example Approvals/Tasks). If multiple apps fail, it may indicate a broader embedded-app/connectivity issue within VDI. (If only Shifts fails, it points more toward Shifts being blocked or a Shifts-specific connectivity restriction.)

    Please understand that our initial response does not always resolve the issue immediately. However, with your help and more detailed information, we can work together to find a solution.

    I truly appreciate your patience and understanding. If you have any further questions or need further clarification, please feel free to reach out. I'm looking forward to hearing from you. 

    Thank you for your cooperation.

    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.

    Was this answer helpful?

  2. AI answer

    2026-05-21T08:17:47.0133333+00:00

    The behavior points to a Shifts/Teams service or session issue in the virtual desktop rather than a local browser/network problem, since it fails in both the Teams desktop client and web, including incognito and different networks.

    Try these steps in order:

    1. Verify Shifts service status and known issues
    • Confirm with the Microsoft 365 admin whether there are any known Shifts or Teams service incidents in the tenant.
    • If UKG Pro WFM or another Shifts connector is in use on shared/pooled devices, be aware of the known SSO/session issue where one user remains signed in to the WFM backend while another uses Teams on the same device. In that case, after signing out of Teams in the virtual desktop:
      • Close all browser windows on the virtual desktop.
      • Clear cookies and site data for the WFM site (for example, mykronos.com) in the browser before trying again.
    1. Test outside the virtual desktop
    • Sign in to the same Teams account on a non‑VDI device (local Windows or macOS machine) and open Shifts in:
      • Teams desktop app
      • Teams web app
    • If Shifts works normally outside VDI, the issue is likely specific to the virtual desktop image, policies, or network routing from that environment.
    1. Check virtual desktop optimization and client
    • Ensure the Remote Desktop or Windows app client used to connect to Azure Virtual Desktop/Windows 365 is up to date, as outdated clients can cause Teams app issues in VDI. See the guidance to upgrade to the latest Remote Desktop or use the Windows app.
    • If using Azure Virtual Desktop and Teams is media‑optimized, confirm the Remote Desktop WebRTC Redirector Service is installed on the session host image as required. If not, install it or redeploy hosts using an image where it is pre‑installed, following Install the Remote Desktop WebRTC Redirector Service.
    1. Collect logs from the virtual desktop
    • On the host VM, collect Teams client logs from:
      • %appdata%\Microsoft\Teams\logs.txt
    • For call/meeting‑related issues (if relevant), start Teams diagnostic logs with Ctrl + Alt + Shift + 1; logs are saved under:
      • %userprofile%\Downloads\MSTeams Diagnostics Log DATE_TIME.txt
    • These logs will help your admin or Microsoft support identify whether Shifts is failing due to authentication, network, or app errors.
    1. Check for VDI/FSLogix issues (if applicable)
    • If the virtual desktop runs Windows Server 2019 with FSLogix and new Teams, ensure the latest FSLogix version is installed to avoid known issues where new Teams fails to launch or crashes.
    1. Use audit logs and support if the problem persists
    • If Shifts loads for some users but not others, an admin can:
      • Turn on auditing in the Microsoft Purview portal (if not already enabled).
      • Search the audit log for Shifts events to confirm whether Shifts activity is being recorded for the affected account.
    • If the issue continues after the above checks, open a support case:
      • From Teams, select Settings and more (… ) > Help > Give feedback, clearly stating it is a Shifts issue in a virtual desktop.
      • Or, an admin can contact Microsoft Teams support via the Microsoft 365 admin center.

    This combination of VDI‑specific checks, service validation, and log collection will help isolate whether the Shifts app failure is due to the virtual desktop configuration, backend connector/SSO, or a broader service problem.

    References:

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

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.