[BULK] - DocuTune - Rebranding of Azure Active Directory to Microsoft Entra

resetting ssms with main

updating a few things

fixing ssma articles

moving ssms articles back

fixing a few more things

updating includes

Author: alexbuckgit

docs/ssma/mysql/migrating-mysql-data-into-sql-server-azure-sql-db-mysqltosql.md

@@ -22,6 +22,8 @@ After you have successfully synchronized the converted objects with [!INCLUDE[ss
 > [!IMPORTANT]  
 > If the engine being used is Server Side Data Migration Engine, then, before migrating data, you must install the SSMA for MySQL Extension Pack and the MySQL providers on the computer that is running SSMA. The [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] Agent service must also be running. For more information about how to install the extension pack, see [Installing SSMA Components on SQL Server (MySQL to SQL)](./installing-ssma-components-on-sql-server-mysqltosql.md)  
   
+[!INCLUDE [entra-id](../../includes/entra-id-hard-coded.md)]
+
 ## Setting Migration Options  
 Before migrating data to [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] or SQL Azure, review the project migration options in the **Project Settings** dialog box.  
 
@@ -110,7 +112,7 @@ When large data size needs to be migrated within a short duration, at scale offl
 
 1. For large offline migration, click on Migrate data at scale. 
 
-1. Provide Azure active directory account for authentication. Once you entered the user name, click on connect.
+1. Provide Microsoft Entra/Azure AD account for authentication. Once you entered the user name, click on connect.
 
 1. Select the tenant and the subscription that already has the Azure SQL VM or Azure SQL database or managed instance configured and click next.
 

docs/ssma/mysql/what-s-new-in-ssma-for-mysql-mysqltosql.md

@@ -16,6 +16,8 @@ ms.custom:
 
 This article lists SQL Server Migration Assistant (SSMA) for MySQL changes in each release.
 
+[!INCLUDE [entra-id](../../includes/entra-id-hard-coded.md)]
+
 ## SSMA v9.5
 
 The v9.5 release of SSMA for MySQL contains the following changes:
@@ -125,7 +127,7 @@ The v8.16 release of SSMA for MySQL contains the following changes:
 In addition to several accessibility improvements, the v8.15 release of SSMA for MySQL contains the following changes:
 
 - Revamp assessment reports to work in modern browsers
-- Use authority provided by the database for Azure AD authentication
+- Use authority provided by the database for Microsoft Entra/Azure AD authentication
 - Improve naming for statements loaded from files
 
 ## SSMA v8.14
@@ -149,7 +151,7 @@ The v8.12 release of SSMA for MySQL contains the following changes:
 
 The v8.11 release of SSMA for MySQL contains the following changes:
 
-- Use MSAL.NET library for interactive Azure Active Directory authentication
+- Use MSAL.NET library for interactive Microsoft Entra/Azure AD authentication
 
 ## SSMA v8.10
 
@@ -191,7 +193,7 @@ To use this setting, in SSMA for MySQL, navigate to **Tools** > **Project Settin
 
 ## SSMA v8.5
 
-The v8.5 release of SSMA for MySQL is enhanced with support for Azure Active Directory authentication and basic support for JSON features in SQL Server, together with a targeted set of fixes designed to improve usability and performance.
+The v8.5 release of SSMA for MySQL is enhanced with support for Microsoft Entra/Azure AD authentication and basic support for JSON features in SQL Server, together with a targeted set of fixes designed to improve usability and performance.
 
 > [!IMPORTANT]  
 > With SSMA v8.5, .NET 4.7.2 is an installation prerequisite. If you need to install this version, you can [download the runtime file](https://dotnet.microsoft.com/download/dotnet-framework/net472).

docs/ssma/oracle/migrating-oracle-data-into-sql-server-oracletosql.md

@@ -22,6 +22,8 @@ After you have successfully synchronized the converted objects with [!INCLUDE[ss
 > [!IMPORTANT]  
 > If the engine being used is Server Side Data Migration Engine, then, before you can migrate data, you must install the SSMA for Oracle Extension Pack and the Oracle providers on the computer that is running SSMA. The SQL Server Agent service must also be running. For more information about how to install the extension pack, see [Installing Server Components (OracleToSQL)](./installing-ssma-components-on-sql-server-oracletosql.md)  
   
+[!INCLUDE [entra-id](../../includes/entra-id-hard-coded.md)]
+
 ## Setting Migration Options  
 Before migrating data to [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)], review the project migration options in the **Project Settings** dialog box.  
 
@@ -103,7 +105,7 @@ When large data size needs to be migrated within a short duration, at scale offl
 
 1. For large offline migration, click on Migrate data at scale. 
 
-1. Provide Azure active directory account for authentication. Once you entered the user name, click on connect.
+1. Provide Microsoft Entra/Azure AD account for authentication. Once you entered the user name, click on connect.
 
 1. Select the tenant and the subscription that already has the Azure SQL VM or Azure SQL database or managed instance configured and click next.
 

docs/ssma/oracle/what-s-new-in-ssma-for-oracle-oracletosql.md

@@ -15,6 +15,8 @@ ms.custom:
 
 This article lists SQL Server Migration Assistant (SSMA) for Oracle changes in each release.
 
+[!INCLUDE [entra-id](../../includes/entra-id-hard-coded.md)]
+
 ## SSMA v9.5
 
 The v9.5 release of SSMA for Oracle contains the following changes:
@@ -140,7 +142,7 @@ In addition to several accessibility improvements, the v8.15 release of SSMA for
 
 * Add setting to use full type specification for `%type` and `%rowtype` attributes
 * Revamp assessment reports to work in modern browsers
-* Use authority provided by the database for Azure AD authentication
+* Use authority provided by the database for Microsoft Entra/Azure AD authentication
 * Improve naming for statements loaded from files
 
 ## SSMA v8.14
@@ -177,7 +179,7 @@ The v8.11 release of SSMA for Oracle contains the following changes:
 * Improved conversion of `COMMIT` statement
 * Fix bug in `CONNECT BY LEVEL` clause conversion
 * Updated parser error recovery logic to be less greedy
-* Use MSAL.NET library for interactive Azure Active Directory authentication
+* Use MSAL.NET library for interactive Microsoft Entra/Azure AD authentication
 
 ## SSMA v8.10
 
@@ -234,7 +236,7 @@ In addition, SSMA for Oracle now provides improved parsing of the `XMLTABLE` cla
 
 ## SSMA v8.5
 
-The v8.5 release of SSMA for Oracle is enhanced with support for Azure Active Directory authentication and basic support for JSON features in SQL Server, together with a targeted set of fixes designed to improve usability and performance.
+The v8.5 release of SSMA for Oracle is enhanced with support for Microsoft Entra/Azure AD authentication and basic support for JSON features in SQL Server, together with a targeted set of fixes designed to improve usability and performance.
 
 In addition, SSMA for Oracle has been enhanced with support for:
 

docs/ssma/sybase/migrating-sybase-ase-data-into-sql-server-azure-sql-db-sybasetosql.md

@@ -110,7 +110,7 @@ When large data size 100GB and above needs to be migrated within a short duratio
 
 1. For large offline migration, click on Migrate data at scale. The offline data migration supports database level migration.
 
-1. Provide Azure active directory account for authentication. Once you entered the user name, click on connect.
+1. Provide Microsoft Entra/Azure AD account for authentication. Once you entered the user name, click on connect.
 
 1. Select the tenant and the subscription that already has the Azure SQL VM or Azure SQL database or managed instance configured and click next.
 

docs/ssma/sybase/what-s-new-in-ssma-for-sybase-sybasetosql.md

@@ -15,6 +15,8 @@ ms.custom:
 
 This article lists SQL Server Migration Assistant (SSMA) for SAP ASE (formerly SSMA for Sybase) changes in each release.
 
+[!INCLUDE [entra-id](../../includes/entra-id-hard-coded.md)]
+
 ## SSMA v9.5
 The v9.5 release of SSMA for SAP ASE contains the following changes:
 * Support for exclude schema in SSMA console mode
@@ -118,7 +120,7 @@ The v8.16 release of SSMA for SAP ASE contains the following changes:
 In addition to several accessibility improvements, the v8.15 release of SSMA for SAP ASE contains the following changes:
 
 * Revamp assessment reports to work in modern browsers
-* Use authority provided by the database for Azure AD authentication
+* Use authority provided by the database for Microsoft Entra/Azure AD authentication
 * Improve naming for statements loaded from files
 
 ## SSMA v8.14
@@ -141,7 +143,7 @@ The v8.12 release of SSMA for SAP ASE contains minor performance improvements an
 The v8.11 release of SSMA for SAP ASE contains the following changes:
 
 * Fix conversion of temporary tables
-* Use MSAL.NET library for interactive Azure Active Directory authentication
+* Use MSAL.NET library for interactive Microsoft Entra/Azure AD authentication
 
 ## SSMA v8.10
 
@@ -182,7 +184,7 @@ To leverage this setting, in SSMA for SAP ASE, navigate to **Tools** > **Project
 
 ## SSMA v8.5
 
-The v8.5 release of SSMA for SAP ASE is enhanced with support for Azure Active Directory authentication and basic support for JSON features in SQL Server, together with a targeted set of fixes designed to improve usability and performance.
+The v8.5 release of SSMA for SAP ASE is enhanced with support for Microsoft Entra/Azure AD authentication and basic support for JSON features in SQL Server, together with a targeted set of fixes designed to improve usability and performance.
 
 In addition, SSMA for SAP ASE now allows you to hide system tables and views (exclude them from conversion).
 

docs/ssms/f1-help/connect-to-server-login-page-database-engine.md

@@ -79,7 +79,7 @@ The current version of SQL Server Management Studio (SSMS) offers eight authenti
 
 The user name to connect with. This setting is read-only when you select **Windows Authentication** or **Microsoft Entra Integrated** authentication. The setting is prefilled with the Windows user name you're currently logged in with.
 
-If you're connecting with **Microsoft Entra Universal with MFA**, **Microsoft Entra Password**, **Microsoft Entra Service Principal**, or **Microsoft Entra Default**, enter the name of the Microsoft Entra identity you're connecting with.
+If you connect with **Microsoft Entra Universal with MFA**, **Microsoft Entra Password**, **Microsoft Entra Service Principal**, or **Microsoft Entra Default**, enter the name of the Microsoft Entra identity you're connecting with.
 
 #### User assigned identity
 

docs/ssms/menu-help/options-azure-services.md

@@ -1,6 +1,6 @@
 ---
 title: SQL Server Options page - Azure Services
-description: Options (Azure Services)
+description: "Options (Azure Services)"
 author: erinstellato-ms
 ms.author: erinstellato
 ms.reviewer: maghan

docs/ssms/menu-help/options-output-window-page.md

@@ -24,6 +24,8 @@ dev_langs:
 
 Use this page to set the default behavior of the output window.
 
+[!INCLUDE [entra-id](../../includes/entra-id-hard-coded.md)]
+
 The Output Window can be opened from the View menu. To access the settings, on the **Tools** menu, select **Options**, and expand the **Output Window** folder or use the key combination Ctrl+Alt+O.
 
 There are multiple logging channels available to provide more information when using SQL Server Management Studio.
@@ -35,6 +37,6 @@ The following table gives an overview of the types of messages associated with e
 | **Object Explorer** | This channel outputs the query text and elapsed times of SQL queries needed to expand nodes in Object Explorer. Each query logs a Begin Query and an End Query event. Each event has a timestamp and the URN associated with the entity being queried. The URN refers to the underlying SQL Management Object and consists of an XPath-style hierarchy. For example, the URN for a table named "Table1" in database "Db" on server "MyServer" would be "Server[@Name='MyServer']/Database[@Name='Db']/Table[/@Name='Table1']". Expanding one node in Object Explorer can require multiple such queries with different parameters. The End Query event contains the elapsed time of the query along with the T-SQL text. This query data is useful for server performance analysis in cases where Object Explorer seems unusually slow to expand a particular node. Note: only some nodes in Object Explorer provide this query detail when expanding. Enabled by default. |
 | **Telemetry** | Telemetry is the stream of anonymous feature usage data collected by Microsoft. These events could be useful for your tracking of SSMS usage. It can help you identify what Object Explorer nodes you expand and what commands run during your SSMS session while the Output window is open. Enabled by default. |
 | **SQL Client** | This channel displays information from the Microsoft.Data.SqlClient data provider. This option requires a restart of SSMS for output to appear. |
-| **Microsoft Entra Interactive authentication** | For cases where Microsoft Entra authentication is used, this channel outputs information specific to the authentication process. |
-| **Azure REST API** | This channel starts after authentication with Microsoft Entra credentials occurs.  This channel outputs information specific to Azure REST API calls when Azure-connected features are used and more troubleshooting information is needed. |
+| **Microsoft Entra interactive authentication** | For cases where Microsoft Entra authentication is used, this channel outputs information specific to the authentication process. |
+| **Azure REST API** | This channel starts after authentication with Microsoft Entra credentials occurs. This channel outputs information specific to Azure REST API calls when Azure-connected features are used and more troubleshooting information is needed. |
 | **Activity Monitor** | This channel starts when [Activity Monitor](../../relational-databases/performance-monitor/activity-monitor.md) opens for a server. This stream contains events showing part of the query text and timestamp of each query, error messages, and notifications of the monitor being paused due to connectivity problems. If Activity Monitor is idle or otherwise failing to update, check this output channel for more information. |

docs/ssms/quickstarts/ssms-connect-query-azure-sql.md

@@ -16,6 +16,8 @@ ms.custom: intro-quickstart
 
 Get started using SQL Server Management Studio (SSMS) to connect to your Azure SQL Database and run some Transact-SQL (T-SQL) commands.
 
+[!INCLUDE [entra-id](../../includes/entra-id-hard-coded.md)]
+
 The article demonstrates the following steps:
 
 > [!div class="checklist"]
@@ -47,10 +49,10 @@ The article demonstrates the following steps:
    | **Server name** | The fully qualified server name | Enter the name of your *Azure SQL Database* or *Azure SQL Managed Instance* name. |
    | **Authentication** | | |
    | | Azure Active Directory <sup>1</sup> | |
-   | | - Universal with MFA | See [Using multi-factor Azure Active Directory authentication](/azure/azure-sql/database/authentication-mfa-ssms-overview). |
-   | | - Password<br />- Integrated<br />- Service Principal | See [Azure Active Directory service principal with Azure SQL](/azure/azure-sql/database/authentication-aad-service-principal). |
-   | | - Managed Identity | See [Managed identities in Azure AD for Azure SQL](/azure/azure-sql/database/authentication-azure-ad-user-assigned-managed-identity).<br />Connecting to a SQL instance with SSMS using a managed identity requires an Azure VM. See [Use a Windows VM system-assigned managed identity to access Azure SQL](/azure/active-directory/managed-identities-azure-resources/tutorial-windows-vm-access-sql)  |
-   | | - Default | The default option can be used when connecting using any Azure AD authentication mode that's passwordless and noninteractive. |
+   | | - Universal with MFA | See [Using multi-factor Microsoft Entra authentication](/azure/azure-sql/database/authentication-mfa-ssms-overview). |
+   | | - Password<br />- Integrated<br />- Service Principal | See [Microsoft Entra service principal with Azure SQL](/azure/azure-sql/database/authentication-aad-service-principal). |
+   | | - Managed Identity | See [Managed identities in Microsoft Entra for Azure SQL](/azure/azure-sql/database/authentication-azure-ad-user-assigned-managed-identity).<br />Connecting to a SQL instance with SSMS using a managed identity requires an Azure VM. See [Use a Windows VM system-assigned managed identity to access Azure SQL](/azure/active-directory/managed-identities-azure-resources/tutorial-windows-vm-access-sql)  |
+   | | - Default | The default option can be used when connecting using any Microsoft Entra authentication mode that's passwordless and noninteractive. |
    | | SQL Server Authentication | Use **SQL Server Authentication** for Azure SQL to connect. |
    | **Login** | Server account user ID | The user ID from the server account used to create the server. |
    | **Password** | Server account password | The password from the server account used to create the server. |

docs/ssms/quickstarts/ssms-connect-query-sql-server-azure-vm.md

@@ -17,13 +17,16 @@ ms.custom: intro-quickstart
 
 Get started using SQL Server Management Studio (SSMS) to connect to your SQL Server instance on an Azure Virtual Machine and run some Transact-SQL (T-SQL) commands.
 
+[!INCLUDE [entra-id](../../includes/entra-id-hard-coded.md)]
+
 > [!div class="checklist"]
 > - Connect to a SQL Server instance
 > - Create a database
 > - Create a table in your new database
 > - Insert rows into your new table
 > - Query the new table and view the results
 > - Use the query window table to verify your connection properties
+
 ## Prerequisites
 
 To complete this article, you need SQL Server Management Studio and access to a data source.
@@ -67,8 +70,8 @@ To connect to the SQL Server Database Engine from the Internet, consider creatin
     |   Setting   |   Suggested Value(s)   |   Description   |
     |--------------|-----------------------|-----------------|
     | **Server type** | Database engine | For **Server type**, select **Database Engine** (usually the default option). |
-    | **Server name** | The fully qualified server name | For **Server name**, enter the name of your Azure SQL VM name. You can also use the Azure SQL VM IP address to connect. | 
-    | **Authentication** | SQL Server Authentication | Use **SQL Server Authentication** for Azure SQL VM to connect. Also, if you have an Azure Active Directory environment setup, you can use any of the Azure Active Directory options. </br> </br> The **Windows Authentication** method isn't supported for Azure SQL VM. For more information, see [Azure SQL authentication](/azure/sql-database/sql-database-security-overview#access-management).|
+    | **Server name** | The fully qualified server name | For **Server name**, enter the name of your SQL Server VM name. You can also use the SQL Server VM IP address to connect. | 
+    | **Authentication** | SQL Server Authentication | Use **SQL Server Authentication** for SQL Server VM to connect. Also, if you have a Microsoft Entra tenant setup, you can use any of the Azure Active Directory options. </br> </br> The **Windows Authentication** method isn't supported for SQL Server VM. For more information, see [Azure SQL authentication](/azure/sql-database/sql-database-security-overview#access-management).|
     | **Login** | Server account user ID | The user ID from the server account used to create the server. A login is required when using **SQL Server Authentication**. |
     | **Password** | Server account password | The password from the server account used to create the server. A password is required when using **SQL Server Authentication**. |