[msid] ms.custom: has-adal-ref 02 (tracking)

Author: mmacy

articles/data-factory/connector-troubleshoot-guide.md

@@ -1,21 +1,22 @@
 ---
 title: Troubleshoot Azure Data Factory Connectors
-description: Learn how to troubleshoot connector issues in Azure Data Factory. 
+description: Learn how to troubleshoot connector issues in Azure Data Factory.
 services: data-factory
 author: linda33wj
 ms.service: data-factory
 ms.topic: troubleshooting
 ms.date: 01/09/2020
 ms.author: jingwang
 ms.reviewer: craigg
+ms.custom: has-adal-ref
 ---
 
 # Troubleshoot Azure Data Factory Connectors
 
 [!INCLUDE[appliesto-adf-asa-md](includes/appliesto-adf-asa-md.md)]
 
 This article explores common troubleshooting methods for connectors in Azure Data Factory.
-  
+
 
 ## Azure Blob Storage
 
@@ -58,8 +59,8 @@ This article explores common troubleshooting methods for connectors in Azure Dat
 - **Symptoms**: When copying data into Cosmos DB, you hit the following error:
 
     ```
-    Message=Partition range id 0 | Failed to import mini-batch. 
-    Exception was Message: {"Errors":["Encountered exception while executing function. Exception = Error: {\"Errors\":[\"Unique index constraint violation.\"]}... 
+    Message=Partition range id 0 | Failed to import mini-batch.
+    Exception was Message: {"Errors":["Encountered exception while executing function. Exception = Error: {\"Errors\":[\"Unique index constraint violation.\"]}...
     ```
 
 - **Cause**: There are two possible causes:
@@ -68,7 +69,7 @@ This article explores common troubleshooting methods for connectors in Azure Dat
 
     - If you use **Upsert** as write behavior and you set another unique key to the container, this error means you source data have rows/objects with different IDs but same value for the defined unique key.
 
-- **Resolution**: 
+- **Resolution**:
 
     - For cause1, set **Upsert** as write behavior.
     - For cause 2, make sure each document has different value for defined unique key.
