Azure bot cannot join teams meeting returns error code 7505 even though tenant is same

Question

Azure bot cannot join teams meeting returns error code 7505 even though tenant is same

Mervyn Vaz 0

My azure bot is unable to join a teams meeting, the api returns Graph returned 403 Forbidden: {"error":{"code":"7505","message":"Request authorization tenant mismatch."}. I have verified that TenantId in token matches the one in my code while joining the meeting and I have given the following permissions to my app

Calls.AccessMedia.All
Calls.Initiate.All
Calls.JoinGroupCall.All
Calls.JoinGroupCallAsGuest.All
CallTranscripts.Read.All
OnlineMeetingArtifact.Read.All
OnlineMeetings.Read.All

is any configuration missing?

SRILAKSHMI C 10,640 Reputation points Microsoft External Staff Moderator

2025-12-02T08:22:00.45+00:00

Hi Mervyn Vaz,

Welcome to Microsoft Q&A and Thank you for reaching out.

I understand that You're seeing error 403 – code 7505 (Request authorization tenant mismatch) when your Azure bot tries to join a Teams meeting. Even though the TenantId appears correct, this behavior aligns with current platform limitations.

Azure Bot + Teams Calling/Meeting APIs do not support multi-tenant scenarios. A bot can only join meetings hosted in the same tenant where the bot is registered. If the meeting organizer belongs to a different tenant even indirectly the join request will fail with 7505 tenant mismatch.

Microsoft is aware of the demand for cross-tenant support, but it is not available yet.

Although the root cause is the tenant-mismatch limitation, it’s good to confirm the following to ensure there are no other configuration issues:

Some tenants require allowlisting for interoperability scenarios. – Make sure your tenant is enabled if needed.

Confirm the TenantId in the token matches the bot’s home tenant and ensure it hasn’t expired.

Bots (and ACS clients) can only join scheduled meetings, not ad-hoc or Meet-Now sessions.

Ensure the meeting organizer allows bots to bypass or be admitted from the lobby. – A bot cannot self-bypass the lobby unless allowed.

The permissions you listed look correct. – No additional meeting-join permissions are required beyond these.

Even with the right token and permissions, the bot cannot join a Teams meeting hosted in another tenant. The platform currently supports only same-tenant meeting joins, which is why you’re getting error 7505.

I can see that you posted a similar question, which has already received a response. You can refer to the following link for details: https://learn.microsoft.com/de-de/answers/questions/5591170/graph-error-403-forbidden-mit-dem-code-7505

I Hope this helps. Do let me know if you have any further queries.

Thank you!
Mervyn Vaz 0 Reputation points

2025-12-02T11:48:24.3133333+00:00

I confirmed that tenant Id of bot matches from token and that the token is not expired. And the meeting is not ad-hoc or Meet-now it is a scheduled call, I'm scheduling a meet and then I add those meeting details in my code for the bot to join.
Can you give me more details on allowlisting and how can I enable it.
SRILAKSHMI C 10,640 Reputation points Microsoft External Staff Moderator

2025-12-04T12:15:30.8466667+00:00

Hi Mervyn Vaz,

Thanks for confirming the TenantId, token validity, and that the meeting is a scheduled meeting. Based on what you’ve shared, the next thing to validate is whether your tenant is enabled for Teams bot calling interoperability which Microsoft internally refers to as allowlisting.

What “allowlisting” means in this context

For calling/meeting bots, Microsoft requires certain tenants to be explicitly enabled to use Graph Calling APIs for media join scenarios. This is a backend configuration that Microsoft Support/PG enables when a tenant is blocked by default for security or regulatory reasons.

Allowlisting does not bypass the tenant-mismatch limitation. It only ensures that your bot can use the Calling/Meeting APIs inside your tenant without backend restrictions.

Even with allowlisting enabled, the platform still only supports same-tenant meeting joins. If the organizer or meeting resource belongs to any other tenant (even via B2B/backed users), Graph will continue to return 7505 – authorization tenant mismatch. This limitation cannot be bypassed.

Thank you!

Your answer

Mervyn Vaz 0 Reputation points

2025-12-02T11:48:24.3133333+00:00

I confirmed that tenant Id of bot matches from token and that the token is not expired. And the meeting is not ad-hoc or Meet-now it is a scheduled call, I'm scheduling a meet and then I add those meeting details in my code for the bot to join.
Can you give me more details on allowlisting and how can I enable it.
SRILAKSHMI C 10,640 Reputation points Microsoft External Staff Moderator

2025-12-04T12:15:30.8466667+00:00

Hi Mervyn Vaz,

Thanks for confirming the TenantId, token validity, and that the meeting is a scheduled meeting. Based on what you’ve shared, the next thing to validate is whether your tenant is enabled for Teams bot calling interoperability which Microsoft internally refers to as allowlisting.

What “allowlisting” means in this context

For calling/meeting bots, Microsoft requires certain tenants to be explicitly enabled to use Graph Calling APIs for media join scenarios. This is a backend configuration that Microsoft Support/PG enables when a tenant is blocked by default for security or regulatory reasons.

Allowlisting does not bypass the tenant-mismatch limitation. It only ensures that your bot can use the Calling/Meeting APIs inside your tenant without backend restrictions.

Even with allowlisting enabled, the platform still only supports same-tenant meeting joins. If the organizer or meeting resource belongs to any other tenant (even via B2B/backed users), Graph will continue to return 7505 – authorization tenant mismatch. This limitation cannot be bypassed.

Thank you!

Share via

Azure bot cannot join teams meeting returns error code 7505 even though tenant is same

Your answer