Merge pull request #115203 from MashaMSFT/move10

Move10

Author: tfosmark

.openpublishing.redirection.json

@@ -52726,6 +52726,136 @@
             "source_path": "articles/sql-database/tutorial-sqlite-db-to-azure-sql-serverless-offline.md",
             "redirect_url": "/azure/azure-sql/database/tutorial-sqlite-db-to-azure-sql-serverless-offline",
             "redirect_document_id": true
+        },
+        {
+            "source_path": "articles/sql-database/quota-increase-request.md",
+            "redirect_url": "/azure/azure-sql/database/quota-increase-request",
+            "redirect_document_id": true
+        },
+        {
+            "source_path": "articles/sql-database/sql-database-aad-authentication-configure.md",
+            "redirect_url": "/azure/azure-sql/database/aad-authentication-configure",
+            "redirect_document_id": true
+        },
+        {
+            "source_path": "articles/sql-database/sql-database-aad-authentication.md",
+            "redirect_url": "/azure/azure-sql/database/aad-authentication-overview",
+            "redirect_document_id": true
+        },
+        {
+            "source_path": "articles/sql-database/sql-database-advanced-data-security.md",
+            "redirect_url": "/azure/azure-sql/database/advanced-data-security",
+            "redirect_document_id": true
+        },
+        {
+            "source_path": "articles/sql-database/sql-database-always-encrypted-azure-key-vault.md",
+            "redirect_url": "/azure/azure-sql/database/always-encrypted-azure-key-vault-configure",
+            "redirect_document_id": true
+        },
+        {
+            "source_path": "articles/sql-database/sql-database-always-encrypted.md",
+            "redirect_url": "/azure/azure-sql/database/always-encrypted-certificate-store-configure",
+            "redirect_document_id": true
+        },
+        {
+            "source_path": "articles/sql-database/sql-database-audit-log-format.md",
+            "redirect_url": "/azure/azure-sql/database/audit-log-format",
+            "redirect_document_id": true
+        },
+        {
+            "source_path": "articles/sql-database/sql-database-auto-failover-group.md",
+            "redirect_url": "/azure/azure-sql/database/auto-failover-group-overview",
+            "redirect_document_id": true
+        },
+        {
+            "source_path": "articles/sql-database/sql-database-automated-backups.md",
+            "redirect_url": "/azure/azure-sql/database/automated-backups-overview",
+            "redirect_document_id": true
+        },
+        {
+            "source_path": "articles/sql-database/sql-database-automatic-tuning.md",
+            "redirect_url": "/azure/azure-sql/database/automatic-tuning-overview",
+            "redirect_document_id": true
+        },
+        {
+            "source_path": "articles/sql-database/sql-database-azure-hybrid-benefit.md",
+            "redirect_url": "/azure/azure-sql/database/azure-hybrid-benefit",
+            "redirect_document_id": true
+        },
+        {
+            "source_path": "articles/sql-database/sql-database-business-continuity.md",
+            "redirect_url": "/azure/azure-sql/database/business-continuity-high-availability-disaster-recover-hadr-overview",
+            "redirect_document_id": true
+        },
+        {
+            "source_path": "articles/sql-database/sql-database-client-id-keys.md",
+            "redirect_url": "/azure/azure-sql/database/application-authentication-get-client-id-keys",
+            "redirect_document_id": true
+        },
+        {
+            "source_path": "articles/sql-database/sql-database-designing-cloud-solutions-for-disaster-recovery.md",
+            "redirect_url": "/azure/azure-sql/database/designing-cloud-solutions-for-disaster-recovery",
+            "redirect_document_id": true
+        },
+        {
+            "source_path": "articles/sql-database/sql-database-develop-overview.md",
+            "redirect_url": "/azure/azure-sql/database/develop-overview",
+            "redirect_document_id": true
+        },
+        {
+            "source_path": "articles/sql-database/sql-database-disaster-recovery.md",
+            "redirect_url": "/azure/azure-sql/database/disaster-recovery-guidance",
+            "redirect_document_id": true
+        },
+        {
+            "source_path": "articles/sql-database/sql-database-disaster-recovery-drills.md",
+            "redirect_url": "/azure/azure-sql/database/disaster-recovery-drills",
+            "redirect_document_id": true
+        },
+        {
+            "source_path": "articles/sql-database/sql-database-manage-automation.md",
+            "redirect_url": "/azure/azure-sql/database/manage-automation",
+            "redirect_document_id": true
+        },
+        {
+            "source_path": "articles/sql-database/sql-database-manage-application-rolling-upgrade.md",
+            "redirect_url": "/azure/azure-sql/database/manage-application-rolling-upgrade",
+            "redirect_document_id": true
+        },
+        {
+            "source_path": "articles/sql-database/sql-database-metrics-diag-logging.md",
+            "redirect_url": "/azure/azure-sql/database/configure-streaming-export-metrics-diagnostic-telemtry-logging",
+            "redirect_document_id": true
+        },
+        {
+            "source_path": "articles/sql-database/sql-database-monitoring-with-dmvs.md",
+            "redirect_url": "/azure/azure-sql/database/monitoring-with-dmvs",
+            "redirect_document_id": true
+        },
+        {
+            "source_path": "articles/sql-database/sql-database-multi-model-features.md",
+            "redirect_url": "/azure/azure-sql/database/multi-model-features",
+            "redirect_document_id": true
+        },
+        {
+            "source_path": "articles/sql-database/sql-database-performance-guidance.md",
+            "redirect_url": "/azure/azure-sql/database/performance-guidance",
+            "redirect_document_id": true
+        },
+        {
+            "source_path": "articles/sql-database/sql-database-service-tier-hyperscale-faq.md",
+            "redirect_url": "/azure/azure-sql/database/service-tier-hyperscale-frequently-asked-questions-faq",
+            "redirect_document_id": true
+        },
+        {
+            "source_path": "articles/sql-database/sql-database-service-tiers-general-purpose-business-critical.md",
+            "redirect_url": "/azure/azure-sql/database/service-tiers-general-purpose-business-critical",
+            "redirect_document_id": true
+        },
+        {
+            "source_path": "articles/sql-database/sql-database-temporal-tables-retention-policy.md",
+            "redirect_url": "/azure/azure-sql/database/temporal-tables-retention-policy",
+            "redirect_document_id": true
         }
     ]
 }

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

