Merge pull request #259589 from MikeRayMSFT/20231127-arc-sql-naming

BULK UPDATE: Product name: SQL Server enabled by Azure Arc | Related content link

Author: v-regandowner

articles/azure-arc/data/about-arcdata-extension.md

@@ -29,6 +29,6 @@ To access the latest reference documentation:
 - [`sql instance-failover-group-arc`](/cli/azure/sql/instance-failover-group-arc)
 - [`az postgres server-arc`](/cli/azure/postgres/server-arc)
 
-## Next steps
+## Related content
 
 [Plan an Azure Arc-enabled data services deployment](plan-azure-arc-data-services.md)

articles/azure-arc/data/active-directory-introduction.md

@@ -11,11 +11,11 @@ ms.date: 10/11/2022
 ms.topic: how-to
 ---
 
-# Azure Arc-enabled SQL Managed Instance with Active Directory authentication 
+# SQL Managed Instance enabled by Azure Arc with Active Directory authentication 
 
-Azure Arc-enabled data services support Active Directory (AD) for Identity and Access Management (IAM). The Arc-enabled SQL Managed Instance uses an existing on-premises Active Directory (AD) domain for authentication. 
+Azure Arc-enabled data services support Active Directory (AD) for Identity and Access Management (IAM). SQL Managed Instance enabled by Azure Arc uses an existing on-premises Active Directory (AD) domain for authentication. 
 
-This article describes how to enable Azure Arc-enabled SQL Managed Instance with Active Directory (AD) Authentication. The article demonstrates two possible AD integration modes: 
+This article describes how to enable SQL Managed Instance enabled by Azure Arc with Active Directory (AD) Authentication. The article demonstrates two possible AD integration modes: 
 -  Customer-managed keytab (CMK) 
 -  Service-managed keytab (SMK)  
 
@@ -31,7 +31,7 @@ To enable Active Directory authentication for SQL Server on Linux and Linux cont
 - [Deploy a customer-managed keytab AD connector](deploy-customer-managed-keytab-active-directory-connector.md) or [Deploy a service-managed keytab AD connector](deploy-system-managed-keytab-active-directory-connector.md)
 - [Deploy SQL managed instances](deploy-active-directory-sql-managed-instance.md)
 
-The following diagram shows how to enable Active Directory authentication for Azure Arc-enabled SQL Managed Instance:
+The following diagram shows how to enable Active Directory authentication for SQL Managed Instance enabled by Azure Arc:
 
 ![Actice Directory Deployment User journey](media/active-directory-deployment/active-directory-user-journey.png)
 
@@ -40,13 +40,13 @@ The following diagram shows how to enable Active Directory authentication for Az
 
 In order to enable Active Directory authentication for SQL Managed Instance, the instance must be deployed in an environment that allows it to communicate with the Active Directory domain. 
 
-To facilitate this, Azure Arc-enabled data services introduces a new Kubernetes-native [Custom Resource Definition (CRD)](https://kubernetes.io/docs/concepts/extend-kubernetes/api-extension/custom-resources/) called `Active Directory Connector`. It provides Azure Arc-enabled SQL managed instances running on the same data controller the ability to perform Active Directory authentication.
+To facilitate this, Azure Arc-enabled data services introduces a new Kubernetes-native [Custom Resource Definition (CRD)](https://kubernetes.io/docs/concepts/extend-kubernetes/api-extension/custom-resources/) called `Active Directory Connector`. It provides instances running on the same data controller the ability to perform Active Directory authentication.
 
 ## Compare AD integration modes
 
 What is the difference between the two Active Directory integration modes?
 
-To enable Active Directory authentication for Arc-enabled SQL Managed Instance, you need an Active Directory connector where you specify the Active Directory integration deployment mode. The two Active Directory integration modes are:
+To enable Active Directory authentication for SQL Managed Instance enabled by Azure Arc, you need an Active Directory connector where you specify the Active Directory integration deployment mode. The two Active Directory integration modes are:
 
 - Customer-managed keytab
 - Service-managed keytab 
@@ -64,13 +64,13 @@ The following section compares these modes.
 
 For either mode, you need a specific Active Directory account, keytab, and Kubernetes secret for each SQL managed instance.
 
-## Enable Active Directory authentication in Arc-enabled SQL Managed Instance
+## Enable Active Directory authentication 
 
-When you deploy SQL Managed Instance with the intention to enable Active Directory authentication, the deployment needs to reference an Active Directory connector instance to use. Referencing the Active Directory connector in managed instance specification automatically sets up the needed environment in the SQL Managed Instance container for the managed instance to authenticate with Active Directory.
+When you deploy an instance with the intention to enable Active Directory authentication, the deployment needs to reference an Active Directory connector instance to use. Referencing the Active Directory connector in managed instance specification automatically sets up the needed environment in instance container to authenticate with Active Directory.
 
-## Next steps
+## Related content
 
 * [Deploy a customer-managed keytab Active Directory (AD) connector](deploy-customer-managed-keytab-active-directory-connector.md)
 * [Deploy a system-managed keytab Active Directory (AD) connector](deploy-system-managed-keytab-active-directory-connector.md)
-* [Deploy an Azure Arc-enabled SQL Managed Instance in Active Directory (AD)](deploy-active-directory-sql-managed-instance.md)
-* [Connect to Azure Arc-enabled SQL Managed Instance using Active Directory authentication](connect-active-directory-sql-managed-instance.md)
+* [Deploy SQL Managed Instance enabled by Azure Arc in Active Directory (AD)](deploy-active-directory-sql-managed-instance.md)
+* [Connect to SQL Managed Instance enabled by Azure Arc using Active Directory authentication](connect-active-directory-sql-managed-instance.md)

articles/azure-arc/data/active-directory-prerequisites.md

@@ -11,7 +11,7 @@ ms.date: 10/11/2022
 ms.topic: how-to
 ---
 
-# Azure Arc-enabled SQL Managed Instance in Active Directory authentication with system-managed keytab - prerequisites
+# SQL Server enabled by Azure Arc in Active Directory authentication with system-managed keytab - prerequisites
 
 This document explains how to prepare to deploy Azure Arc-enabled data services with Active Directory (AD) authentication. Specifically the article describes Active Directory objects you need to configure before the deployment of Kubernetes resources.
 
@@ -137,9 +137,9 @@ Whether you have created a new account for the DSA or are using an existing Acti
 
 - Select **OK** twice more to close open dialog boxes.
 
-## Next steps
+## Related content
 
 * [Deploy a customer-managed keytab Active Directory (AD) connector](deploy-customer-managed-keytab-active-directory-connector.md)
 * [Deploy a system-managed keytab Active Directory (AD) connector](deploy-system-managed-keytab-active-directory-connector.md)
-* [Deploy an Azure Arc-enabled SQL Managed Instance in Active Directory (AD)](deploy-active-directory-sql-managed-instance.md)
-* [Connect to Azure Arc-enabled SQL Managed Instance using Active Directory authentication](connect-active-directory-sql-managed-instance.md)
+* [Deploy a SQL Managed Instance enabled by Azure Arc in Active Directory (AD)](deploy-active-directory-sql-managed-instance.md)
+* [Connect to SQL Managed Instance enabled by Azure Arc using Active Directory authentication](connect-active-directory-sql-managed-instance.md)

articles/azure-arc/data/automated-integration-testing.md

@@ -15,7 +15,7 @@ ms.custom: template-tutorial
 
 # Tutorial: Automated validation testing
 
-As part of each commit that builds up Arc-enabled data services, Microsoft runs automated CI/CD pipelines that perform end-to-end tests. These tests are orchestrated via two containers that are maintained alongside the core-product (Data Controller, Azure Arc-enabled SQL Managed Instance & PostgreSQL server). These containers are:
+As part of each commit that builds up Arc-enabled data services, Microsoft runs automated CI/CD pipelines that perform end-to-end tests. These tests are orchestrated via two containers that are maintained alongside the core-product (Data Controller, SQL Managed Instance enabled by Azure Arc & PostgreSQL server). These containers are:
 
 - `arc-ci-launcher`: Containing deployment dependencies (for example, CLI extensions), as well product deployment code (using Azure CLI) for both Direct and Indirect connectivity modes. Once Kubernetes is onboarded with the Data Controller, the container leverages [Sonobuoy](https://sonobuoy.io/) to trigger parallel integration tests.
 -  `arc-sb-plugin`: A [Sonobuoy plugin](https://sonobuoy.io/plugins/) containing [Pytest](https://docs.pytest.org/en/7.1.x/)-based end-to-end integration tests, ranging from simple smoke-tests (deployments, deletes), to complex high-availability scenarios, chaos-tests (resource deletions) etc.
@@ -499,7 +499,7 @@ kubectl delete -k arc_data_services/test/launcher/overlays/aks
 
 This cleans up the resource manifests deployed as part of the launcher.
 
-## Next steps
+## Related content
 
 > [!div class="nextstepaction"]
 > [Pre-release testing](preview-testing.md)

articles/azure-arc/data/azure-data-studio-dashboards.md

@@ -91,6 +91,6 @@ The **Diagnose and solve problems** tab on the left, launches the PostgreSQL tro
 
 For Azure support, select the **New support request** tab. This launches the Azure portal in context to the server group. Create an Azure support request from there.
 
-## Next steps
+## Related content
 
 - [View SQL Managed Instance in the Azure portal](view-arc-data-services-inventory-in-azure-portal.md)

articles/azure-arc/data/backup-controller-database.md

@@ -16,7 +16,7 @@ ms.topic: how-to
 When you deploy Azure Arc data services, the Azure Arc Data Controller is one of the most critical components that is deployed. The functions of the  data controller include:
 
 - Provision, de-provision and update resources
-- Orchestrate most of the activities for Azure Arc-enabled SQL Managed Instance such as upgrades, scale out etc. 
+- Orchestrate most of the activities for SQL Managed Instance enabled by Azure Arc such as upgrades, scale out etc. 
 - Capture the billing and usage information of each Arc SQL managed instance. 
 
 In order to perform above functions, the Data controller needs to store an inventory of all the current Arc SQL managed instances, billing, usage and the current state of all these SQL managed instances. All this data is stored  in a database called `controller` within the SQL Server instance that is deployed into the `controldb-0` pod. 
@@ -253,6 +253,6 @@ Follow these steps to restore the controller database from a backup with new sto
 
 16. Scale the controller ReplicaSet back up to 1 replica using the `kubectl scale` command.
 
-## Next steps
+## Related content
 
 [Azure Data Studio dashboards](azure-data-studio-dashboards.md)

articles/azure-arc/data/backup-restore-postgresql.md

@@ -35,7 +35,7 @@ Update the backup retention period for an Azure Arc-enabled PostgreSQL server:
 az postgres server-arc update -n pg01 -k test --retention-days <number of days> --use-k8s 
 ```
 
-## Next steps
+## Related content
 
 - [Restore Azure Arc-enabled PostgreSQL servers](restore-postgresql.md)
 - [Scaling up or down (increasing/decreasing memory/vcores)](scale-up-down-postgresql-server-using-cli.md) your server.

articles/azure-arc/data/change-postgresql-port.md

@@ -61,6 +61,6 @@ In addition, note the value for `primaryEndpoint`.
 "primaryEndpoint": "12.345.67.890:866",
 ```
 
-## Next steps
+## Related content
 - Read about [how to connect to your server group](get-connection-endpoints-and-connection-strings-postgresql-server.md).
 - Read about how you can configure other aspects of your server group in the section How-to\Manage\Configure & scale section of the documentation.

articles/azure-arc/data/clean-up-past-installation.md

@@ -82,8 +82,8 @@ kubectl delete apiservice v1.sql.arcdata.microsoft.com
 kubectl delete mutatingwebhookconfiguration arcdata.microsoft.com-webhook-{namespace}
 ```
 
-## Next steps
+## Related content
 
 [Start by creating a Data Controller](create-data-controller-indirect-cli.md)
 
-Already created a Data Controller? [Create an Azure Arc-enabled SQL Managed Instance](create-sql-managed-instance.md)
+Already created a Data Controller? [Create a SQL Managed Instance enabled by Azure Arc](create-sql-managed-instance.md)

articles/azure-arc/data/configure-managed-instance.md

@@ -1,6 +1,6 @@
 ---
-title: Configure Azure Arc-enabled SQL managed instance
-description: Configure Azure Arc-enabled SQL managed instance
+title: Configure SQL Managed Instance enabled by Azure Arc
+description: Configure SQL Managed Instance enabled by Azure Arc
 services: azure-arc
 ms.service: azure-arc
 ms.subservice: azure-arc-data-sqlmi
@@ -12,22 +12,22 @@ ms.date: 05/05/2023
 ms.topic: how-to
 ---
 
-# Configure Azure Arc-enabled SQL managed instance
+# Configure SQL Managed Instance enabled by Azure Arc
 
-This article explains how to configure Azure Arc-enabled SQL managed instance.
+This article explains how to configure SQL Managed Instance enabled by Azure Arc.
 
 ## Configure resources such as cores, memory
 
 
 ### Configure using CLI
 
-You can update the configuration of Azure Arc-enabled SQL Managed Instances with the CLI. Run the following command to see configuration options. 
+To update the configuration of an instance with the CLI. Run the following command to see configuration options. 
 
 ```azurecli
 az sql mi-arc update --help
 ```
 
-You can update the available memory and cores for an Azure Arc-enabled SQL managed instance using the following command:
+To update the available memory and cores for an instance use:
 
 ```azurecli
 az sql mi-arc update --cores-limit 4 --cores-request 2 --memory-limit 4Gi --memory-request 2Gi -n <NAME_OF_SQL_MI> --k8s-namespace <namespace> --use-k8s
@@ -39,7 +39,7 @@ The following example sets the cpu core and memory requests and limits.
 az sql mi-arc update --cores-limit 4 --cores-request 2 --memory-limit 4Gi --memory-request 2Gi -n sqlinstance1 --k8s-namespace arc --use-k8s
 ```
 
-To view the changes made to the Azure Arc-enabled SQL managed instance, you can use the following commands to view the configuration yaml file:
+To view the changes made to the instance, you can use the following commands to view the configuration yaml file:
 
 ```azurecli
 az sql mi-arc show -n <NAME_OF_SQL_MI> --k8s-namespace <namespace> --use-k8s
@@ -80,7 +80,7 @@ az sql mi-arc update --name sqlmi1 --replicas 2 --k8s-namespace mynamespace --us
 
 ## Configure Server options
 
-You can configure certain server configuration settings for Azure Arc-enabled SQL managed instance either during or after creation time. This article describes how to configure settings like enabling "Ad Hoc Distributed Queries" or "backup compression default" etc. 
+You can configure certain server configuration settings for SQL Managed Instance enabled by Azure Arc either during or after creation time. This article describes how to configure settings like enabling "Ad Hoc Distributed Queries" or "backup compression default" etc. 
 
 Currently the following server options can be configured:
 - Ad Hoc Distributed Queries