Unhide private preview

Author: wajihaparvez

deploy-manage/monitor/autoops/cc-autoops-as-cloud-connected.md

@@ -4,7 +4,7 @@ applies_to:
     self:
     ece:
     eck:
-navigation_title: AutoOps for self-managed clusters
+navigation_title: For self-managed clusters
 products:
   - id: cloud-kubernetes
   - id: cloud-enterprise

deploy-manage/monitor/autoops/ec-autoops-faq.md

@@ -12,6 +12,7 @@ products:
   - id: cloud-hosted
   - id: cloud-kubernetes
   - id: cloud-enterprise
+navigation_title: FAQ
 ---
 
 # AutoOps FAQ [ec-autoops-faq]
@@ -22,7 +23,10 @@ $$$faq-what-is-autoops$$$What does AutoOps do?
 :   AutoOps for {{es}} significantly simplifies cluster management with performance recommendations, resource utilization and cost insights, real-time issue detection and resolution paths. By analyzing hundreds of {{es}} metrics, your configuration, and usage patterns, AutoOps recommends operational and monitoring insights that deliver savings in administration time and hardware costs.
 
 $$$faq-autoops-deployment-types$$$Is AutoOps available in all types of deployments?
-:   AutoOps is available in all {{ech}} deployments and {{serverless-full}} projects, and can be set up for ECE, ECK, and self-managed clusters.
+:   In the [regions](ec-autoops-regions.md) where it has been rolled out, AutoOps is automatically available in [{{ech}} deployments](/deploy-manage/monitor/autoops/ec-autoops-how-to-access.md) and {{serverless-full}} projects, and can be [set up](/deploy-manage/monitor/autoops/cc-connect-self-managed-to-autoops.md) for ECE, ECK, and self-managed clusters.
+
+$$$faq-autoops-regions$$$Why can't I see AutoOps in some deployments?
+:   AutoOps is rolling out in phases across CSPs and [regions](ec-autoops-regions.md), so you may not see it if your deployment is in a region where AutoOps is not available yet. 
 
 $$$faq-autoops-monitoring$$$Does AutoOps monitor the entire {{stack}}?
 :   AutoOps is currently limited to {{es}} (not {{kib}}, Logstash, and Beats).
@@ -35,9 +39,6 @@ $$$faq-autoops-license$$$How is AutoOps currently licensed?
     :::{include} /deploy-manage/_snippets/autoops-cc-payment-faq.md
     ::: 
 
-$$$faq-autoops-installation$$$How does AutoOps get installed and why may I not see AutoOps available on specific deployments?
-:   AutoOps is automatically available in {{es}} clusters on {{ecloud}} and can be [set up](/deploy-manage/monitor/autoops/cc-connect-self-managed-to-autoops.md) for ECE, ECK, and self-managed clusters. AutoOps is rolling out in phases across CSPs and [regions](ec-autoops-regions.md), so you may not see it if your deployment is in a region where AutoOps is not available yet. 
-
 $$$faq-autoops-issue-resolution$$$Can AutoOps currently automatically resolve issues?
 :   AutoOps only analyzes metrics, and is a read-only solution.
 

deploy-manage/monitor/autoops/ec-autoops-how-to-access.md

@@ -6,14 +6,14 @@ applies_to:
     ess: all
 products:
   - id: cloud-hosted
+navigation_title: For {{ech}}
 ---
 
-# How to access AutoOps [ec-autoops-how-to-access]
+# AutoOps for {{ech}}
 
-::::{note}
-AutoOps supports {{es}} versions according to the [supported {{stack}} versions](https://www.elastic.co/support/eol).
-::::
+AutoOps is available in all {{ech}} deployments in supported [regions](ec-autoops-regions.md#autoops-for-ech-regions). More regions are coming soon. 
 
+## How to access AutoOps [ec-autoops-how-to-access]
 
 To access AutoOps from your {{ecloud}} console, follow these steps:
 

deploy-manage/toc.yml

@@ -657,12 +657,20 @@ toc:
           - file: remote-clusters/remote-clusters-migrate.md
           - file: remote-clusters/remote-clusters-settings.md
       - file: remote-clusters/eck-remote-clusters.md
-  - hidden: cloud-connect.md
+  - file: cloud-connect.md
   - file: monitor.md
     children:
       - file: monitor/autoops.md
         children:
           - file: monitor/autoops/ec-autoops-how-to-access.md
+          - file: monitor/autoops/cc-autoops-as-cloud-connected.md
+            children: 
+            - file: monitor/autoops/cc-connect-self-managed-to-autoops.md
+            - file: monitor/autoops/cc-connect-local-dev-to-autoops.md
+            - file: monitor/autoops/cc-manage-users.md
+            - file: monitor/autoops/cc-cloud-connect-autoops-faq.md
+            - file: monitor/autoops/cc-cloud-connect-autoops-troubleshooting.md
+          - file: monitor/autoops/ec-autoops-regions.md
           - file: monitor/autoops/ec-autoops-events.md
             children:
               - file: monitor/autoops/ec-autoops-event-settings.md
@@ -676,14 +684,7 @@ toc:
               - file: monitor/autoops/ec-autoops-shards-view.md
               - file: monitor/autoops/ec-autoops-template-optimizer.md
           - hidden: monitor/autoops/ec-autoops-dismiss-event.md
-          - file: monitor/autoops/ec-autoops-regions.md
           - file: monitor/autoops/ec-autoops-faq.md
-          - hidden: monitor/autoops/cc-autoops-as-cloud-connected.md
-          - hidden: monitor/autoops/cc-connect-self-managed-to-autoops.md
-          - hidden: monitor/autoops/cc-connect-local-dev-to-autoops.md
-          - hidden: monitor/autoops/cc-manage-users.md
-          - hidden: monitor/autoops/cc-cloud-connect-autoops-faq.md
-          - hidden: monitor/autoops/cc-cloud-connect-autoops-troubleshooting.md
       - file: monitor/stack-monitoring.md
         children:
           - file: monitor/stack-monitoring/ece-ech-stack-monitoring.md