@@ -87,13 +88,13 @@ Cosmos DB calculates RU from [here](../cosmos-db/request-units.md#request-unit-c
 
 - **Resolution**: Here are two solutions:
 
-    1. **Increase the container RU** to bigger value in Cosmos DB, which will improve the copy activity performance, though incur more cost in Cosmos DB. 
+    1. **Increase the container RU** to bigger value in Cosmos DB, which will improve the copy activity performance, though incur more cost in Cosmos DB.
 
     2. Decrease **writeBatchSize** to smaller value (such as 1000) and set **parallelCopies** to smaller value such as 1, which will make copy run performance worse than current but will not incur more cost in Cosmos DB.
 
 ### Column missing in column mapping
 
-- **Symptoms**: When you import schema for Cosmos DB for column mapping, some columns are missing. 
+- **Symptoms**: When you import schema for Cosmos DB for column mapping, some columns are missing.
 
 - **Cause**: ADF infers the schema from the first 10 Cosmos DB documents. If some columns/properties don't have value in those documents, they won't be detected by ADF thus won't show up.
 
@@ -116,7 +117,7 @@ Cosmos DB calculates RU from [here](../cosmos-db/request-units.md#request-unit-c
 - **Cause**: There are two ways to represent UUID in BSON - UuidStardard and UuidLegacy. By default, UuidLegacy is used to read data. You will hit error if your UUID data in MongoDB is UuidStandard.
 
 - **Resolution**: In MongoDB connection string, add option "**uuidRepresentation=standard**". For more information, see [MongoDB connection string](connector-mongodb.md#linked-service-properties).
-			
+
 
 ## Azure Data Lake Storage Gen2
 
@@ -161,10 +162,10 @@ Cosmos DB calculates RU from [here](../cosmos-db/request-units.md#request-unit-c
 
 ### Error message: The remote server returned an error: (403) Forbidden
 
-- **Symptoms**: Copy activity fail with the following error: 
+- **Symptoms**: Copy activity fail with the following error:
 
     ```
-    Message: The remote server returned an error: (403) Forbidden.. 
+    Message: The remote server returned an error: (403) Forbidden..
     Response details: {"RemoteException":{"exception":"AccessControlException""message":"CREATE failed with error 0x83090aa2 (Forbidden. ACL verification failed. Either the resource does not exist or the user is not authorized to perform the requested operation.)....
     ```
 
@@ -177,15 +178,15 @@ Cosmos DB calculates RU from [here](../cosmos-db/request-units.md#request-unit-c
 - **Symptoms**: Copy activity fail with the following error:
 
     ```
-    Failed to get access token by using service principal. 
+    Failed to get access token by using service principal.
     ADAL Error: service_unavailable, The remote server returned an error: (503) Server Unavailable.
     ```
 
 - **Cause**: When the Service Token Server (STS) owned by Azure Active Directory is not unavailable, i.e., too
-busy to handle requests, it returns an HTTP error 503. 
+busy to handle requests, it returns an HTTP error 503.
 
 - **Resolution**: Rerun the copy activity after several minutes.
-			      
+
 
 ## Azure SQL Data Warehouse/Azure SQL Database/SQL Server
 
@@ -360,7 +361,7 @@ busy to handle requests, it returns an HTTP error 503.
     ErrorCode=FailedDbOperation,Type=Microsoft.DataTransfer.Common.Shared.HybridDeliveryException,
     Message=Error happened when loading data into SQL Data Warehouse.,
     Source=Microsoft.DataTransfer.ClientLibrary,Type=System.Data.SqlClient.SqlException,
-    Message=Query aborted-- the maximum reject threshold (0 rows) was reached while reading from an external source: 1 rows rejected out of total 415 rows processed. (/file_name.txt) 
+    Message=Query aborted-- the maximum reject threshold (0 rows) was reached while reading from an external source: 1 rows rejected out of total 415 rows processed. (/file_name.txt)
     Column ordinal: 18, Expected data type: DECIMAL(x,x), Offending value:..
     ```
 
@@ -373,9 +374,9 @@ busy to handle requests, it returns an HTTP error 503.
 - **Symptoms**: You copy data into Azure SQL Data Warehouse using PolyBase, and hit the following error:
 
     ```
-    Message=110802;An internal DMS error occurred that caused this operation to fail. 
-    Details: Exception: Microsoft.SqlServer.DataWarehouse.DataMovement.Common.ExternalAccess.HdfsAccessException, 
-    Message: Java exception raised on call to HdfsBridge_CreateRecordReader. 
+    Message=110802;An internal DMS error occurred that caused this operation to fail.
+    Details: Exception: Microsoft.SqlServer.DataWarehouse.DataMovement.Common.ExternalAccess.HdfsAccessException,
+    Message: Java exception raised on call to HdfsBridge_CreateRecordReader.
     Java exception message:HdfsBridge::CreateRecordReader - Unexpected error encountered creating the record reader.: Error [HdfsBridge::CreateRecordReader - Unexpected error encountered creating the record reader.] occurred while accessing external file.....
     ```
 
@@ -412,7 +413,7 @@ busy to handle requests, it returns an HTTP error 503.
 - **Cause**: Azure SQL Data Warehouse hit issue querying the external table in Azure Storage.
 
 - **Resolution**: Run the same query in SSMS and check if you see the same result. If yes, open a support ticket to Azure SQL Data Warehouse and provide your SQL DW server and database name to further troubleshoot.
-            
+
 
 ## Delimited Text Format
 
@@ -677,4 +678,3 @@ For more troubleshooting help, try these resources:
 *  [MSDN forum](https://social.msdn.microsoft.com/Forums/home?sort=relevancedesc&brandIgnore=True&searchTerm=data+factory)
 *  [Stack Overflow forum for Data Factory](https://stackoverflow.com/questions/tagged/azure-data-factory)
 *  [Twitter information about Data Factory](https://twitter.com/hashtag/DataFactory)
-            

articles/remote-rendering/how-tos/authentication.md

@@ -5,6 +5,7 @@ author: florianborn71
 ms.author: flborn
 ms.date: 02/12/2019
 ms.topic: how-to
+ms.custom: has-adal-ref
 ---
 
 # Configure authentication

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

@@ -1,10 +1,10 @@
 ---
-title: ActiveDirectoryInteractive connects to SQL 
+title: ActiveDirectoryInteractive connects to SQL
 description: "C# Code example, with explanations, for connecting to Azure SQL Database by using SqlAuthenticationMethod.ActiveDirectoryInteractive mode."
 services: sql-database
 ms.service: sql-database
 ms.subservice: security
-ms.custom: active directory
+ms.custom: active directory, has-adal-ref
 ms.devlang:
 ms.topic: conceptual
 author: GithubMirek
@@ -75,7 +75,7 @@ To register and set necessary permissions for your application:
 
 ### Set an Azure AD admin for your SQL Database server
 
-For your C# program to run, an Azure SQL server admin needs to assign an Azure AD admin for your SQL Database server. 
+For your C# program to run, an Azure SQL server admin needs to assign an Azure AD admin for your SQL Database server.
 
 On the **SQL Server** page, select **Active Directory admin** > **Set admin**.
 
@@ -238,9 +238,9 @@ namespace ADInteractive5
     /// <summary>
     /// SqlAuthenticationProvider - Is a public class that defines 3 different Azure AD
     /// authentication methods.  The methods are supported in the new .NET 4.7.2.
-    ///  . 
+    ///  .
     /// 1. Interactive,  2. Integrated,  3. Password
-    ///  . 
+    ///  .
     /// All 3 authentication methods are based on the Azure
     /// Active Directory Authentication Library (ADAL) managed library.
     /// </summary>

articles/sql-database/sql-database-aad-authentication-configure.md

@@ -4,8 +4,8 @@ description: Learn how to connect to SQL Database, managed instance, and Azure S
 services: sql-database
 ms.service: sql-database
 ms.subservice: security
-ms.custom: azure-synapse
-ms.devlang: 
+ms.custom: azure-synapse, has-adal-ref
+ms.devlang:
 ms.topic: conceptual
 author: GithubMirek
 ms.author: mireks
@@ -19,7 +19,7 @@ This article shows you how to create and populate Azure AD, and then use Azure A
 > [!NOTE]
 > This article applies to Azure SQL server, and to both SQL Database and Azure Synapse. For simplicity, SQL Database is used when referring to both SQL Database and Azure Synapse.
 
-> [!IMPORTANT]  
+> [!IMPORTANT]
 > Connecting to SQL Server running on an Azure VM is not supported using an Azure Active Directory account. Use a domain Active Directory account instead.
 
 ## Azure AD authentication methods
@@ -184,7 +184,7 @@ As a best practice for existing Azure AD admins for MI created before GA, and st
 - If an Azure AD login exists in the master database for MI, created using the T-SQL command `CREATE LOGIN [myaadaccount] FROM EXTERNAL PROVIDER`,
 it can't be set up as an Azure AD admin for MI. You'll experience an error setting the login as an Azure AD admin using the Azure portal, PowerShell, or CLI commands to create the Azure AD login.
   - The login must be dropped in the master database using the command `DROP LOGIN [myaadaccount]`, before the account can be created as an Azure AD admin.
-  - Set up the Azure AD admin account in the Azure portal after the `DROP LOGIN` succeeds. 
+  - Set up the Azure AD admin account in the Azure portal after the `DROP LOGIN` succeeds.
   - If you can't set up the Azure AD admin account, check in the master database of the managed instance for the login. Use the following command: `SELECT * FROM sys.server_principals`
   - Setting up an Azure AD admin for MI will automatically create a login in the master database for this account. Removing the Azure AD admin will automatically drop the login from the master database.
 
@@ -271,11 +271,11 @@ The following two procedures show you how to provision an Azure Active Directory
 
 4. In the **Active Directory admin** page, select **Set admin**.
 
-    ![SQL servers set Active Directory admin](./media/sql-database-aad-authentication/sql-servers-set-active-directory-admin.png)  
+    ![SQL servers set Active Directory admin](./media/sql-database-aad-authentication/sql-servers-set-active-directory-admin.png)
 
 5. In the **Add admin** page, search for a user, select the user or group to be an administrator, and then select **Select**. (The Active Directory admin page shows all members and groups of your Active Directory. Users or groups that are grayed out cannot be selected because they are not supported as Azure AD administrators. (See the list of supported admins in the **Azure AD Features and Limitations** section of [Use Azure Active Directory Authentication for authentication with SQL Database or Azure Synapse](sql-database-aad-authentication.md).) Role-based access control (RBAC) applies only to the portal and is not propagated to SQL Server.
 
-    ![Select Azure Active Directory admin](./media/sql-database-aad-authentication/select-azure-active-directory-admin.png)  
+    ![Select Azure Active Directory admin](./media/sql-database-aad-authentication/select-azure-active-directory-admin.png)
 
 6. At the top of the **Active Directory admin** page, select **SAVE**.
 
@@ -437,7 +437,7 @@ A federated domain user account that is imported into a managed domain as an ext
 > [!NOTE]
 > Azure AD users are marked in the database metadata with type E (EXTERNAL_USER) and for groups with type X (EXTERNAL_GROUPS). For more information, see [sys.database_principals](https://msdn.microsoft.com/library/ms187328.aspx).
 
-## Connect to the user database or Azure Synapse by using SSMS or SSDT  
+## Connect to the user database or Azure Synapse by using SSMS or SSDT
 
 To confirm the Azure AD administrator is properly set up, connect to the **master** database using the Azure AD administrator account.
 To provision an Azure AD-based contained database user (other than the server administrator that owns the database), connect to the database with an Azure AD identity that has access to the database.
@@ -447,7 +447,7 @@ To provision an Azure AD-based contained database user (other than the server ad
 
 ## Using an Azure AD identity to connect using SSMS or SSDT
 
-The following procedures show you how to connect to a SQL database with an Azure AD identity using SQL Server Management Studio or SQL Server Database Tools. 
+The following procedures show you how to connect to a SQL database with an Azure AD identity using SQL Server Management Studio or SQL Server Database Tools.
 
 ### Active Directory integrated authentication
 
@@ -457,7 +457,7 @@ Use this method if you are logged into Windows using your Azure Active Directory
 
     ![Select AD Integrated Authentication][11]
 
-2. Select the **Options** button, and on the **Connection Properties** page, in the **Connect to database** box, type the name of the user database you want to connect to. For more information, see the article [Multi-factor AAD auth](sql-database-ssms-mfa-authentication.md#azure-ad-domain-name-or-tenant-id-parameter) on the differences between the Connection Properties for SSMS 17.x and 18.x. 
+2. Select the **Options** button, and on the **Connection Properties** page, in the **Connect to database** box, type the name of the user database you want to connect to. For more information, see the article [Multi-factor AAD auth](sql-database-ssms-mfa-authentication.md#azure-ad-domain-name-or-tenant-id-parameter) on the differences between the Connection Properties for SSMS 17.x and 18.x.
 
     ![Select the database name][13]
 
@@ -547,7 +547,7 @@ The following statements, connect using version 13.1 of sqlcmd, which is availab
 > `sqlcmd` with the `-G` command does not work with system identities, and requires a user principal login.
 
 ```cmd
-sqlcmd -S Target_DB_or_DW.testsrv.database.windows.net -G  
+sqlcmd -S Target_DB_or_DW.testsrv.database.windows.net -G
 sqlcmd -S Target_DB_or_DW.testsrv.database.windows.net -U [email protected] -P MyAADPassword -G -l 30
 ```