Closed golfalot closed 1 year ago
@golfalot Thank you for sharing feedback. We are actively validating it. We will share updates soon.
@filippopovic Could you please validate customer feedback and update or enhance documentation as appropriate? Thank you.
@ShaikMaheer-MSFT , adding @azaricstefan for help
I am also facing the same issue. any timeline for fix?
@azaricstefan could you please take a look?
I created a PR for this, it will be merged soon.
synapse error message bug
There is horrible very time wasting bug that occurs when using Built-in SQL, writing to ADLS gen2 with synapse Data Exfiltration Protection enabled, and Managed Service Identity If you follow the current documentation and use
https://<mystoageaccount>.blob.core.windows.net/<mycontainer>/<mybaseoutputfolderpath>
Instead ofhttps://<mystoageaccount>.dfs.core.windows.net/<mycontainer>/<mybaseoutputfolderpath>
You get errorOperation failed since the external data source 'https://<mystorageaccount>.blob.core.windows.net/<mycontainer>/<mybaseoutputfolderpath>/<myoutputsubfolder>/' has underlying storage account that is not in the list of Outbound Firewall Rules on the server. Please add this storage account to the list of Outbound Firewall Rules on your server and retry the operation.
a better end to end example
The documentation needs a better end to end example, using ADSL gen2 and Managed Service Identity which should be the the majority use case.
I wish to propose the following replacement example
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.