Merging changes synced from https://github.com/MicrosoftDocs/sql-docs-pr (branch live)

Author: Learn Build Service GitHub App

azure-sql/database-watcher-overview.md

@@ -34,3 +34,4 @@ ms.topic: include
 - Enable the [SQL Best Practices Assessment](../virtual-machines/windows/sql-assessment-for-sql-vm.md) to identify possible performance issues and evaluate that your SQL Server VM is configured to follow best practices.
 - Review and monitor disk and VM limits using [Storage IO utilization metrics](/azure/virtual-machines/disks-metrics#storage-io-utilization-metrics).
 - [Exclude SQL Server files](/troubleshoot/sql/database-engine/security/antivirus-and-sql-server) from antivirus software scanning, including data files, log files, and backup files.
+- [Resize the storage pool appropriately](../virtual-machines/windows/performance-guidelines-best-practices-storage.md#resize-storage-pools-appropriately).

azure-sql/includes/virtual-machines-best-practices-storage.md

@@ -25,7 +25,7 @@ Try [Azure SQL Managed Instance](sql-managed-instance-paas-overview.md) free of
 - 64 GB of storage
 
 > [!NOTE]  
-> The free Azure SQL Managed Instance offer is currently in preview.
+> The free Azure SQL Managed Instance offer is currently in [preview](doc-changes-updates-release-notes-whats-new.md#preview).
 
 ## Overview
 

azure-sql/managed-instance/free-offer.md

@@ -169,7 +169,7 @@ sections:
 
       - question: Can I change DNS zone prefix?
         answer: |
-          Yes, the SQL Managed Instance default DNS zone *.database.windows.net* can be changed with your own. However, the managed instance hostname part of its FQDN should remain the same.
+          Yes, the SQL Managed Instance default DNS zone `.database.windows.net` can be changed with your own. However, the managed instance hostname part of its FQDN, including the randomized subzone (ex: `sqlmiFQDN.randomized-subzone` before the `.database.windows.net`) should remain the same.
 
           To use another DNS zone instead of the default, for example, *.contoso.com*: 
           - Use SQL Server Client Network Utility (CliConfg) to define an alias. You can use either just the managed instance hostname, or the managed instance hostname followed by a custom domain name. The CliConfg tool just adds alias in the registry under "HKLM\SOFTWARE\Microsoft\MSSQLServer\Client\ConnectTo" or "HKLM\SOFTWARE\WOW6432Node\Microsoft\MSSQLServer\Client\ConnectTo" depending if you use the 64-bit version (C:\Windows\System32\cliconfg.exe) or the 32-bit version (C:\Windows\SysWOW64\cliconfg.exe), so it can be done using group policy or a script as well. Use both to ensure 32-bit and 64-bit programs can resolve the alias.

azure-sql/managed-instance/frequently-asked-questions-faq.yml

@@ -5,7 +5,7 @@ description: Connect to Azure SQL Managed Instance with SQL Server Management St
 author: zoran-rilak-msft
 ms.author: zoranrilak
 ms.reviewer: mathoma, bonova, jovanpop
-ms.date: 09/27/2023
+ms.date: 04/27/2025
 ms.service: azure-sql-managed-instance
 ms.subservice: deployment-configuration
 ms.topic: quickstart
@@ -17,6 +17,12 @@ ms.custom: mode-other
 
 This quickstart teaches you how to connect to Azure SQL Managed Instance by using [SQL Server Management Studio](/sql/ssms/sql-server-management-studio-ssms) (SSMS) from an on-premises client computer over a point-to-site connection. For information about point-to-site connections, see [About Point-to-Site VPN](/azure/vpn-gateway/point-to-site-about).
 
+## Considerations
+
+This quickstart demonstrates a quick and easy way to connect to Azure SQL Managed Instance. Consider the following:
+- The steps in this article are for demonstration purposes only, and not intended for Enterprise solutions. For production workloads, use a [site-to-site](/azure/vpn-gateway/tutorial-site-to-site-portal), or [ExpressRoute](/azure/expressroute/) connection instead of a point-to-site connection. 
+- The procedure to attach the VPN gateway in this quickstart is intended for a single user to get started with Azure SQL Managed Instance quickly. This VPN uses a certificate-based authentication method tied to the user that establishes the VPN connection. A different user is unable to use the same VPN gateway to connect to SQL Managed Instance without first installing the client certificate that was generated by the first user, which is out of scope for this quickstart, but documented in [Azure point-to-site VPN](/azure/vpn-gateway/point-to-site-about). Additional users following the steps in this quickstart for the same SQL managed instance invalidate the previous user's VPN connection, which prevents them from connecting to the instance. 
+
 ## Prerequisites
 
 This quickstart:
@@ -52,7 +58,7 @@ This quickstart:
 1. Paste the script in your PowerShell window and provide the required parameters. The values for `<subscriptionId>`, `<resourceGroup>`, and `<virtualNetworkName>` should match the ones that you used for the [Create a managed instance](instance-create-quickstart.md) quickstart. The value for `<certificateNamePrefix>` can be a string of your choice.
 
     > [!NOTE]  
-    > If you get an error about parsing the Internet Explorer engine, either launch Internet Explorer to complete the initial set up or upgrade to a newer version of PowerShell.
+    > If you get an error about parsing the Internet Explorer engine, either launch Internet Explorer to complete the initial setup or upgrade to a newer version of PowerShell.
 
 1. Execute the PowerShell script.
 

azure-sql/managed-instance/point-to-site-p2s-configure.md

@@ -171,8 +171,8 @@ The following screenshot shows an example output:
 `tempdb` max size is the limit after which your `tempdb` can't grow further. 
 
 `tempdb` max size in SQL Managed Instance has the following limitations: 
-- In the General Purpose service tier, the maximum size for `tempdb` is limited to 24 GB/vCore (96-1920 GB), and the log file is 120 GB. 
-- In the Business Critical service tier, `tempdb` competes with other databases for resources, so the reserved storage is shared between `tempdb` and other databases. The max size of the `tempdb` log file is 2 TB. 
+- In the General Purpose service tier, the maximum size for `tempdb` is limited to 24 GB/vCore (96-1920 GB). The max size of the `tempdb` log file is 120 GB. 
+- In the Business Critical service tier, `tempdb` competes with other databases for resources, so the reserved storage is shared between `tempdb` and other databases up to the max storage size allocated to the instance. The max size of the `tempdb` log file is 2 TB. 
 
 `tempdb` files grow until they reach either the maximum limit allowed by the service tier, or by the manually configured max `tempdb` file size. 
 
@@ -256,7 +256,8 @@ The following table defines limits for various `tempdb` configuration settings:
 |Initial size of `tempdb` log files     |    16 MB     |
 |Default growth increment of `tempdb` log files     |   64 MB      |
 |Initial max `tempdb`size    |   -1 (unlimited)       |
-|Max size of `tempdb` | Up to the storage size | 
+|Max size of `tempdb` data files | - In the General Purpose service tier: 24 GB/vCore up to 1920 GB total  <br /> In the Business Critical service tier: Up to the storage size | 
+|Max size of `tempdb` log files | - In the General Purpose service tier: 120 GB <br /> In the Business Critical service tier: 2 TB |
 
 
 ## Next steps