Hi! The important detail is that the repositories and SRE Agent are in different tenants. The agent’s connection identity must exist in the corporate tenant and have explicit access to the Azure DevOps organization and repositories. If cross-tenant repository connections are not supported by the current agent experience, deploy the agent in the corporate tenant or mirror the required repositories into an accessible organization. Also check the agent’s connection logs for the exact tenant or authorization failure.
unable to add repos to SRE Agent
unable to add repos whether as attached or remote search both, repos are in Corp tenant while SRE agent sits in the PME tenant.
Azure DevOps
Hi Harsh Gupta,
Welcome to Microsoft Q&A Platform.
As discussed , the Azure SRE Agent was not using the Corp account for Azure DevOps authentication from the PME tenant. Once the correct account was used, the repositories were successfully discovered and added, which is the expected behavior.
This is consistent with the prerequisites outlined in the Microsoft Learn documentation for cross-account Azure DevOps access: https://learn.microsoft.com/en-us/azure/sre-agent/cross-account-azdo-oauth-authorization
Please
and “up-vote” wherever the information provided helps you, **this can be beneficial to other community members.