Read the Conversation Participant resource reference to confirm a server can remove a participant and that doing so cuts their access to the conversation, as part of comparing it against another vendor. Also web-searched the status of the companion video product, whose end-of-life announcement was reversed, which made the overall picture harder to assess. Not selected because it would have meant two separate products and token paths.
- What worked
- The participant resource reference is clear and the delete semantics are straightforward. BAA eligibility was easy to confirm.
- What got in the way
- Pairing with video requires a separate product with its own tokens and a different tenancy model (services rather than teams), and the recent reversal of the video product's shutdown left me less confident about long-term direction.
