Teams tries to connect to network drives during start up - and ends up starting really slow

Copper Contributor

I run Microsoft Teams on MacOS and noticed the following, to much frustration:


I have a NAS on my home office network, which is not always connected. When Teams starts up, and the NAS is not connected (also when I'm travelling) it tries (without notification) to connect to this NAS, resulting in a startup time of up to 5 minutes, and 3-6 messages popping up that it cannot connect to the NAS.

It is not only frustrating, but also unnecessary - why would Teams need anything from a network storage location during startup?


Anyone who recognises this and knows how to get rid of it? I run on MacOS, so no registry hack solutions please ;)

11 Replies

@adam deltinger not right now, but all it says is Unable to connect to delphinosvr, followed by an OK button. Screenshots won’t show more than that, and in fairness I think it’s a clear design/implementation flaw. Teams had no business on that network location, certainly not during startup and login.

It shouldn’t afaik! Have you somehow installed the Teams profile on the NAS?
You can check the logs and see what they say or post them:


@adam deltinger thanks for that tip. 


Here's what I did tonight: 


1. logout of Teams

2. shutdown NAS

3. restart Teams 


Before getting to the login stage the attached window had already popped up 5 times. The list with accounts to select from (I have 3 Teams accounts) showed up immediately after the 5th one.


4. Login


That was flawless as always.


6. Collect log files as you suggested


I found no reference to my NAS in any of the log files


7. Did a grep for the NAS on all files in ~/Library/Application Support/Microsoft/Teams


No reference foud at all


I'm completely puzzled - the startup time is 3-4 minutes due to this, whenever I am not on my home-network.






Have the same issue at startup, as well as at shutdown.  In fact, Teams locks up and becomes non-responsive trying shutdown if the network drive is not available.  Creepy behavior. 

I've been having the same issue for several months now. Makes me very concerned about privacy issues.
Same here. And have several colleagues cursing teams because of this behavior. Looks like the Microsoft guys either have always perfect network connection to their network drives, don't use home office at all or don't have any network drives in use. Otherwise they would have fixed that in a second.

Same problem, and same concern.  What is it looking for on that drive?

That is what fixed it for me:

- Uninstall Teams (On Mac I used AppCleaner for this to make sure it's really gone)
- Disable all drives on startup (don't connect any drive on startup)
- Install Teams again
- Enable "connect drives at startup" again
I have exactly the same problem. Is there a solution?