You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/spec/v1beta3/providers.md
+11-8Lines changed: 11 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -350,23 +350,26 @@ stringData:
350
350
##### Microsoft Teams
351
351
352
352
When `.spec.type` is set to `msteams`, the controller will send a payload for
353
-
an [Event](events.md#event-structure) to the provided Microsoft Teams [Address](#address).
353
+
an [Event](events.md#event-structure) to the provided [Address](#address). The address
354
+
may be a [Microsoft Teams Incoming Webhook Workflow](https://support.microsoft.com/en-us/office/create-incoming-webhooks-with-workflows-for-microsoft-teams-8ae491c7-0394-4861-ba59-055e33f75498), or
355
+
the deprecated [Office 365 Connector](https://devblogs.microsoft.com/microsoft365dev/retirement-of-office-365-connectors-within-microsoft-teams/).
354
356
355
-
The Event will be formatted into a Microsoft Teams
with the metadata attached as facts, and the involved object as summary.
357
+
**Note:** If the Address host contains the suffix `.webhook.office.com`, the controller will imply that
358
+
the backend is the deprecated Office 365 Connector and is expecting the Event in the [connector message](https://learn.microsoft.com/en-us/microsoftteams/platform/webhooks-and-connectors/how-to/connectors-using#example-of-connector-message) format. Otherwise, the controller will format the Event as a [Microsoft Adaptive Card](https://adaptivecards.io/explorer/) message.
359
+
360
+
In both cases the Event metadata is attached as facts, and the involved object as a summary/title.
358
361
The severity of the Event is used to set the color of the message.
359
362
360
363
This Provider type supports the configuration of a [proxy URL](#https-proxy)
361
364
and/or [TLS certificates](#tls-certificates), but lacks support for
362
365
configuring a [Channel](#channel). This can be configured during the
363
-
creation of the incoming webhook in Microsoft Teams.
366
+
creation of the Incoming Webhook Workflow in Microsoft Teams.
364
367
365
368
###### Microsoft Teams example
366
369
367
370
To configure a Provider for Microsoft Teams, create a Secret with [the
368
-
`address`](#address-example) set to the [webhook URL](https://learn.microsoft.com/en-us/microsoftteams/platform/webhooks-and-connectors/how-to/add-incoming-webhook#create-incoming-webhooks-1),
369
-
and a `msteams` Provider with a [Secret reference](#address-example).
371
+
`address`](#address-example) set to the [webhook URL](https://support.microsoft.com/en-us/office/create-incoming-webhooks-with-workflows-for-microsoft-teams-8ae491c7-0394-4861-ba59-055e33f75498),
372
+
and an `msteams` Provider with a [Secret reference](#secret-reference).
0 commit comments