find and replace SQL Analytics

Author: Kat-Campise

articles/synapse-analytics/sql/access-control.md

@@ -168,4 +168,4 @@ DROP USER [<workspacename>];
 
 ## Next steps
 
-For an overview of access and control in SQL Analytics, see [SQL Analytics access control](../sql/access-control.md). To learn more about database principals, see [Principals](https://msdn.microsoft.com/library/ms181127.aspx). Additional information about database roles, can be found in the [Database roles](https://msdn.microsoft.com/library/ms189121.aspx) article.
+For an overview of access and control in Synapse SQL, see [Synapse SQL access control](../sql/access-control.md). To learn more about database principals, see [Principals](https://msdn.microsoft.com/library/ms181127.aspx). Additional information about database roles, can be found in the [Database roles](https://msdn.microsoft.com/library/ms189121.aspx) article.

articles/synapse-analytics/sql/active-directory-authentication.md

@@ -1,6 +1,6 @@
 ---
 title: Azure Active Directory
-description: Learn about how to use Azure Active Directory for authentication with SQL Database, Managed Instance, and SQL Analytics
+description: Learn about how to use Azure Active Directory for authentication with SQL Database, Managed Instance, and Synapse SQL
 services: synapse-analytics
 author: vvasic-msft
 ms.service: synapse-analytics
@@ -9,7 +9,7 @@ ms.date: 1/23/2020
 ms.author: vvasic
 ms.reviewer: jrasnick
 ---
-# Use Azure Active Directory Authentication for authentication with SQL Analytics
+# Use Azure Active Directory Authentication for authentication with Synapse SQL
 
 Azure Active Directory authentication is a mechanism of connecting to [Azure Synapse Analytics](../overview-faq.md) by using identities in Azure Active Directory (Azure AD).
 
@@ -22,7 +22,7 @@ With Azure AD authentication, you can centrally manage the identities of users h
 - It can eliminate storing passwords by enabling integrated Windows authentication and other forms of authentication supported by Azure Active Directory.
 - Azure AD supports token-based authentication for applications connecting to Azure Synapse.
 - Azure AD authentication supports ADFS (domain federation) or native user/password authentication for a local Azure Active Directory without domain synchronization.
-- Azure AD supports connections from SQL Server Management Studio that use Active Directory Universal Authentication, which includes Multi-Factor Authentication (MFA).  MFA includes strong authentication with a range of easy verification options — phone call, text message, smart cards with pin, or mobile app notification. For more information, see [SSMS support for Azure AD MFA with SQL Analytics](mfa-authentication.md).
+- Azure AD supports connections from SQL Server Management Studio that use Active Directory Universal Authentication, which includes Multi-Factor Authentication (MFA).  MFA includes strong authentication with a range of easy verification options — phone call, text message, smart cards with pin, or mobile app notification. For more information, see [SSMS support for Azure AD MFA with Synapse SQL](mfa-authentication.md).
 - Azure AD supports similar connections from SQL Server Data Tools (SSDT) that use Active Directory Interactive Authentication. For more information, see
 [Azure Active Directory support in SQL Server Data Tools (SSDT)](/sql/ssdt/azure-active-directory?toc=/azure/synapse-analytics/toc.json&bc=/azure/synapse-analytics/breadcrumb/toc.json&view=azure-sqldw-latest).
 
@@ -41,7 +41,7 @@ Defining access rights on the files and data that is respected in different data
 
 ## Trust architecture
 
-The following high-level diagram summarizes the solution architecture of using Azure AD authentication with SQL Analytics. To support Azure AD native user password, only the Cloud portion and Azure AD/Synapse SQL Analytics is considered. To support Federated authentication (or user/password for Windows credentials), the communication with ADFS block is required. The arrows indicate communication pathways.
+The following high-level diagram summarizes the solution architecture of using Azure AD authentication with Synapse SQL. To support Azure AD native user password, only the Cloud portion and Azure AD/Synapse Synapse SQL is considered. To support Federated authentication (or user/password for Windows credentials), the communication with ADFS block is required. The arrows indicate communication pathways.
 
 ![aad auth diagram][1]
 
@@ -51,26 +51,28 @@ The following diagram indicates the federation, trust, and hosting relationships
 
 ## Administrator structure
 
-When using Azure AD authentication, there are two Administrator accounts for the SQL Analytics; the original SQL Server administrator and the Azure AD administrator. Only the administrator based on an Azure AD account can create the first Azure AD contained database user in a user database. The Azure AD administrator login can be an Azure AD user or an Azure AD group. When the administrator is a group account, it can be used by any group member, enabling multiple Azure AD administrators for the SQL Analytics instance. Using group account as an administrator enhances manageability by allowing you to centrally add and remove group members in Azure AD without changing the users or permissions in Synapse Analytics workspace. Only one Azure AD administrator (a user or group) can be configured at any time.
+When using Azure AD authentication, there are two Administrator accounts for the Synapse SQL; the original SQL Server administrator and the Azure AD administrator. Only the administrator based on an Azure AD account can create the first Azure AD contained database user in a user database. The Azure AD administrator login can be an Azure AD user or an Azure AD group. 
+
+When the administrator is a group account, it can be used by any group member, enabling multiple Azure AD administrators for the Synapse SQL instance. Using group account as an administrator enhances manageability by allowing you to centrally add and remove group members in Azure AD without changing the users or permissions in Synapse Analytics workspace. Only one Azure AD administrator (a user or group) can be configured at any time.
 
 ![admin structure][3]
 
 ## Permissions
 
 To create new users, you must have the `ALTER ANY USER` permission in the database. The `ALTER ANY USER` permission can be granted to any database user. The `ALTER ANY USER` permission is also held by the server administrator accounts, and database users with the `CONTROL ON DATABASE` or `ALTER ON DATABASE` permission for that database, and by members of the `db_owner` database role.
 
-To create a contained database user in SQL Analytics, you must connect to the database or instance using an Azure AD identity. To create the first contained database user, you must connect to the database by using an Azure AD administrator (who is the owner of the database). Any Azure AD authentication is only possible if the Azure AD admin was created for SQL Analytics. If the Azure Active Directory admin was removed from the server, existing Azure Active Directory users created previously inside SQL Analytics can no longer connect to the database using their Azure Active Directory credentials.
+To create a contained database user in Synapse SQL, you must connect to the database or instance using an Azure AD identity. To create the first contained database user, you must connect to the database by using an Azure AD administrator (who is the owner of the database). Any Azure AD authentication is only possible if the Azure AD admin was created for Synapse SQL. If the Azure Active Directory admin was removed from the server, existing Azure Active Directory users created previously inside Synapse SQL can no longer connect to the database using their Azure Active Directory credentials.
 
 ## Azure AD features and limitations
 
-- The following members of Azure AD can be provisioned in SQL Analytics:
+- The following members of Azure AD can be provisioned in Synapse SQL:
 
   - Native members: A member created in Azure AD in the managed domain or in a customer domain. For more information, see [Add your own domain name to Azure AD](../../active-directory/fundamentals/add-custom-domain.md?toc=/azure/synapse-analytics/toc.json&bc=/azure/synapse-analytics/breadcrumb/toc.json).
   - Federated domain members: A member created in Azure AD with a federated domain. For more information, see [Microsoft Azure now supports federation with Windows Server Active Directory](https://azure.microsoft.com/blog/20../../windows-azure-now-supports-federation-with-windows-server-active-directory/).
   - Imported members from other Azure AD's who are native or federated domain members.
   - Active Directory groups created as security groups.
 
-- Azure AD users that are part of a group that has `db_owner` server role cannot use the **[CREATE DATABASE SCOPED CREDENTIAL](/sql/t-sql/statements/create-database-scoped-credential-transact-sql?toc=/azure/synapse-analytics/toc.json&bc=/azure/synapse-analytics/breadcrumb/toc.json&view=azure-sqldw-latest)** syntax against SQL Analytics. You will see the following error:
+- Azure AD users that are part of a group that has `db_owner` server role cannot use the **[CREATE DATABASE SCOPED CREDENTIAL](/sql/t-sql/statements/create-database-scoped-credential-transact-sql?toc=/azure/synapse-analytics/toc.json&bc=/azure/synapse-analytics/breadcrumb/toc.json&view=azure-sqldw-latest)** syntax against Synapse SQL. You will see the following error:
 
     `SQL Error [2760] [S0001]: The specified schema name '[email protected]' either does not exist or you do not have permission to use it.`
 
@@ -102,9 +104,9 @@ The following authentication methods are supported for Azure AD server principal
 ### Additional considerations
 
 - To enhance manageability, we recommend you provision a dedicated Azure AD group as an administrator.
-- Only one Azure AD administrator (a user or group) can be configured for SQL Analytics pool at any time.
+- Only one Azure AD administrator (a user or group) can be configured for Synapse SQL pool at any time.
   - The addition of Azure AD server principals (logins) for SQL on-demand (preview) allows the possibility of creating multiple Azure AD server principals (logins) that can be added to the `sysadmin` role.
-- Only an Azure AD administrator for SQL Analytics can initially connect to the SQL Analytics using an Azure Active Directory account. The Active Directory administrator can configure subsequent Azure AD database users.
+- Only an Azure AD administrator for Synapse SQL can initially connect to the Synapse SQL using an Azure Active Directory account. The Active Directory administrator can configure subsequent Azure AD database users.
 - We recommend setting the connection timeout to 30 seconds.
 - SQL Server 2016 Management Studio and SQL Server Data Tools for Visual Studio 2015 (version 14.0.60311.1April 2016 or later) support Azure Active Directory authentication. (Azure AD authentication is supported by the **.NET Framework Data Provider for SqlServer**; at least version .NET Framework 4.6). Therefore the newest versions of these tools and data-tier applications (DAC and .BACPAC) can use Azure AD authentication.
 - Beginning with version 15.0.1, [sqlcmd utility](/sql/tools/sqlcmd-utility?toc=/azure/synapse-analytics/toc.json&bc=/azure/synapse-analytics/breadcrumb/toc.json&view=azure-sqldw-latest) and [bcp utility](/sql/tools/bcp-utility?toc=/azure/synapse-analytics/toc.json&bc=/azure/synapse-analytics/breadcrumb/toc.json&view=azure-sqldw-latest) support Active Directory Interactive authentication with MFA.
@@ -113,7 +115,7 @@ The following authentication methods are supported for Azure AD server principal
 
 ## Next steps
 
-For an overview of access and control in SQL Analytics, see [SQL Analytics access control](../sql/access-control.md). To learn more about database principals, see [Principals](https://msdn.microsoft.com/library/ms181127.aspx). Additional information about database roles, can be found in the [Database roles](https://msdn.microsoft.com/library/ms189121.aspx) article.
+For an overview of access and control in Synapse SQL, see [Synapse SQL access control](../sql/access-control.md). To learn more about database principals, see [Principals](https://msdn.microsoft.com/library/ms181127.aspx). Additional information about database roles, can be found in the [Database roles](https://msdn.microsoft.com/library/ms189121.aspx) article.
 
 
 <!--Image references-->

articles/synapse-analytics/sql/get-started-power-bi-professional.md

@@ -12,7 +12,7 @@ ms.reviewer: jrasnick, carlrab
 ---
 
 
-# Connect to SQL Analytics with Power BI Professional
+# Connect to Synapse SQL with Power BI Professional
 
 > [!div class="op_single_selector"]
 >

articles/synapse-analytics/sql/mfa-authentication.md

@@ -1,6 +1,6 @@
 ---
 title: Using Multi-factor AAD authentication
-description: SQL Analytics support connections from SQL Server Management Studio (SSMS) using Active Directory Universal Authentication. 
+description: Synapse SQL support connections from SQL Server Management Studio (SSMS) using Active Directory Universal Authentication. 
 services: synapse-analytics
 author: vvasic-msft
 ms.service: synapse-analytics
@@ -10,9 +10,9 @@ ms.author: vvasic
 ms.reviewer: jrasnick
 ---
 
-# Using Multi-factor AAD authentication with SQL Analytics (SSMS support for MFA)
+# Using Multi-factor AAD authentication with Synapse SQL (SSMS support for MFA)
 
-SQL Analytics support connections from SQL Server Management Studio (SSMS) using *Active Directory Universal Authentication*. 
+Synapse SQL support connections from SQL Server Management Studio (SSMS) using *Active Directory Universal Authentication*. 
 
 This article discusses the differences between the various authentication options, and also the limitations associated with using Universal Authentication. 
 
@@ -66,7 +66,7 @@ If you are running SSMS 18.x or later then the AD domain name or tenant ID is no
    ![mfa-tenant-ssms](./media/mfa-authentication/mfa-no-tenant-ssms.png)
 
 ### Azure AD business to business support   
-Azure AD users supported for Azure AD B2B scenarios as guest users (see [What is Azure B2B collaboration](../../active-directory/b2b/what-is-b2b.md?toc=/azure/synapse-analytics/toc.json&bc=/azure/synapse-analytics/breadcrumb/toc.json) can connect to SQL Analytics only as part of members of a group created in current Azure AD and mapped manually using the Transact-SQL `CREATE USER` statement in a given database. 
+Azure AD users supported for Azure AD B2B scenarios as guest users (see [What is Azure B2B collaboration](../../active-directory/b2b/what-is-b2b.md?toc=/azure/synapse-analytics/toc.json&bc=/azure/synapse-analytics/breadcrumb/toc.json) can connect to Synapse SQL only as part of members of a group created in current Azure AD and mapped manually using the Transact-SQL `CREATE USER` statement in a given database. 
 
 For example, if `[email protected]` is invited to Azure AD `contosotest` (with the Azure Ad domain `contosotest.onmicrosoft.com`), an Azure AD group, such as `usergroup` must be created in the Azure AD that contains the `[email protected]` member. Then, this group must be created for a specific  database (that is, MyDatabase) by Azure AD SQL admin or Azure AD DBO  by executing a Transact-SQL `CREATE USER [usergroup] FROM EXTERNAL PROVIDER` statement. 
 
@@ -76,7 +76,7 @@ The usergroup, by default, has only the connect permission and any further data
 
 Note that user `[email protected]` as a guest user must check the box and add the AD domain name `contosotest.onmicrosoft.com` in the SSMS **Connection Property** dialog box. The **AD domain name or tenant ID** option is only supported for the Universal with MFA connection options, otherwise it is greyed out.
 
-## Universal Authentication limitations for SQL Analytics
+## Universal Authentication limitations for Synapse SQL
 
 - SSMS and SqlPackage.exe are the only tools currently enabled for MFA through Active Directory Universal Authentication.
 - SSMS version 17.2, supports multi-user concurrent access using Universal Authentication with MFA. Version 17.0 and 17.1, restricted a login for an instance of SSMS using Universal Authentication to a single Azure Active Directory account. To log in as another Azure AD account, you must use another instance of SSMS. (This restriction is limited to Active Directory Universal Authentication; you can log in to different servers using Active Directory Password Authentication, Active Directory Integrated Authentication, or SQL Server Authentication).
@@ -87,5 +87,5 @@ Note that user `[email protected]` as a guest user must check the box and add the
 - The Active Directory Authentication Library (ADAL) version for Universal authentication was updated to its latest ADAL.dll 3.13.9 available released version. See [Active Directory Authentication Library 3.14.1](https://www.nuget.org/packages/Microsoft.IdentityModel.Clients.ActiveDirectory/).  
 
 ## Next steps
-For more information, see the [Connect to SQL Analytics with SQL Server Management Studio](get-started-ssms.md) article. 
+For more information, see the [Connect to Synapse SQL with SQL Server Management Studio](get-started-ssms.md) article. 
 

articles/synapse-analytics/sql/on-demand-workspace-overview.md

@@ -1,6 +1,6 @@
 ---
 title: SQL on-demand (preview)
-description: Learn about SQL Analytics on-demand in Azure Synapse Analytics.
+description: Learn about Synapse SQL on-demand in Azure Synapse Analytics.
 services: sql-datawarehouse
 author: vvasic-msft
 ms.service: synapse-analytics
@@ -27,7 +27,7 @@ If you need to explore data in the data lake, gain insights from it or optimize
 
 - Basic discovery and exploration - Quickly reason about the data in various formats (Parquet, CSV, JSON) in your data lake, so you can plan how to extract insights from it.
 - Logical data warehouse – Provide a relational abstraction on top of raw or disparate data without relocating and transforming data, allowing always up-to-date view of your data.
-- Data transformation - Simple, scalable, and performant way to transform data in the lake using T-SQL, so it can fed to BI and other tools, or loaded into a relational data store (SQL Analytics databases, Azure SQL Database, etc.).
+- Data transformation - Simple, scalable, and performant way to transform data in the lake using T-SQL, so it can fed to BI and other tools, or loaded into a relational data store (Synapse SQL databases, Azure SQL Database, etc.).
 
 Different professional roles can benefit from SQL on-demand:
 
@@ -42,7 +42,7 @@ SQL on-demand endpoint is provided within every Azure Synapse workspace. You can
 
 ## Client tools
 
-SQL on-demand enables existing SQL ad-hoc querying and business intelligence tools to tap into the data lake. As it provides familiar T-SQL syntax, any tool capable to establish TDS connection SQL offerings can [connect to and query SQL Analytics](connect-overview.md) on-demand. You can connect with Azure Data Studio and run ad-hoc queries or connect with Power BI to gain insights in a matter of minutes.
+SQL on-demand enables existing SQL ad-hoc querying and business intelligence tools to tap into the data lake. As it provides familiar T-SQL syntax, any tool capable to establish TDS connection SQL offerings can [connect to and query Synapse SQL](connect-overview.md) on-demand. You can connect with Azure Data Studio and run ad-hoc queries or connect with Power BI to gain insights in a matter of minutes.
 
 At this moment, latest version of Azure Data Studio is fully supported. Latest version of SSMS can be used to connect and query but is not supported yet. It will be fully supported until GA. Please make sure you use latest versions of tools.