Troubleshooting Microsoft Teams and client log locations

In this post I point out where to start troubleshooting and where logs for a Microsoft Teams (windows) client are located by default. Where to start (client) troubleshooting? Well, this depends at which deployment state you are. If you are evaluating Teams in a PoC and all PoC Teams users are affected you might start to check your infrastructure and connectivity before digging deeper into client log analysis.


First of all you should verify and validate that your infrastructure and network connectivity towards Microsoft Cloud Edge is alright. To do this you can verify that all “Office 365 URLs and IP address ranges” are accessible via your network and internet breakout. Ensure that you have configured the required proxy exceptions and firewall rules allowing to connect to Microsoft Cloud services. Common misconfigurations are missing proxy exceptions, firewall rules, firewall (ssl) interception or deep packet inspection mechanisms. Also, an unbenifical and/or legacy network design can cause increased latency, roundtrip times (rtt), jitter, packet loss and lead to bad user experience. So, you should better make your infrastructure and especially your network ready for cloud communication and collaboration (see “Prepare your organization’s network for Microsoft Teams”).

Easy ways to check your network connectivity towards Microsoft Cloud Data Center edges is the “Skype for Business Network Assessment Tool”. It’s a powershell-based tool and helps you to get a snapshot on certain network performance parameters (latency, rtt, packet loss, jitter) as well as a list of blocked or unreachable “Office 365 URLs and IP address ranges”.


I assume that your general (hybrid) cloud configuration with all related topics (AD Connect, DNS, … user license assignment) is fine, also to keep this post short. Otherwise, having infrastructure issues, you’d probably have not only an issue with Teams.

Teams Client Logs on Windows

Where to find client logs for Teams? What’s the Teams client logs path?

Teams desktop logs

  1. (Windows) Open Teams client
  2. Press STRG+SHIFT+ALT+1 on the keyboard
  3. Find logs here: %userprofile%\Downloads

Teams media logs

These logs provide insights regarding media communication flows.

  1. (Windows) %appdata%\Microsoft\Teams\media-stack
  2. *media-stack*.etl

Teams debug logs

Debug logs shows flows regarding login, connection, call and conversations.

  1. (Windows) right click the Teams app icon in the tray bar
  2. notepad opens and shows the log data

Conclusion, opinion and summary

In case your infrastructure and connectivity is alright, the client logs may help to dig deeper into the issue analysis. Although, in my experience I rarely need these logs because often it comes down to an infrastructure and connectivity issue towards Microsoft Cloud services either for a single or multiple client endpoints.

Additional Ressources


Busy on busy in Microsoft Teams

I stumbled upon a new feature which is under development for Microsoft Teams. Belief it or not but on the official Microsoft 365 (M365) roadmap “Microsoft Teams: Busy on Busy” (short, abbr. BoB) appeared in the list. It’s planned for May 2019.

