Quick question! Are You Really Using Teams in Teams? This is a question that I was inspired to ask when delivering training at the Albert Hall.
So then, What did a full day of Microsoft 365 training at the Royal Albert Hall teach me about Teams, OneDrive and Outlook?
At the Royal Albert Hall, people know a thing or two about working together.
Behind every performance is an extraordinary network of people, departments and moving parts, all needing to stay in tune. So, during a recent full day of Microsoft 365 training there, one small irony stood out.
Many people were using Teams, but they were not actually using teams.
That sounds like a riddle. It is also a problem I suspect exists in organisations everywhere.
Teams Had Quietly Become Another Chat App
Throughout the day, I trained several different groups in Microsoft Teams, OneDrive and Outlook. The people changed. Their roles and experience varied. Yet the same pattern kept appearing.
They were familiar with Teams. They used it for one-to-one chats, group chats and meeting chats. Notifications arrived. Messages were answered. Files were passed around.
But teams and channels? For many, that was unfamiliar territory.
This was not because people were unwilling to use them. In many cases, they simply did not have permission to create a team. Some did not belong to the teams they needed, while others were unsure how to request one.
So they did what any sensible person would do. They found a way to get the job done.
They created another group chat.
The Group Chat That Grew into a Filing Cabinet

A group chat is ideal for a quick discussion. It becomes less ideal when it quietly turns into the home of an ongoing project.
The conversation grows. More people join. Decisions disappear somewhere above a collection of GIFs, replies and meeting messages. Files are shared, reshared and downloaded. Then, weeks later, someone asks the question that brings everything to a halt:
"Where did we put that document?"
A team and its channels give continuing work a proper home. Channels can be organised around a department, project or topic. Conversations remain visible to the relevant team, files have a shared location, and useful apps, lists, websites and resources can be added as tabs.
Most importantly, the knowledge belongs to the team rather than being buried in a chat that only certain people can see.
Microsoft's combined chat and channels experience may blur the distinction further. Chats and channels can appear together in the same view, which is convenient, but it also makes it possible to spend every working day in Microsoft Teams without ever discovering what a team and its channels are designed to do.
One Small File Can Reveal a Much Bigger Difference
Here is the part that often surprises people.
When you upload a file to a Teams chat, it is stored in the sender's OneDrive and shared with the people in that conversation.
When you upload a file to a channel, it is stored in the team's SharePoint document library.
On screen, both actions can feel almost identical. Behind the scenes, they create two very different working arrangements.
One is a file owned by an individual and shared into a conversation. The other sits in a workspace designed for the team.
That difference matters when a project grows, when new colleagues join, when responsibilities change, or when someone leaves the organisation.
Suddenly, the question "chat or channel?" is not merely about where to type a message. It is about who owns the information and whether people will still be able to find it months from now.
Then Came the Encouraging Part
Training should do more than reveal what people do not know. At its best, it gives people enough understanding to change what happens next.
By the end of the day, some of the participants had gained permission to create their own team. Others were arranging for one to be created for them.
That was an important moment.
The obstacle had not simply been a lack of knowledge. People also needed the right access and a clear process. Once those two things began to come together, Teams could become more than a place to send messages.
This is why successful Microsoft 365 adoption needs both sides:
- People who understand how the tools can improve their work
- An organisation that gives them a secure, well-governed way to use those tools
Without training, permissions alone can create chaos. Without appropriate permissions, training can show people a better way of working that they are unable to use.
The OneDrive Moment That Made Ears Prick Up

The room became particularly attentive when we moved on to sharing links from OneDrive.
Sharing a link is often safer and far more efficient than emailing another copy of a file. It can also be used to collaborate with people outside the organisation.
But a link is not automatically safe simply because it came from Microsoft 365.
Before selecting Send, it is worth pausing long enough to ask:
- Who will this link work for?
- Do they need to sign in?
- Can they edit the file or only view it?
- Could the link be forwarded to someone else?
- Is an expiry date needed and available?
- Who will review or remove access later?
"Anyone with the link" can be useful, but it deserves particular care because possession of the link can be enough to open the content. Administrators can set policies requiring these links to expire, although the options people see will depend on the organisation's Microsoft 365 settings.
The lesson is not to avoid external sharing. It is to share deliberately.
And Then There Is the Outlook Attachment Habit
This brought us neatly to Outlook.
We all know the ritual. Attach a document. Send it to five people. Receive three edited copies in return. Save the one you think is newest. Rename it.
Soon the folder contains:
- Annual Report Final.docx
- Annual Report Final Updated.docx
- Annual Report Final Updated 2.docx
- Annual Report Final Updated 2 USE THIS ONE.docx
At that point, nobody is collaborating. They are taking part in a very polite version of file roulette.
Sharing a OneDrive or SharePoint link through Outlook can keep everyone working on the same document. The latest changes remain in one place, permissions can be controlled, and the inbox does not become a breeding ground for competing versions.
Traditional attachments still have a purpose. Sometimes a separate, fixed snapshot is exactly what is needed. But if the intention is to work together, a link will often make far more sense.
The Real Question Is Not Whether You Have Microsoft 365
Microsoft 365 can give an organisation Teams, OneDrive, SharePoint and Outlook. It cannot guarantee that people understand how the pieces fit together.
That is where the real value of training often appears. It is not always the dramatic new feature that changes the way people work. Sometimes it is one simple realisation:
A chat is not a channel. A copied file is not a shared file. Access is not the same as adoption.
So, how is your organisation really using its Microsoft 365 cloud?
- Are projects being managed through structured teams and channels, or disappearing into group chats?
- Do people know where their chat and channel files are stored?
- Can staff create or request the workspaces they need?
- Are external sharing links checked for the right audience, permissions and expiry?
- Are colleagues collaborating on one live file, or emailing copies back and forth?
You may not need another app, another licence or another grand digital transformation project.
You may simply need to help people discover what the tools already on their screens were designed to do.