Microsoft 365 governance

Teams guest access: a review process owners actually answer

Guests are easy to invite and rarely removed. How to set Teams guest access, run a short review that team owners answer, find inactive guests with Microsoft Entra ID, check which licences each step needs and keep the records an auditor will ask for.

9 min read Neptune Group

Navy illustration: a guest access review card showing 37 of 41 owners answered, with three example guests marked keep or awaiting owner and a former contractor marked remove, flagged in coral, example data.

Teams guest access lets people from outside your organisation join a team: each guest gets an account in your Microsoft Entra directory and can work in the team's channels and files. That access rarely ends on its own. A short review, answered by team owners on a schedule you set and with an agreed default, keeps it under control.

Guest access is easy to grant and awkward to end. Inviting a supplier takes a minute. Removing them takes a decision that nobody has been asked to make, so the project ends, the team stays and the guest stays with it. Our approach to guest access reviews starts from that gap: give one person the job of saying keep or remove, and make it quick to do.

What is the difference between guest access and external access?

They are two separate settings. External access lets your users find, call and chat with people in other organisations that have a Microsoft identity. It is on by default, and it gives those people no access to your teams or files.

Guest access adds an outside person to a team. They get a Microsoft Entra B2B guest account in your directory, and with it access to the team's channels and files. External access is about conversations. Guest access creates accounts, and every guest account needs a sponsor, an end date and an owner who decides to keep or remove it.

Why do guests keep their access after the work ends?

Because nobody is asked to remove them, and several Microsoft controls leave the guests already in place. Four details catch admins out:

  • Removing a guest from a team, or the guest leaving it, does not delete their guest account. An admin deletes it in Microsoft Entra ID.
  • Switching guest access off for the organisation cuts guests off, but they stay visible in the team.
  • SharePoint guest expiration does not cover guests who already had access before the setting was turned on, and it does not delete the guest account either.
  • Changing a sensitivity label's setting to block guests does not remove the guests already in the teams that carry it.

The team owner usually knows whether a guest still works with you. IT sees the account, not the relationship. A review puts the question to the owner, with the facts IT already holds.

Which Teams guest access settings should you decide first?

Decide the organisation-wide settings once, then handle exceptions team by team. Guest access is switched on for the whole organisation in the Teams admin center and narrowed per team with sensitivity labels. It also depends on Microsoft Entra ID, Microsoft 365 groups and SharePoint, so review those settings together.

Teams guest access settings to decide first

The defaults below are starting choices, not Microsoft rules. Adjust them to your partners and your risk.

SettingWhereSensible default
Guest access for the organisation Teams admin center, Users, then Guest access On if you work with partners, so outside collaboration happens in teams you can see and review
What guests can do in calls and chats Teams admin center, guest access settings Keep chat and meetings, and decide on screen sharing and private calls deliberately
Who may add guests to a team Sensitivity label on the team, or the AllowToAddGuests group setting in Microsoft Entra ID Allowed on the label used for partner teams, blocked on labels for confidential teams
External sharing level SharePoint admin center, for the organisation, then site by site New and existing guests for the organisation, and a stricter level on sensitive sites
Guest expiration for sites and OneDrive SharePoint admin center, Policies, then Sharing On, after a number of days you set, knowing it does not cover guests already in or their team membership
Microsoft 365 group expiration Microsoft Entra ID, groups Optional, since active groups renew automatically and only idle teams reach their owner
Guest access reviews Microsoft Entra ID, access reviews One review per team with guests, answered by the team owner

A few details behind the table:

  • SharePoint and OneDrive have four external sharing levels: Anyone, New and existing guests, Existing guests, and Only people in your organization. A site can be stricter than the organisation, never looser, and the guest settings of a group or team affect its connected site.
  • Admins can stop owners adding guests to all groups or to specific ones. If adding guests is switched off for the organisation, the per-group setting is ignored, admins can still add guests, and a container label can override the group setting.
  • Sensitivity labels for teams and groups also need at least one active Microsoft Entra ID P1 licence in the tenant.