Microsoft Teams: Busy on Busy (Source:

What’s “Busy on Busy”?

Well, this feature gives a caller a busy ton or sound in case the callee is busy with another call/meeting. So, you as a caller then now “Ah, well the person I’m calling is busy, right now. I’ll try it later, send an IM or mail …”

Do you need this?

It depends. It’s a frequently and common feature in Germany. Most people are used to it. In US and other countries it is not so widely used as far as I’m aware of. There is a little different “telephony mindset”, e.g. “If I cannot get a call because I’m busy the caller can leave a voicemail… or it is forwarded to my delegates/assistant …” or “The caller can try another communication option…” That’s why it depends if you need it or not. In general to have it is a good idea so you can decide if you enable it for all or a few users (depending on how the feature can be configured after it’s development).

Update May 16, 2019 – Enable BoB

You can now enable/disable BoB via Calling Policies within the Teams Admin Center\VoiP\Calling Policies or via PowerShell. For details, please see the linkt below “Microsoft Teams Calling Policies (PowerShell Cmdlet Reference)”.

Either within the global or an user policy.

Conclusion, opinion and summary

I remember, in the past, that the announcement of Busy-on-Busy for Skype for Business Server was a big deal. Many customers in Germany were waiting for this nativ feature for SFB. It was released as part of a SFB Server 2015 cumulative update. The busy-on-busy implementation was not 100% as some customers expected it to be. Compared to their known and legacy busy-on-buy feature by their legacy PBX. However it was adopted partially. And third party app and tools for this previously SFB Server 2015 feature gap vanished. Finally, I’m sure Microsoft Teams Busy on Busy will be adopted by some Team users instead of or even supplementary to voicemail, call forwarding or else depending on the configuration and assignment options for BoB.

Please note that this post and its contents might be subject to change. Especially, because it was added and last modified on April 1, 2019.

Additional Resources

What’s new in managing apps and integration in Microsoft Teams? (03-19)

In this post I’d like to note a recent announcement which improves the admin experience to manage apps and integrations in Microsoft Teams. To keep it short and simple, the following configuration options were announced by Microsoft:

  • Teams App Setup Policies – Who get’s which apps displayed?
  • Teams App Permission Policies – Define who can install which apps
  • Bulk Assignment via PowerShell – Assign the above policies by using a PowerShell (Script and CSV)

Conclusion, opinion and summary

To me, these two options for managing apps and integration will help to enable what Teams users need or don’t need. Plus it’s another step in the right direction towards a more comprehensive and granular management of Microsoft Teams as a hub for modern teamwork.

Additional Resources

Speaking at abtis Modern Teamwork Roadshow 2019

Soon, I’ll speak at the abtis Modern Teamwork Roadshow in Pforzheim (19/03/2019), Heidenheim (20/03/2019) and Freiburg i.B. (19/03/2019). The event and speakers cover different topics all around modern teamwork.

I’ll talk about Microsoft Teams and (PSTN) telephony. My session “Telefonie mit Microsoft Teams – Das sollten Sie wissen” is about frequently asked questions and things you should know regarding Teams and (PSTN) telephony. I’ll give answers to frequently asked questions and provide first ideas on how you could start with adding PSTN telephony to Teams to enable your fellow employees for modern teamwork throughout your business.

Additional Ressources

Microsoft Teams Devices and IP Phones

In this post I’d like to highlight and share resources about Teams devices and IP Phones. Does one of the following questions or even both apply to you?

  • Are you planning to transition your conference rooms to collaborative spaces and rooms? 
  • Are you planning to migrate telephony completely or partially to Microsoft Teams?

In both cases, to begin planning, I recommend to browser to and do not miss to check the below links. Microsoft as well as third-party vendors offer a wide range of devices to cover your needs by leveraging the Microsoft Teams platform. The best place to go and check for (certified) devices is the “Microsoft Teams Devices Marketplace”. There you’ll find … 

  • Headsets 
  • Speaker phones 
  • Desk phones 
  • Room systems 
  • Conference phones and 
  • Cameras 

Conclusion, opinion and summary

I recommend to take a look on the linked pages to get an overview on available certified devices.  

If you are about to start your journey towards Microsoft Teams it might help you assess your users/rooms /spaces requirements and to create suited personas (e.g. 6-Seat-Room –> Surface Hub, Office Information Worker –> Notebook + wired Headset, Assistant –> Notebook + Mobile + Teams IP Phone xyz).

Additional Ressources 

My Microsoft Teams Federation Notes

In this post I’ll describe how federation towards federated partners can work. I’ll not describe meetings and guest access for Teams which are great capabilities for modern teamwork across companies but not subject for this post. Teams provides options for federation with external organisations like suppliers, clients and partners.

Basically there are eight federation scenarios I’d like to describe below. The federation scenarios are based on Microsoft Teams as well as Skype for Business.

Skype for Business Federation

Let’s take a look on federation with Skype for Business. In Microsoft Skype for Business Server / Online (hereinafter: SFBx) there are two major federation types:

  • open federation: Users can communicate openly to everyone except users behind blocked domains.
  • closed federation: Users can communicate only to federated domains configured by the SFBx admin.

Teams Federation

Now, with Microsoft Teams federation is similair to SFBx federation but not 1:1 alike.

You can decide to federate with everyone, openly, except towards blocked domains (blacklist).

Or you can decide to federate only with allowed domains (whitelist).

Another thing to keep in mind is what’s your current Teams upgrade mode or status?

In Microsoft Docs there are five modes listed but not all are available by now.

  • Islands: All workloads on SFBx + Teams
  • Skype for Business-only: SFB for all workloads. Single client.
  • Teams-only: Teams for all workloads. Single client.
  • (not in Admin Center, Feb. 2019, TAP customers-only) Skype for Business with Teams (collaboration-only): SFB for chat, calling and meetings. Teams for collaboration.
  • (not in Admin Center, Feb. 2019, TAP customers-only) Skype for Business with Teams (collaboration and meetings-only): SFB for chat and calling, Teams for meetings and collaboration.

Scenario 1a+1b

You are on Microsoft Teams.

You can federate with other organisations having a) SFBx or b) Microsoft Teams, too.

Scenario 2a+2b

You are still on SFBx.

You can federate with other organisations having a) SFBx or b) Microsoft Teams, too.

Scenario 3a+3b

You are on SFBx as well as Microsoft Teams but your Teams Upgrade mode is “Islands”.

Your users are having two clients installed and only the SFBx works for federation communication.

You can federate only via SFBx with other organisations having a) SFBx or b) Microsoft Teams, too.

