Skip to content

Initialize fails when using self-hosted agents and Managed Identity #533

@StefanIvemo

Description

@StefanIvemo

Describe the bug

When using self-hosted agents and Managed Identity instead of service principal the initialize step fails. In my case I'm using VMSS.

Steps to reproduce

  1. Deploy self-hosted agents and enable Managed Identity. Configure new Agent Pool and update pipelines to use the new pool.
  2. Update the connect step in sharedSteps.yml to: Connect-AzAccount -TenantId $(ARM_TENANT_ID) -SubscriptionId $(ARM_SUBSCRIPTION_ID) -Identity
  3. Run Pull pipeline.

Screenshots

Initialize will fail on Invoke-AzOpsPull.

image

If I add Import-Module AzOps -Force to the initialize step I get the following error instead.

image

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions