What changed

GitHub Copilot code review can choose Lite, Balanced or Max effort from pull-request complexity, use related public repositories as context and flag both patterned and model-detected secrets. Azure DevOps code review moved to general availability with audit and Azure billing controls.

Why it matters

Review depth, cross-repository reads and secret finding now influence cost and exposure automatically. Enterprise maximums constrain adaptive effort, but public context and probabilistic secret detection still need explicit false-positive and leakage tests.

What to do

Pilot on a synthetic repository with known secrets, a public dependency and low- and high-risk changes; set an enterprise effort ceiling, record missed and false findings, verify audit events and reconcile AI credits.

Caveat

Adaptive, cross-repository context and secret detection are public previews. Model-detected secrets are probabilistic, public-repository context may be incomplete and Azure DevOps usage is billed through linked Azure subscriptions.