topicsidentity & access3 numbers3 guides

guest access

Any colleague can let an outsider in, and nothing about the invitation ends. Why the guest list only grows, and why nobody can say who is on it.

in one lineGuest access is when people outside your company hold a standing place in your collaboration tools, as guest accounts or as grants on your files, channels and groups.

the numbers

all the numbers →

1what it is

Clients, freelancers, suppliers and partner agencies need to work in your tools, so your staff invite them in. Each product keeps those outsiders in a different place:

  • Microsoft 365 creates a guest account in your Entra directory. Microsoft's Teams documentation says inviting a guest to a team creates that account, and that anyone with a business or consumer address, Gmail included, can be one.
  • Slack gives a guest a seat limited to chosen channels, on paid plans only.
  • Google Workspace keeps no guest object. The outsider uses their own Google account, and their access sits on each file, shared drive or group someone shared with them.

This explainer covers those standing places. Links that anyone can open are covered in the external file sharing explainer, admin rights held by an IT partner in the delegated admin explainer, and the full product settings in the guest list guide.

2why it accumulates

Anyone can invite. Microsoft's external collaboration settings page (updated 24 April 2026) says that by default all users in your organisation, guests included, can invite external users. Every team owner is a door, and the decision never reaches IT.

The end of a project removes nothing. Microsoft's Teams page says that a guest leaving a team does not remove the guest account from your directory, and that an Entra admin has to do it. In all three products, unless someone sets an end date, a share or a seat stays until someone takes it away.

The record of who invited them fades. Microsoft's data retention page puts Entra audit logs at seven days on Entra ID Free and 30 days on P1 or P2. After that the invitation event is gone unless the logs were exported. Microsoft's sponsors page says the inviter becomes the guest's sponsor automatically, which helps, but guests created by sharing a file in SharePoint get no sponsor, a gap Microsoft lists as a known issue. When the sponsor leaves your company, the field keeps pointing at them until an admin changes it.

Old settings stay old. Google's groups policy page (updated 10 November 2026) says changing the external members setting does not affect anyone already in a group. Tightening a default today leaves the outsiders added under the old one where they are.

3what it costs you

A guest invited to one channel can see more than that channel. Microsoft's default user permissions page (updated 18 June 2026) says a guest under the default setting can read other users' names, email addresses and photos, read manager and direct report information, and read the membership of groups they have not joined. The same page says "Guests can be added to administrator roles."

Each stale guest is also a login you do not control. The password, the device and the sign-in protection belong to someone else, with an employer, or no employer at all, that has no reason to tell you when that person moves on. If their account is taken over, the attacker inherits whatever your staff shared with them over the years.

Next to guest accounts sits a door that needs no guest account at all. Microsoft's Teams external access page says chat with other Microsoft 365 organisations is on by default, with "Allow all external domains" as the default setting. People reached this way get no access to your files, but they can message your staff. Microsoft Threat Intelligence reported on 2 August 2023 that Midnight Blizzard used compromised small-business tenants to send Teams chats posing as support and talk people into entering a sign-in code in their authenticator app, at fewer than 40 organisations according to Microsoft's investigation at the time.

what it looks like when it goes wrong

Three ways this tends to go, each one taken from a real case.

your company
the gap nobody seesGuests are invited for one project and stay after it ends, because the invitation has no end date and the person who sent it moves on.access that outlives the job
  1. howThe person logs back in from home, weeks after leaving.
    what leavescustomer lists and reportswho ends up with itthe former employee and whoever they work for next
    it happenedCash App / Block, 2022
  2. howThe forgotten account's password turns up in a breach dump.
    what leavesa working way into the networkwho ends up with ita ransomware crew
    it happenedColonial Pipeline, 2021
  3. howA key or token set up for old work keeps working after everyone forgets it.
    what leavesinternal systems and documentswho ends up with itwhoever tries the key first
    it happenedCloudflare, 2023

4what works

The work is an inventory, an owner and an end date, in that order.

  1. Count the guests in each tool. In Entra, filter users by type Guest and add the "Last interactive sign-in time" column; Microsoft's inactive accounts page says this needs at least the Reports Reader role. In Slack, export guests with their inviter, which Slack's help says appears on each guest's profile. In Google, list external members of groups and the files shared outside the company.
  2. Give every guest an owner. Fill the sponsor field in Entra and replace sponsors who have left. A guest nobody will own is a guest to remove.
  3. Remove what nobody can explain. Microsoft's inactive accounts page suggests a window of 90 to 180 days without sign-in as a reasonable starting point for review.
  4. Put end dates where the product has them. Slack's guest settings can deactivate a guest after a period or on a date, with a reminder five days before. Google Drive lets you set an expiry on someone's access to a file, up to one year ahead, on work and school accounts.
  5. Narrow who can invite. In Entra's external collaboration settings, pick an option stricter than the default so ordinary guests can no longer invite other guests, and decide which external domains your staff should be able to chat with in Teams.

The people behind those accounts, and the contract that ends without telling anyone, are covered in the contractor guide and the contractor access explainer. Old shares that outlived their guests are in the SharePoint graveyard guide.

When the export is in front of you, how many guests can someone in your company still name?

on the record

← all topics

your turn

what you can do about it

  1. this week

    Export every guest from Microsoft Entra and Slack with the person who invited them and their last sign-in.

    A guest whose inviter has left and who has not signed in for months is the first to remove. Give every guest you keep a named owner and an end date.

  2. go deeper

  3. if you're not sure where to start

    Run the offboarding checklist on one leaver. It covers every account and token to close when someone leaves.

    open the checklist →

the letter · every two weeks

one access gap in your inbox, with the fix.

Every issue takes one way access creeps in, shows a real incident where it went wrong, and ends with one thing to check that week. Written for the people who run the tools, without a security team behind them.

  • 1one mechanism, explained plainly
  • 2one real incident, taken apart
  • 3one step you can take on Monday

get the next issue

One email every two weeks. Your address stays here and is never passed to vendors. One click to unsubscribe. Privacy.