Guest access is one of nine areas in our Microsoft 365 governance best practices, next to ownership, sharing and labels.

How do you run a Teams guest access review that owners actually answer?

Keep it short, send it to the person who knows the guest, and agree in advance what happens if nobody answers. Five principles make the difference:

  • One team, guests only. Ask the owner about the guests in their team, not about every member. A list of four names gets answered. A list of four hundred does not.
  • Facts next to each name. Show the last sign-in date and who invited the guest. An owner who sees months without a sign-in decides in seconds.
  • A default agreed beforehand. Decide with security and the business what happens when an owner does not answer: access removed after a reminder, or the team escalated to IT. Either can work. Leaving it undecided cannot.
  • A reason with each decision. "Keep, audit firm, engagement still running" tells an auditor more than a ticked box.
  • An owner who is still there. A team whose owner has left needs a new owner before its review means anything.

Guest access review checklist

  1. List every team and site with guests, with each guest's last sign-in date.
  2. Sort out the obvious cases first: invitations never accepted and guests who never signed in.
  3. Check that each team has an owner who is still with you, and a second one where the team holds business data.
  4. Agree the scope and the cycle: which teams go first, and how often each type of team is reviewed.
  5. Send each owner one request that lists only their guests, with a deadline.
  6. Send one reminder, then apply the agreed default.
  7. Remove the access the owner rejects, and decide whether the guest account itself should go.
  8. Record each decision with who made it, when and why.
  9. Report completion to IT and security, and follow up the teams that never answer.
  10. If the same owners never answer, change the request, not the number of reminders.

Guest reviews belong with the other access checks we recommend for Microsoft Copilot (formerly Microsoft 365 Copilot) in our Copilot governance best practices. For links shared with outsiders rather than team membership, SharePoint has its own process. A SharePoint admin starts a site access review from a data access governance report, including the report on links shared with specific people outside the organisation. The site owner fixes access on a review page and marks the review complete. Site access reviews cover SharePoint sites, not OneDrive. They are part of SharePoint Advanced Management, available once at least one user has a Microsoft Copilot licence, and our article on SharePoint Advanced Management walks through them.

What can you automate in guest access?

Automate detection, reminders and expiry, and keep the keep-or-remove decision with people. Microsoft gives you several building blocks:

  • Find inactive guests. The last sign-in date in Microsoft Entra ID shows which accounts, guests included, have not been used for months. The signInActivity property in Microsoft Graph holds the last interactive, non-interactive and successful sign-ins. The last successful sign-in needs Microsoft Entra ID P1 or P2, and the data can lag by up to 24 hours. This works without ID Governance.
  • Review inactive guests. Microsoft Entra ID Governance adds an inactive guests report, with a 90-day default you can change. A guest who never signed in counts from the day the account was created. A review scoped to inactive users, set to remove denied guests, can then block the guests nobody keeps for 30 days before deleting them, and a deleted account can be restored within 30 days.
  • Let site access expire. SharePoint guest expiration ends guest access to sites and OneDrive after the number of days you set. Owners can extend or remove access, and a banner appears before access expires. Because existing guests are not covered, run one review of the guests already in when you switch it on. It applies to site and link access only: a guest can keep access to a team through its group membership.
  • Expire idle teams. A Microsoft 365 group expiration policy renews active groups automatically and asks owners to renew the others before they are deleted. It needs Microsoft Entra ID P1, and it acts on the whole team, not on individual guests.
  • Combine requests. In SharePoint Advanced Management, site lifecycle management can ask owners to confirm their sites periodically. Run the guest review on the same cycle, so owners deal with both together.

What stays human: whether a guest still works with you, whether an exception is justified, and what the default should be.

Which licences do guest access reviews need?

Basic access reviews come with Microsoft Entra ID P2, and also with Microsoft Entra ID Governance and the Microsoft Entra Suite. Reviews focused on inactive users and machine-learning recommendations need ID Governance or the Entra Suite. Microsoft says it will not add new identity governance features to P2.

