Nick McDermaid
My feedback
-
3 votesNick McDermaid
supported this idea
·
-
879 votesNick McDermaid
supported this idea
·
An error occurred while saving the comment -
2,526 votes
-
543 votesNick McDermaid
supported this idea
·
-
47 votes
Will follow-up with the team on this. Stay tuned!
An error occurred while saving the comment Nick McDermaid
commented
Can't believe this has only 7 votes. Are people really still happy to have to go back to SQL authentication?
Nick McDermaid
supported this idea
·
-
17 votes
We do support service principals. The next SSMS will make them a lot easier to set in roles and we also have some client lib changes that will make them easier to use. Now you can use them by getting the token yourself and passing it in as the password on the connection string.
An error occurred while saving the comment Nick McDermaid
commented
If I understand correctly this is about triggering a process. It's possible right now to use the REST API to kick off a model process via MSI authentication. The REST API is quite unwieldy from ADF but it works.
-
35 votes
Thanks for suggesting this. It’s on the backlog for prioritization …
An error occurred while saving the comment Nick McDermaid
commented
This should be implemented on the presentation side, not the modelling side.
-
1 vote
An error occurred while saving the comment Nick McDermaid
commented
More to the point: if a process fails, there is no way to capture the error message! Currently when I process models through the REST API, they fail but I can't find an error message anywhere.
Nick McDermaid
shared this idea
·
-
35 votesNick McDermaid
supported this idea
·
-
73 votesNick McDermaid
supported this idea
·
Great minds think alike - I am doing exactly the same thing. I think I'll do a database call with RAISERROR. Nasty but I'm already working around the fact that you can't capture refreshId directly from the initial REST call. If we got raiserror capability in ADF and conditional workflow it would make all of my pipelines waaaay simpler.