• Find Teams on the web at To use Teams, you need a Microsoft 365 account with a Business or Enterprise Microsoft 365 license plan. For more information, see How do I get access to Microsoft Teams? For information about supported browsers for Teams on the web, see Web clients for Microsoft Teams.
  • Download Microsoft Teams now and get connected across devices on Windows, Mac, iOS, and Android. Collaborate better with the Microsoft Teams app.
  • Here are the steps to create teams and channels in Microsoft Teams: 1. Step 1: Open the Microsoft Teams app and click on the “Join or create a team” option at the bottom of the Teams sidebar on the left. Step 2: On the new screen that appears, click on the “Create team” button.

The Microsoft Teams web app works for most desktop browsers, including Chrome, Firefox, and Internet Explorer. This article explains how to host your own Microsoft Teams meeting on a desktop or a mobile device. Using Microsoft Teams, you can create, connect, share, and collaborate with family and friends online. What You Need to Host a Microsoft Teams Meeting.


There are three types of log files automatically produced by the client, which can be leveraged to assist in monitoring and troubleshooting Teams:

This article describes the three logs and how they are used.

For information about troubleshooting specific issues, see: Teams Troubleshooting. For information about how to contact support, see Get support.

When creating a support request with Microsoft Support, the support engineer will require the debug logs. Having the debug logs on hand before creating the support request will allow Microsoft to quickly start troubleshooting the problem. Media or Desktop logs are only required if requested by Microsoft.

Teams Desktop Version


In this article, the term Debug logs refers to the logs that are used for troubleshooting. However, the files that are generated for these logs will contain the term diagnostic logs in their names.

The following table outlines the various clients and their associated logs. Log files are stored in locations specific to the client and operating system.


For a complete list of supported operating systems and browsers, see Get clients for Microsoft Teams.


Debug logs

These are the most common logs and are required for all Microsoft support cases. Debug logs are produced by the Windows and Mac desktop clients, as well as by browser-based clients. The logs are text based and are read from the bottom-up. They can be read using any text-based editor, and new logs are created when logging into the client.

Debug logs show the following data flows:

  • Login

  • Connection requests to middle-tier services

  • Call/conversation

The debug logs are produced using the following OS-specific methods:

  • Windows:

    Keyboard shortcut: Ctrl + Alt + Shift + 1

  • Mac OSX:

    Keyboard shortcut: Option + Command + Shift+1

  • Linux:

    Keyboard shortcut: Ctrl + Alt + Shift + 1

The debug logs are automatically downloaded to the following folders:

Teams Desktop App Download

  • Windows: %userprofile%Downloads

  • Mac OSX: ~/Downloads

  • Linux: ~/Downloads

  • Browser: You will be prompted to save the debug log to default save location

Media logs

Media logs contain diagnostic data about audio, video, and screen sharing in Teams meetings. They are required for support cases that are linked to call-related issues.

Media logging is turned off by default. To log diagnostic data for Teams meetings, users must turn on the option in the Teams client. Go to Settings > General, select the Enable logging for meeting diagnostics (requires restarting Teams) check box, restart Teams, and reproduce the issue.

Teams desktop api

The following table outlines the media log locations. When you send the log files to Microsoft support, please verify the timestamp of the log files to ensure the logs cover the time frame when you reproduced the issue.

