Live
Cloudflare Images Analytics Dashboard Adds 30‑Day Delivery VisibilityAmazon ECS Adds Native Blue/Green, Canary, and Linear Deployments for Safer Container RolloutsGemini agentic tools add LLM‑driven automation to Partner Marketing StudioGitHub Actions makes RHEL 9/10 runner images generally available for larger workloadsIntegrating Decider Models to Reduce Latency and Cost in AI Agent WorkflowsAWS Emulator Enables Local Testing of 200+ Services, but Lacks IAM ValidationSageMaker AI monitoring adds automatic latency drift, idle GPU, and configuration gap detection for inference endpointsEmbedding Proactive Governance into Enterprise‑Scale Agentic AICloudflare Images Analytics Dashboard Adds 30‑Day Delivery VisibilityAmazon ECS Adds Native Blue/Green, Canary, and Linear Deployments for Safer Container RolloutsGemini agentic tools add LLM‑driven automation to Partner Marketing StudioGitHub Actions makes RHEL 9/10 runner images generally available for larger workloadsIntegrating Decider Models to Reduce Latency and Cost in AI Agent WorkflowsAWS Emulator Enables Local Testing of 200+ Services, but Lacks IAM ValidationSageMaker AI monitoring adds automatic latency drift, idle GPU, and configuration gap detection for inference endpointsEmbedding Proactive Governance into Enterprise‑Scale Agentic AI
GitHub

GitHub Copilot app expands to Azure DevOps, browser extensions, and GA GHES support

AI SummaryPowered by AI

The Copilot desktop client now integrates Azure DevOps repositories, adds public‑preview browser usage, and moves GitHub Enterprise Server support to general availability. These changes let engineers manage code and AI assistance across more environments, but they also introduce new configuration and security considerations.

The latest GitHub Copilot app release adds three concrete capabilities: public‑preview integration with Azure DevOps repositories, public‑preview browser‑based usage via a Chrome extension, and general‑availability support for GitHub Enterprise Server (GHES). Each feature is gated behind explicit settings and version requirements, meaning teams must update the app and adjust their workflows to benefit.

Azure DevOps repository integration

Developers can now clone an Azure DevOps repo directly in the Copilot app, create branches, edit code, and open pull requests without leaving the client. The sidebar tracks PR status, and an “Fix” action can address review comments automatically. An optional “agent merge” feature can resolve CI failures and complete the PR once Azure DevOps checks and policies succeed. This integration is in public preview and must be enabled via Settings > Experimental > Azure DevOps integration, then adding an account under Accounts > Add account with the Microsoft identity used for Azure DevOps. Cloud sessions are not provided for Azure DevOps repos, so any remote compute assistance remains unavailable.

Browser‑based Copilot usage

Copilot can now operate inside Chromium‑based browsers (Chrome, Edge) through the GitHub Copilot extension. The extension runs in an isolated tab group and can fill forms, scrape web pages, or debug web apps while you browse. Browser use is disabled by default; enabling it requires installing the extension and toggling both Enable Computer Use and Enable Browser Use in Settings > Computer Use. Permission levels are configurable in the extension’s settings. The same browser capability is also exposed in Copilot CLI, VS Code, and JetBrains IDEs.

General‑availability GHES support

Support for on‑premises GitHub Enterprise Server moves from an opt‑in preview to GA. Users must run Copilot app version 1.2.0 or later, sign in with a GitHub.com or GHE.com account, and add a GHES account via Settings > Accounts > Add account > GitHub Enterprise Server. As with Azure DevOps, cloud sessions are not available for GHES repositories, limiting remote AI compute to local resources.

Operational and security considerations

  • Version management: Teams need to ensure the Copilot app is at least version 1.2.0 to access GHES and the new integrations.
  • Feature gating: Both Azure DevOps and browser use are public previews; enabling them requires explicit opt‑in, which can be tracked in configuration management.
  • Permission scope: The browser extension introduces additional permission surfaces; reviewing the extension’s settings is advisable to align with organizational policies.
  • Policy compliance: The “agent merge” workflow respects Azure DevOps checks and policies, so existing gate definitions remain enforced.
  • Session limitations: Absence of cloud sessions for Azure DevOps and GHES means AI‑driven compute stays on the client, affecting performance expectations for large code‑gen tasks.

Related CloudNinjas coverage: AI engineering.

What This Means For Practitioners

Adopt the new integrations only after confirming version compliance and updating internal configuration baselines. Evaluate the browser extension’s permission model against your security standards before enabling it for developers. For Azure DevOps teams, test the “agent merge” flow in a sandbox to verify that existing CI policies behave as expected. GHES administrators should plan rollout alongside the app update, noting the lack of cloud sessions for any remote AI workloads. Monitoring upcoming announcements about moving these previews to GA will help you stay aligned with the evolving Copilot ecosystem.

Originally published atGitHub Changelog