Merge branch 'main' into release-dallas

Author: v-alje

azure-sql/database/elastic-jobs-overview.md

@@ -23,7 +23,7 @@ If you have not used Elastic jobs, [learn more about the job automation concepts
 
 ## Create and configure the agent
 
-1. Create or identify an empty S0 or higher database. This database will be used as the *Job database* during Elastic Job agent creation.
+1. Create or identify an empty S1 or higher database. This database will be used as the *Job database* during Elastic Job agent creation.
 2. Create an Elastic Job agent in the [portal](https://portal.azure.com/#create/Microsoft.SQLElasticJobAgent) or with [PowerShell](elastic-jobs-powershell-create.md#create-the-elastic-job-agent).
 
    ![Creating Elastic Job agent](./media/elastic-jobs-overview/create-elastic-job-agent.png)

azure-sql/database/elastic-jobs-powershell-create.md

@@ -59,7 +59,7 @@ In addition to the **Az.Sql** module, this tutorial also requires the *SqlServer
 
 ## Create required resources
 
-Creating an Elastic Job agent requires a database (S0 or higher) for use as the [Job database](job-automation-overview.md#elastic-job-database).
+Creating an Elastic Job agent requires a database (S1 or higher) for use as the [Job database](job-automation-overview.md#elastic-job-database).
 
 The script below creates a new resource group, server, and database for use as the Job database. The second script creates a second server with two blank databases to execute jobs against.
 
@@ -95,7 +95,7 @@ $agentServer
 # create the job database
 Write-Output "Creating a blank database to be used as the Job Database..."
 $jobDatabaseName = "JobDatabase"
-$jobDatabase = New-AzSqlDatabase -ResourceGroupName $resourceGroupName -ServerName $agentServerName -DatabaseName $jobDatabaseName -RequestedServiceObjectiveName "S0"
+$jobDatabase = New-AzSqlDatabase -ResourceGroupName $resourceGroupName -ServerName $agentServerName -DatabaseName $jobDatabaseName -RequestedServiceObjectiveName "S1"
 $jobDatabase
 ```
 

azure-sql/database/job-automation-overview.md

@@ -92,9 +92,9 @@ The Elastic Job agent is free. The job database is billed at the same rate as an
 
 The *Job database* is used for defining jobs and tracking the status and history of job executions. The *Job database* is also used to store agent metadata, logs, results, job definitions, and also contains many useful stored procedures and other database objects for creating, running, and managing jobs using T-SQL.
 
-For the current preview, an existing database in Azure SQL Database (S0 or higher) is required to create an Elastic Job agent.
+For the current preview, an existing database in Azure SQL Database (S1 or higher) is recommended to create an Elastic Job agent.
 
-The *Job database* should be a clean, empty, S0 or higher service objective Azure SQL Database. The recommended service objective of the *Job database* is S1 or higher, but the optimal choice depends on the performance needs of your job(s): the number of job steps, the number of job targets, and how frequently jobs are run. 
+The *Job database* should be a clean, empty, S1 or higher service objective Azure SQL Database. The recommended service objective of the *Job database* is S1 or higher, but the optimal choice depends on the performance needs of your job(s): the number of job steps, the number of job targets, and how frequently jobs are run. 
 
 If operations against the job database are slower than expected, [monitor](monitor-tune-overview.md#azure-sql-database-and-azure-sql-managed-instance-resource-monitoring) database performance and the resource utilization in the job database during periods of slowness using Azure portal or the [sys.dm_db_resource_stats](/sql/relational-databases/system-dynamic-management-views/sys-dm-db-resource-stats-azure-sql-database) DMV. If utilization of a resource, such as CPU, Data IO, or Log Write approaches 100% and correlates with periods of slowness, consider incrementally scaling the database to higher service objectives (either in the [DTU model](service-tiers-dtu.md) or in the [vCore model](service-tiers-vcore.md)) until job database performance is sufficiently improved.
 

azure-sql/database/sql-database-vulnerability-assessment-rules.md

@@ -14,7 +14,7 @@ monikerRange: "= azuresql || = azuresql-db || = azuresql-mi"
 ---
 
 # SQL Vulnerability Assessment rules reference guide
-[!INCLUDE[appliesto-sqldb-sqlmi-asa](../includes/appliesto-sqldb-sqlmi-asa.md)]  :::image type="icon" source="../media/applies-to/yes.png" border="false"::: SQL Server (all supported versions)
+[!INCLUDE[appliesto-sqldb-sqlmi-asa](../includes/appliesto-sqldb-sqlmi-asa-ss.md)]
 
 This article lists the set of built-in rules that are used to flag security vulnerabilities and highlight deviations from best practices, such as misconfigurations and excessive permissions. The rules are based on Microsoft's best practices and focus on the security issues that present the biggest risks to your database and its valuable data. They cover both database-level issues as well as server-level security issues, like server firewall settings and server-level permissions. These rules also represent many of the requirements from various regulatory bodies to meet their compliance standards.
 

azure-sql/database/threat-detection-overview.md

@@ -18,7 +18,7 @@ monikerRange: "= azuresql || = azuresql-db || = azuresql-mi"
 ---
 
 # SQL Advanced Threat Protection
-[!INCLUDE[appliesto-sqldb-sqlmi-asa](../includes/appliesto-sqldb-sqlmi-asa.md)] :::image type="icon" source="../media/applies-to/yes.png" border="false":::SQL Server on Azure VM :::image type="icon" source="../media/applies-to/yes.png" border="false":::Azure Arc-enabled SQL Server
+[!INCLUDE[appliesto-sqldb-sqlmi-asa](../includes/appliesto-sqldb-sqlmi-asa-asvm-arc.md)]
 
 Advanced Threat Protection for [Azure SQL Database](sql-database-paas-overview.md), [Azure SQL Managed Instance](../managed-instance/sql-managed-instance-paas-overview.md), [Azure Synapse Analytics](/azure/synapse-analytics/sql-data-warehouse/sql-data-warehouse-overview-what-is), [SQL Server on Azure Virtual Machines](../virtual-machines/windows/sql-server-on-azure-vm-iaas-what-is-overview.md) and [Azure Arc-enabled SQL Server](/sql/sql-server/azure-arc/overview) detects anomalous activities indicating unusual and potentially harmful attempts to access or exploit databases.
 

azure-sql/includes/appliesto-asf.md

@@ -1,2 +1,2 @@
-[!INCLUDE [applies-md](applies-md.md)] :::image type="icon" source="../media/applies-to/yes.png" border="false":::Azure SQL Database :::image type="icon" source="../media/applies-to/yes.png" border="false":::Azure SQL Managed Instance :::image type="icon" source="../media/applies-to/yes.png" border="false":::SQL Server on Azure VM
+[!INCLUDE [applies-md](applies-md.md)] :::image type="icon" source="../media/applies-to/yes-icon.svg" border="false"::: Azure SQL Database :::image type="icon" source="../media/applies-to/yes-icon.svg" border="false"::: Azure SQL Managed Instance :::image type="icon" source="../media/applies-to/yes-icon.svg" border="false"::: SQL Server on Azure VM
 

azure-sql/includes/appliesto-sqldb-asa-formerly-sqldw.md

@@ -6,5 +6,5 @@ author: WilliamDAssafMSFT
 ms.author: wiassaf
 ---
 
-[!INCLUDE [applies-md](applies-md.md)] :::image type="icon" source="../media/applies-to/yes.png" border="false":::Azure SQL Database :::image type="icon" source="../media/applies-to/yes.png" border="false":::Azure Synapse Analytics (dedicated SQL pool (formerly SQL DW) only)
+[!INCLUDE [applies-md](applies-md.md)] :::image type="icon" source="../media/applies-to/yes-icon.svg" border="false"::: Azure SQL Database :::image type="icon" source="../media/applies-to/yes-icon.svg" border="false"::: Azure Synapse Analytics (dedicated SQL pool (formerly SQL DW) only)
 

azure-sql/includes/appliesto-sqldb-asa.md

@@ -1,2 +1,2 @@
-[!INCLUDE [applies-md](applies-md.md)] :::image type="icon" source="../media/applies-to/yes.png" border="false":::Azure SQL Database :::image type="icon" source="../media/applies-to/yes.png" border="false":::Azure Synapse Analytics  
+[!INCLUDE [applies-md](applies-md.md)] :::image type="icon" source="../media/applies-to/yes-icon.svg" border="false"::: Azure SQL Database :::image type="icon" source="../media/applies-to/yes-icon.svg" border="false"::: Azure Synapse Analytics  
 

azure-sql/includes/appliesto-sqldb-sqlmi-asa-asvm-arc.md

@@ -0,0 +1 @@
+[!INCLUDE [applies-md](applies-md.md)] :::image type="icon" source="../media/applies-to/yes-icon.svg" border="false"::: Azure SQL Database :::image type="icon" source="../media/applies-to/yes-icon.svg" border="false"::: Azure SQL Managed Instance :::image type="icon" source="../media/applies-to/yes-icon.svg" border="false"::: Azure Synapse Analytics :::image type="icon" source="../media/applies-to/yes-icon.svg" border="false"::: SQL Server on Azure VM :::image type="icon" source="../media/applies-to/yes-icon.svg" border="false"::: Azure Arc-enabled SQL Server

azure-sql/includes/appliesto-sqldb-sqlmi-asa-dedicated-only.md

@@ -6,5 +6,5 @@ author: WilliamDAssafMSFT
 ms.author: wiassaf
 ---
 
-[!INCLUDE [applies-md](applies-md.md)] :::image type="icon" source="../media/applies-to/yes.png" border="false":::Azure SQL Database :::image type="icon" source="../media/applies-to/yes.png" border="false":::Azure SQL Managed Instance :::image type="icon" source="../media/applies-to/yes.png" border="false":::Azure Synapse Analytics (dedicated SQL pools only)
+[!INCLUDE [applies-md](applies-md.md)] :::image type="icon" source="../media/applies-to/yes-icon.svg" border="false"::: Azure SQL Database :::image type="icon" source="../media/applies-to/yes-icon.svg" border="false"::: Azure SQL Managed Instance :::image type="icon" source="../media/applies-to/yes-icon.svg" border="false"::: Azure Synapse Analytics (dedicated SQL pools only)