Prepare your governance guides, guidelines and policies!
New update from Microsoft about sharing file in chat with external users
For years, I’ve said the same thing in workshops and leadership sessions:
People don’t break governance on purpose, they do it because the tools get in the way of getting work done.
External collaboration in Microsoft Teams has been a perfect example of that.
Sharing files with people outside your organization has often meant extra steps, unclear permissions, links pasted into chats, or, worst case, falling back to email “just to be safe”.
With Microsoft 365 Roadmap ID 492625, Microsoft is removing much of that friction. Still, with less friction also comes greater responsibility.
Let’s talk about what’s changing and what organizations must do to keep control without slowing people down.
What’s actually changing?
We have already been able to share files with guest users in a Teams group that has been set up for external users, or if we have added external users with user IDs in our own tenants. However, there have been tools that you couldn’t share with external users (guests), such as Loop components (e.g the entire workspace in Loop). You can share individual Copilot Pages, entire Loop workspaces, or individual Loop pages and Loop components with external users (guests) if your organization allows it. You can’t share the entire My workspace in Loop.
Microsoft Teams will allow users to share files and Loop components directly in chats with external users, including:
- 1:1 chats
- Group chats
- Meeting chats
When a user attaches a file or shares a Loop component, access is automatically provisioned to everyone in the chat by default. No manual sharing. No extra steps. No broken flow.
This applies across Teams for Windows, Mac, and Web, and is rolling out globally starting November 2026.
From a user perspective, this finally feels right.
From a governance perspective, this is a big shift.
Why this is an adoption win (and a governance wake‑up call)
Let’s be honest:
People already collaborate externally and they just haven’t always done it inside Teams.
They’ve:
- Sent files by email instead
- Used personal cloud storage
- Copied content into chats
- Created parallel workspaces “on the side”
This update removes the excuse.
Now users can collaborate with external partners in context, using the same tools they already know:
- Files live in OneDrive or SharePoint
- Loop components enable real-time co‑creation
- Everything happens where the conversation happens.
That’s great for productivity.
This also means:
External collaboration is no longer a special case it may be the default.
Loop components + external users = shared ownership in practice
One of the most important parts of this update is Loop support in external chats.
Loop components (task lists, tables, shared notes) now:
- Render directly inside external chats
- Are editable by internal and external participants
- Are stored as
.loopfiles in the creator’s OneDrive. [learn.microsoft.com]
This changes the dynamic of collaboration.
We’re no longer “sending information out”.
We’re co‑creating content across organizational boundaries.
That’s powerful, if organizations are clear on:
- Who owns the content
- Where it lives
- What happens when collaboration ends
Automatic sharing is not “loss of control” if governance is intentional
A lot of leaders hear automatic provisioning and immediately think:
“Have we just lost control?”
Not necessarily.
Microsoft has been very clear:
- All sharing still respects SharePoint and OneDrive policies
- Sensitivity labels still apply
- External users access content as Entra B2B guests
- Admins can disable automatic provisioning and require manual sharing instead.
In other words:
Governance didn’t disappear — it moved upstream.
If your policies, labels, and access rules are clear, this feature works with governance, not against it.
If they’re not… this feature will expose the gaps very quickly.
An important shift: guests can now share their files too
This update isn’t just about what your users can share.
External guests can now:
- Upload files from their own home tenant
- Share content from their own OneDrive or SharePoint.
That’s a big deal.
It reflects how modern work actually happens; partnerships, vendors, cross‑org teams, and it reinforces the need for:
- Clear expectations
- Clear ownership
- Clear exit strategies when collaboration ends
What I recommend organizations do now
No technical action is required to enable the feature.
Organizationally, this is the moment to act.
1. Revisit your external collaboration principles
Not just settings; principles.
- What is okay to share in chat?
- When should content move to a shared workspace?
- When does a Loop component become “real documentation”?
2. Align Teams, SharePoint, and Entra B2B governance
This feature crosses service boundaries. Your governance needs to do the same.
If Teams allows something that SharePoint later blocks, users will feel it immediately.
3. Update guidance and not just policies
A short, practical “How we collaborate with external partners” guide will do more than a 20‑page policy document.
Explain the why, not just the rules.
4. Treat this as an adoption opportunity
This is a perfect moment to talk about:
- Working in the open
- Shared ownership
- From chat → collaboration → structured knowledge
Let the tools make our workdays better
This update doesn’t remove the need for governance.
It removes the friction that made people work around it.
If we want responsible, secure, and effective collaboration, we have to stop relying on barriers and start relying on clarity, competence, and trust.
Microsoft has done its part by making the tools better.
Now it’s our job to make the way we use them better too.
Check out these related blogs:
Microsoft Learn Loop Component overview:
Overview of Loop components in the Microsoft 365 ecosystem | Microsoft Learn
Overview of Loop components and Loop workspaces permissions | Microsoft Learn
Microsoft Learn Purview management for SharePoint embedded containers: Purview management for SharePoint Embedded containers | Microsoft Learn
By Merill – Microsoft 365 Message Center Archive: MC1181772 – Microsoft Teams: File attachment control now enabled by default in external 1:1 and group chats | Microsoft 365 Message Center Archive
By Joao Ferreira: Microsoft Teams: File attachment control now enabled by default in external 1:1 and group chats – M365 Admin
By the Purview expert: Message MC1181772 • Purview.expert
Roadmap ID: 492625
Rollout November 2026
Collaborating with users outside your organization has become more streamlined. You can now share files and Loop components with external users in 1:1, group, and meeting chats. When sending a file or Loop component, it will be automatically provisioned to users in the chat, or you can change its permissions.
👀👉Read more and follow the update here.