{"id":15707,"date":"2026-04-01T08:01:07","date_gmt":"2026-03-31T23:01:07","guid":{"rendered":"https:\/\/m365jp.net\/?p=15707"},"modified":"2026-04-01T08:01:24","modified_gmt":"2026-03-31T23:01:24","slug":"mc1266901-microsoft-teams-retirement-of-legacy-third-party-meeting-and-call-control-apis","status":"publish","type":"post","link":"https:\/\/m365jp.net\/index.php\/2026-04-01-mc1266901-microsoft-teams-retirement-of-legacy-third-party-meeting-and-call-control-apis","title":{"rendered":"MC1266901 | Microsoft Teams: Retirement of legacy third\u2011party meeting and call control APIs"},"content":{"rendered":"
\n
\n
\n\n\n\n
MC1266901 | Microsoft Teams: Retirement of legacy third\u2011party meeting and call control APIs<\/th>\n<\/tr>\n<\/tbody>\n<\/table>\n
\n\n\n\n\n\n\n\n\n\n
Classification<\/th>\nplanForChange<\/td>\n<\/tr>\n
Last Updated<\/th>\n03\/31\/2026 22:55:49<\/td>\n<\/tr>\n
Start Time<\/th>\n03\/31\/2026 22:54:57<\/td>\n<\/tr>\n
End Time<\/th>\n07\/30\/2026 07:00:00<\/td>\n<\/tr>\n
Action Required By Date<\/th>\n2026-06-29T07:00:00Z<\/td>\n<\/tr>\n
Message Content<\/th>\n\n<\/p>\n

<\/p>\n

[Introduction]<\/b> <\/p>\n

<\/b>To improve the reliability, security, and maintainability of Microsoft Teams, Microsoft will retire a legacy external Teams meeting controls integration capability in the Teams desktop client (Windows and Mac). This capability previously enabled select external hardware devices and applications to control Teams meeting or calling functionality from outside of the Teams client through a limited, non\u2011published integration method. This integration method is no longer supported or maintained. Retiring this functionality allows Microsoft Teams to continue investing in secure and supported integration models. <\/p>\n

[When this will happen]<\/b><\/p>\n

Retirement date: June 30, 2026 <\/p>\n

On this date, <\/p>\n

    \n
  • The legacy external meeting controls integration capability will be permanently removed. <\/li>\n
  • The related user setting in the Teams desktop client will no longer be available. <\/li>\n<\/ul>\n

    This communication provides more than 30 days\u2019 notice in alignment with Message center retirement best practices. <\/p>\n

    [How this affects your organization] <\/b><\/p>\n

    <\/i>Who is affected<\/i><\/p>\n

    This change may affect organizations where users enabled external hardware devices or applications to control Teams meetings (or Teams calls in some cases) functionality from outside of the Teams desktop client. Examples of affected scenarios may include external software or hardware used to: <\/p>\n

      \n
    • Mute or unmute the microphone <\/li>\n
    • Turn the camera on or off <\/li>\n
    • Apply or remove background blur <\/li>\n
    • Raise or lower hand <\/li>\n
    • Send meeting reactions <\/li>\n
    • End meeting <\/li>\n<\/ul>\n

      Microsoft Teams desktop users on Windows and Mac may experience changes if such integrations are in use. <\/p>\n

      [What will happen]<\/b><\/p>\n

      Beginning June 30, 2026: <\/p>\n

        \n
      • External applications or devices will no longer be able to control Teams meeting or calling functionality using this legacy integration capability. <\/li>\n
      • If basic media controls (for example, mute\/unmute or camera on\/off) were previously triggered during Teams calls by an external device or application, those controls may also no longer function when initiated externally. <\/li>\n
      • The Teams desktop client setting located at: Settings > Privacy that previously allowed external applications or devices to control meeting features will be removed. <\/li>\n
      • Previously configured third\u2011party meeting or calling control integrations that relied on this capability may stop functioning. <\/li>\n<\/ul>\n

        Native Microsoft Teams meeting and calling controls will continue to function normally.
        Select device or application providers may have previously notified customers regarding the end-of-support (EOS) for integrations that relied on this functionality.
        This change does not affect supported Microsoft Teams integration models or published Microsoft Graph APIs. <\/p>\n

        [What you can do to prepare]<\/b><\/p>\n

        No configuration change is required by admins within Microsoft 365 for this retirement. However, we recommend that you: <\/p>\n

Machine Translation<\/th>\n\n<\/p>\n

<\/p>\n

[\u306f\u3058\u3081\u306b]<\/b> <\/p>\n

<\/b>Microsoft Teams\u306e\u4fe1\u983c\u6027\u3001\u30bb\u30ad\u30e5\u30ea\u30c6\u30a3\u3001\u4fdd\u5b88\u6027\u3092\u5411\u4e0a\u3055\u305b\u308b\u305f\u3081\u306b\u3001Microsoft\u306fTeams\u30c7\u30b9\u30af\u30c8\u30c3\u30d7\u30af\u30e9\u30a4\u30a2\u30f3\u30c8(Windows\u304a\u3088\u3073Mac)\u306b\u304a\u3051\u308b\u30ec\u30ac\u30b7\u30fc\u306a\u5916\u90e8Teams\u4f1a\u8b70\u5236\u5fa1\u7d71\u5408\u6a5f\u80fd\u3092\u5ec3\u6b62\u3057\u307e\u3059\u3002\u3053\u306e\u6a5f\u80fd\u306f\u4ee5\u524d\u3001\u9650\u5b9a\u7684\u3067\u975e\u516c\u958b\u306e\u7d71\u5408\u65b9\u6cd5\u3092\u901a\u3058\u3066\u3001\u7279\u5b9a\u306e\u5916\u90e8\u30cf\u30fc\u30c9\u30a6\u30a7\u30a2\u30c7\u30d0\u30a4\u30b9\u3084\u30a2\u30d7\u30ea\u30b1\u30fc\u30b7\u30e7\u30f3\u304cTeams\u30af\u30e9\u30a4\u30a2\u30f3\u30c8\u306e\u5916\u90e8\u304b\u3089Teams\u306e\u4f1a\u8b70\u3084\u901a\u8a71\u6a5f\u80fd\u3092\u5236\u5fa1\u3059\u308b\u3053\u3068\u3092\u53ef\u80fd\u306b\u3057\u3066\u3044\u307e\u3057\u305f\u3002\u3053\u306e\u7d71\u5408\u65b9\u6cd5\u306f\u73fe\u5728\u30b5\u30dd\u30fc\u30c8\u3082\u7dad\u6301\u3082\u3055\u308c\u3066\u3044\u307e\u305b\u3093\u3002\u3053\u306e\u6a5f\u80fd\u3092\u5ec3\u6b62\u3059\u308b\u3053\u3068\u3067\u3001Microsoft Teams\u306f\u5b89\u5168\u3067\u30b5\u30dd\u30fc\u30c8\u3055\u308c\u305f\u7d71\u5408\u30e2\u30c7\u30eb\u3078\u306e\u6295\u8cc7\u3092\u7d99\u7d9a\u3067\u304d\u307e\u3059\u3002 <\/p>\n

[\u3044\u3064\u8d77\u3053\u308b\u304b]<\/b><\/p>\n

\u9000\u8077\u65e5:2026\u5e746\u670830\u65e5<\/p>\n

\u3053\u306e\u65e5\u306b\u3001<\/p>\n