@@ -46,7 +46,7 @@ To debug your app using SQL Database as the back end, make sure that you've allo
 
 ## Grant database access to Azure AD user
 
-First enable Azure AD authentication to SQL Database by assigning an Azure AD user as the Active Directory admin of the server. This user is different from the Microsoft account you used to sign up for your Azure subscription. It must be a user that you created, imported, synced, or invited into Azure AD. For more information on allowed Azure AD users, see [Azure AD features and limitations in SQL Database](../sql-database/sql-database-aad-authentication.md#azure-ad-features-and-limitations).
+First enable Azure AD authentication to SQL Database by assigning an Azure AD user as the Active Directory admin of the server. This user is different from the Microsoft account you used to sign up for your Azure subscription. It must be a user that you created, imported, synced, or invited into Azure AD. For more information on allowed Azure AD users, see [Azure AD features and limitations in SQL Database](../azure-sql/database/aad-authentication-overview.md#azure-ad-features-and-limitations).
 
 If your Azure AD tenant doesn't have a user yet, create one by following the steps at [Add or delete users using Azure Active Directory](../active-directory/fundamentals/add-users-azure-active-directory.md).
 
@@ -65,7 +65,7 @@ Add this Azure AD user as an Active Directory admin using [`az sql server ad-adm
 az sql server ad-admin create --resource-group myResourceGroup --server-name <server-name> --display-name ADMIN --object-id $azureaduser
 ```
 
-For more information on adding an Active Directory admin, see [Provision an Azure Active Directory administrator for your server](../sql-database/sql-database-aad-authentication-configure.md#provision-azure-ad-admin-sql-managed-instance)
+For more information on adding an Active Directory admin, see [Provision an Azure Active Directory administrator for your server](../azure-sql/database/aad-authentication-configure.md#provision-azure-ad-admin-sql-managed-instance)
 
 ## Set up Visual Studio
 

articles/azure-databricks/howto-regional-disaster-recovery.md

@@ -302,7 +302,7 @@ To create your own regional disaster recovery topology, follow these requirement
 
 ## Disaster recovery for your Azure ecosystem
 
-If you are using other Azure services, be sure to implement disaster recovery best practices for those services, too. For example, if you choose to use an external Hive metastore instance, you should consider disaster recovery for [Azure SQL Database](../sql-database/sql-database-disaster-recovery.md), [Azure HDInsight](../hdinsight/hdinsight-high-availability-linux.md), and/or [Azure Database for MySQL](../mysql/concepts-business-continuity.md). For general information about disaster recovery, see [Disaster recovery for Azure applications](https://docs.microsoft.com/azure/architecture/resiliency/disaster-recovery-azure-applications).
+If you are using other Azure services, be sure to implement disaster recovery best practices for those services, too. For example, if you choose to use an external Hive metastore instance, you should consider disaster recovery for [Azure SQL Database](../azure-sql/database/disaster-recovery-guidance.md), [Azure HDInsight](../hdinsight/hdinsight-high-availability-linux.md), and/or [Azure Database for MySQL](../mysql/concepts-business-continuity.md). For general information about disaster recovery, see [Disaster recovery for Azure applications](https://docs.microsoft.com/azure/architecture/resiliency/disaster-recovery-azure-applications).
 
 ## Next steps
 

articles/azure-monitor/insights/azure-sql.md

@@ -59,7 +59,7 @@ Use the process described in [Add Azure Monitor solutions from the Solutions Gal
 
 Once you have created Azure SQL Analytics solution in your workspace, you need to **configure each** resource that you want to monitor to stream its diagnostics telemetry to Azure SQL Analytics. Follow detailed instructions on this page:
 
-- Enable Azure Diagnostics for your Azure SQL database to [stream diagnostics telemetry to Azure SQL Analytics](../../sql-database/sql-database-metrics-diag-logging.md).
+- Enable Azure Diagnostics for your Azure SQL database to [stream diagnostics telemetry to Azure SQL Analytics](../../azure-sql/database/configure-streaming-export-metrics-diagnostic-telemtry-logging.md).
 
 The above page also provides instructions on enabling support for monitoring multiple Azure subscriptions from a single Azure SQL Analytics workspace as a single pane of glass.
 
@@ -167,7 +167,7 @@ Once the new role is created, assign this role to each user that you need to gra
 
 ## Analyze data and create alerts
 
-Data analysis in Azure SQL Analytics is based on [Log Analytics language](../log-query/get-started-queries.md) for your custom querying and reporting. Find description of the available data collected from database resource for custom querying in [metrics and logs available](../../sql-database/sql-database-metrics-diag-logging.md#metrics-and-logs-available).
+Data analysis in Azure SQL Analytics is based on [Log Analytics language](../log-query/get-started-queries.md) for your custom querying and reporting. Find description of the available data collected from database resource for custom querying in [metrics and logs available](../../azure-sql/database/configure-streaming-export-metrics-diagnostic-telemtry-logging.md#metrics-and-logs-available).
 
 Automated alerting in Azure SQL Analytics is based on writing a Log Analytics query that triggers an alert upon a condition met. Find below several examples on Log Analytics queries upon which alerting can be set up in Azure SQL Analytics.
 

articles/azure-monitor/platform/diagnostic-logs-schema.md

@@ -72,15 +72,15 @@ The schema for resource diagnostic logs varies depending on the resource and log
 | Recovery Services | [Data Model for Azure Backup](../../backup/backup-azure-reports-data-model.md)|
 | Search |[Enabling and using Search Traffic Analytics](../../search/search-traffic-analytics.md) |
 | Service Bus |[Azure Service Bus logs](../../service-bus-messaging/service-bus-diagnostic-logs.md) |
-| SQL Database | [Azure SQL Database logging](../../sql-database/sql-database-metrics-diag-logging.md) |
+| SQL Database | [Azure SQL Database logging](../../azure-sql/database/configure-streaming-export-metrics-diagnostic-telemtry-logging.md) |
 | Stream Analytics |[Job logs](../../stream-analytics/stream-analytics-job-diagnostic-logs.md) |
 | Traffic Manager | [Traffic Manager Log schema](../../traffic-manager/traffic-manager-diagnostic-logs.md) |
 | Virtual Networks | Schema not available. |
 | Virtual Network Gateways | Schema not available. |
 
 ## Supported log categories per resource type
 
-Some categories may only be supported for specific types of resources. This is list of all that are available in some form.  For example, Microsoft.Sql/servers/databases categories aren't available for all types of databases. For more information, see [information on SQL Database diagnostic logging](../../sql-database/sql-database-metrics-diag-logging.md). 
+Some categories may only be supported for specific types of resources. This is list of all that are available in some form.  For example, Microsoft.Sql/servers/databases categories aren't available for all types of databases. For more information, see [information on SQL Database diagnostic logging](../../azure-sql/database/configure-streaming-export-metrics-diagnostic-telemtry-logging.md). 
 
 |Resource Type|Category|Category Display Name|
 |---|---|---|