Send a message (plain text or Adaptive Card) to a Microsoft Teams conversation using the Bot Framework REST API. Use this for proactive sends (alerts, replies, threaded notifications) or as the outbound leg of a custom Teams bot. Unlike incoming-webhook MessageCards, the Bot Framework path supports threaded replies, Adaptive Cards 1.4+, and any conversation the bot has been added to (channels, group chats, 1:1). Requirements: - An Azure Bot resource (https://portal.azure.com) with its messaging endpoint pointing at a Windmill HTTP trigger (or wherever your bot logic lives). - A stored ConversationReference object - captured by your bot's installationUpdate / message handler when the bot was first added to the conversation. Stash it in a database, DataTable, or wmill.setState keyed by the conversation you want to reach. - The Azure Bot resource credentials (app_id, app_password) saved as an azure_bot Windmill resource. For a complete Teams to Discord bridge using this script, see the Windmill blog post: https://www.windmill.dev/blog/teams-discord-bridge
by hugo989 ยท 5/21/2026
1 | |
2 | |
3 | |
4 | |
5 | |
6 | |
7 | |
8 | |
9 | |
10 | |
11 | |
12 | |
13 | |
14 | |
15 | |
16 | |
17 | |
18 | |
19 | |
20 | |
21 | |
22 | |
23 | |
24 | |
25 | |
26 | |
27 | |
28 | |
29 | |
30 | |
31 | |
32 | |
33 | |
34 | |
35 | |
36 | |
37 | |
38 | |
39 | |
40 | |
41 | |
42 | |
43 | |
44 | |
45 | |
46 | |
47 | |
48 | |
49 | |
50 | |
51 | |
52 | |
53 | |
54 | |
55 | |
56 | |
57 | |
58 | |
59 | |
60 | |
61 | |
62 | |
63 | |
64 | |
65 | |
66 | |
67 | |
68 | |
69 | |
70 | |
71 | |
72 | |
73 | |
74 | |
75 | |
76 | |
77 | |
78 | |
79 | |
80 | |
81 | |
82 | |
83 | |
84 | |
85 | |
86 | |
87 | |
88 | |
89 | |
90 | |
91 | |
92 | |
93 | |
94 | |
95 | |
96 | |
97 | |
98 | |
99 | |
100 | |
101 | |
102 | |
103 | |
104 | |
105 | |
106 | |
107 | |