Merge pull request #34784 from MicrosoftDocs/main

Auto Publish – main to live - 2025-07-24 17:30 UTC

Author: learn-build-service-prod[bot]

azure-sql/database/convert-to-hyperscale.md

@@ -40,7 +40,8 @@ If a geo-primary database is in an elastic pool, it can be moved to an existing
 
 The conversion process is divided into two stages - the conversion of database, which occurs while the existing database is online, and then a cutover to the new Hyperscale database. 
 
-- The time required to move an existing database to Hyperscale consists of the time to copy data and the time to replay the changes made in the source database while copying data. The data copy time is proportional to data size. We recommend converting to Hyperscale during a lower write activity period so that the time to replay accumulated changes is shorter.
+- The time required to move an existing database to Hyperscale consists of the time to copy data and the time to replay the changes made in the source database while copying data. While the data copy time scales roughly with the size of the database, actual copy speed can vary due to factors such as network throughput, I/O bandwidth, storage latency, and transient service load. We recommend converting to Hyperscale during a lower write activity period so that the time to replay accumulated changes is shorter. It is recommended to use manual cutover to control the next stage.
+
 - You have the ability to choose when the cutover occurs - as soon as the database is ready, or manually at a time of your choosing. By default, the process to convert to Hyperscale will cutover automatically.
   - If you choose to manually cutover at a time of your choosing, you have 24 hours to initiate a manual cutover after the point when the database ready for cutover. You can initiate a manual cutover via the Azure portal, Azure CLI, PowerShell, or T-SQL.
 - During the final cutover to Hyperscale, your applications only experience a short period of downtime, usually less than a minute.

azure-sql/database/json-features.md

@@ -2,10 +2,10 @@
 title: Work with JSON Data
 titleSuffix: Azure SQL Database & Azure SQL Managed Instance
 description: JSON functionality in the database enables you to parse, query, and format data in JavaScript Object Notation (JSON) notation.
-author: uc-msft
-ms.author: umajay
-ms.reviewer: wiassaf, mathoma
-ms.date: 06/13/2025
+author: WilliamDAssafMSFT
+ms.author: wiassaf
+ms.reviewer: jovanpop, umajay, mathoma
+ms.date: 07/23/2025
 ms.service: azure-sql
 ms.subservice: development
 ms.topic: how-to

azure-sql/virtual-machines/windows/automated-backup.md

@@ -421,9 +421,7 @@ The following table lists the possible solutions if you're having issues enablin
 | **Automated Backup fails for SQL 2016 +**| **Allow Blob Public Access** is enabled on the storage Account. This provides a temporary workaround to a known issue. |
 
 
-
-
-### Common issues with Automated or Managed Backup
+### Common issues with Automated or Managed Backups
 
 The following table lists possible errors and solutions when working with Automated Backups: 
 
@@ -440,6 +438,7 @@ The following table lists possible errors and solutions when working with Automa
 | **Error 3202: Write on Storage account failed 13 (The data is invalid)** | Remove the immutable blob policy on the storage container and make sure the storage account is using, at minimum, TLS 1.0.  | 
 | **Error 3063: Write to backup block blob device. Device has reached its limit of allowed blocks.** | This can happen if you're running automated backups from a secondary Always On availability group replica that has the `Readable` configuration set to `NO`. For automated backups to work on a secondary replica, the replica must be readable. | 
 | **Unable to schedule a backup for a particular day** | If you're using [Automated backups for SQL Server 2014](automated-backup-sql-2014.md), this is expected. You can configure a backup schedule starting with SQL Server 2016. |
+| **403 forbidden error when connecting to the remote server** | To resolve this: <br > - **Check network security**: Make sure that the network security group (NSG) allows traffic on the necessary ports, particularly port `443` for HTTPS. <br /> - **Verify IP addresses**: Ensure the IP addresses of the VMs that need access to the storage account are added to the allowed list  for the storage account. <br /> - **Review DNS settings**: Confirm that the DNS settings are correctly configured to resolve the storage account name. | 
 
 
 ### Disabling Automated Backup or Managed Backup fails

azure-sql/virtual-machines/windows/automated-patching.md

