[7.17] [DOCS] Microsoft Teams connector known issue (#191143) (#191227)

# Backport

This will backport the following commits from `main` to `7.17`:
- [[DOCS] Microsoft Teams connector known issue
(#191143)](https://github.com/elastic/kibana/pull/191143)
 - https://github.com/elastic/kibana/pull/190568

<!--- Backport version: 8.9.8 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)

<!--BACKPORT [{"author":{"name":"Lisa
Cawley","email":"lcawley@elastic.co"},"sourceCommit":{"committedDate":"2024-08-23T17:15:05Z","message":"[DOCS]
Microsoft Teams connector known issue
(#191143)","sha":"bb7466e44358d0b577dc2eeb0af9816a331d5ca3","branchLabelMapping":{"^v8.16.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:ResponseOps","docs","Feature:Actions/ConnectorsManagement","backport:all-open","v8.16.0","v8.15.1"],"number":191143,"url":"https://github.com/elastic/kibana/pull/191143","mergeCommit":{"message":"[DOCS]
Microsoft Teams connector known issue
(#191143)","sha":"bb7466e44358d0b577dc2eeb0af9816a331d5ca3"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v8.16.0","labelRegex":"^v8.16.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/191143","number":191143,"mergeCommit":{"message":"[DOCS]
Microsoft Teams connector known issue
(#191143)","sha":"bb7466e44358d0b577dc2eeb0af9816a331d5ca3"}},{"branch":"8.15","label":"v8.15.1","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/191219","number":191219,"state":"MERGED","mergeCommit":{"sha":"0437c1bbda4984c51edd18a94182336906a9767a","message":"[8.15]
[DOCS] Microsoft Teams connector known issue (#191143) (#191219)\n\n#
Backport\n\nThis will backport the following commits from `main` to
`8.15`:\n- [[DOCS] Microsoft Teams connector known
issue\n(#191143)](https://github.com/elastic/kibana/pull/191143)\n\n<!---
Backport version: 9.4.3 -->\n\n### Questions ?\nPlease refer to the
[Backport
tool\ndocumentation](https://github.com/sqren/backport)\n\n<!--BACKPORT
[{\"author\":{\"name\":\"Lisa\nCawley\",\"email\":\"lcawley@elastic.co\"},\"sourceCommit\":{\"committedDate\":\"2024-08-23T17:15:05Z\",\"message\":\"[DOCS]\nMicrosoft
Teams connector known
issue\n(#191143)\",\"sha\":\"bb7466e44358d0b577dc2eeb0af9816a331d5ca3\",\"branchLabelMapping\":{\"^v8.16.0$\":\"main\",\"^v(\\\\d+).(\\\\d+).\\\\d+$\":\"$1.$2\"}},\"sourcePullRequest\":{\"labels\":[\"release_note:skip\",\"Team:ResponseOps\",\"docs\",\"Feature:Actions/ConnectorsManagement\",\"backport:all-open\",\"v8.16.0\"],\"title\":\"[DOCS]\nMicrosoft
Teams connector
known\nissue\",\"number\":191143,\"url\":\"https://github.com/elastic/kibana/pull/191143\",\"mergeCommit\":{\"message\":\"[DOCS]\nMicrosoft
Teams connector known
issue\n(#191143)\",\"sha\":\"bb7466e44358d0b577dc2eeb0af9816a331d5ca3\"}},\"sourceBranch\":\"main\",\"suggestedTargetBranches\":[],\"targetPullRequestStates\":[{\"branch\":\"main\",\"label\":\"v8.16.0\",\"branchLabelMappingKey\":\"^v8.16.0$\",\"isSourceBranch\":true,\"state\":\"MERGED\",\"url\":\"https://github.com/elastic/kibana/pull/191143\",\"number\":191143,\"mergeCommit\":{\"message\":\"[DOCS]\nMicrosoft
Teams connector known
issue\n(#191143)\",\"sha\":\"bb7466e44358d0b577dc2eeb0af9816a331d5ca3\"}}]}]\nBACKPORT-->\n\nCo-authored-by:
Lisa Cawley <lcawley@elastic.co>"}}]}] BACKPORT-->

### Preview

-
https://kibana_bk_191227.docs-preview.app.elstc.co/guide/en/kibana/7.17/release-notes-7.17.23.html#known-issues-v7.17.23
-
https://kibana_bk_191227.docs-preview.app.elstc.co/guide/en/kibana/7.17/teams-action-type.html#configuring-teams

docs/CHANGELOG.asciidoc

@@ -97,7 +97,28 @@ Review important information about the {kib} 7.17.x releases.
 [[release-notes-7.17.23]]
 == {kib} 7.17.23
 
-The 7.17.23 release includes the following bug fixes.
+The 7.17.23 release includes the following known issues and bug fixes.
+
+[float]
+[[known-issues-v7.17.23]]
+=== Known issues
+
+[discrete]
+[[known-187823]]
+.Connectors require update due to Microsoft Teams product retirement
+[%collapsible]
+====
+*Details* +
+The original method for configuring incoming webhooks in Microsoft Teams is being retired.
+Refer to https://devblogs.microsoft.com/microsoft365dev/retirement-of-office-365-connectors-within-microsoft-teams/[Retirement of Office 365 connectors within Microsoft Teams] and {kibana-issue}187823[#187823].
+
+*Impact* +
+If you used the *Incoming Webhook* app in Microsoft Teams to generate a webhook URL for a <<teams-action-type,Microsoft Teams connector>>, it will stop working in December 2024.
+
+*Workaround* +
+Use the *Workflows* app in Microsoft Teams to create a new webhook URL, as described in <<configuring-teams>>.
+Update your Microsoft Teams connector to use the new URL before the end of December 2024.
+====
 
 [float]
 [[fixes-v7.17.23]]

docs/management/connectors/action-types/teams.asciidoc

@@ -5,7 +5,7 @@
 <titleabbrev>Microsoft Teams</titleabbrev>
 ++++
 
-The Microsoft Teams connector uses https://docs.microsoft.com/en-us/microsoftteams/platform/webhooks-and-connectors/how-to/add-incoming-webhook[Incoming Webhooks].
+The Microsoft Teams connector uses a webhook to send notifications.
 
 [float]
 [[teams-connector-configuration]]
@@ -13,8 +13,8 @@ The Microsoft Teams connector uses https://docs.microsoft.com/en-us/microsofttea
 
 Microsoft Teams connectors have the following configuration properties.
 
-Name::      The name of the connector. The name is used to identify a  connector in the management UI connector listing, or in the connector list when configuring an action.
+Name::      The name of the connector. The name is used to identify a connector in the management UI connector listing, or in the connector list when configuring an action.
-Webhook URL::   The URL of the incoming webhook. See https://docs.microsoft.com/en-us/microsoftteams/platform/webhooks-and-connectors/how-to/add-incoming-webhook#add-an-incoming-webhook-to-a-teams-channel[Add Incoming Webhooks] for instructions on generating this URL. If you are using the <<action-settings, `xpack.actions.allowedHosts`>> setting, make sure the hostname is added to the allowed hosts.
+Webhook URL::   The URL of the incoming webhook. Refer to <<configuring-teams>>. If you are using the <<action-settings, `xpack.actions.allowedHosts`>> setting, make sure the hostname is added to the allowed hosts.
 
 [float]
 [[teams-connector-networking-configuration]]
@@ -65,17 +65,38 @@ Message::   The message	text, converted to the `text` field in the Webhook JSON
 [[configuring-teams]]
 ==== Configure a Microsoft Teams account
 
-You need a https://docs.microsoft.com/en-us/microsoftteams/platform/webhooks-and-connectors/how-to/add-incoming-webhook[Microsoft Teams webhook URL] to 
+Microsoft 365 connectors are being https://devblogs.microsoft.com/microsoft365dev/retirement-of-office-365-connectors-within-microsoft-teams/[retired]; you must use the *Workflows* app to create a webhook URL.
-configure a Microsoft Teams action. To create a webhook
+For example:
-URL, add the **Incoming Webhook App** through the Microsoft Teams console:
 
-. Log in to http://teams.microsoft.com[teams.microsoft.com] as a team administrator.
+. Go to the *Workflows* app in Teams and select the *Create* tab.
-. Navigate to the Apps directory, search for and select the *Incoming Webhook* app.
+. Create a workflow from a blank template.
-. Choose _Add to team_ and select a team and channel for the app.
-. Enter a name for your webhook and (optionally) upload a custom icon.
 +
-image::images/teams-add-webhook-integration.png[]
+--
-. Click *Create*.
+NOTE: You cannot use the "Post to a channel when a webhook request is received" template; it does not work with the Microsoft Teams connector.
-. Copy the generated webhook URL so you can paste it into your Teams connector form.
+--
+. Add a trigger as the first step in the workflow. Search for webhook triggers and select *When a Teams webhook request is received*. Set *Who can trigger the flow?* to `Anyone`.
+. Add *Post message in a chat or channel* as the second step in the workflow.
+.. Set *Post as* to `Flow bot`.
+.. Set *Post in* to `Channel`.
+.. Set *Team* and *Channel* to the appropriate values for where you want the message displayed.
 +
-image::images/teams-copy-webhook-url.png[]
+--
+NOTE: Per https://learn.microsoft.com/en-us/power-automate/teams/send-a-message-in-teams#known-issues-and-limitations, you cannot use a private channel.
+--
+.. Set the *Message* to `@{triggerBody()?['text']}`.
++
+--
+Alternatively, you can add a *Parse JSON* step before the *Post message in a chat or channel* step in the workflow. Set the *Content* to `Body` and the *Schema* to the following value:
+
+```json
+{
+    "type": "object",
+    "properties": {
+        "text": {
+            "type": "string"
+        }
+    }
+}
+```
+--
+. Save the workflow and copy the HTTP POST URL from the first step. This is the URL required by the Microsoft Teams connector.