Merge pull request #35912 from rwestMSFT/rw-1124-ssms-url

[SCOPED] Fix SSMS links

Author: Carolyn135

azure-sql/database-watcher-analyze.md

@@ -771,7 +771,7 @@ wait_type_sample
 
 If you are already familiar with T-SQL, you can start querying and analyzing SQL monitoring data right away without having to learn KQL. However, [KQL](#use-kql-to-analyze-monitoring-data) is the recommended language for querying data in Azure Data Explorer or Real-Time Analytics because it provides unparalleled support for querying telemetry data.
 
-You can connect to your Azure Data Explorer or Real-Time Analytics database from [SQL Server Management Studio (SSMS)](/sql/ssms/download-sql-server-management-studio-ssms), Visual Studio Code with the [SQL server mssql](https://marketplace.visualstudio.com/items?itemName=ms-mssql.mssql) extension, and other [common tools](/azure/data-explorer/connect-common-apps). You can query an Azure Data Explorer or a KQL database as if it were a SQL Server or an Azure SQL database. For more information, see [Query data in Azure Data Explorer using SQL Server emulation](/azure/data-explorer/sql-server-emulation-overview).
+You can connect to your Azure Data Explorer or Real-Time Analytics database from [SQL Server Management Studio (SSMS)](/ssms/sql-server-management-studio-ssms), Visual Studio Code with the [SQL server mssql](https://marketplace.visualstudio.com/items?itemName=ms-mssql.mssql) extension, and other [common tools](/azure/data-explorer/connect-common-apps). You can query an Azure Data Explorer or a KQL database as if it were a SQL Server or an Azure SQL database. For more information, see [Query data in Azure Data Explorer using SQL Server emulation](/azure/data-explorer/sql-server-emulation-overview).
 
 > [!NOTE]
 > Not every T-SQL construct is supported in Azure Data Explorer and Real-Time Analytics. For details, see [Query data using T-SQL](/azure/data-explorer/t-sql).

azure-sql/database-watcher-manage.md

@@ -58,7 +58,7 @@ To use database watcher, the following prerequisites are required.
 
 - The user who configures the watcher must have administrator access to the Azure SQL targets. An administrator grants the watcher limited, specific access to SQL monitoring targets. For more information, see [Grant access to targets](#grant-access-to-sql-targets).
 
-- To grant a watcher access to a SQL target, an administrator needs to execute T-SQL scripts using [SQL Server Management Studio (SSMS)](/sql/ssms/download-sql-server-management-studio-ssms), Visual Studio Code with the [SQL server mssql](https://marketplace.visualstudio.com/items?itemName=ms-mssql.mssql) extension, or other SQL client tools.
+- To grant a watcher access to a SQL target, an administrator needs to execute T-SQL scripts using [SQL Server Management Studio (SSMS)](/ssms/sql-server-management-studio-ssms), Visual Studio Code with the [SQL server mssql](https://marketplace.visualstudio.com/items?itemName=ms-mssql.mssql) extension, or other SQL client tools.
 
 - To use [Azure Private Link](/azure/private-link/private-link-overview) for private connectivity to Azure resources, the user who approves the private endpoint must be a member of the **Owner** RBAC role, or must have the required RBAC permissions. For more information, see [Approval RBAC for private endpoint](/azure/private-link/rbac-permissions#approval-rbac-for-private-endpoint).
 

azure-sql/database/active-directory-interactive-connect-azure-sql-db.md

@@ -74,7 +74,7 @@ The C# example relies on the [Microsoft.Data.SqlClient](/sql/connect/ado-net/int
 
 ## Verify with SQL Server Management Studio
 
-Before you run the C# example, it's a good idea to check that your setup and configurations are correct in [SQL Server Management Studio (SSMS)](/sql/ssms/download-sql-server-management-studio-ssms). Any C# program failure can then be narrowed to source code.
+Before you run the C# example, it's a good idea to check that your setup and configurations are correct in [SQL Server Management Studio (SSMS)](/ssms/sql-server-management-studio-ssms). Any C# program failure can then be narrowed to source code.
 
 ### Verify server-level firewall IP addresses
 

azure-sql/database/always-encrypted-enclaves-enable.md

@@ -77,7 +77,7 @@ You can set the **preferredEnclaveType** property using the Azure portal, SQL Se
 
 ## Enable VBS enclaves using SQL Server Management Studio
 
-Download the latest version of [SQL Server Management Studio (SSMS)](/sql/ssms/download-sql-server-management-studio-ssms).
+Download the latest version of [SQL Server Management Studio (SSMS)](/ssms/install/install).
 
 ### Create a new database with a VBS enclave
 

azure-sql/database/always-encrypted-enclaves-getting-started-sgx.md

@@ -29,7 +29,7 @@ This tutorial teaches you how to get started with [Always Encrypted with secure
 - Optional, but recommended for storing your column master key for Always Encrypted: a key vault in Azure Key Vault. For information on how to create a key vault, see [Quickstart: Create a key vault using the Azure portal](/azure/key-vault/general/quick-create-portal). 
   - If your key vault uses the access policy permissions model, make sure you have the following key permissions in the key vault: `get`, `list`, `create`, `unwrap key`, `wrap key`, `verify`, `sign`. For more information, see [Assign a Key Vault access policy](/azure/key-vault/general/assign-access-policy).
   - If you're using the Azure role-based access control (RBAC) permission model, make you sure you're a member of the [Key Vault Crypto Officer](/azure/role-based-access-control/built-in-roles#key-vault-crypto-officer) role for your key vault. See [Provide access to Key Vault keys, certificates, and secrets with an Azure role-based access control](/azure/key-vault/general/rbac-migration).
-- The latest version of [SQL Server Management Studio (SSMS)](/sql/ssms/download-sql-server-management-studio-ssms).
+- The latest version of [SQL Server Management Studio (SSMS)](/ssms/install/install).
 
 ### PowerShell requirements
 

azure-sql/database/always-encrypted-enclaves-getting-started-vbs.md

@@ -35,7 +35,7 @@ SQL Server Management Studio (SSMS) is required for this tutorial. You can choos
 
 # [SSMS](#tab/ssmsrequirements)
 
-Download the latest version of [SQL Server Management Studio (SSMS)](/sql/ssms/download-sql-server-management-studio-ssms).
+Download the latest version of [SQL Server Management Studio (SSMS)](/ssms/install/install).
 
 # [PowerShell](#tab/azure-powershellrequirements)
 

azure-sql/database/auditing-overview.md

@@ -72,7 +72,7 @@ You can use SQL Database auditing to:
 - **Premium storage** with **BlockBlobStorage** is supported. Standard storage is supported. However, for audit to write to a storage account behind a virtual network or firewall, you must have a **general-purpose v2 storage account**. If you have a general-purpose v1 or Blob Storage account, [upgrade to a general-purpose v2 storage account](/azure/storage/common/storage-account-upgrade). For specific instructions see, [Write audit to a storage account behind VNet and firewall](audit-write-storage-account-behind-vnet-firewall.md). For more information, see [Types of storage accounts](/azure/storage/common/storage-account-overview#types-of-storage-accounts).
 - **Hierarchical namespace** for all types of **standard storage account** and **premium storage account with BlockBlobStorage** is supported.
 - Audit logs are written to **Append Blobs** in an Azure Blob Storage on your Azure subscription
-- Audit logs are in .xel format and can be opened with [SQL Server Management Studio (SSMS)](/sql/ssms/download-sql-server-management-studio-ssms).
+- Audit logs are in .xel format and can be opened with [SQL Server Management Studio (SSMS)](/ssms/sql-server-management-studio-ssms).
 - To configure an immutable log store for the server or database-level audit events, follow the [instructions provided by Azure Storage](/azure/storage/blobs/immutable-time-based-retention-policy-overview#allow-protected-append-blobs-writes). When configuring immutable blob storage for auditing, ensure that **Allow protected append writes** is set to either **Append blobs** or **Block and append blobs**. The **None** option isn't supported. For time-based retention policies, the storage account's retention interval must be shorter than the SQL Auditing retention setting. Configurations where the storage policy is set, but SQL Auditing retention is `0`, aren't supported.
 
 - You can write audit logs to an Azure Storage account behind a virtual network or firewall.

azure-sql/database/authentication-aad-guest-users.md

@@ -53,7 +53,7 @@ Follow these steps to create a database user using a Microsoft Entra guest user.
    SELECT * FROM sys.database_principals;
    ```
 
-1. Disconnect and sign into the database as the guest user using [SQL Server Management Studio (SSMS)](/sql/ssms/download-sql-server-management-studio-ssms) using the authentication method **Azure Active Directory - Universal with MFA**. For more information, see [Using Microsoft Entra multifactor authentication](authentication-mfa-ssms-overview.md).
+1. Disconnect and sign into the database as the guest user using [SQL Server Management Studio (SSMS)](/ssms/sql-server-management-studio-ssms) using the authentication method **Azure Active Directory - Universal with MFA**. For more information, see [Using Microsoft Entra multifactor authentication](authentication-mfa-ssms-overview.md).
 
 ### Create guest user in SQL Managed Instance
 
@@ -84,7 +84,7 @@ Follow these steps to create a database user using a Microsoft Entra guest user.
 
 1. There should now be a database user created for the guest user.
 
-1. Disconnect and sign into the database as the guest user using [SQL Server Management Studio (SSMS)](/sql/ssms/download-sql-server-management-studio-ssms) using the authentication method **Azure Active Directory - Universal with MFA**. For more information, see [Using Microsoft Entra multifactor authentication](authentication-mfa-ssms-overview.md).
+1. Disconnect and sign into the database as the guest user using [SQL Server Management Studio (SSMS)](/ssms/sql-server-management-studio-ssms) using the authentication method **Azure Active Directory - Universal with MFA**. For more information, see [Using Microsoft Entra multifactor authentication](authentication-mfa-ssms-overview.md).
 
 ## Set a guest user as a Microsoft Entra admin
 

azure-sql/database/authentication-aad-overview.md

@@ -271,7 +271,7 @@ For creating Microsoft Entra principals and a few other scenarios, Azure SQL nee
 
 ## Tools support
 
-[SQL Server Management Studio (SSMS)](/sql/ssms/download-sql-server-management-studio-ssms) supports a number of Microsoft Entra authentication connection options, including [multifactor authentication](authentication-mfa-ssms-overview.md).
+[SQL Server Management Studio (SSMS)](/ssms/sql-server-management-studio-ssms) supports a number of Microsoft Entra authentication connection options, including [multifactor authentication](authentication-mfa-ssms-overview.md).
 
 [SQL Server Data Tools (SSDT)](/sql/ssdt/sql-server-data-tools) for Visual Studio, starting with 2015, supports Password, Integrated, and Interactive authentication with Microsoft Entra ID. For more information, see [Microsoft Entra ID support in SQL Server Data Tools (SSDT)](/sql/ssdt/azure-active-directory).
 - Currently, Microsoft Entra users aren't shown in SSDT Object Explorer. As a workaround, view the users in [sys.database_principals](/sql/relational-databases/system-catalog-views/sys-database-principals-transact-sql).

azure-sql/database/authentication-azure-ad-logins-tutorial.md

@@ -58,7 +58,7 @@ In this tutorial, you learn how to:
    >
    > For more information, see [Microsoft Entra logins and users with nonunique display names](authentication-microsoft-entra-create-users-with-nonunique-names.md).
 
-1. Using [SQL Server Management Studio (SSMS)](/sql/ssms/download-sql-server-management-studio-ssms), log into your SQL Database with the Microsoft Entra admin account set up for the server.
+1. Using [SQL Server Management Studio (SSMS)](/ssms/sql-server-management-studio-ssms), log into your SQL Database with the Microsoft Entra admin account set up for the server.
 1. Expand **Databases** > **System Databases**. Right-click the `master` database and select **New Query** to open a new query window in the context of the `master` database.
 1. Run the following query: