Teams interop: all meeting chat operations return 403 Forbidden for ACS users since ~Aug 24 2026 (calls work; Teams web anonymous can chat in same meeting)

未关闭

#600 创建于 2026年8月31日 0 条评论 0 个 reaction 已指派 0 人在 GitHub 查看

还没有人认领这个 Issue。

评估

难度: 5/5
预计耗时: 一周以上
新手友好度: 20/100

Issue 类型: 缺陷
描述清晰度: 需要澄清
活跃度: 活跃
技术栈: azure
领域: cloud

调研方向

未识别出任何仓库文件或测试；首先使用列出的 ACS 包版本、CallWithChatComposite 以及文档所述的 POST 端点重现故障。将 ACS 的行为与匿名 Teams Web 参与者的行为进行比较，然后利用 Azure 支持案例和关联的交叉帖子，确定是否可以修改仓库；完成的条件是确认解决问题，或由 maintainer 指导归属责任。

由索引模型根据 Issue 内容生成。

描述

Describe the bug; what happened?

Since approximately Aug 24, 2026, every ACS (anonymous interop) user joining Microsoft Teams meetings in our tenant receives 403 Forbidden on ALL meeting chat operations — ChatThreadClient.sendMessage and sendTypingNotification both fail with:

CommunicationError: {
  "Code": "Forbidden",
  "Message": "The initiator doesn't have the permission to perform the requested operation."
}

— and the user receives no incoming thread messages. Calling, roster, screen share, and reactions all work normally. The CallWithChatComposite shows "You are no longer in this chat thread" immediately after joining. No changes were made on our side (no deploys, no tenant/policy changes).

Key discriminator: in the SAME meeting, an anonymous participant joining via the Teams web client (display name only, unverified — no email OTP) can send meeting chat messages normally. The failure exists only on the ACS interop path.

What are the steps to reproduce the issue?

Create a Teams meeting (either via Graph app-created onlineMeetings or by a human organizer in the Teams desktop app with default options — both reproduce).
Mint an ACS identity + token (voip, chat scopes) and join the meeting with createAzureCommunicationCallWithChatAdapter + CallWithChatComposite (minimal quickstart, no custom code).
Wait for call state Connected (fully admitted).
Send a chat message.

Result: POST /chat/threads/19%3Ameeting_...%40thread.v2/messages returns 403 (on both api-version=2024-06-05-preview and 2025-03-15).

What behavior did you expect?

ACS interop users can send/receive meeting chat while in the call, per the documented Teams external-user capabilities.

If applicable, provide screenshots:

Sample failing request: Ms-Cv: IGMF4wkAI0+MIaxuFQ0kJw.0, 2026-08-31 16:04:38 UTC, resource in Canada region. Happy to share more Ms-Cv values and a live repro meeting privately.

In what environment did you see the issue?

@azure/communication-react: 1.32.0
@azure/communication-calling: 1.42.1
@azure/communication-chat: 1.6.0-beta.7
OS & Device: Windows 11 PC (also reproduced tenant-wide across devices/users in production)
Browser: Google Chrome (latest); production users on multiple browsers

Is there any additional information?

Tenant configuration verified as Global Admin, all permissive:

MeetingChatEnabledType = Enabled on ALL CsTeamsMeetingPolicy instances
ACS federation configured: EnableAcsUsers = True, resource immutable ID present in AllowedAcsResources
EnableAcsFederationAccess = True on all external access policies
BlockedAnonymousJoinClientTypes empty
EnableExternalAccessRestrictionsForChatParticipants / EnableMutualFederationForChatParticipants both False
per-meeting allowMeetingChat = enabled

A test policy with AnonymousUserAuthenticationMethod = None assigned to the organizer did not help (a fresh meeting created after assignment still fails). This is NOT the known join-timing issue — the failure persists for the entire meeting while Connected.

A Severity-A Azure support case is open in parallel. Also posted on Microsoft Q&A: https://learn.microsoft.com/en-us/answers/questions/5990218/

Cross-posted with full details on the UI library repo: https://github.com/Azure/communication-ui-library/issues/6074 (filed there first; posting here as this appears to be a service-side issue in the ACS↔Teams interop chat gateway rather than an SDK/UI defect).

