Merge pull request #18030 from kevinvngo/patch-59

PRMerger9 · web-flow · commit 4e2a22918511 · 2020-12-07T15:13:45.000-08:00
MSI is not supported for Synapse workspaces - COPY
diff --git a/docs/t-sql/statements/copy-into-transact-sql.md b/docs/t-sql/statements/copy-into-transact-sql.md
@@ -427,18 +427,7 @@ There is no need to split Parquet and ORC files because the COPY command will au
 ### Are there any limitations on the number or size of files?
 There are no limitations on the number or size of files; however, for best performance, we recommend files that are at least 4MB.
 
-### Are there any limitations with COPY using Synapse workspaces?
-
-Authenticating using Managed Identity (MSI) is not supported with the COPY statement or PolyBase (including when used in pipelines). You may run into a similiar error message:
-
-*com.microsoft.sqlserver.jdbc.SQLServerException: Managed Service Identity has not been enabled on this server. Please enable Managed Service Identity and try again.*
-
-MSI authentication is required when the storage account is associated with a VNet. You must use BCP/Bulk insert to load data instead of COPY or PolyBase if your storage account is attached to a VNet.
-
-This limitation is only applicable to SQL pools belonging to a Synapse workspace. We will enable MSI support in Synapse workspaces in an upcoming release. 
-
-Please send any feedback or issues to the following distribution list: sqldwcopypreview@service.microsoft.com
 
 ## See also  
 
- [Loading overview with [!INCLUDE[ssSDW](../../includes/sssdwfull-md.md)]](/azure/sql-data-warehouse/design-elt-data-loading)
+ [Loading overview with [!INCLUDE[ssSDW](../../includes/sssdwfull-md.md)]](/azure/sql-data-warehouse/design-elt-data-loading)
