Repository navigation
Commit 103d5d6
spec: clarify direct-to-Teams stretch as speculative (no Bot Service)
Split the WhatsApp + direct-to-Teams stretch entry into two
distinct items and reword the direct-to-Teams item to be honest
about its current feasibility:
- It MUST not rely on Azure Bot Service (otherwise it is just
ActivityChannel / TeamsChannel under a different name).
- No such transport is publicly available today: Graph chat APIs
and microsoft/teams.py both ultimately route through Bot Service
for the bot-as-conversation-participant pattern.
- The slot is kept on the roadmap to preserve the naming line in
case Microsoft ships a Bot-Service-free transport (native Teams
REST/RPC, a Graph subscription strong enough to drive both
inbound and outbound message flow, ...).
- Reaffirm TeamsChannel (req #28) as the canonical Teams channel
until then.
Co-authored-by: Copilot <[email protected]>1 parent 2cf068c commit 103d5d6
1 file changed
Lines changed: 2 additions & 1 deletion
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
150 | 150 | | |
151 | 151 | | |
152 | 152 | | |
153 | | - | |
| 153 | + | |
| 154 | + | |
154 | 155 | | |
155 | 156 | | |
156 | 157 | | |
| |||
0 commit comments