@@ -48,8 +48,6 @@ The following table describes the options that can be configured for Automated P
 | **Maintenance window duration** | 30-180 | The number of minutes permitted to complete the download and installation of updates. |
 | **Patch Category** | Important | The category of Windows updates to download and install. |
 
-
-
 ## Configure in the Azure portal
 
 You can use the Azure portal to configure Automated Patching during provisioning or for existing VMs.
@@ -120,6 +118,8 @@ Consider the following:
 
 - Automated Patching isn't aware of Always On availability group configurations for your SQL Server VM, so be cautious when creating patching schedules for availability group replicas to avoid unexpected failovers.
 - If your SQL Server VMs are in an availability set and you've configured an Always On availability group, both nodes might be restarted if patches are applied at the same time, so it's important the patching schedules are set for a different day/time for each node. 
+- Your virtual machine can restart during a predefined maintenance window. You can use Event Viewer to confirm that your VM restarted during a maintenance window from automated patching. [Guest patching](/azure/virtual-machines/automatic-vm-guest-patching#how-does-automatic-vm-guest-patching-work) can restart your VM outside of a maintenance window. 
+- If your update fails with an error message that states `The user data or log directory is invalid`, it's likely due to the default locations of new data or log files for a database pointing to an invalid location. To resolve this, review [Invalid directory error](/troubleshoot/sql/database-engine/install/windows/user-data-log-directory-invalid).
 
 
 ## Migrate from Automated Patching to Azure Update Manager

azure-sql/virtual-machines/windows/configure-azure-ad-authentication-for-sql-vm.md

@@ -308,8 +308,11 @@ Set-AzVMExtension -ExtensionName "SqlIaasExtension" -ResourceGroupName $resource
 
 ## Create logins and users
 
-Follow the steps in the [Microsoft Entra tutorial](/sql/sql-server/azure-arc/entra-authentication-setup-tutorial#create-logins-and-users) to create logins and Users for the managed identity.
+Follow the steps in the [Microsoft Entra tutorial](/sql/sql-server/azure-arc/entra-authentication-setup-tutorial#create-logins-and-users) to create logins and users for the managed identity.
 
+## Connect to your instance
+
+Follow the instructions in the [Microsoft Entra tutorial](/sql/sql-server/azure-arc/entra-authentication-setup-tutorial#connect-with-a-supported-authentication-method) to connect to your SQL Server instance using Microsoft Entra authentication.
 
 ## Limitations
 

azure-sql/virtual-machines/windows/frequently-asked-questions-faq.yml

@@ -130,7 +130,7 @@ sections:
         answer: |
              There are three ways to do this. If you're an Enterprise Agreement (EA) customer, you can provision one of the [virtual machine images](sql-server-on-azure-vm-iaas-what-is-overview.md#licensing). If you have [Software Assurance](https://www.microsoft.com/en-us/licensing/licensing-programs/software-assurance-default), you can enable the [Azure Hybrid Benefit](licensing-model-azure-hybrid-benefit-ahb-change.md) on an existing pay-as-you-go (PAYG) image. Or you can copy the SQL Server installation media to a Windows Server VM, and then install SQL Server on the VM. Be sure to register your SQL Server VM with the [extension](sql-agent-extension-manually-register-single-vm.md) for features such as portal management, automated backup and automated patching. 
           
-          
+ 
       - question: |
           Does a customer need SQL Server Client Access Licenses (CALs) to connect to a SQL Server pay-as-you-go image that is running on Azure Virtual Machines?
         answer:  No. Customers need CALs when they use bring-your-own-license and move their SQL Server SA server / CAL VM to Azure VMs. 
@@ -195,7 +195,12 @@ sections:
           Why do I see that my licenses are assigned at a scope level when I try to modify the license for my SQL Server VM?
         answer: |
               Changing the license type for individual SQL Server VMs deployed to subscriptions with [Centrally managed Azure Hybrid Benefit](licensing-model-azure-hybrid-benefit-ahb-change.md#integration-with-centrally-managed-azure-hybrid-benefit) isn't supported as the licensing is managed at the subscription level - a message displays such as `Your organization manages licenses assigned to Azure at a scope level such as Azure subscription instead of each individual resources.`
-              
+
+      - question: |
+          How many core licenses should I use for my SQL Server on Azure VM if I have 'N' number of vCores?
+        answer: |
+              A vCore on an Azure VM is the equivalent of physical CPU. For SQL Server on Azure VMs, there is a 1:1 relationship between vCores and core licenses. This means that if you have 'N' number of vCores, you should use 'N' number of core licenses. For example, if you have a VM with 8 vCores, that VM uses 8 core licenses. 
+                
                    
   - name: Administration
     questions:
@@ -287,7 +292,11 @@ sections:
         answer: |
              You can get [free extended security updates](sql-server-extend-end-of-support.md) by moving your SQL Server as-is to an Azure virtual machine. Updates are available through the Windows Update channel. For more information, see [end of support options](/sql/sql-server/end-of-support/sql-server-end-of-support-overview). 
             
-             
+      - question: |
+          Why did my configuration change or update fail with the error 'The User Data directory in the registry is not valid?'
+        answer: |
+            The issue happens when the default locations of new data or log files for a database point to an invalid location. To resolve this, review [Invalid directory error](/troubleshoot/sql/database-engine/install/windows/user-data-log-directory-invalid).
+                  
           
   - name: General
     questions:

docs/includes/applies-to-version/sqlserver2016-asdb-asdbmi-asa-serverless-pool-only-fabricsqldb.md

@@ -0,0 +1,9 @@
+---
+author: WilliamDAssafMSFT
+ms.author: wiassaf
+ms.date: 07/23/2025
+ms.service: sql
+ms.topic: include
+---
+
+[!INCLUDE [Applies to](../../includes/applies-md.md)] [!INCLUDE [SQL Server 2016](_ss2016.md)] and later versions [!INCLUDE [Azure SQL Database](_asdb.md)] [!INCLUDE [Azure SQL Managed Instance](_asmi.md)] [!INCLUDE [Azure Synapse Analytics (serverless SQL pool only)](_asa-svrless-sqlpool-only.md)] [!INCLUDE [fabric-sqldb](_fabric-sqldb.md)]

docs/includes/applies-to-version/sqlserver2016-asdb-asdbmi-asa-svrless-only-fabricse-fabricdw-fabricsqldb.md

@@ -0,0 +1,9 @@
+---
+author: WilliamDAssafMSFT
+ms.author: wiassaf
+ms.date: 07/23/2025
+ms.service: sql
+ms.topic: include
+---
+
+[!INCLUDE [Applies to](../../includes/applies-md.md)] [!INCLUDE [SQL Server 2016](_ss2016.md)] and later versions [!INCLUDE [Azure SQL Database](_asdb.md)] [!INCLUDE [Azure SQL Managed Instance](_asmi.md)] [!INCLUDE [Azure Synapse Analytics (serverless SQL pool only)](_asa-svrless-sqlpool-only.md)] [!INCLUDE [Fabric SQL analytics endpoint](_fabric-se.md)] [!INCLUDE [Fabric Data Warehouse](_fabric-dw.md)] [!INCLUDE [fabric-sqldb](_fabric-sqldb.md)]

docs/includes/applies-to-version/sqlserver2022-asdb-asmi-asa-fabricse-fabricdw-fabricsqldb.md

@@ -0,0 +1,9 @@
+---
+author: WilliamDAssafMSFT
+ms.author: wiassaf
+ms.date: 07/23/2025
+ms.service: sql
+ms.topic: include
+---
+
+[!INCLUDE [Applies to](../applies-md.md)] [!INCLUDE [SQL Server 2022](_ss2022.md)] and later versions [!INCLUDE [Azure SQL Database](_asdb.md)] [!INCLUDE [Azure SQL Managed Instance](_asmi.md)] [!INCLUDE [Synapse Analytics](_asa.md)] [!INCLUDE [fabric-sqldb](_fabric-sqldb.md)]

docs/relational-databases/backup-restore/sql-server-backup-to-url.md

@@ -169,6 +169,8 @@ The following are security considerations and requirements when backing up to or
 
 - [Immutable storage for Azure Blob Storage](/azure/storage/blobs/storage-blob-immutable-storage) isn't supported. Set the **Immutable Storage** policy to false.
 
+- Backup to URL isn't supported to [premium storage](/azure/storage/blobs/storage-blob-block-blob-premium). 
+
 ## Supported arguments and statements in Azure Blob Storage
 
 <a id="Support"></a>