Guest user can't access teams channel

Chief HR 0 Reputation points
2026-08-26T01:11:15.7833333+00:00

I have set up a Teams channel and invited 10 guest users from external organisations. 9 have access, and 1 can't get access. Discussions with invited org (Ext Org) have led to them responding as below. Our (Org) Microsoft365 account is via GoDaddy, but GoDaddy have said they cannot help with this issue, and to go to Microsoft directly.

Invited org validation completed:

  • Cross-tenant B2B Collaboration is configured as Allowed by default for both inbound and outbound access.
  • Org is not explicitly blocked within Ext Org Cross-Tenant Access settings and therefore inherits the default configuration.
  • Conditional Access policies are not being evaluated, as the failure occurs before authentication reaches that stage.
  • The failure occurs during the Microsoft Invitation Acceptance Portal process rather than during Teams access itself.
  • The issue has been reproduced with multiple users on Ext Org side
  • No licensing, Teams client, user entitlement, or Conditional Access issues have been identified within Ext Org.

The remaining gap is that we can only see the sign-in activity from the Ext Org side. The sign-in logs available to us show that access to the Org tenant is being denied during the guest invitation redemption process, but they do not expose the policy decision or configuration that is being applied within the Org tenant.

For that reason, it would be helpful for the administrators to review the corresponding sign-in activity and External Identity configuration from the Org tenant side using the request and correlation IDs already provided. Those logs should indicate precisely why the guest invitation redemption request is being rejected and whether any tenant-specific policy or restriction is involved.

I would like direction on how to troubleshoot this issue.

Microsoft Teams | Microsoft Teams for business | Teams and channels | Other
0 comments

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Kien 895 Reputation points Independent Advisor
    2026-08-26T02:36:29.6966667+00:00

    Dear @Chief HR,

    Based on your description, please try removing the affected user and then adding them again. This process can help refresh the user’s access and address any temporary configuration or synchronization issue. Once the user has been re-added, kindly ask them to sign in again and repeat the action that previously caused the issue.

    If the behavior continues, please share the exact issue message or a screenshot so that I can investigate further.

    I hope the information shared helps point you in the right direction.

    The first response may not always resolve the issue right away, but with your help and more details, we can work toward a solution.

    If the answer is helpful, please click "Yes" and kindly upvote it. If you have extra questions about this answer, please click "Comment". 

    Note: Please follow the steps in the forum documentation to enable e-mail notifications if you want to receive the related email notification for this thread. 

    Was this answer helpful?

  2. AI answer

    2026-08-26T01:11:38.5633333+00:00

    For this scenario, focus on the Org tenant configuration and logs, because the failure is happening during guest invitation redemption, before Teams access and before Conditional Access is evaluated.

    Recommended troubleshooting path:

    1. Run the Teams guest access diagnostic
      • In the Microsoft 365 admin center, run the guest access diagnostic for Teams.
      • This validates whether the tenant is configured correctly for guest access.
      • If the tenant is not configured correctly, the diagnostic returns the configuration issue and the remediation steps.
    2. Verify that guest access is enabled for Teams at the organization level
      • Guest access in Teams is an organization-wide setting.
      • If guest access is not fully configured in Teams and the related Microsoft 365 services, guest invitation and access can fail.
      • Teams guest access also depends on settings in Microsoft Entra ID, Microsoft 365 Groups, and SharePoint.
    3. Check Microsoft Entra B2B invitation settings in the Org tenant
      • In the Azure portal, go to Users > User settings.
      • Under External collaboration settings, confirm that guest invitations are allowed.
      • If non-admins are expected to invite guests, Members can invite must be set to Yes.
      • If this setting is too restrictive, guest addition or redemption can be blocked.
    4. Confirm the guest object exists and is usable in the Org tenant
      • When a guest is invited to Teams, a guest account is created in Microsoft Entra ID.
      • Verify that the affected guest user exists in Microsoft Entra ID in the Org tenant.
      • If the object is missing or stuck in a bad invitation state, remove the guest and send a fresh invitation.
    5. Check Org-tenant sign-in activity and audit records
      • Review the corresponding sign-in activity in the Org tenant using the request/correlation IDs already collected.
      • Also review audit records for guest additions. Adding a guest in Teams is audited and logged as the Microsoft Entra group administration activity Added member to group.
      • This helps confirm whether the guest was successfully added and whether the failure is at invitation redemption rather than team membership.
    6. Make sure the guest was added to a team
      • Guest access features and functionality are available only after the guest is added to at least one team.
      • If the guest account exists but was not actually added to the intended team, Teams access will not be available.
    7. If the issue is isolated to one external organization or user set, recheck cross-tenant settings only if shared channels are involved
      • For standard Teams guest access, the main path is guest invitation and B2B collaboration.
      • If this is actually a shared channel scenario rather than a guest-in-team scenario, review External Identities > Cross-tenant access settings and confirm the relevant inbound/outbound B2B direct connect settings allow the external users and groups.

    Based on the details provided, the most likely next actions are:

    • Run the Microsoft 365 guest access diagnostic.
    • Review Org-tenant sign-in logs for the failed invitation redemption.
    • Verify Microsoft Entra external collaboration settings.
    • Remove and re-invite the affected guest user.
    • Confirm the guest is present in Microsoft Entra ID and added to the team.
    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.