Skip to content
This repository was archived by the owner on Sep 25, 2026. It is now read-only.
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

Closed

Description

@KBaroni

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.

Activity

  1. eedorenko commented on Aug 28, 2019

    @eedorenko
    Contributor

    Kate Baroni (@KBaroni) what permission do you have in the subscription used to create a service connection? Can you provide the error message?

  2. KBaroni commented on Aug 28, 2019

    @KBaroni
    Author
  3. eedorenko commented on Aug 28, 2019

    @eedorenko
    Contributor

    So, yes, it expects to be an "Owner" or "User Access Administrator".

  4. KBaroni commented on Aug 28, 2019

    @KBaroni
    Author
  5. eedorenko commented on Aug 28, 2019

    @eedorenko
    Contributor

    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.

  6. KBaroni commented on Aug 30, 2019

    @KBaroni
    Author

    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.

  7. eedorenko commented on Aug 30, 2019

    @eedorenko
    Contributor

    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.

  8. sudivate commented on Sep 4, 2019

    @sudivate
    Contributor

    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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions