Microsoft Teams

It sounds like you are experiencing a network issue that is causing your Microsoft Teams meeting to end prematurely. This can happen if there are connectivity problems that prevent your device from maintaining a stable connection to the meeting. In such cases, Teams may suggest that you join the meeting again or use a phone to dial in for audio.

To resolve this issue, you can try the following steps:

1. Check your internet connection to ensure it is stable.
2. If the problem persists, consider using the "Call me" feature to join the meeting audio through your phone, which can help if your computer audio is not working properly.
3. Ensure that your Teams app is updated to the latest version, as updates can fix bugs and improve performance.

If the issue continues, you may want to reach out to your IT support for further assistance.

Hi @Sameer Siddiqui, 

Welcome to the Microsoft Q&A forum.  

Based on the details you shared, your Microsoft Teams meeting automatically ends after 20 to 30 seconds and displays the message “Try joining again, or dial in… due to a network issue.”  I understand the impact this has on your meeting experience, and I genuinely appreciate the time and effort you put into sharing the exact timing and message. 

This usually happens because Teams performs a quick connectivity check when you join, and if the connection becomes unstable during the initial audio or video setup, the session may end to protect call quality. Additionally, certain network paths can interrupt real time communication, such as WiFi instability, VPN or proxy inspection, or firewall filtering, which can trigger the rejoin or dial in prompt. In some cases, an outdated Teams build or a corrupted local cache can also contribute, because the client may not complete the connection handshake consistently. 

To address this, please follow these steps in order, since each one targets a common root cause and builds toward a stable join experience: 

1/ Confirm network stability before you join the meeting 

• If you are on WiFi, move closer to the router, or connect using Ethernet if available, because a stronger signal reduces packet loss during the first seconds of the call. 
• Then try joining the same meeting on an alternate network, such as a mobile hotspot, to confirm whether the issue is tied to your current connection. 
• Finally, pause bandwidth heavy activity, such as cloud sync or large downloads, and rejoin the meeting, since high usage can interrupt the initial Teams connection setup. 

2/ Refresh Teams by signing out and clearing the local cache 

• Fully close Teams, and ensure it is not running in the background. 
• Clear the Teams cache, then reopen Teams and sign in again. 
  • On Microsoft: Press Windows + R, then type: %userprofile%\appdata\local\Packages\MSTeams_8wekyb3d8bbwe\LocalCache\Microsoft\MSTeams  
  • On Mac: Press Command + Q, type:

        rm -rf ~/Library/Group Containers/UBF8T346G9.com.microsoft.teams  
        rm -rf ~/Library/Containers/com.microsoft.teams2 
    

• After that, rejoin the meeting and check whether the session stays connected beyond 30 seconds. 

3/ Remove network filters that can interrupt real time media 

• If you are connected to a VPN or using a proxy, disconnect temporarily and test joining the meeting again, because these services can inspect or reroute traffic during the join process. 
• If you manage your device firewall settings, ensure Microsoft Teams is permitted, then retry the meeting to confirm the connection is no longer being interrupted. 

4/ Contact IT administrator 

• If you are on a corporate network, please ask your IT admin to allow Teams real time media traffic and to avoid security inspection that can interfere with audio and video negotiation. 
• If the issue persists after these checks, ask your IT administrator to submit a support request directly to Microsoft Support team.       

They can raise a support ticket by visiting: Get support - Microsoft 365 admin | Microsoft Learn 

As community moderators, we appreciate your understanding that our access to internal development details is limited. Our primary role is to guide users toward the appropriate resources and support channels. While we may not have visibility into deeper backend analysis, we’ll continue doing our best to support you within the scope of our responsibilities.     

I hope this information is helpful. Please follow these steps and let me know if it works for you. If you have any updates regarding the issue, please feel free to share them with me.       

Thank you for your patience and your understanding. I look forward to continuing the conversation. 

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.