Blog posts

Last updated 10/10/2022

When Microsoft announced at MS Ignite in November 2021 that Microsoft Teams Shared Channels would be made generally available in 2022, I realised it was a good time for us to shine the light on Atlas Extranet. 

In this fast-paced world, Atlas Extranet is a feature ClearPeople developed and launched in Q1 of 2021. It’s a bit like Cinderella, working reliably in the background, waiting for the grand ball. 

In this blog:

• What is Microsoft Teams Shared Channels? And why is it relevant to Atlas Extranet?
• How MS Teams Shared Channels transforms cross-organisational collaboration
• Availability of Microsoft Teams Shared Channels
• How to set up Microsoft Teams Shared Channels
• How to set up Atlas Extranet
• How Atlas Extranet differs from Microsoft Teams Shared Channels
• Can Microsoft Teams Shared Channels and Atlas Extranet work together?
• Microsoft Teams Shared Channels and Atlas Extranet pricing
• Microsoft Teams Shared Channels resources

The current rate of Microsoft Teams adoption is monumental. This trend has been excelling for the last few years. Statistics show staggering rises, for example between 2019 and Q2 2021 the number of Microsoft Teams users jumped from 20 million to 145 million.

ClearPeople is the first Microsoft partner to globally achieve this new Microsoft Advanced Specialization. This is an incredible achievement that we are all proud of.

The aim of an employee experience platform is to help employees bring about balance to their working lives. The modern working life is becoming increasingly digitalised. This has many benefits including more flexibility and convenience within the working day.

Everyday we spend a number of hours diving in Microsoft Teams. There are a lot of actions that we can perform from there; opening documents, attending meetings, chat with different members of the team, and much more.

This may be the shortest blog ever written - but then again, that might be fitting for a blog dedicated to the only keyboard shortcut you will ever need to know in Teams. I just wish I had spotted it sooner myself.