Merge pull request #31774 from WilliamDAssafMSFT/20240905-freshness-pass

20240905 freshness pass

Author: ttorble

azure-sql/database-watcher-faq.yml

@@ -5,7 +5,7 @@ metadata:
   description: Frequently asked questions about database watcher for Azure SQL
   author: dimitri-furman
   ms.author: dfurman
-  ms.date: 07/12/2024
+  ms.date: 09/05/2024
   ms.reviewer: wiassaf
   ms.service: azure-sql
   ms.subservice: monitoring
@@ -18,7 +18,7 @@ summary: |
 
   This article provides answers to frequently asked questions about database watcher for Azure SQL. It is intended for readers who have a general understanding of Azure SQL, and are looking for answers to specific, commonly asked questions about database watcher.
 
-  For an overview of database watcher, see [Monitor Azure SQL workloads with database watcher](database-watcher-overview.md).
+  For an overview of database watcher, see [Monitor Azure SQL workloads with database watcher (preview)](database-watcher-overview.md).
 
 sections:
   - name: General
@@ -101,7 +101,7 @@ sections:
     questions:
       - question: |
           Which data services are supported as the data store for the SQL monitoring data?
-        answer: You can use a database on an [Azure Data Explorer cluster](/azure/data-explorer/data-explorer-overview), on a [free Azure Data Explorer cluster](/azure/data-explorer/start-for-free), or in [Real-Time Analytics](/fabric/real-time-analytics/overview) in Microsoft Fabric. To compare between these options, see [What is the difference between Real-Time Analytics and Azure Data Explorer?](/fabric/real-time-analytics/realtime-analytics-compare).
+        answer: You can use a database on an [Azure Data Explorer cluster](/azure/data-explorer/data-explorer-overview), on a [free Azure Data Explorer cluster](/azure/data-explorer/start-for-free), or in [Real-Time Analytics](/fabric/real-time-analytics/overview) in Microsoft Fabric. To compare between these options, see [What is the difference between Real-Time Analytics and Azure Data Explorer?](/fabric/real-time-analytics/realtime-analytics-compare)
 
       - question: |
           I already have an Azure Data Explorer cluster. Can I use it for my database watcher data store?

azure-sql/database/authentication-azure-ad-only-authentication-policy.md

@@ -5,16 +5,16 @@ description: This article provides information on how to enforce an Azure policy
 author: nofield
 ms.author: nofield
 ms.reviewer: wiassaf, vanto, mathoma
-ms.date: 11/02/2021
+ms.date: 09/05/2024
 ms.service: azure-sql
 ms.subservice: security
 ms.topic: conceptual
-monikerRange: "= azuresql || = azuresql-db || = azuresql-mi"
+monikerRange: "=azuresql||=azuresql-db||=azuresql-mi"
 ---
 
 # Azure Policy for Microsoft Entra-only authentication with Azure SQL
 
-[!INCLUDE[appliesto-sqldb-sqlmi](../includes/appliesto-sqldb-sqlmi.md)]
+[!INCLUDE [appliesto-sqldb-sqlmi](../includes/appliesto-sqldb-sqlmi.md)]
 
 Azure Policy can enforce the creation of an Azure SQL Database or Azure SQL Managed Instance with [Microsoft Entra-only authentication](authentication-azure-ad-only-authentication.md) enabled during provisioning. With this policy in place, any attempts to create a [logical server in Azure](logical-servers.md) or managed instance will fail if it isn't created with Microsoft Entra-only authentication enabled.
 
