Select Language:
If you’ve been having trouble with your Azure SRE Agent not authenticate properly with Azure DevOps from your PME tenant, here’s a simple solution that can help you get things working smoothly again.
The issue often comes down to the account being used during the authentication process. In some cases, the agent might try to use a corporate (Corp) account that doesn’t have the right permissions or isn’t linked correctly to your Azure DevOps repositories. When this happens, the agent won’t be able to discover or add your repositories as expected.
To fix this, make sure the agent uses the correct account—specifically, the account associated with your Azure DevOps project. Once you switch to this correct account, the repositories should be discovered and added successfully. This is exactly what should happen if everything is configured properly.
This approach aligns with the official guidance from Microsoft on cross-account Azure DevOps access and OAuth authorization. You can review the detailed instructions here: Microsoft Docs – Cross-Account Azure DevOps OAuth Authorization.
If you find this information helpful, please consider up-voting or leaving feedback. Sharing your experience can help others in the community facing similar issues.
ChatGPT
Perplexity
Gemini AI
Grok AI
