Shared channels are here, and they’re awesome!
M365 - Microsoft Teams Center
ENow Software's Microsoft Teams blog built by Microsoft MVPs for IT/Sys Admins.
Over 20 years in IT Loryan has had the opportunity to work with many leading edge technologies - allowing him to be a part of major transformations in the industry. Starting out in web design prior to the dot com era, Loryan then took on more technical roles and has been involved in some of the first Australian deployments of metropolitan networks, voice over IP and video streaming over the Internet. His technical experiences were followed by 15 solid years in various senior consulting positions advising both internal and external senior management / stakeholders on strategic technology adoption and selection along with delivery of solutions across a range of business sectors, and managing technical resources for delivery. Many of his roles have involved coaching and mentoring team members along with establishing incentive schemes to drive results and growth. One of his strengths is the ability to thoroughly understand each client’s challenges and deliver solution in line with their unique business requirements. Loryan is passionate about the cloud and the opportunities it brings. Having spent most of his career delivering on-premise business productivity technology, he founded Paradyne to deliver cost-effective solutions and to advance how people work by means of the cloud. His deep technical expertise is backed by practical business experience, ensuring that customers get the best of both worlds – world-class technology that delivers real business benefits.
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.
Yes, you read that right. The title is not a question or suggestion, but a statement of fact: Your approach to Microsoft Teams governance is wrong.
Right now, you must be thinking I have some serious chutzpah to make such a statement, and you’d be correct – but that chutzpah is built on real-world experience working with organizations of all sizes and industries.