I was recently asked to set up a Microsoft Teams team for a large project that would bring in a number of external staff. Consultants, contractors and people from partner firms, all needing to work alongside our own people in the same channels and files.
Adding a guest to a team takes about ten seconds. Setting it up so guests only see what they should, sign in securely, and lose access when the project finishes takes more thought, and that’s what most guides skip. Get it wrong and you find out three years later, when an audit turns up a list of contractors who still have access to your project files.
Guests, shared channels or external chat?
Microsoft gives you three different ways to work with people outside your organisation in Teams, and it’s worth picking deliberately.
| Guest access | Shared channel (external participant) | External access (chat only) | |
|---|---|---|---|
| What they get | Membership of a whole team, its channels and files | One specific channel and its files | Chats and calls, no team or files |
| Account in your tenant | Yes, a guest account | No, they use their home account | No |
| Their side needs | Any email address | Their own Microsoft 365 tenant with matching settings | Their own Teams |
| Switching organisations in Teams | Yes | No | No |
Shared channels are the nicer experience. External people stay signed in to their own organisation, and the channel just appears in their Teams. The catch, according to Microsoft’s external collaboration planning guide, is that both organisations have to configure cross-tenant access settings for each other. That’s workable with one or two large partner companies. It doesn’t work for a sole-trader engineer using a Gmail address, or a small subcontractor whose IT person is also their estimator.
For a project with people from lots of different firms, guest access is usually the only option that works for everyone. You can still use shared channels alongside it for a big partner whose tenant you’ve connected to. Just know that guests can’t be added to shared channels, so the two don’t mix in the same channel.
The four settings that all have to agree
The most common guest problem is a guest who can see the team but gets an error opening the Files tab. That happens because Teams guest access depends on four separate settings in four different admin centres, and all of them have to allow it. Microsoft’s guide to collaborating with guests in a team walks through each one:
- Entra ID external collaboration settings. Who can invite guests, what guests can see in your directory, and which domains are allowed.
- Teams admin centre guest access. The on/off switch for guests in Teams, plus what guests can do in calls, meetings and chat.
- Microsoft 365 Groups guest settings. Whether groups, which every team is built on, can have guest members at all.
- SharePoint sharing settings, at both the organisation and the site level. If the team’s SharePoint site doesn’t allow sharing with existing guests, guests get into the team but can’t open a single file.
If a guest reports a problem, check the team’s SharePoint site sharing level first. It’s the one people forget, because it lives on the site rather than in Teams.
Tighten the tenant-wide settings first
Before you add anyone, review the Entra settings that apply to every guest in your tenant. You’ll find them in the Entra admin centre under External Identities, External collaboration settings.
What guests can see. The guest user access setting controls how much of your directory a guest can browse. The default lets guests see limited information about other users and groups. The most restrictive option limits them to their own account and group memberships. Restrictive is the better choice for a large external group, but test a guest’s experience in Teams before you roll it out, so you know what they will and won’t see.
Who can invite guests. If you restrict invitations to admins only, a team owner can still add a guest who already exists in your directory, but can’t invite someone new by email. For a project team, a good middle ground is to restrict invitations and then give the project’s team owners the Guest Inviter role in Entra. They can bring in new people when needed, and nobody else in the business can.
Which domains are allowed. You can allow invitations only to specific domains, or block specific domains. An allowlist is the tightest option, but on a project where new subcontractors appear every few weeks, it becomes a constant stream of change requests. A blocklist of personal email domains is often a more practical compromise, if your project doesn’t rely on people using them.
Require MFA for guests
A guest account is a door into your files, and its password is managed by someone else. Create a Conditional Access policy that targets Guest or external users and requires multifactor authentication for all cloud apps.
Guests from other Microsoft 365 organisations will already be doing MFA at home. To save them doing it twice, go to Cross-tenant access settings in Entra and, in the default inbound settings, turn on Trust multifactor authentication from Microsoft Entra tenants. Your policy then accepts MFA they’ve completed in their own tenant. Guests without a tenant, such as those on Gmail, sign in with a one-time passcode sent to their email and register MFA with your organisation.
Design the team with guests in mind
The design rule I’d put above all others: anything a guest shouldn’t see doesn’t belong in a channel they can open.
On a construction project, that’s usually commercial material: pricing, tenders, variations, disputes and internal performance discussions. Guests see every standard channel in the team, and every file in those channels. Teams will happily let someone drop a cost report into the General channel.
There are two ways to handle it:
- A private channel inside the project team, for internal people only. Private channels have their own SharePoint site and membership, and guests can only get in if a channel owner adds them.
- A separate internal team for the project’s commercial side. More to manage, but there’s no way for a guest to end up in it by accident, and it’s easier to explain to staff.
For anything genuinely sensitive, I prefer the separate team. A private channel works well technically. It’s just one wrong click away from a guest being added.
Keep at least two internal owners on the team. Guests can’t be owners, but if your only owner goes on leave, nobody can add or remove anyone.
Know who’s in the team
Guests pile up quietly. Someone leaves the subcontractor, their access stays. The consultant finishes their package, their access stays. Six months later, a third of your guest list belongs to people who no longer work on the project.
If you have Entra ID P2 or ID Governance, set up an access review on the team so owners are asked every month or quarter to confirm each guest still needs access. Microsoft covers this in its guest access overview for Teams.
Without those licences, run a review yourself. This lists every guest in the team, oldest sign-in first, so the stale accounts are at the top:
Connect-MgGraph -Scopes "GroupMember.Read.All", "User.Read.All", "AuditLog.Read.All"
$team = Get-MgGroup -Filter "displayName eq 'Project Riverside'"
Get-MgGroupMember -GroupId $team.Id -All |
ForEach-Object {
Get-MgUser -UserId $_.Id -Property DisplayName, Mail, UserType, CreatedDateTime, SignInActivity
} |
Where-Object UserType -eq "Guest" |
Select-Object DisplayName, Mail, CreatedDateTime,
@{ n = "LastSignIn"; e = { $_.SignInActivity.LastSignInDateTime } } |
Sort-Object LastSignInSign-in activity needs Entra ID P1. A blank last sign-in means the guest accepted an invitation and never came back, or never accepted at all. Both are worth a conversation with the team owner.
Ending the project properly
Most guest setups go wrong at the end. When the project finishes, someone archives the team and considers the job done. Two things are worth knowing.
First, archiving makes the team read-only, but it doesn’t remove anyone. Guests who are still members can keep reading every conversation and file. Remove the guests first, then archive.
Second, removing a guest from a team doesn’t delete their guest account. It stays in your directory, and depending on your settings, they may still have access to anything else that was shared with them directly. If a guest has no ongoing relationship with your organisation, delete the guest account in Entra as well.
Put a closeout step in the project plan: export what needs keeping, remove guests, delete guest accounts that have no other purpose, then archive. It takes half an hour at the end of a project, and it saves an uncomfortable conversation in an audit.

From my early days on the helpdesk through roles as a service desk manager, systems administrator, and network engineer, I’ve spent more than 25 years in the IT world. As I transition into cyber security, my goal is to make tech a little less confusing by sharing what I’ve learned and helping others wherever I can.