Scenario 3c+3d

You are on SFBx as well as Microsoft Teams but your Teams Upgrade mode is “Islands”.

Your users are having two clients installed and only the SFBx works for federation communication.

Your users cannot have an internal cross-client chat or else c) from SFB to Teams or d) from Teams to SFB.

Drawn via Microsoft Whiteboard App by Erik

Conclusion and summary

Teams federation provides the ability to federate with external organisations similair to what we’ve used to from SfBx. Nevertheless we need to pay attention to the user experience and federation experience which migh be slightly different during a coexistence of SFBx and Teams.

Further Ressources

Microsoft Teams Backup and Restore?

In this blogpost I’d like to describe on a high level what you can do regarding backup (and restore) Microsoft Teams chats and files (January 2019, this might be subject to change).
Do you need backups of Teams (data) stored within a global hyperscaler cloud infrastructure? Shouldn’t it be resilient and highly available based on the SLAs …? Well, there is no one-size-fits-all-answer. It depends on your requirements and needs. However, in my opinion, it’s not a bad idea to have a (working) backup in place in case data was deleted or became inaccessible, anyhow.

Where are my Teams conversations and files located?

We need to differentiate between actual Teams and Chat (see screenshot below, I’ll call it hereinafter “Personal Chat”). “Personal Chat” are direct one on one (1:1) as well as one to many (1:m) chats or conversations. The difference is what’s being used under the hood. Let’s dig in a bit deeper.

“Personal Chat”

Your chats are stored on your Exchange Online (EXO) Mailbox in an hidden folder (not on Exchange Server). The hidden folder “TeamChat” on your EXO mailbox is underneath of the “Conversation history”-folder. By default the chat copies are available for 14 days in the Deleted Items folder in Outlook.

Teams Chat

Teams are Office 365-based, i.e. Office 365 Groups with SharePoint Online and Exchange Online are utilized.

For Teams Chats almost the same as for “Personal Chat” applies: Due to the fact that we therefore have Office 365 Groups, its mailbox hidden folder on EXO (not Exchange Server) are the storing the chats.

“Personal Chat” Data

If you exchange files it will be stored in your OneDrive For Business\Microsoft Teams Chat Files.

Teams Data

If you share files in a Teams Channel it will be stored in its associated SharePoint Online Document Library Folder of the Teams channel.

By default deleted files on SharePoint online are available for 93 day to be restored if no other configuration was set or quotas are applied and excceeded.

What backup and restore limitations do I have (after a “soft-delete”period)? (January 2019)

If a Team was deleted and you notice this or get requested to restore a Team after the “soft-delete” period of 30 days (default) the content is permanently deleted and cannot be restored, see link at the bottom “Restore a deleted Office 365 Group”.

You cannot restore a Team 1:1 after its 30 days “soft-delete” period.

Chat even if you have the data cannot be restored or at least I did not find a way to accomplish this easily. I was thinking about importing chats based on scripts in a newly re-created Team and it’s channels but it seemed to be a way to cumbersome to quickly test it with some lines of ps script code.

What backup options are there?

Option 1: Archive Teams

Archiving is not backup. However if you archived instead of deleting it, you can restore it easily via the Teams Admin Center or via the Teams Client, see link at the bottom “Archive or restore a team”.

Option 2:  Office 365 Security and compliance center (eDiscovery cases, retention policies)

You can maintain copies of chats  by using eDiscovery cases/litigation/inplace hold/retention policies. You can set this up to store the copies hidden in the mailbox. Either for a certain periode of time or indefinitely.

You can configure retention policies to retain files longer and to be stored in the preservation hold library. However, you might search and access the retained chat/files but not within Teams as it were before the “permanent” delete.

Option 3: Thirdparty solution/s?

Most of the thirdparty backup solutions are offering options to backup Exchange Online, SharePoint Online and OneDrive For Business data. Some providers also mention capabilities to restore Office 365 groups but it needs clarification if they have working restore procedures to recover a deleted Teams after the default “soft-delete” period of 30 days. If you consider to leverage a thirdparty solution you should take this into account for your Microsoft Teams evaluation and proof of concept phase.

Conclusion and summary

If a Team get’s (soft) deleted you can restore it within 30 days by default.

Beyond 30 days, there no default or extend restore procedure to get the deleted Team to 100 % recovered as it was before.

Thirdparty solutions might provide an exception to a certain extent and add value based to extensible restore capabilities which should be thoroughly examined during an evaluation or proof of concept phase.

In case you have certain security and compliance requirements you should evalute features provided by the Office 365 security and compliance center, Teams Lifecycle Management options based on the Graph API ( as well as thirdparty backup solutions.

Further Resources