Update support policy information

Author: MikeRayMSFT

articles/azure-arc/data/includes/upgrade-supported-path.md

@@ -12,33 +12,31 @@ ms.author: "dinethi"
 ---
 # Azure Arc-enabled data services support policy. 
 
-This article explains the support policy for Azure Arc-enabled data services.
+This article describes the support policies and troubleshooting boundaries for Azure Arc-enabled data services. This article specifically explains support for Azure Arc data controller and Azure Arc-enabled SQL Managed Instance.
 
 ## Support policy
 - Azur Arc-enabled data services follows [Microsoft Modern Lifecycle Policy](https://support.microsoft.com/help/30881/modern-lifecycle-policy).
 - Read the original [Modern Lifecycle Policy announcement](https://support.microsoft.com/help/447912/announcing-microsoft-modern-lifecycle-policy).
 - For additional information, see [Modern Policy FAQs](https://support.microsoft.com/help/30882/modern-lifecycle-policy-faq).
 
-## Supported updates
+## Support versions
 
-Microsoft supports Azure Arc-enabled data services for one year from the date of the release. This support applies to the data controller, and any supported data services. For example, this support also applies to Azure Arc-enabled SQL Managed Instance.
+Microsoft supports Azure Arc-enabled data services for one year from the date of the release. This support applies to the data controller, and any supported data services. For example, this support also applies to Azure Arc-enabled SQL Managed Instance. 
+
+For descriptions, and instructions on how to identify a version release date, see [Supported versions](upgrade-overview.md#supported-versions). 
 
 Microsoft releases new versions periodically. [Version log](version-log.md) shows the history of releases.
 
-Each release contains an image tag. Use the image tag to identify when Microsoft released the component. Microsoft supports the component for 1 full year after the release.
+To plan updates, see [Upgrade Azure Arc-enabled data services](upgrade-overview.md).
 
-### Example
+## Support by components
 
-For example, a complete image tag for the release in June, 2022 is: `v1.8.0_2022-06-1`.
+Microsoft supports Azure Arc-enabled data services, including the data controller, and the data services (like Azure Arc-enabled SQL Managed Instance) that we provide. Data services requires a Kubernetes distribution deployed in a customer operated environment. Microsoft does not provide support for the Kubernetes distribution. Support for the environment and hardware that hosts Kubernetes is provided by the operator of the environment and hardware.
 
-The image tag follows this pattern, *\<version\>_\<date\>-#*.  
-- \<version\> identifies the data services major and minor version numbers. The pattern is: **v**#.#.#
-- \<date\> identifies the year, month, and day of the release. The pattern is: YYYY-MM-DD-#. 
-- -# identifies an internal build number.
+Microsoft has worked with industry partners to validate specific distributions for Azure Arc-enabled data services. You can see a list of partners and validated solutions in [Azure Arc-enabled data services Kubernetes validation](validation-program.md).
 
-The example image released on June 6th, 2022. 
+Microsoft recommends that you run Azure Arc-enabled data services on a validated solution.
 
-Microsoft supports this release through June 5th, 2023.
+## See also
 
-> [!NOTE]
-> The latest current branch version is always in the **Full Support** servicing phase. This support statement means that if you encounter a code defect that warrants a critical update, you must have the latest current branch version installed in order to receive a fix.
+[SQL Server running in Linux containers](/troubleshoot/sql/general/support-policy-sql-server)

articles/azure-arc/data/support-policy.md

@@ -98,6 +98,8 @@ items:
           href: update-service-principal-credentials.md
     - name: Upgrade
       items:
+        - name: Overview
+          href: upgrade-overview.md
         - name: Indirect connectivity mode
           items:
             - name: Data controller indirect - CLI

articles/azure-arc/data/toc.yml

@@ -64,8 +64,7 @@ This section shows how to upgrade a directly connected data controller.
 > To upgrade, delete all non-GA database instances. You can find the list of generally available 
 > and preview services in the [Release Notes](./release-notes.md).
 
-[!INCLUDE [upgrade-supported-path](includes/upgrade-supported-path.md)]
-
+For supported upgrade paths, see [Upgrade Azure Arc-enabled data services](upgrade-overview.md).
 
 ### Authenticate  
 

articles/azure-arc/data/upgrade-data-controller-direct-cli.md

@@ -37,7 +37,7 @@ This section shows how to upgrade a directly connected data controller.
 > To upgrade, delete all non-GA database instances. You can find the list of generally available 
 > and preview services in the [Release Notes](./release-notes.md).
 
-[!INCLUDE [upgrade-supported-path](includes/upgrade-supported-path.md)]
+For supported upgrade paths, see [Upgrade Azure Arc-enabled data services](upgrade-overview.md).
 
 
 ### Upgrade

articles/azure-arc/data/upgrade-data-controller-direct-portal.md

@@ -64,7 +64,7 @@ This section shows how to upgrade an indirectly connected data controller.
 > To upgrade, delete all non-GA database instances. You can find the list of generally available 
 > and preview services in the [Release Notes](./release-notes.md).
 
-[!INCLUDE [upgrade-supported-path](includes/upgrade-supported-path.md)]
+For supported upgrade paths, see [Upgrade Azure Arc-enabled data services](upgrade-overview.md).
 
 
 ### Upgrade

articles/azure-arc/data/upgrade-data-controller-indirect-cli.md

@@ -73,7 +73,7 @@ This section shows how to upgrade an indirectly connected data controller.
 > To upgrade, delete all non-GA database instances. You can find the list of generally available 
 > and preview services in the [Release Notes](./release-notes.md).
 
-[!INCLUDE [upgrade-supported-path](includes/upgrade-supported-path.md)]
+For supported upgrade paths, see [Upgrade Azure Arc-enabled data services](upgrade-overview.md).
 
 
 ### Upgrade

articles/azure-arc/data/upgrade-data-controller-indirect-kubernetes-tools.md

@@ -0,0 +1,85 @@
+---
+title: Overview - upgrade Azure Arc-enabled data services
+description: Explains how to upgrade Azure Arc-enabled data controller, and other data services.
+services: azure-arc
+ms.service: azure-arc
+ms.subservice: azure-arc-data
+author: dnethi
+ms.author: dinethi
+ms.reviewer: mikeray
+ms.date: 08/15/2022
+ms.topic: conceptual
+---
+
+# Upgrade Azure Arc-enabled data services
+
+This article describes the paths and options to upgrade Azure Arc-enabled data controller and data services.
+
+## Supported versions
+
+Each release contains an image tag. Use the image tag to identify when Microsoft released the component. Microsoft supports the component for 1 full year after the release. 
+
+Identify your current version by image tag. The image tag version scheme is:
+- `<Major>.<Minor>.<optional:revision>_<date>`.
+- `<date>` identifies the year, month, and day of the release. The pattern is: YYYY-MM-DD. 
+
+For example, a complete image tag for the release in June, 2022 is: `v1.8.0_2022-06-06`.
+
+The example image released on June 6th, 2022. 
+
+Microsoft supports this release through June 5th, 2023.
+
+> [!NOTE]
+> The latest current branch version is always in the **Full Support** servicing phase. This support statement means that if you encounter a code defect that warrants a critical update, you must have the latest current branch version installed in order to receive a fix.
+
+## Upgrade path
+
+Upgrades are limited to the next incremental minor or major version. For example:
+
+- Supported version upgrades:
+    - 1.1 -> 1.2
+    - 1.3 -> 2.0
+- Unsupported version upgrades:
+    - 1.1 -> 1.4 Not supported because one or more minor versions are skipped.
+
+## Upgrade order
+
+Upgrade the data controller before you upgrade any data service. Azure Arc-enabled SQL Managed Instance is an example of a data service.
+
+A data controller may be up to one version ahead of a data service. A data service major version may not be one version ahead, or more than one version behind a data controller. 
+
+The following list displays supported and unsupported configurations, based on image tag.
+
+- Supported configurations.
+   - Data controller and data service at same version:
+      - Data controller: `v1.9.0_2022-07-12`
+      - Data service: `v1.9.0_2022-07-12`
+   - Data controller ahead of data service by one version:
+      - Data controller: `v1.9.0_2022-07-12`
+      - Data service: `v1.8.0_2022-06-14`
+
+- Unsupported configurations:
+   - Data controller behind data service:
+      - Data controller: `v1.8.0_2022-06-14`
+      - Data service: `v1.9.0_2022-07-12`
+   - Data controller ahead of data service by more than one version:
+      - Data controller: `v1.9.0_2022-07-12`
+      - Data service: `v1.6.0_2022-05-02`
+
+## Schedule maintenance
+
+The upgrade will cause a service interruption (downtime).
+
+The amount of time to upgrade the data service depends on the service tier.
+
+The data controller upgrade does not cause application downtime. 
+
+- General Purpose: A single replica is not available during the upgrade.
+- Business Critical: A SQL managed instance incurs a brief service interruption (downtime) once during an upgrade. After the data controller upgrades a secondary replicas, the service fails over to an upgraded replica. The controller then upgrades the previous primary replica.
+
+> [!TIP]
+> Upgrade the data services during scheduled maintenance time. 
+
+### Automatic upgrades
+
+When a SQL managed instance `desiredVersion` is set to `auto`, the data controller will automatically upgrade the managed instance.