You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Sep 25, 2026. It is now read-only.
Repository navigation
This repository was archived by the owner on Sep 25, 2026. It is now read-only.
Unable to create service connection using a scope level of AzureMLWorkspace #56
In Azure DevOps, I cannot create a service connection using the scope level of 'AzureMLWorkspace'. The error generated suggests i don't have permission to add a role. As a workaround, i manually created an SP and had my subscription admin provide it 'contributor' role access. This approach also fails from the ADO side likely because the SP is not added as a user to the AML Workspace - and i don't have sufficient permissions as a 'contributor' to do so. This is a blocker for using Azure Model registration as an artifact for Azure DevOps and I have documented it on the ML Platform/AzureMLPython SDK teams channel.
It definitely works with the "owner" permission on the Azure subscription. But we'll check how it works with the "owner" permissions on AML Workspace only.
It does not work with 'owner' permissions on AML Workspace only. It works with owner permissions on RG - which can only be assigned by an azure subscription admin.
Kate Baroni (@KBaroni) Please ensure you have owner or user admin access on the workspace. Most probably your contributor access from the subscription is inherited to the workspace.
I have also updated doc with an explicit note on this.
Activity
eedorenko commentedon Aug 28, 2019
Kate Baroni (@KBaroni) what permission do you have in the subscription used to create a service connection? Can you provide the error message?
KBaroni commentedon Aug 28, 2019
eedorenko commentedon Aug 28, 2019
So, yes, it expects to be an "Owner" or "User Access Administrator".
KBaroni commentedon Aug 28, 2019
eedorenko commentedon Aug 28, 2019
It definitely works with the "owner" permission on the Azure subscription. But we'll check how it works with the "owner" permissions on AML Workspace only.
KBaroni commentedon Aug 30, 2019
It does not work with 'owner' permissions on AML Workspace only. It works with owner permissions on RG - which can only be assigned by an azure subscription admin.
eedorenko commentedon Aug 30, 2019
Thanks for confirming that. We'll add a note to the documentation that one should have owner permission on RG to create a service connection.
update doc to address issue 56
sudivate commentedon Sep 4, 2019
Kate Baroni (@KBaroni) Please ensure you have owner or user admin access on the workspace. Most probably your contributor access from the subscription is inherited to the workspace.
I have also updated doc with an explicit note on this.
Update doc to address AzDO ML Task permissions (#61)