Merge pull request #115174 from MashaMSFT/move7

Move7

Author: rmca14

.openpublishing.redirection.json

@@ -52446,6 +52446,81 @@
             "source_path": "articles/sql-database/sql-database-file-space-management.md",
             "redirect_url": "/azure/azure-sql/database/file-space-manage",
             "redirect_document_id": true
+        },
+        {
+            "source_path": "articles/sql-database/sql-database-firewall-configure.md",
+            "redirect_url": "/azure/azure-sql/database/firewall-configure",
+            "redirect_document_id": true
+        },
+        {
+            "source_path": "articles/sql-database/sql-database-gateway-migration.md",
+            "redirect_url": "/azure/azure-sql/database/gateway-migration",
+            "redirect_document_id": true
+        },
+        {
+            "source_path": "articles/sql-database/sql-database-get-started-sql-data-sync.md",
+            "redirect_url": "/azure/azure-sql/database/data-sync-sql-server-configure",
+            "redirect_document_id": true
+        },
+        {
+            "source_path": "articles/sql-database/sql-database-howto-single-database.md",
+            "redirect_url": "/azure/azure-sql/database/how-to-content-reference-guide",
+            "redirect_document_id": true
+        },
+        {
+            "source_path": "articles/sql-database/sql-database-hyperscale-performance-diagnostics.md",
+            "redirect_url": "/azure/azure-sql/database/hyperscale-performance-diagnostics",
+            "redirect_document_id": true
+        },
+        {
+            "source_path": "articles/sql-database/sql-database-implement-geo-distributed-database.md",
+            "redirect_url": "/azure/azure-sql/database/tutorial-geo-distributed-application-configure",
+            "redirect_document_id": true
+        },
+        {
+            "source_path": "articles/sql-database/sql-database-insights-alerts-portal.md",
+            "redirect_url": "/azure/azure-sql/database/alerts-insights-configure-portal",
+            "redirect_document_id": true
+        },
+        {
+            "source_path": "articles/sql-database/sql-database-long-term-backup-retention-configure.md",
+            "redirect_url": "/azure/azure-sql/database/long-term-backup-retention-configure",
+            "redirect_document_id": true
+        },
+        {
+            "source_path": "articles/sql-database/sql-database-long-term-retention.md",
+            "redirect_url": "/azure/azure-sql/database/long-term-retention-overview",
+            "redirect_document_id": true
+        },
+        {
+            "source_path": "articles/sql-database/sql-database-machine-learning-services-add-r-packages.md",
+            "redirect_url": "/azure/azure-sql/database/machine-learning-services-add-r-packages",
+            "redirect_document_id": true
+        },
+        {
+            "source_path": "articles/sql-database/sql-database-machine-learning-services-data-issues.md",
+            "redirect_url": "/azure/azure-sql/database/machine-learning-services-data-issues",
+            "redirect_document_id": true
+        },
+        {
+            "source_path": "articles/sql-database/sql-database-machine-learning-services-differences.md",
+            "redirect_url": "/azure/azure-sql/database/machine-learning-services-differences",
+            "redirect_document_id": true
+        },
+        {
+            "source_path": "articles/sql-database/sql-database-machine-learning-services-functions.md",
+            "redirect_url": "/azure/azure-sql/database/machine-learning-services-functions",
+            "redirect_document_id": true
+        },
+        {
+            "source_path": "articles/sql-database/sql-database-manage-after-migration.md",
+            "redirect_url": "/azure/azure-sql/database/manage-data-after-migrating-to-database",
+            "redirect_document_id": true
+        },
+        {
+            "source_path": "articles/sql-database/sql-database-machine-learning-services-overview.md",
+            "redirect_url": "/azure/azure-sql/database/machine-learning-services-overview",
+            "redirect_document_id": true
         }
     ]
 }

articles/app-service/app-service-web-tutorial-connect-msi.md

@@ -40,7 +40,7 @@ What you will learn:
 
 This article continues where you left off in [Tutorial: Build an ASP.NET app in Azure with SQL Database](app-service-web-tutorial-dotnet-sqldatabase.md) or [Tutorial: Build an ASP.NET Core and SQL Database app in Azure App Service](app-service-web-tutorial-dotnetcore-sqldb.md). If you haven't already, follow one of the two tutorials first. Alternatively, you can adapt the steps for your own .NET app with SQL Database.
 
-To debug your app using SQL Database as the back end, make sure that you've allowed client connection from your computer. If not, add the client IP by following the steps at [Manage server-level IP firewall rules using the Azure portal](../sql-database/sql-database-firewall-configure.md#use-the-azure-portal-to-manage-server-level-ip-firewall-rules).
+To debug your app using SQL Database as the back end, make sure that you've allowed client connection from your computer. If not, add the client IP by following the steps at [Manage server-level IP firewall rules using the Azure portal](../azure-sql/database/firewall-configure.md#use-the-azure-portal-to-manage-server-level-ip-firewall-rules).
 
 [!INCLUDE [cloud-shell-try-it.md](../../includes/cloud-shell-try-it.md)]
 

articles/app-service/app-service-web-tutorial-dotnetcore-sqldb.md

@@ -113,7 +113,7 @@ When the server is created, the Azure CLI shows information similar to the follo
 
 ### Configure a server firewall rule
 
-Create a [server-level firewall rule](../sql-database/sql-database-firewall-configure.md) using the [`az sql server firewall create`](/cli/azure/sql/server/firewall-rule?view=azure-cli-latest#az-sql-server-firewall-rule-create) command. When both starting IP and end IP are set to 0.0.0.0, the firewall is only opened for other Azure resources.
+Create a [server-level firewall rule](../azure-sql/database/firewall-configure.md) using the [`az sql server firewall create`](/cli/azure/sql/server/firewall-rule?view=azure-cli-latest#az-sql-server-firewall-rule-create) command. When both starting IP and end IP are set to 0.0.0.0, the firewall is only opened for other Azure resources.
 
 ```azurecli-interactive
 az sql server firewall-rule create --resource-group myResourceGroup --server <server-name> --name AllowAzureIps --start-ip-address 0.0.0.0 --end-ip-address 0.0.0.0

articles/app-service/containers/tutorial-dotnetcore-sqldb-app.md

@@ -112,7 +112,7 @@ When the server is created, the Azure CLI shows information similar to the follo
 
 ### Configure a server firewall rule
 
-Create a [server-level firewall rule](../../sql-database/sql-database-firewall-configure.md) using the [`az sql server firewall create`](/cli/azure/sql/server/firewall-rule?view=azure-cli-latest#az-sql-server-firewall-rule-create) command. When both starting IP and end IP are set to 0.0.0.0, the firewall is only opened for other Azure resources.
+Create a [server-level firewall rule](../../azure-sql/database/firewall-configure.md) using the [`az sql server firewall create`](/cli/azure/sql/server/firewall-rule?view=azure-cli-latest#az-sql-server-firewall-rule-create) command. When both starting IP and end IP are set to 0.0.0.0, the firewall is only opened for other Azure resources.
 
 ```azurecli-interactive
 az sql server firewall-rule create --resource-group myResourceGroup --server <server-name> --name AllowAzureIps --start-ip-address 0.0.0.0 --end-ip-address 0.0.0.0

articles/azure-government/documentation-government-connect-ssms.md

@@ -33,7 +33,7 @@ If you don't have an Azure Government subscription, create a [free account](http
 
 Before you connect to Azure Government from SSMS, you must set up an Azure SQL Server firewall rule to allow your local IP address to access your computer that's running SQL Server. 
 
-Follow these steps to [Manage firewall rules by using the Azure portal](../sql-database/sql-database-firewall-configure.md#use-the-azure-portal-to-manage-server-level-ip-firewall-rules).
+Follow these steps to [Manage firewall rules by using the Azure portal](../azure-sql/database/firewall-configure.md#use-the-azure-portal-to-manage-server-level-ip-firewall-rules).
 
 ## Specify Azure Government as the environment to connect
 

articles/azure-resource-manager/templates/template-tutorial-deploy-sql-extensions-bacpac.md

@@ -234,7 +234,7 @@ Use a generated password. See [Prerequisites](#prerequisites).
 
 ## Verify the deployment
 
-To access the server from your client computer, you need to add an additional firewall rule. For more information, see [Create and manage IP firewall rules](../../sql-database/sql-database-firewall-configure.md#create-and-manage-ip-firewall-rules).
+To access the server from your client computer, you need to add an additional firewall rule. For more information, see [Create and manage IP firewall rules](../../azure-sql/database/firewall-configure.md#create-and-manage-ip-firewall-rules).
 
 In the Azure portal, select the SQL database from the newly deployed resource group. Select **Query editor (preview)**, and then enter the administrator credentials. You'll see two tables imported into the database.
 

articles/azure-sql/database/active-geo-replication-overview.md

@@ -135,7 +135,7 @@ The client performing the changes needs network access to the primary server. Al
 
 ### On the master of the primary server
 
-1. Add the IP address to the allow list of the client performing the changes (for more information see, [Configure firewall](../../sql-database/sql-database-firewall-configure.md)).
+1. Add the IP address to the allow list of the client performing the changes (for more information see, [Configure firewall](firewall-configure.md)).
 1. Create a login dedicated to setup active geo-replication (and adjust the credentials as needed):
 
    ```sql
@@ -198,7 +198,7 @@ After the initial setup, the users, logins, and firewall rules created can be re
 
 ## Keeping credentials and firewall rules in sync
 
-We recommend using [database-level IP firewall rules](../../sql-database/sql-database-firewall-configure.md) for geo-replicated databases so these rules can be replicated with the database to ensure all secondary databases have the same IP firewall rules as the primary. This approach eliminates the need for customers to manually configure and maintain firewall rules on servers hosting both the primary and secondary databases. Similarly, using [contained database users](../../sql-database/sql-database-manage-logins.md) for data access ensures both primary and secondary databases always have the same user credentials so during a failover, there is no disruptions due to mismatches with logins and passwords. With the addition of [Azure Active Directory](../../active-directory/fundamentals/active-directory-whatis.md), customers can manage user access to both primary and secondary databases and eliminating the need for managing credentials in databases altogether.
+We recommend using [database-level IP firewall rules](firewall-configure.md) for geo-replicated databases so these rules can be replicated with the database to ensure all secondary databases have the same IP firewall rules as the primary. This approach eliminates the need for customers to manually configure and maintain firewall rules on servers hosting both the primary and secondary databases. Similarly, using [contained database users](../../sql-database/sql-database-manage-logins.md) for data access ensures both primary and secondary databases always have the same user credentials so during a failover, there is no disruptions due to mismatches with logins and passwords. With the addition of [Azure Active Directory](../../active-directory/fundamentals/active-directory-whatis.md), customers can manage user access to both primary and secondary databases and eliminating the need for managing credentials in databases altogether.
 
 ## Upgrading or downgrading primary database
 

articles/azure-sql/database/adonet-v12-develop-direct-route-ports.md

@@ -78,4 +78,4 @@ https://techcommunity.microsoft.com/t5/DataCAT/Connect-to-Azure-SQL-Database-V12
 
 * [TDS protocol version list](https://www.freetds.org/userguide/tdshistory.htm)
 * [SQL Database Development Overview](../../sql-database/sql-database-develop-overview.md)
-* [Azure SQL Database firewall](../../sql-database/sql-database-firewall-configure.md)
+* [Azure SQL Database firewall](firewall-configure.md)

articles/sql-database/sql-database-insights-alerts-portal.md renamed to articles/azure-sql/database/alerts-insights-configure-portal.md

@@ -19,7 +19,7 @@ ms.date: 05/04/2020
 This article shows you how to set up alerts for databases in Azure SQL Database and Azure Synapse (formerly Azure SQL Data Warehouse) using the Azure portal. Alerts can send you an email or call a web hook when some metric (for example database size or CPU usage) reaches the threshold. This article also provides best practices for setting alert periods.
 
 > [!NOTE]
-> For SQL managed instance specific instructions, see [Create alerts for Azure SQL Managed Instance](sql-database-managed-instance-alerts.md).
+> For SQL managed instance specific instructions, see [Create alerts for Azure SQL Managed Instance](../../sql-database/sql-database-managed-instance-alerts.md).
 
 You can receive an alert based on monitoring metrics for, or events on, your Azure services.
 
@@ -34,35 +34,35 @@ You can configure an alert to do the following when it triggers:
 
 You can configure and get information about alert rules using
 
-* [Azure portal](../monitoring-and-diagnostics/insights-alerts-portal.md)
-* [PowerShell](../azure-monitor/platform/alerts-classic-portal.md)
-* [command-line interface (CLI)](../azure-monitor/platform/alerts-classic-portal.md)
+* [Azure portal](../../azure-monitor/platform/alerts-classic-portal.md)
+* [PowerShell](../../azure-monitor/platform/alerts-classic-portal.md)
+* [command-line interface (CLI)](../../azure-monitor/platform/alerts-classic-portal.md)
 * [Azure Monitor REST API](https://msdn.microsoft.com/library/azure/dn931945.aspx)
 
 ## Create an alert rule on a metric with the Azure portal
 
 1. In the [portal](https://portal.azure.com/), locate the resource you are interested in monitoring and select it.
 2. Select **Alerts** in the Monitoring section. The text and icon may vary slightly for different resources.  
 
-   ![Monitoring](media/sql-database-insights-alerts-portal/Alerts.png)
+   ![Monitoring](./media/alerts-insights-configure-portal/Alerts.png)
 
 3. Select the **New alert rule** button to open the **Create rule** page.
-  ![Create rule](media/sql-database-insights-alerts-portal/create-rule.png)
+  ![Create rule](./media/alerts-insights-configure-portal/create-rule.png)
 
 4. In the **Condition** section, click **Add**.
-  ![Define condition](media/sql-database-insights-alerts-portal/create-rule.png)
+  ![Define condition](./media/alerts-insights-configure-portal/create-rule.png)
 5. In the **Configure signal logic** page, select a signal.
-  ![Select signal](media/sql-database-insights-alerts-portal/select-signal.png).
+  ![Select signal](./media/alerts-insights-configure-portal/select-signal.png).
 6. After selecting a signal, such as **CPU percentage**, the **Configure signal logic** page appears.
-  ![Configure signal logic](media/sql-database-insights-alerts-portal/configure-signal-logic.png)
+  ![Configure signal logic](./media/alerts-insights-configure-portal/configure-signal-logic.png)
 7. On this page, configure that threshold type, operator, aggregation type, threshold value, aggregation granularity, and frequency of evaluation. Then click **Done**.
 8. On the **Create rule**, select an existing **Action group** or create a new group. An action group enables you to define the action to be taken when an alert condition occurs.
-  ![Define action group](media/sql-database-insights-alerts-portal/action-group.png)
+  ![Define action group](./media/alerts-insights-configure-portal/action-group.png)
 
 9. Define a name for the rule, provide an optional description, choose a severity level for the rule, choose whether to enable the rule upon rule creation, and then click **Create rule alert** to create the metric rule alert.
 
 Within 10 minutes, the alert is active and triggers as previously described.
 
 ## Next steps
 
-* Learn more about [configuring webhooks in alerts](../azure-monitor/platform/alerts-webhooks.md).
+* Learn more about [configuring webhooks in alerts](../../azure-monitor/platform/alerts-webhooks.md).

articles/azure-sql/database/connect-query-r.md

@@ -26,7 +26,7 @@ In this quickstart, you use R with Machine Learning Services to connect to an Az
 
 - An Azure account with an active subscription. [Create an account for free](https://azure.microsoft.com/free/?ref=microsoft.com&utm_source=microsoft.com&utm_medium=docs&utm_campaign=visualstudio).
 - An [Azure SQL Database](../../sql-database/sql-database-single-database-get-started.md)
-- [Machine Learning Services](../../sql-database/sql-database-machine-learning-services-overview.md) with R enabled.
+- [Machine Learning Services](machine-learning-services-overview.md) with R enabled.
 - [SQL Server Management Studio](/sql/ssms/sql-server-management-studio-ssms) (SSMS)
 
 > [!IMPORTANT]
@@ -76,6 +76,6 @@ Get the connection information you need to connect to the Azure SQL Database. Yo
 ## Next steps
 
 - [Design your first Azure SQL Database](../../sql-database/sql-database-design-first-database.md)
-- [Azure SQL Database Machine Learning Services (with R)](../../sql-database/sql-database-machine-learning-services-overview.md)
+- [Azure SQL Database Machine Learning Services (with R)](machine-learning-services-overview.md)
 - [Create and run simple R scripts in Azure SQL Database Machine Learning Services (preview)](../../sql-database/sql-database-quickstart-r-create-script.md)
-- [Write advanced R functions in Azure SQL Database using Machine Learning Services (preview)](../../sql-database/sql-database-machine-learning-services-functions.md)
+- [Write advanced R functions in Azure SQL Database using Machine Learning Services (preview)](machine-learning-services-functions.md)