Changed AAD to Azure AD x3

Author: megvanhuygen

articles/synapse-analytics/sql-data-warehouse/sql-data-warehouse-troubleshoot.md

@@ -20,16 +20,16 @@ This article lists common troubleshooting question.
 ## Connecting
 | Issue                                                        | Resolution                                                   |
 | :----------------------------------------------------------- | :----------------------------------------------------------- |
-| Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. (Microsoft SQL Server, Error: 18456) | This error occurs when an AAD user tries to connect to the master database, but does not have a user in master.  To correct this issue, either specify the SQL pool you wish to connect to at connection time or add the user to the master database.  See [Security overview](sql-data-warehouse-overview-manage-security.md) article for more details. |
-| The server principal "MyUserName" is not able to access the database "master" under the current security context. Cannot open user default database. Login failed. Login failed for user 'MyUserName'. (Microsoft SQL Server, Error: 916) | This error occurs when an AAD user tries to connect to the master database, but does not have a user in master.  To correct this issue, either specify the SQL pool you wish to connect to at connection time or add the user to the master database.  See [Security overview](sql-data-warehouse-overview-manage-security.md) article for more details. |
+| Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. (Microsoft SQL Server, Error: 18456) | This error occurs when an Azure AD user tries to connect to the master database, but does not have a user in master.  To correct this issue, either specify the SQL pool you wish to connect to at connection time or add the user to the master database.  See [Security overview](sql-data-warehouse-overview-manage-security.md) article for more details. |
+| The server principal "MyUserName" is not able to access the database "master" under the current security context. Cannot open user default database. Login failed. Login failed for user 'MyUserName'. (Microsoft SQL Server, Error: 916) | This error occurs when an Azure AD user tries to connect to the master database, but does not have a user in master.  To correct this issue, either specify the SQL pool you wish to connect to at connection time or add the user to the master database.  See [Security overview](sql-data-warehouse-overview-manage-security.md) article for more details. |
 | CTAIP error                                                  | This error can occur when a login has been created on the SQL server master database, but not in the SQL database.  If you encounter this error, take a look at the [Security overview](sql-data-warehouse-overview-manage-security.md) article.  This article explains how to create a login and user on master, and then how to create a user in the SQL database. |
 | Blocked by Firewall                                          | SQL pools are protected by firewalls to ensure only known IP addresses have access to a database. The firewalls are secure by default, which means that you must explicitly enable and IP address or range of addresses before you can connect.  To configure your firewall for access, follow the steps in [Configure server firewall access for your client IP](create-data-warehouse-portal.md) in the [Provisioning instructions](create-data-warehouse-portal.md). |
 | Cannot connect with tool or driver                           | Synapse SQL pool recommends using [SSMS](/sql/ssms/download-sql-server-management-studio-ssms?view=sql-server-ver15), [SSDT for Visual Studio](sql-data-warehouse-install-visual-studio.md), or [sqlcmd](sql-data-warehouse-get-started-connect-sqlcmd.md) to query your data. For more information on drivers and connecting to Azure Synapse, see [Drivers for Azure Synapse](sql-data-warehouse-connection-strings.md) and [Connect to Azure Synapse](sql-data-warehouse-connect-overview.md) articles. |
 
 ## Tools
 | Issue                                                        | Resolution                                                   |
 | :----------------------------------------------------------- | :----------------------------------------------------------- |
-| Visual Studio object explorer is missing AAD users           | This is a known issue.  As a workaround, view the users in [sys.database_principals](https://docs.microsoft.com/sql/relational-databases/system-catalog-views/sys-database-principals-transact-sql?view=sql-server-ver15).  See [Authentication to Azure Synapse](sql-data-warehouse-authentication.md) to learn more about using Azure Active Directory with Synapse SQL pool. |
+| Visual Studio object explorer is missing Azure AD users           | This is a known issue.  As a workaround, view the users in [sys.database_principals](https://docs.microsoft.com/sql/relational-databases/system-catalog-views/sys-database-principals-transact-sql?view=sql-server-ver15).  See [Authentication to Azure Synapse](sql-data-warehouse-authentication.md) to learn more about using Azure Active Directory with Synapse SQL pool. |
 | Manual scripting, using the scripting wizard, or connecting via SSMS is slow, not responding, or producing errors | Ensure that users have been created in the master database. In scripting options, also make sure that the engine edition is set as "Microsoft Azure SQL Data Warehouse Edition" and engine type is "Microsoft Azure SQL Database". |
 | Generate scripts fails in SSMS                               | Generating a script for Synapse SQL pool fails if the option "Generate script for dependent objects" option is set to "True." As a workaround, users must manually go to **Tools -> Options ->SQL Server Object Explorer -> Generate script for dependent options and set to false** |