@@ -53,14 +53,14 @@ For more information on custom roles, see [Azure custom roles](/azure/role-based
 
 The Azure AD-only authentication policies can be managed by going to the [Azure portal](https://portal.azure.com), and searching for the **Policy** service. Under **Definitions**, search for *Azure Active Directory-only authentication*.
 
-:::image type="content" source="media/authentication-azure-ad-only-authentication-policy/policy-azure-ad-only-authentication.png" alt-text="Screenshot of Azure Policy for Azure AD-only authentication":::
+:::image type="content" source="media/authentication-azure-ad-only-authentication-policy/policy-azure-ad-only-authentication.png" alt-text="Screenshot of Azure Policy for Azure AD-only authentication." lightbox="media/authentication-azure-ad-only-authentication-policy/policy-azure-ad-only-authentication.png":::
 
-For a guide, see [Using Azure Policy to enforce Azure AD-only authentication with Azure SQL](authentication-azure-ad-only-authentication-policy-how-to.md).
+For a guide, see [Using Azure Policy to enforce Microsoft Entra-only authentication with Azure SQL](authentication-azure-ad-only-authentication-policy-how-to.md).
 
 There are three effects for these policies:
 
 - **Audit** - The default setting, and will only capture an audit report in the Azure Policy activity logs
-- **Deny** - Prevents logical server or managed instance creation without [Microsoft Entra-only authentication](authentication-azure-ad-only-authentication.md) enabled
+- **Deny** - Prevents logical server or managed instance creation without [Microsoft Entra-only authentication with Azure SQL](authentication-azure-ad-only-authentication.md) enabled
 - **Disabled** - Will disable the policy, and won't restrict users from creating a logical server or managed instance without Microsoft Entra-only authentication enabled
 
 If the Azure Policy for Azure AD-only authentication is set to **Deny**, creating a logical server or managed instance fails. The details of this failure are recorded in the **Activity log** of the resource group.
@@ -71,14 +71,14 @@ You can view the **Compliance** setting under the **Policy** service to see the
 
 The Azure Policy can prevent a new logical server or managed instance from being created without having Microsoft Entra-only authentication enabled, but the feature can be changed after server or managed instance creation. If a user has disabled Microsoft Entra-only authentication after the server or managed instance was created, the compliance state will be `Non-compliant` if the Azure Policy is set to **Deny**.
 
-:::image type="content" source="media/authentication-azure-ad-only-authentication-policy/check-compliance-policy-azure-ad-only-authentication.png" alt-text="Screenshot of Azure Policy Compliance menu for Azure AD-only authentication.":::
+:::image type="content" source="media/authentication-azure-ad-only-authentication-policy/check-compliance-policy-azure-ad-only-authentication.png" alt-text="Screenshot of Azure Policy Compliance menu for Azure AD-only authentication." lightbox="media/authentication-azure-ad-only-authentication-policy/check-compliance-policy-azure-ad-only-authentication.png":::
 
 ## Limitations
 
 - Azure Policy enforces Azure AD-only authentication during logical server or managed instance creation. Once the server is created, authorized Microsoft Entra users with special roles (for example, SQL Security Manager) can disable the Azure AD-only authentication feature. The Azure Policy allows it, but in this case, the server or managed instance will be listed in the compliance report as `Non-compliant` and the report will indicate the server or managed instance name.  
-- For more remarks, known issues, and permissions needed, see [Microsoft Entra-only authentication](authentication-azure-ad-only-authentication.md).
+- For more remarks, known issues, and permissions needed, see [Microsoft Entra-only authentication with Azure SQL](authentication-azure-ad-only-authentication.md).
 
-## Next steps
+## Next step
 
 > [!div class="nextstepaction"]
-> [Using Azure Policy to enforce Azure AD-only authentication with Azure SQL](authentication-azure-ad-only-authentication-policy-how-to.md)
+> [Using Azure Policy to enforce Microsoft Entra-only authentication with Azure SQL](authentication-azure-ad-only-authentication-policy-how-to.md)

azure-sql/database/doc-changes-updates-release-notes-whats-new-archive.md

@@ -67,7 +67,7 @@ Return to [What's new in Azure SQL Database?](doc-changes-updates-release-notes-
 | Changes | Details |
 | --- | --- |
 | **128 vCore preview** | It's now possible to provision your Azure SQL Database with up to 128 vCores in both the General Purpose, and Business Critical service tiers. For more information, review [resource limits](resource-limits-vcore-single-databases.md#general-purpose---provisioned-compute---gen5). |
-| **Azure Synapse Link for SQL GA** | Azure Synapse Link for SQL, now generally available, enables near real-time analytics over operational data in SQL Server 2022 and Azure SQL Database. With a seamless integration between operational stores and Azure Synapse Analytics dedicated SQL pools, Azure Synapse Link for SQL enables you to run analytics, business intelligence and machine learning scenarios on your operational data with minimum impact on source databases with a new change feed technology. For more information, review [What is Azure Synapse Link for SQL?](/azure/synapse-analytics/synapse-link/sql-synapse-link-overview). |
+| **Azure Synapse Link for SQL GA** | Azure Synapse Link for SQL, now generally available, enables near real-time analytics over operational data in SQL Server 2022 and Azure SQL Database. With a seamless integration between operational stores and Azure Synapse Analytics dedicated SQL pools, Azure Synapse Link for SQL enables you to run analytics, business intelligence and machine learning scenarios on your operational data with minimum impact on source databases with a new change feed technology. For more information, review [What is Azure Synapse Link for SQL?](/azure/synapse-analytics/synapse-link/sql-synapse-link-overview) |
 | **Gen5 hardware rename** | The Gen5 hardware in the vCore purchasing model has been renamed to **standard-series (Gen5)**. |
 | **Hyperscale premium-series and premium-series memory optimized hardware preview** | Premium-series and premium-series memory optimized hardware is [in preview for Hyperscale databases](service-tier-hyperscale.md#compute-resources). For more information, read the [Premium-series announcement blog post](https://aka.ms/AAiq28n). |
 | **Invoke external REST endpoints preview** | It's now possible to call an HTTPS REST endpoint natively, using a new system stored procedure. This feature is currently in preview. For more information, review [sp_invoke_external_rest_endpoint](/sql/relational-databases/system-stored-procedures/sp-invoke-external-rest-endpoint-transact-sql). |

azure-sql/database/doc-changes-updates-release-notes-whats-new.md

@@ -23,7 +23,7 @@ monikerRange: "=azuresql||=azuresql-db"
 > * [Azure SQL Managed Instance](../managed-instance/doc-changes-updates-release-notes-whats-new.md?view=azuresql&preserve-view=true)
 > * [SQL Server on Azure VMs](../virtual-machines/windows/doc-changes-updates-release-notes-whats-new.md?view=azuresql&preserve-view=true)
 
-This article summarizes the documentation changes associated with new features and improvements in the recent releases of [Azure SQL Database](https://azure.microsoft.com/products/azure-sql/database/). For more information about Azure SQL Database, see [What is Azure SQL Database?](sql-database-paas-overview.md).
+This article summarizes the documentation changes associated with new features and improvements in the recent releases of [Azure SQL Database](https://azure.microsoft.com/products/azure-sql/database/). For more information about Azure SQL Database, see [What is Azure SQL Database?](sql-database-paas-overview.md)
 
 > [!TIP]
 > For more announcements, discussion, and community content, see the [Azure SQL Database blog](https://techcommunity.microsoft.com/t5/azure-sql-blog/bg-p/AzureSQLBlog).