Microsoft Teams is still recovering from a global outage of their major collaboration and communication tool. The outage was listed by Microsoft to have started on July 21, 2022 at 6:07 PM Pacific time and is currently listed as service restored. There were reports from around the globe of users that were unable to get into Microsoft Teams or to be able to communicate with others on the platform.
So, we’re back to look at what other mistakes Microsoft Teams administrators make when it comes to the platform. It’s as if I’ve never read Dale Carnegie’s “How to Win Friends and Influence People”…
Putting aside the clickbait-y title (which I created, so lay the blame at my feet), there are a number of mistakes I see Microsoft Teams administrators make on a regular basis.
Microsoft Teams is the darling of the Microsoft 365 suite, with pretty much every app in the ecosystem pushing for their share of user real estate.
2022, here we are. It's been a couple of years since I was invited to write one of these "look back" articles (maybe I was too harsh last time?) but with the rapid pace of innovation in Microsoft Teams, I think it's good to look back at how far we've come.
Wow. As I sit here and reflect on the afterglow of Comms vNext Reconnect, that's all I can think. With all the craziness of the past 18-20 months, I know many have been wondering if in-person events would ever come back and if they did, would they be any good? From my experience, there is only one word to answer both of those questions: yes.
An integral part of Microsoft Teams is the ability to attend meetings and live events. The appointments for these event types are usually planned directly via the personal calendar in a Microsoft Teams client. The calendar also enables quick and easy participation in meetings.
Over the past year, many organizations have adopted entirely new collaboration systems then...
Lately I have been approached by a fair number of customers (both small as well as large Organizations) complaining about not so obvious and very confusing behavior between Skype for Business and Microsoft Teams. Those Organizations are already using Skype for Business (mainly On-Premises for their Enterprise Voice solution) and have started trials or pilots for Microsoft Teams.
There is no denying that as IT Pros we are writing more ‘code’ than ever before. I like to think of this an an evolution – If you cast your mind back 13 years to 2007 when PowerShell first made an appearance, many of us were just coming to terms with using single cmdlets to perform tasks instead of clicking GUI buttons. Over time, cmdlets became one-liners which in turn led to PowerShell scripts all the while helping us automate repetitive tasks in a predictable manner with orchestrated runbooks being a lot more commonplace today