1
submitted 3 days ago by [email protected] to c/[email protected]

cross-posted from: https://sopuli.xyz/post/30528273

Hi everyone!

Let's see if we can get put some live into this community! :)

I just started my journey with Azure Automation Accounts and Source Control and hit a snag. Couldn't find 100% certain information online, so hoping someone here might help.

We have an Automation Account that runs a bunch of Runbooks.

We have an Azure DevOps repo where I want all these Runbooks to live.

When setting up Source Control I need to Authenticate. From what I found out, in order to authenticate for automatic sync, the account used for authentication needs to be a Project Administrator with a Basic license on the Azure DevOps side, and have Contributor permissions on the Automation Account's side.

We have a Managed Identity set up with all those permissions.

Question: is it possible to use the Managed Identity for Authentication? When I click the "Authenticate" button, I get a regular interactive login page, and I can't switch to the MI. Do I need to spend two Basic licenses (one for MI, another for a Service Account) just to set up Source Control to Azure DevOps?

no comments (yet)
sorted by: hot top new old
there doesn't seem to be anything here
this post was submitted on 17 Jul 2025
1 points (60.0% liked)

Service Clouds: AWS, Azure, GCP, etc.

205 readers
2 users here now

A community for discussions related to all cloud service providers and the tools of the trade.

Related Communities:

General

Tools

Platforms

Infrastructure Orchestration

Programming

founded 2 years ago
MODERATORS