{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreiggpzec4vkgs433hhpbe6ztmyyofw32f4be7rcgzqznygtn5kn354",
    "uri": "at://did:plc:xxrzfynfiasdpbxteqxi4jgq/app.bsky.feed.post/3mekbooctlam2"
  },
  "description": "Voice tethering in Microsoft Teams attributes captions, transcripts, and meeting intelligence to Deaf or hard-of-hearing participants instead of their sign language interpreters, improving accuracy and accountability. It rolls out worldwide from mid-March to mid-April 2026, is on by default, and ...",
  "path": "/m365-message-center/message/mc1230459/",
  "publishedAt": "2026-02-11T01:00:15.000Z",
  "site": "https://blog.tophhie.cloud",
  "tags": [
    "553223"
  ],
  "textContent": "**[Introduction]**\n\n**Voice tethering** builds on the recent introduction of **Sign Language Mode** in _Microsoft Teams_. When a sign language interpreter voices on behalf of a Deaf or hard‑of‑hearing (D/HH) participant, Teams will now attribute captions, transcripts, and meeting intelligence—such as Copilot notes, summaries, action items, and insights—to the D/HH participant rather than the interpreter. This update ensures accurate representation in meetings, clarifies who is contributing to the conversation, and improves downstream meeting accuracy and accountability.\n\nThis message is associated with Microsoft 365 Roadmap ID 553223.\n\n**[When this will happen]**\n\n  * **Targeted Release (Worldwide):** We will begin rolling out in **mid-March 2026** and expect to complete by **late March 2026**.\n  * **General Availability (Worldwide, GCC):** We will begin rolling out in **early April 2026** and expect to complete by **mid-April 2026**.\n\n\n\n**[How this affects your organization]**\n\n_Who is affected_\n\n  * Organizations with meeting participants who are Deaf or hard‑of‑hearing and use sign language interpreters in  _Teams meetings_.\n  * Any users who participate in meetings with **Sign Language Mode enabled**.\n\n\n\n_What will happen_\n\n  * Voice contributions made by interpreters will be attributed to the D/HH participant across:\n\n    * Live captions\n    * Meeting transcripts\n    * Copilot notes, summaries, action items, and insights\n    * Other Teams meeting intelligence\n  * Meeting data becomes more accurate by ensuring the correct participant is represented.\n  * Interpreter identity is no longer conflated with the signer they support.\n  * Sign Language Mode is already available to all users; voice tethering enhances it automatically.\n  * The feature is **on by default** when sign language mode and interpreter assignment are used.\n  * No admin controls are required to enable or manage the feature.\n\n\n\n**[What you can do to prepare]**\n\nNo action is required.\n\nOptional preparation steps:\n\n  * Inform D/HH users and interpreters that speech attribution in meetings will change.\n  * Update internal training or accessibility resources if you document interpreter workflows.\n  * Notify helpdesk or support teams that captioning and transcript attribution will appear differently for interpreted meetings.\n\n\n\n**[Compliance considerations]**\n\nNo compliance considerations identified. Review as appropriate for your organization.",
  "title": "MC1230459: Microsoft Teams: Voice tethering",
  "updatedAt": "2026-02-11T01:00:15.000Z"
}