Can I Use Managed Identity for Azure DevOps Source Control Authentication?

Yeah, that's a bummer. I had hoped maybe I'd misunderstood it, but it sounds like you're spot on. We started the connection with my admin account, and when we removed that Basic license, the connection broke immediately.

You could definitely set up a pipeline that runs in the context of a service principal instead of the Managed Identity. This way, you can deploy your Runbooks into the automation account and keep them updated with the repo. Honestly, I tried using the source control feature on the Automation Account; I got it to work to some extent, but it never triggered on commits, so I eventually gave up on it.

I totally get the confusion here. After reviewing the Microsoft docs, my understanding was that when you authenticate to Azure DevOps, you delegate access either with the Managed Identity or by creating a personal access token (PAT). They describe it like this: When you first set up source control integration, you authenticate using your user credentials via OAuth, which is tied to your identity for the initial setup. After this, Azure Automation uses the Managed Identity to handle syncing jobs. So it seems like while the sync runs under the Managed Identity, the actual Git operations still depend on that initial OAuth token. Unfortunately, Managed Identity is not designed for direct authentication with Azure DevOps for Git tasks, so you'll likely need the user credentials for OAuth to maintain the connection.