Mac OSX~/Library/Application Support/Microsoft/Teams/media-stack/*.blog
~/Library/Application Support/Microsoft/Teams/skylib/*.blog
Linux~/.config/Microsoft/Microsoft Teams/media-stack/*.blog
~/.config/Microsoft/Microsoft Teams/skylib/*.blog

Here's a list of the log files that are generated and the information they contain.

Log file nameDescription
Teams.msrtc-0-s1039525249.blogContains information related to the media stack. This includes channel status such as resolution, decoders and encoders used, and the number of frames sent and received, and camera and video-based screen sharing (VBSS) session status.
rtmcontrol.msrtc-0-2415069487.blogRecords information related to remote control actions, such as the time stamp when control is given, and mouse pointer information.
Teams_MediaStackETW-2-U-xr-U.etlRecords media stack trace events.
Debug-0-s2790420889.blogContains information related to the media agent, including rendering quality.
tscalling-0-2061129496.blogRecords events in the ts-calling API.

Desktop logs

Desktop logs, also known as bootstrapper logs, contain log data that occurs between the desktop client and the browser. Like media logs, these logs are only needed if requested by Microsoft. The logs are text based and can be read using any text-based editor in a top-down format.


  • Right-click the Microsoft Teams icon in your system tray, and select Get Logs.

Mac OsX:

Teams Desktop App Download

Teams Desktop
  • Choose Get Logs from the Help pull-down menu.


  • Click on the Microsoft Teams icon in your system tray, and select Get Logs.
Mac OSX~/Library/Application Support/Microsoft/Teams/logs.txt
Linux~/.config/Microsoft/Microsoft Teams/logs.txt

Browser trace

For some categories of errors, Microsoft Support might require you to collect a browser trace. This information can provide important details about the state of the Teams client when the error occurs.

Before you start the browser trace, make sure that you’re signed in to Teams. It's important to do this before you start the trace so that the trace doesn't contain sensitive sign-in information.


After you’re signed in, select one of the following links, as appropriate for your browser, and follow the provided steps.


In the steps, replace all references to the Azure portal with the Teams client.

Related topics


This article describes the requirements and limitations for using Microsoft Teams in a remote desktop services (RDS) environment.

What is RDS?

Remote Desktop Services (RDS) is the platform of choice for building virtualization solutions for every end customer need. RDS lets you deliver individual virtualized applications, provide secure mobile and remote desktop access, and provide end users the ability to run their applications and desktops from the cloud.

RDS offers deployment flexibility, cost efficiency, and extensibility. RDS is delivered through a variety of deployment options, including Windows Server 2016 for on-premises deployments, Microsoft Azure for cloud deployments, and a robust array of partner solutions.Depending on your environment and preferences, you can set up the RDS solution for session-based virtualization, as a virtual desktop infrastructure (VDI)

Currently, Teams in a remote desktop services environment is available with support for collaboration and chat functionality. To ensure an optimal user experience, follow the guidance in this article.

Teams on RDS with chat and collaboration

If your organization wants to only use chat and collaboration features in Teams, you can set user-level policies to turn off calling and meeting functionality in Teams.

Set policies to turn off calling and meeting functionality

You can set policies by using the Microsoft Teams admin center or PowerShell. It might take some time (a few hours) for the policy changes to propagate. If you don't see changes for a given account immediately, try again in a few hours.


Calling polices: Teams includes the built-in DisallowCalling calling policy, in which all calling features are turned off. Assign the DisallowCalling policy to all users in your organization who use Teams in a virtualized environment.

Meeting policies: Teams includes the built-in AllOff meeting policy, in which all meeting features are turned off. Assign the AllOff policy to all users in your organization who use Teams in a virtualized environment.

Assign policies using the Microsoft Teams admin center

To assign the DisallowCalling calling policy and the AllOff meeting policy to a user:

  1. In the left navigation of the Microsoft Teams admin center, go to Users.

  2. Select the user by selecting to the left of the user name, and then select Edit settings.

  3. Do the following steps:

    a. Under Calling policy, select DisallowCalling.

    b. Under Meeting policy, select AllOff.

  4. Select Apply.

To assign a policy to multiple users at a time:

  1. In the left navigation of the Microsoft Teams admin center, go to Users, and then search for the users or filter the view to show the users you want.
  2. In the (check mark) column, select the users. To select all users, select the ✓ (check mark) at the top of the table.
  3. Select Edit settings, make the changes that you want, and then select Apply.

Or, you can also do the following steps:

  1. In the left navigation of the Microsoft Teams admin center, go to the policy you want to assign. For example:

    • Go to Voice > Calling policies, and then select DisallowCalling.
    • Go to Meetings > Meeting policies, and then select AllOff.
  2. Select Manage users.

  3. In the Manage users pane, search for the user by display name or by user name, select the name, and then select Add. Repeat this step for each user that you want to add.

  4. When you're finished adding users, select Save.

Assign policies using PowerShell

The following example shows how to use the Grant-CsTeamsCallingPolicy to assign the DisallowCalling calling policy to a user.

To learn more about using PowerShell to manage calling policies, see Set-CsTeamsCallingPolicy.

The following example shows how to use the Grant-CsTeamsMeetingPolicy to assign the AllOff meeting policy to a user.

To learn more about using PowerShell to manage meeting policies, see Set-CsTeamsMeetingPolicy.

Coments are closed

Most Viewed Posts

  • Retroarch Pi 4
  • Ps2 Emulator Retroarch
  • Firefox Onion
  • Stadia On Ios
  • Tor Browser Official

Scroll to top