We’ll look at this for future release.
Now OData connector support AAD-based OAuth, you can try it out via copy wizard. And more details on OData connector can be found at https://azure.microsoft.com/en-us/documentation/articles/data-factory-odata-connector/. Keep this feedback live – if you need OAuth for Web, please leave comment.
Not a good workaround and silly it's not supported by ADF but we've been working around it using an Azure Function...
3.5 years (since April 8th, 2016) and counting for a request to support the most widely used API authentication method for OData and more importantly REST.
We need OAuth for Web and more importantly REST!
Thanks for the feedback! We are interested in collecting feedback on this request – please vote for it if this is something you like to see.
We’re also interested in learning more what people want to use the SFTP/FTPS for and which protocol they prefer. Please feel free to leave us a comment letting us know more detail!
Program Manager, Azure Files
Totally agree, @657567118-greg-lloyd! "Will people please stop posting about 3rd party SFTP solutions leveraging Azure Storage. This is a request that the feature be added by Microsoft. We don't another vendor, we want native support."
I gave it a shot via twitter: https://twitter.com/JeroenHabets/status/1159413205258702848
@169969542-microsoft-azure-storage-team Will Gries, please prioritize this.
Joshua Drake of Postgresql fame, by any chance? At any rate, looks like we shouldn't be holding our breathe...
Has this been planned already? If so, for when?
Almost 10th anniversary! For a wish with 8 pages of supportive comments and over 3400 votes...
NOTE: Apparently the Microsoft Storage team lives in its own world and considers the industry standard SFTP a legacy protocol so don't hold your breath :(.
How can I put politely what an absurd, almost obscene, position that is. Particularly in view of the 3000 votes here that should have given them an idea, or else just a quick look at the SFTP page on Wikipedia.
Hi Will Gries,
Could you please give us an update?
Thanks in advance,
Thank you for your feedback. We will evaluate this ask as part of the product roadmap.
And unfortunately ADF REST does not support "Bearer" tokens or OAuth :(
Please close as the category "Azure Key Vault" is there now: https://feedback.azure.com/forums/906355-azure-key-vault
Indeed, please close as there is a web UI
21st century: SFTP
20th century: FTP and FTPS
Apparently the REST of Microsoft (pun intended) does understand REST API authentication: e.g. all Azure APIs: https://docs.microsoft.com/en-us/rest/api/azure/
Thanks everybody for providing the list. I’ve passed the info to the Visual Studio Team.
In the meanwhile, I have 2 more requests:
1) If you happen to have Visual Studio 2017 (version 15.9.11 or greater), could you check and see if it shows the same behavior?
2) If you happen to have SSMS 17.9.1 on the same machine, could you check and see if it shows the same behavior?
I’m hearing from folks here that “changing SSMS such that it disables h/w acceleration by default” is not a recommended thing to do… However, quite honestly, at this point, it may be the only option I can think about.. :-(
Hmmm... 4 months and two point releases later this critical usability issue is still not fixed??? (Was using 17.9 before)
Besides catalog server connection also support Key Vault for the custom setup script:
customSetupScriptProperties: blobContainerUri + sasToken
(not only catalogServerEndpoint", "catalogAdminUserName", and "catalogAdminPassword)
Data tool that does not support XML... Is this 1995? (And I appreciate that JSON support is there, but XML is not going away soon in the big wide world)
The main driver is to allow easy user-friendly discoverable access to items catalogued in the Data Catalog for end users.
Your work around requires intensive M programming and therefore more complex than manually navigating the Data Catalog and then in Get Data manually navigating to discovered items.
NOTE: That lack of this feature including manually having to check relations is the main impediment raised by our business users (as they are used to it in tools like Business Objects)
At first glance I thought this idea covers my urgent need for Power BI to show data catalog data. But rather than reporting on this data I need to be able to use Azure Data Catalog data to connect to (objects in) sources.
As this idea does not cover that, I logged a separate idea:
I urgently need Power BI integration as well but rather to use Azure Data Catalog to connect to (objects in) sources.
As this idea does not cover that, on the risk that I need to wait 4+ years, I logged a separate idea: