Azure DevOps Blog

We’re excited to announce the release candidate (RC) of Azure DevOps Server, bringing new features previously available in our hosted version. You can  download Azure DevOps Server RC today. A direct upgrade to Azure DevOps Server RC is supported from any version of Team Foundation Server, including Team Foundation Server 2015 and newer. Note: October The post Announcing the new Azure DevOps Server RC Release appeared first on Azure DevOps Blog.

Several months ago, GitHub introduced the public preview of its Copilot coding agent, a powerful new capability that allows you to assign GitHub Issues directly to Copilot. From there, the agent works independently in the background, much like a human developer, to complete the task. Copilot evaluates the request based on the information you provide, The post Azure Boards integration with GitHub Copilot (Private Preview) appeared first on Azure DevOps Blog.

Delivering high-quality software is a necessity and that’s why Azure Test Plans has introduced the all-new Test Run Hub, an enabler for teams who want to take control of their testing process and drive continuous improvement. What Makes the Test Run Hub a Must-Have? The Test Run Hub is designed to help teams track test The post New Test Run Hub in Azure Test Plans appeared first on Azure DevOps Blog.

Building on our previous post about implementing dev-to-prod promotion with GitHub Actions, this follow-up demonstrates the same “build once, deploy everywhere” pattern using Azure DevOps Pipelines. You’ll learn how to leverage Azure DevOps YAML pipelines with Azure Developer CLI (azd). This approach ensures consistent, reliable deployments across environments. Environment-Specific Infrastructure The infrastructure approach is identical The post Azure Developer CLI: From Dev to Prod with Azure DevOps Pipelines appeared first on Azure DevOps Blog.

We’re making an important change to how Azure DevOps displays OAuth client secrets to align with industry best practices and improve our overall security posture. Starting September, newly generated client secrets will be shown only once at the time of creation. After that, they will no longer be retrievable via the UI or API. This The post Azure DevOps OAuth Client Secrets Now Shown Only Once appeared first on Azure DevOps Blog.

If you’ve ever waded through a swamp of secret scanning alerts wondering, “Which of these are actually dangerous right now?” — this enhancement is for you. Secret validity checks in GitHub Advanced Security for Azure DevOps (and the standalone Secret Protection experience) add a high‑signal field to each alert: Active (still usable), or Unknown (couldn’t The post Hunting Living Secrets: Secret Validity Checks Arrive in GitHub Advanced Security for Azure DevOps appeared first on Azure DevOps Blog.

Update (Oct 1): Continuous Access Evaluation (CAE) was temporarily paused as we addressed customer-reported issues. It will be reenabled for all customers by end of October. We’re thrilled to announce that Continuous Access Evaluation (CAE) is now supported on Azure DevOps, bringing a new level of near real-time security enforcement to your development workflows. 🔐 The post Real-Time Security with Continuous Access Evaluation (CAE) comes to Azure DevOps appeared first on Azure DevOps Blog.

Any experiences that require additional setup is cumbersome, especially when there are multiple people needed. In GitHub Advanced Security for Azure DevOps, we’re working to make it easier to enable features and scale out enablement across your enterprise. You can now automatically inject the dependency scanning task into any pipeline run targeting your default branch. The post Automate your open-source dependency scanning with Advanced Security appeared first on Azure DevOps Blog.

In today’s fast-paced software development cycles, manual testing often becomes a significant bottleneck. Our team was facing a growing backlog of test cases that required repetitive manual execution—running the entire test suite every sprint. This consumed valuable time that could be better spent on exploratory testing and higher-value tasks. We set out to solve this The post From Manual Testing to AI-Generated Automation: Our Azure DevOps MCP + Playwright Success Story appeared first on Azure DevOps Blog.

This post walks through how to implement a “build once, deploy everywhere” pattern using Azure Developer CLI (azd) that provisions environment-specific infrastructure and promotes applications from dev to prod with the same build artifacts. You’ll learn how to use conditional Bicep deployment, environment variable injection, package preservation across environments, and automated CI/CD promotion from development The post Azure Developer CLI: From Dev to Prod with One Click appeared first on Azure DevOps Blog.