The connection changed.
Start with what your tool needs.

What Microsoft retired.

The local third-party app API let tools read meeting signals and send commands to the Teams desktop app. Microsoft announced its retirement under Message Center notice MC1266901, effective 30 June 2026.

Examples include some Stream Deck and Touch Portal tools, Home Assistant integrations and scripts built around teams-ws. The platform name alone does not tell you whether your particular tool used this API.

How the connection changed.

Your tool used to talk to Teams directly on port 8124. Since the retirement, nothing answers there. With Call State, Teams Emulation answers on that port again and passes the meeting state on.

A replacement, not a universal adapter.

Call State reads meeting status from the desktop app without relying on the retired connection. Teams Emulation can provide a compatible endpoint for existing tools on the same computer, at ws://127.0.0.1:8124.

Emulation is not a complete recreation of every Teams feature. A compatible tool still connects, but three parts of the retired API have no equivalent here:

• Background blur. Blur state is not read, so it is reported as a fixed compatibility value, and blur cannot be switched.
• Unread messages. The retired API exposed an unread flag, but Call State does not sense it. Chat-pane state does not mean unread messages or access to message content.
• Stop sharing. Sharing state is read, but the stop-sharing permission is a fixed compatibility value, not a live signal.

The other signals and commands — mute, camera, hand, leave, reactions and the remaining meeting state — reflect what Call State actually senses and controls.

The emulated endpoint needs no old token and no pairing step. A client on the same computer connects to ws://127.0.0.1:8124. Call State listens on port 8124 on all interfaces, so treat that port as reachable from your network while Emulation is on — block it at the firewall, or leave Emulation off on shared or untrusted networks. Any existing listener or port forward must be stopped before Call State can use the port.

Commands also need a reachable Teams meeting interface. A blocking dialog, a minimized meeting window or missing permissions can prevent an action. Check the exact workflow you rely on.

Check it in a real call.

1. Identify your integration. Check its documentation for the local meeting API, port 8124 or teams-ws. If it uses a different connection, Teams Emulation may not help.
2. Install Call State and sign in. Use the Mac or Windows build for your computer and complete the permissions setup. Every new account includes a 7-day Paid trial.
3. Enable Teams Emulation. Make sure no other app, old shim or socat forward is already listening on port 8124.
4. Verify the features you need. Join and leave a meeting, mute and unmute, and check camera, hand and screen-sharing behavior as applicable. Test status updates and commands separately.
5. Choose your plan after testing. Keep Paid for compatible legacy tools, or use Free for live status and your own CLI/REST automations.

What is available today.

• Free: the desktop app, live status, commands, CLI and REST access. Free requires signing in every 24 hours; accounts are deleted after 30 days without use.
• Paid: adds Teams Emulation for compatible legacy tools and removes the daily sign-in requirement. €1.50 monthly or €12 yearly.
• Planned: dedicated Call State plugins for Stream Deck and Touch Portal, plus browser extensions. These are not available in either plan yet. Chrome and Edge are the first browser targets; Firefox and Safari remain under consideration.

The trial is free and needs no card. A paid purchase also carries our worldwide 30-day money-back guarantee. That guarantee does not limit statutory withdrawal rights.