主要语言: 没有语言数据
星标: 339
派生: 113
平均合并: 36 分钟
30 天内合并 PR: 1

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南，环境需要你自己搭建：先看它的 README，通用步骤见我们的新手贡献指南。

从这里开始

先读完整个 Issue，再读项目的贡献指南。
在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
Fork 仓库，在一个分支上完成修改。
提交 Pull Request，并在描述里引用这个 Issue 编号。

Azure/Communication 的其他 Issue

10DLC Brand/Campaign registration: portal shows "subscription is not eligible" on a qualifying Pay-As-You-Go subscription with US billing
未关闭
- 哪里不对？
难度 4/5 3-5 天新手友好度 35/100

Azure/Communication#599 · 4 条评论 · 1 个 reaction · 2026年7月9日创建
ACS Call Automation playToAll silent in Teams Online Meeting (CallConnected + PlayCompleted, list_participants=0)
未关闭
- 哪里不对？
难度 5/5 一周以上新手友好度 20/100

Azure/Communication#598 · 2026年6月30日创建
Email Opt-out and Suppression list functionality
未关闭
- 哪里不对？
难度 5/5 一周以上新手友好度 25/100

Azure/Communication#543 · 2024年1月16日创建
[Android] [Calling - 2.0.0] Absent library logs
未关闭
- 哪里不对？
Needs: triage :mag:

难度 4/5 3-5 天新手友好度 35/100

Azure/Communication#447 · 2022年3月9日创建
[BUG] CommunicationCalling crashes on hangup
未关闭
- 哪里不对？
Needs: triage :mag:

难度 4/5 3-5 天新手友好度 25/100

Azure/Communication#440 · 4 条评论 · 2022年2月8日创建

查看 Azure/Communication 的全部 Issue

相似的 Issue

[Bug]: External Storage - Document Attachments fails on Purch. Cr. Memo Hdr. due to trailing dot in generated SharePoint folder name
未关闭
- 哪里不对？
Team: SCM

难度 2/5 1-3 小时新手友好度 78/100

microsoft/BCApps#12012 · 1 条评论 · 2026年9月28日创建

维护者通常 1 天内回复
Document the deploy rollback path and a pre-`db push` backup step
未关闭
- 哪里不对？
developer-experience documentation high

难度 2/5 1-3 小时新手友好度 76/100

anchapin/staging-studio#1117 · 2026年9月28日创建

维护者通常 1 天内回复
Sprites: explain the exec size limit when a command or its `env` is too large
未关闭
- 哪里不对？
enhancement

难度 2/5 1-3 小时新手友好度 78/100

pydantic/pydantic-ai#8935 · 2026年9月28日创建

维护者通常 1 天内回复
[AVM Module Issue]: linuxFxVersion generates DOTNETCORE|10.0 instead of DOTNET-ISOLATED|10.0 for .NET 10 isolated function apps
未关闭
- 哪里不对？
Language: Terraform :globe_with_meridians: Needs: Triage :mag: Type: Bug :bug:

难度 2/5 1-3 小时新手友好度 74/100

Azure/terraform-azurerm-avm-res-web-site#408 · 1 条评论 · 2026年9月28日创建

维护者通常 1 天内回复
[AVM Module Issue]: Problem with SQLServer2025
未关闭
- 哪里不对？
Language: Terraform :globe_with_meridians: Needs: More Evidence :balance_scale: Needs: Triage :mag: Type: Bug :bug:

难度 2/5 1-3 小时新手友好度 78/100

Azure/terraform-azurerm-avm-res-sql-managedinstance#152 · 2026年9月28日创建

维护者通常 1 天内回复

更多 Cloud Issue

Teams interop: all meeting chat operations return 403 Forbidden for ACS users since ~Aug 24 2026 (calls work; Teams web anonymous can chat in same meeting)

哪里不对？

评估

调研方向

描述

环境准备

从这里开始

Azure/Communication 的其他 Issue

哪里不对？

哪里不对？

哪里不对？

哪里不对？

哪里不对？

相似的 Issue

哪里不对？

哪里不对？

哪里不对？

哪里不对？

哪里不对？

把新 issue 发到你的邮箱