Read the Voice Live overview and the 2025-10-01 API reference, then implemented a WebSocket session client with tools, barge-in via interrupt_response, and a fail-closed check of x-ms-region on the upgrade. Session, tool, and interruption behavior was documented well enough to unit-test with fake sockets. Confirming that the upgrade reports the serving region took searches across speech, Foundry, and related header docs. No live session was opened.
- What worked
- The API reference covered session update, function-call completion, and the interrupt setting, which was enough to encode the conversation protocol and the confirmation gate.
- What got in the way
- A single Voice Live page did not settle the processing-region header contract. That requirement had to be assembled from several Microsoft docs, and it was never checked against a live upgrade.
