I thought it was just me or the version of Teams I was working with. But looking at the thread, seems like this has been an ongoing issue since last year and what makes it worse is that I don't see any response from Microsoft. I would think this has enough weight to bubble up to the top of their break/fix bug process. Very disappointing and beyond annoying.
Nadine Winslow
I thought it was just me or the version of Teams I was working with. But looking at the thread, seems like this has been an ongoing issue since last year and what makes it worse is that I don't see any response from Microsoft. I would think this has enough weight to bubble up to the top of their break/fix bug process. Very disappointing and beyond annoying.