Merge branch 'main' into autoops-react-updates

Author: wajihaparvez

deploy-manage/security/_snippets/private-connectivity-limitations-ech.md

@@ -1,7 +1,7 @@
 * **Transport client:** The {{es}} transport client is not supported over private connections.
 * **Managed OTLP endpoint:** In {{ech}} deployments, the [managed OTLP endpoint](opentelemetry://reference/motlp.md) is not accessible over private connections. The public endpoint is still available.
-* **SSO to {{kib}} from the {{ecloud}} console:** You can't use SSO to log in to {{kib}} endpoints that are protected by private connections. The connection to {{kib}} public URL is still available.
+* **SSO to {{kib}} from the {{ecloud}} console:** In {{ech}} deployments, you can't use SSO to log in to {{kib}} endpoints that are protected by private connections. The connection to the {{kib}} public URL is still available. In {{serverless-full}}, this limitation does not apply.
 
   As a workaround, you can [add an IP filter](/deploy-manage/security/ip-filtering-cloud.md) for the hosts that will use SSO through the {{ecloud}} console.
 
-  In {{ech}}, you can still SSO into private {{kib}} endpoints individually using the [SAML](/deploy-manage/users-roles/cluster-or-deployment-auth/saml.md) or [OIDC](/deploy-manage/users-roles/cluster-or-deployment-auth/openid-connect.md) protocol from your own identity provider, just not through the {{ecloud}} console. Stack-level authentication using the {{es}} username and password also works with `{{kibana-id}}.vpce.{region}.aws.elastic-cloud.com` URLs.
+  In {{ech}}, you can still SSO into private {{kib}} endpoints individually using the [SAML](/deploy-manage/users-roles/cluster-or-deployment-auth/saml.md) or [OIDC](/deploy-manage/users-roles/cluster-or-deployment-auth/openid-connect.md) protocol from your own identity provider, just not through the {{ecloud}} console. Stack-level authentication using the {{es}} username and password also works with `{{kibana-id}}.vpce.{region}.aws.elastic-cloud.com` URLs.

explore-analyze/find-and-organize/data-views.md

@@ -28,6 +28,8 @@ In certain apps, you can also query your {{es}} data using [{{esql}}](elasticsea
 * If a read-only indicator appears, you have insufficient privileges to create or save {{data-sources}}. In addition, the buttons to create {{data-sources}} or save existing {{data-sources}} are not visible.
 * {applies_to}`stack: ga 9.2` Some data views are exclusively configured and **managed** by Elastic. You can view and use these managed data views, but you can't edit them. If you'd like to use a modified version of a managed data view, you can [duplicate it](#duplicate-managed-data-view) and edit that new copy as needed.
 
+  {applies_to}`stack: ga 9.4` You also can't delete a managed data view.
+
 
 ## Create a data view [settings-create-pattern]
 
@@ -170,6 +172,8 @@ To restrict a {{data-source}} to specific projects regardless of the active scop
 
 When you delete a {{data-source}}, you cannot recover the associated field formatters, runtime fields, source filters, and field popularity data. Deleting a {{data-source}} does not remove any indices or data documents from {{es}}.
 
+{applies_to}`stack: ga 9.4` You can't delete managed data views. On the **Data Views** management page, the delete action isn't available for these data views, and they can't be selected for bulk deletion. To use a modified version of a managed data view, [duplicate it](#duplicate-managed-data-view) instead.
+
 ::::{warning}
 Deleting a {{data-source}} breaks all visualizations, saved Discover sessions, and other saved objects that reference the data view.
 ::::