Unable to message , call, and meeting in the MS Teams.

A Teams administrator should first run the Teams Federation diagnostic for the affected account and external domain, then correct the tenant domain setting or assigned external-access policy identified by the test.

If you are not a Teams administrator

Send this information to your IT or Microsoft 365 administrator:

• Your Microsoft 365 email address.
• The external user’s full email/SIP address and domain.
• Whether the external account is:
  • A work or school account in another Microsoft 365 organization,
  • An unmanaged/personal Teams account, or
  • A guest account in your organization.
• The exact error message or a screenshot.
• Whether the failure affects one external domain or all external users.
• Whether chat, direct Teams calls, and scheduled meetings fail separately.

Configuration changes require a Teams Administrator or Global Administrator role.^1^

1. Run the federation diagnostic

In the Microsoft 365 admin center, run the Teams Federation diagnostic:

1. Enter the affected internal user’s email address.
2. Enter the external organization’s domain.
3. Select Run Tests.
4. Apply the remediation shown for failed domain, federation, or policy checks.

The diagnostic verifies whether the user can communicate with an external federated Teams user. It is not available in Microsoft 365 Government, Microsoft 365 operated by 21Vianet, or Microsoft 365 Germany.^2^

2. Check organization-level external access

For external users with work or school accounts:

1. Open Teams admin center → Users → External access.
2. Under Teams and Skype for Business users in external organizations, verify that:
   • Allow all external domains is selected, or
   • The external user’s exact domain is included in Allow only specific external domains.
3. Ensure the domain is not on a block list.
4. Save any changes.

If an allow list is used, every domain not listed is blocked. External access must also be permitted by the other organization; your administrator cannot change the partner tenant’s configuration.^3^

3. Check the affected user’s external-access policy

Organization settings and user policies must both permit external communication:

1. Go to Teams admin center → Users → External access → Policies.
2. Open Org-wide default settings, or the custom policy assigned to the affected user.
3. Enable the applicable control:
   • Communication with other Microsoft 365 organizations.
   • Communication with unmanaged Teams accounts, if applicable.
4. Save the policy and assign the custom policy to the affected user or group if it is not already assigned.

The organization-level setting can override a user policy.^3^

4. Treat unmanaged/personal Teams accounts separately

If the external person uses Teams Free or another account not managed by an organization:

1. Go to Teams admin center → Users → External access.
2. Turn on People in my organization can communicate with unmanaged Teams accounts.
3. If those external users must initiate contact, also enable External users with Teams accounts not managed by an organization can contact users in my organization.
4. Select Save.

These controls document chat and meeting communication with unmanaged accounts; they should not be treated as a guarantee that direct 1:1 calling will become available.^3^

5. Configure external meeting participation separately

Meeting join is controlled separately from external chat and calling.

For anonymous participants:

1. Go to Teams admin center → Meetings → Meeting settings.
2. Enable Anonymous users can join a meeting.
3. Go to Meetings → Meeting policies and open the policy assigned to the organizer.
4. Under the meeting join/lobby settings, enable Anonymous users can join a meeting.
5. Confirm external access allows the participant’s domain.

If guests are used, go to Settings and policies → Guest access and set Allow guest access in Teams to On.^4^

External access supports finding, calling, chatting, and scheduling meetings with users in other organizations. Guest access is different: it creates a Microsoft Entra B2B guest account and requires the guest to sign in and switch to your organization.^5^

If the diagnostic passes but the issue remains, collect the exact error, affected internal and external SIP addresses, timestamp, and whether the failure occurs in chat, direct calls, or meeting join, then open a Microsoft 365 support request.

References

1. Teams External Access Settings Not Applying: CommunicationWithExternalOrgs and CustomizeFederation Issues - Microsoft Q&A
2. External federated contacts don't appear in Teams search
3. IT Admins - Manage external meetings and chat with people and organizations using Microsoft identities
4. Errors when external participants try to join a Teams meeting
5. Use guest access and external access to collaborate with people outside your organization