Merge pull request #34347 from MicrosoftDocs/main

6/6/2025 PM Publish

Author: Albertyang0

azure-sql/virtual-machines/windows/backup-restore-to-url-using-managed-identities.md

@@ -1,10 +1,10 @@
 ---
-title: Backup and restore to URL using managed identities
+title: Backup and Restore to URL Using Managed Identities
 description: Learn how to back up and restore SQL Server databases to Azure Blob storage using managed identities for SQL Server on Azure VMs.
 author: PratimDasgupta
 ms.author: prdasgu
-ms.reviewer: vanto, mathoma
-ms.date: 02/16/2025
+ms.reviewer: vanto, mathoma, randolphwest
+ms.date: 06/06/2025
 ms.service: azure-vm-sql-server
 ms.subservice: security
 ms.topic: how-to
@@ -78,25 +78,45 @@ RESTORE DATABASE [AdventureWorks]
 
 If a primary managed identity isn't assigned to the SQL Server on Azure VM, the backup and restore operations will fail with an error message indicating that the managed identity isn't selected.
 
-```sql
+```output
 Msg 37563, Level 16, State 2, Line 14
 The primary managed identity is not selected for this server. Enable the primary managed identity for Microsoft Entra authentication for this server. For more information see (https://aka.ms/sql-server-managed-identity-doc).`
 ```
 
 ### No `Storage Blob Data Contributor` role assigned
 
-If the primary managed identity for the SQL Server on Azure VM isn't given the `Storage Blob Data Contributor` role to the storage account, the **BACKUP** operation will fail with an error message indicating that access is denied.
+If the primary managed identity for the SQL Server on Azure VM isn't given the `Storage Blob Data Contributor` role to the storage account, the `BACKUP` operation will fail with an error message indicating that access is denied.
 
-```sql
+```output
+Msg 3201, Level 16, State 1, Line 31
+Cannot open backup device 'https://<storage-account-name>.blob.core.windows.net/<container-name>/AdventureWorks.bak'. Operating system error 5(Access is denied.).
+Msg 3013, Level 16, State 1, Line 31
+BACKUP DATABASE is terminating abnormally.
+```
+
+If the managed identity for the SQL Server on Azure VM isn't given the `Storage Blob Data Contributor` role to the storage account, the `RESTORE` operation will fail with an error message indicating that access is denied.
+
+```output
+Msg 3201, Level 16, State 1, Line 31
+Cannot open backup device 'https://<storage-account-name>.blob.core.windows.net/<container-name>/AdventureWorks.bak'. Operating system error 5(Access is denied.).
+Msg 3013, Level 16, State 1, Line 31
+RESTORE DATABASE is terminating abnormally.
+```
+
+### Network or firewall issues
+
+If you haven't configured valid network access to the Azure Blob storage, and Windows Firewall permissions on the host, to allow the outbound connection, and valid storage account service endpoints aren't configured, the `BACKUP` operation fails with an error message indicating that access is denied.
+
+```output
 Msg 3201, Level 16, State 1, Line 31
 Cannot open backup device 'https://<storage-account-name>.blob.core.windows.net/<container-name>/AdventureWorks.bak'. Operating system error 5(Access is denied.).
 Msg 3013, Level 16, State 1, Line 31
 BACKUP DATABASE is terminating abnormally. 
 ```
 
-If the managed identity for the SQL Server on Azure VM isn't given the `Storage Blob Data Contributor` role to the storage account, the **RESTORE** operation will fail with an error message indicating that access is denied.
+If you haven't configured valid network access to the Azure Blob storage, and Windows Firewall permissions on the host, to allow the outbound connection, and valid storage account service endpoints aren't configured, the `RESTORE` operation fails with an error message indicating that access is denied.
 
-```sql
+```output
 Msg 3201, Level 16, State 1, Line 31
 Cannot open backup device 'https://<storage-account-name>.blob.core.windows.net/<container-name>/AdventureWorks.bak'. Operating system error 5(Access is denied.).
 Msg 3013, Level 16, State 1, Line 31
@@ -107,7 +127,7 @@ RESTORE DATABASE is terminating abnormally.
 
 When the original database with the same name exists in the storage, the backup of a new database to the same storage path will fail with the following error:
 
-```sql
+```output
 Msg 1834, Level 16, State 1, Line 35
 RESTORE DATABASE AdventureWorks 
 from URL = 'https://<storage-account-name>.blob.core.windows.net/<container-name>/AdventureWorks.bak' 

docs/linux/quickstart-install-connect-docker.md

@@ -1,10 +1,10 @@
 ---
-title: "Docker: Install Containers for SQL Server on Linux"
+title: "Docker: Run Containers for SQL Server on Linux"
 description: This quickstart shows how to use Docker to run the SQL Server Linux container images. You connect to a database and run a query.
 author: amitkh-msft
 ms.author: amitkh
 ms.reviewer: vanto, randolphwest
-ms.date: 05/02/2025
+ms.date: 06/06/2025
 ms.service: sql
 ms.subservice: linux
 ms.topic: quickstart
@@ -241,7 +241,7 @@ docker run -e "ACCEPT_EULA=Y" -e "MSSQL_SA_PASSWORD=<password>" `
 > [!CAUTION]  
 > [!INCLUDE [password-complexity](includes/password-complexity.md)] If you don't follow these password requirements, the container can't set up [!INCLUDE [ssnoversion-md](../includes/ssnoversion-md.md)], and stops working. You can examine the error log by using the [`docker logs`](https://docs.docker.com/reference/cli/docker/container/logs) command.
 
-By default, this quickstart creates a container with the Developer edition of [!INCLUDE [ssnoversion-md](../includes/ssnoversion-md.md)]. The process for running production editions in containers is slightly different. For more information, see [Run production container images](./sql-server-linux-docker-container-deployment.md#production).
+By default, this quickstart creates a container with the Developer edition of [!INCLUDE [ssnoversion-md](../includes/ssnoversion-md.md)]. The process for running production editions in containers is slightly different. For more information, see [Run production container images](sql-server-linux-docker-container-deployment.md#production).
 
 The following table provides a description of the parameters in the previous `docker run` example:
 
@@ -485,7 +485,7 @@ docker run -e "ACCEPT_EULA=Y" -e "MSSQL_SA_PASSWORD=<password>" `
 > [!CAUTION]  
 > [!INCLUDE [password-complexity](includes/password-complexity.md)] If you don't follow these password requirements, the container can't set up [!INCLUDE [ssnoversion-md](../includes/ssnoversion-md.md)], and stops working. You can examine the error log by using the [`docker logs`](https://docs.docker.com/reference/cli/docker/container/logs) command.
 
-By default, this quickstart creates a container with the Developer edition of [!INCLUDE [ssnoversion-md](../includes/ssnoversion-md.md)]. The process for running production editions in containers is slightly different. For more information, see [Run production container images](./sql-server-linux-docker-container-deployment.md#production).
+By default, this quickstart creates a container with the Developer edition of [!INCLUDE [ssnoversion-md](../includes/ssnoversion-md.md)]. The process for running production editions in containers is slightly different. For more information, see [Run production container images](sql-server-linux-docker-container-deployment.md#production).
 
 The following table provides a description of the parameters in the previous `docker run` example:
 
@@ -562,7 +562,7 @@ sqlcmd create mssql get-tags
 
 ::: zone-end
 
-By default, this quickstart creates a container with the Developer edition of [!INCLUDE [ssnoversion-md](../includes/ssnoversion-md.md)]. The process for running production editions in containers is slightly different. For more information, see [Run production container images](./sql-server-linux-docker-container-deployment.md#production).
+By default, this quickstart creates a container with the Developer edition of [!INCLUDE [ssnoversion-md](../includes/ssnoversion-md.md)]. The process for running production editions in containers is slightly different. For more information, see [Run production container images](sql-server-linux-docker-container-deployment.md#production).
 
 The following table provides a description of the parameters in the previous `docker run` example:
 
@@ -728,7 +728,7 @@ docker run -e "ACCEPT_EULA=Y" -e "MSSQL_SA_PASSWORD=<password>" `
 > [!CAUTION]  
 > [!INCLUDE [password-complexity](includes/password-complexity.md)] If you don't follow these password requirements, the container can't set up [!INCLUDE [ssnoversion-md](../includes/ssnoversion-md.md)], and stops working. You can examine the error log by using the [`docker logs`](https://docs.docker.com/reference/cli/docker/container/logs) command.
 
-By default, this quickstart creates a container with the Developer edition of [!INCLUDE [ssnoversion-md](../includes/ssnoversion-md.md)]. The process for running production editions in containers is slightly different. For more information, see [Run production container images](./sql-server-linux-docker-container-deployment.md#production).
+By default, this quickstart creates a container with the Developer edition of [!INCLUDE [ssnoversion-md](../includes/ssnoversion-md.md)]. The process for running production editions in containers is slightly different. For more information, see [Run production container images](sql-server-linux-docker-container-deployment.md#production).
 
 The following table provides a description of the parameters in the previous `docker run` example:
 
@@ -858,7 +858,7 @@ sqlcmd create mssql get-tags
 
 ::: zone-end
 
-By default, this quickstart creates a container with the Developer edition of [!INCLUDE [ssnoversion-md](../includes/ssnoversion-md.md)]. The process for running production editions in containers is slightly different. For more information, see [Run production container images](./sql-server-linux-docker-container-deployment.md#production).
+By default, this quickstart creates a container with the Developer edition of [!INCLUDE [ssnoversion-md](../includes/ssnoversion-md.md)]. The process for running production editions in containers is slightly different. For more information, see [Run production container images](sql-server-linux-docker-container-deployment.md#production).
 
 The following table provides a description of the parameters in the previous `docker run` example:
 
@@ -1048,7 +1048,7 @@ docker run -e "ACCEPT_EULA=Y" -e "MSSQL_SA_PASSWORD=<password>" `
 > [!CAUTION]  
 > [!INCLUDE [password-complexity](includes/password-complexity.md)] If you don't follow these password requirements, the container can't set up [!INCLUDE [ssnoversion-md](../includes/ssnoversion-md.md)], and stops working. You can examine the error log by using the [`docker logs`](https://docs.docker.com/reference/cli/docker/container/logs) command.
 
-By default, this quickstart creates a container with the Developer edition of [!INCLUDE [ssnoversion-md](../includes/ssnoversion-md.md)]. The process for running production editions in containers is slightly different. For more information, see [Run production container images](./sql-server-linux-docker-container-deployment.md#production).
+By default, this quickstart creates a container with the Developer edition of [!INCLUDE [ssnoversion-md](../includes/ssnoversion-md.md)]. The process for running production editions in containers is slightly different. For more information, see [Run production container images](sql-server-linux-docker-container-deployment.md#production).
 
 The following table provides a description of the parameters in the previous `docker run` example:
 
@@ -1178,7 +1178,7 @@ sqlcmd create mssql get-tags
 
 ::: zone-end
 
-By default, this quickstart creates a container with the Developer edition of [!INCLUDE [ssnoversion-md](../includes/ssnoversion-md.md)]. The process for running production editions in containers is slightly different. For more information, see [Run production container images](./sql-server-linux-docker-container-deployment.md#production).
+By default, this quickstart creates a container with the Developer edition of [!INCLUDE [ssnoversion-md](../includes/ssnoversion-md.md)]. The process for running production editions in containers is slightly different. For more information, see [Run production container images](sql-server-linux-docker-container-deployment.md#production).
 
 The following table provides a description of the parameters in the previous `docker run` example: