From 42c44a8bdde2809013be50124f2521e2d3450eee Mon Sep 17 00:00:00 2001
From: Adam Locke <adam.locke@elastic.co>
Date: Fri, 29 Oct 2021 11:55:57 -0400
Subject: [PATCH 1/2] [DOCS] Add system indices deprecation

---
 .../reference/migration/migrate_7_16.asciidoc | 29 +++++++++++++++++--
 1 file changed, 27 insertions(+), 2 deletions(-)

diff --git a/docs/reference/migration/migrate_7_16.asciidoc b/docs/reference/migration/migrate_7_16.asciidoc
index 1e4d6dbcffe82..bde9b7731fdbe 100644
--- a/docs/reference/migration/migrate_7_16.asciidoc
+++ b/docs/reference/migration/migrate_7_16.asciidoc
@@ -10,10 +10,12 @@ your application to {es} 7.16.
 See also <<release-highlights>> and <<es-release-notes>>.
 
 * <<breaking_716_settings_changes>>
+* <<breaking_716_tls_changes>>
 * <<breaking_716_ilm_changes>>
 * <<breaking_716_monitoring_changes>>
-
 * <<breaking_716_settings_deprecations>>
+* <<breaking_716_indices_deprecations>>
+* <<breaking_716_cluster_deprecations>>
 
 //NOTE: The notable-breaking-changes tagged regions are re-used in the
 //Installation and Upgrade Guide
@@ -296,6 +298,29 @@ your cluster settings through the `PUT _cluster/settings` REST API. When modifyi
 use only persistent settings.
 ====
 
+[discrete]
+[[breaking_716_indices_deprecations]]
+==== Indices deprecations
+
+[[deprecation-system-indices]]
+.Direct access to system indices is deprecated.
+[%collapsible]
+====
+*Details* +
+Directly accessing system indices is deprecated. In {es} 8.0, you must add the
+`allow_restricted_indices` permission set to `true` on a user role to access
+system indices. Refer to 
+{ref}/defining-roles.html#roles-indices-priv[indices privileges] for
+information on adding this permission to an index privilege.
+
+*Impact* +
+Accessing system indices directly results in warnings in the header of API 
+responses. Use {kib} or the associated feature's {es} APIs to manage the data 
+that you want to access. While it's still possible to access system indices in
+{es} 7.16, they are reserved only for internal use by Elastic products and
+should not be accessed directly.
+====
+
 [discrete]
 [[breaking_716_cluster_deprecations]]
 ==== Cluster deprecations
@@ -322,7 +347,7 @@ parameter `?return_200_for_cluster_health_timeout` in your request.
 ====
 
 [[script-context-cache-deprecated]]
-.The script context cache is deprecated
+.The script context cache is deprecated.
 [%collapsible]
 ====
 *Details* +

From b013970a0f1ca827da6e7ee9dbdcad0bb74ede8f Mon Sep 17 00:00:00 2001
From: Adam Locke <adam.locke@elastic.co>
Date: Tue, 2 Nov 2021 14:31:20 -0400
Subject: [PATCH 2/2] Clarify impact on deprecation log

---
 docs/reference/migration/migrate_7_16.asciidoc | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/docs/reference/migration/migrate_7_16.asciidoc b/docs/reference/migration/migrate_7_16.asciidoc
index bde9b7731fdbe..e05e39d94de5d 100644
--- a/docs/reference/migration/migrate_7_16.asciidoc
+++ b/docs/reference/migration/migrate_7_16.asciidoc
@@ -315,10 +315,10 @@ information on adding this permission to an index privilege.
 
 *Impact* +
 Accessing system indices directly results in warnings in the header of API 
-responses. Use {kib} or the associated feature's {es} APIs to manage the data 
-that you want to access. While it's still possible to access system indices in
-{es} 7.16, they are reserved only for internal use by Elastic products and
-should not be accessed directly.
+responses and in the deprecation logs. Use {kib} or the associated feature's
+{es} APIs to manage the data that you want to access. While it's still possible 
+to access system indices in {es} 7.16, they are reserved only for internal use
+by Elastic products and should not be accessed directly.
 ====
 
 [discrete]