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/migration/migrate_8_0.asciidoc
+6Lines changed: 6 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -36,6 +36,12 @@ for example, `logstash-*`.
36
36
=== Settings changes
37
37
38
38
// tag::notable-breaking-changes[]
39
+
[float]
40
+
==== Multitenancy by changing `kibana.index` is no longer supported
41
+
*Details:* `kibana.index`, `xpack.reporting.index` and `xpack.task_manager.index` can no longer be specified.
42
+
43
+
*Impact:* Users who relied on changing these settings to achieve multitenancy should use *Spaces*, cross-cluster replication, or cross-cluster search instead. To migrate to *Spaces*, users are encouraged to use saved object management to export their saved objects from a tenant into the default tenant in a space. Improvements are planned to improve on this workflow. See https://github.com/elastic/kibana/issues/82020 for more details.
44
+
39
45
[float]
40
46
==== Legacy browsers are now rejected by default
41
47
*Details:* `csp.strict` is now enabled by default, so Kibana will fail to load for older, legacy browsers that do not enforce basic Content Security Policy protections - notably Internet Explorer 11.
The Microsoft Teams action type uses https://docs.microsoft.com/en-us/microsoftteams/platform/webhooks-and-connectors/how-to/add-incoming-webhook[Incoming Webhooks].
6
+
7
+
[float]
8
+
[[teams-connector-configuration]]
9
+
==== Connector configuration
10
+
11
+
Microsoft Teams connectors have the following configuration properties:
12
+
13
+
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.
14
+
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.
`config` defines the action type specific to the configuration.
30
+
`config` contains
31
+
`webhookUrl`, a string that corresponds to *Webhook URL*.
32
+
33
+
34
+
[float]
35
+
[[teams-action-configuration]]
36
+
==== Action configuration
37
+
38
+
Microsoft Teams actions have the following properties:
39
+
40
+
Message:: The message text, converted to the `text` field in the Webhook JSON payload. Currently only the text field is supported. Markdown, images, and other advanced formatting are not yet supported.
41
+
42
+
[[configuring-teams]]
43
+
==== Configuring Microsoft Teams Accounts
44
+
45
+
You need a https://docs.microsoft.com/en-us/microsoftteams/platform/webhooks-and-connectors/how-to/add-incoming-webhook[Microsoft Teams webhook URL] to
46
+
configure a Microsoft Teams action. To create a webhook
47
+
URL, add the **Incoming Webhook App** through the Microsoft Teams console:
48
+
49
+
. Log in to http://teams.microsoft.com[teams.microsoft.com] as a team administrator.
50
+
. Navigate to the Apps directory, search for and select the *Incoming Webhook* app.
51
+
. Choose _Add to team_ and select a team and channel for the app.
52
+
. Enter a name for your webhook and (optionally) upload a custom icon.
53
+
+
54
+
image::images/teams-add-webhook-integration.png[]
55
+
. Click *Create*.
56
+
. Copy the generated webhook URL so you can paste it into your Teams connector form.
0 commit comments