Earlier this month, Microsoft announced that GitHub Copilot code review is now in technical preview for Azure Repos. On-demand AI review, directly inside Azure DevOps pull requests — no GitHub Copilot license required. It's a notable expansion, and the timing matters.
For the first time, Copilot's review capabilities are crossing provider boundaries in a production-facing way. That's an acknowledgment of something engineering teams have known for years: the code doesn't all live in one place. Most teams above a certain scale run repos across at least two providers. GitHub for product work, Azure DevOps for enterprise workloads, GitLab for self-hosted requirements. The organizational reality is messy in a way that single-provider tooling has historically pretended not to see.
Now that AI review is beginning to travel across providers, the structural gap shifts. The question stops being "does the AI understand my diff?" and starts being "does anyone have a clear view of everything that's moving across the org right now?"
A PR in Azure Repos that touches a shared authentication library might have a directly related PR open on GitHub. An interface refactor on GitLab might be blocking three other services. The AI reviewer sees the diff in front of it. It doesn't see the adjacent PRs two tabs over — because those don't live in the review interface. They live in your institutional memory, or they don't get seen at all.
As teams ship faster and merge more frequently, the cost of missed cross-repo dependencies rises. Faster individual review cycles don't automatically produce better org-level visibility. The stale PR you missed wasn't invisible — it was just in a different tab on a different provider.
The teams that get the most out of cross-provider AI review will be the ones who solve the visibility layer first. Otherwise, you're adding intelligence to individual diffs while the broader picture stays fragmented.
Engineering leaders watching the AI code review space should track this shift carefully. Cross-provider AI review capability is maturing quickly. The next bottleneck is unified PR visibility — a live view of all open pull requests across every repo and every provider, without tab-hopping.
For teams managing that problem today, Code Board aggregates PRs from GitHub and GitLab into a single Kanban-style board, so cross-repo context is part of every review — not something you reconstruct after the fact.