Guests are billed differently. Reviewing guests with the advanced ID Governance features is billed per active guest each month through a linked Azure subscription. Basic P2 reviews of guests are not.

What evidence will an auditor ask for?

Proof that guest access is reviewed regularly, by someone able to judge it, and that decisions are carried out. Prepare:

  • A dated list of guests per team or site, with the owner and each guest's last sign-in
  • The review itself: who was asked, when, and who answered
  • Each decision, with its reason
  • Proof that rejected access was removed
  • The exceptions, and who approved them

Microsoft keeps part of this record. Microsoft Entra access reviews keep each decision: a review history report lists, for each person reviewed, the decision, the reviewer, the date, any justification the reviewer gave and when the result was applied. For site access reviews, the admin sees the outcome and the owner's comments, and the "My review requests" tab lists each completed review with the reviewer's name and the date. What usually needs building is the link between the two, and a report security can read without opening three admin centres. Our compliance reporting approach covers how that evidence is exported.

How Neptune helps

Neptune is an integrator. We select the governance tool that fits your tenant, implement it with your team, train your admins, and stay with you afterwards: professional services during the engagement, then a customer success manager. Microsoft Entra ID still manages the guest accounts; the tool runs the reviews and keeps the decisions. With the tools we integrate:

  • One view of every team with guests, each guest's last sign-in and every invitation that was never accepted, with the trend over time
  • Guests who have not signed in for a period you set, for example 90 days, shown to the team owner in the review
  • Review campaigns sent to owners and sponsors in Microsoft Teams, with a deadline and reminders, so IT is no longer the bottleneck
  • Each decision logged with its reason, and access removed once the owner decides
  • Files and links shared outside the organisation with no expiry date listed, so they can be withdrawn when the project ends
  • A clear report for your security team

See how guest access fits with the rest on our Microsoft 365 governance page, or talk to us about your tenant.

Sources

Guests piling up across your teams? See how we govern guest access in Microsoft 365.

FAQ

Questions on this topic

Can guests see everything in a team?

No. A guest sees the team's standard channels and the team's files, and a private channel only if its owner adds them. Guests cannot create teams, browse public teams or get OneDrive storage, and they can create channels only if the team owner allows it. Each private channel has its own SharePoint site, so its guests are worth reviewing separately.

Do Microsoft Entra access reviews need an extra licence?

It depends on your plan. Basic access reviews need Microsoft Entra ID P2, which Microsoft 365 E5 includes, or Microsoft Entra ID Governance or the Microsoft Entra Suite. Reviews limited to inactive users, and machine-learning recommendations, need ID Governance or the Entra Suite. For employees, licences count for reviewers and for the people reviewed. For guests, the advanced ID Governance features are billed per active guest each month through Azure, while basic P2 reviews of guests are not.

Does removing a guest from a team delete their account?

No. Removing a guest from a team, or the guest leaving it, keeps their guest account in Microsoft Entra ID. The account goes when an admin deletes it, or when an access review set to remove denied guests denies it: the account is then blocked from signing in for 30 days, then deleted, and it can be restored within those 30 days. Decide in your process when the account itself should go.

How often should we review guest accounts?

There is no single right interval, so treat it as a choice for each type of team. Teams that hold sensitive data, or many guests, justify a shorter cycle than a project team working with one supplier. Aligning reviews with contract and project milestones helps owners answer, because they review when the work changes. Whatever you choose, write it down, apply it consistently and keep a record of each review.

How do we find inactive guests in Microsoft 365?

Start with the last sign-in date in Microsoft Entra ID, shown in the Entra admin center and available through the signInActivity property in Microsoft Graph. The last successful sign-in needs Microsoft Entra ID P1 or P2, and the data can lag by up to 24 hours. With Microsoft Entra ID Governance, an inactive guests report and a review scoped to inactive users do the sorting and the clean-up for you.

Have a question about your own tenant?

Tell us what you are working on and we will tell you where we would start.