Skip to content

Commit 9089026

Browse files
gloridelmoralesgloridelmorales
authored
Merge pull request #8189 from MicrosoftDocs/users/glmorale/sprint260releasenotes
Azure DevOps Sprint 260 release notes
2 parents 8075581 + ff9dc77 commit 9089026

23 files changed

+314
-2
lines changed

‎release-notes/2025/boards/sprint-260-update.md‎

Lines changed: 17 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,17 @@
1+
---
2+
title: Azure DevOps Release Notes - Azure Boards Sprint 260 Update
3+
description: See the Sprint 260 feature updates for Azure Boards, including next steps.
4+
author: gloridelmorales
5+
ms.author: glmorale
6+
ms.date: 8/11/2025
7+
---
8+
9+
# Azure Boards - Sprint 260 Update
10+
11+
## Features
12+
13+
[!INCLUDE [sprint-260-update-links](../includes/boards/sprint-260-update-links.md)]
14+
15+
[!INCLUDE [sprint-260-update](../includes/boards/sprint-260-update.md)]
16+
17+
[!INCLUDE [nextsteps](../includes/nextsteps.md)]

‎release-notes/2025/general/sprint-260-update.md‎

Lines changed: 17 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,17 @@
1+
---
2+
title: Azure DevOps release notes - Azure DevOps Sprint 260 Update
3+
description: See the Sprint 260 feature updates for Azure DevOps, including next steps.
4+
author: gloridelmorales
5+
ms.author: glmorale
6+
ms.date: 8/11/2025
7+
---
8+
9+
# Azure DevOps - Sprint 260 Update
10+
11+
## Features
12+
13+
[!INCLUDE [sprint-260-update-links](../includes/general/sprint-260-update-links.md)]
14+
15+
[!INCLUDE [sprint-260-update](../includes/general/sprint-260-update.md)]
16+
17+
[!INCLUDE [nextsteps](../includes/nextsteps.md)]

‎release-notes/2025/ghazdo/sprint-260-update.md‎

Lines changed: 17 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,17 @@
1+
---
2+
title: Azure DevOps release notes - GitHub Advanced Security for Azure DevOps 260 Update
3+
description: See the Sprint 260 feature updates for GitHub Advanced Security for Azure DevOps, including next steps.
4+
author: gloridelmorales
5+
ms.author: glmorale
6+
ms.date: 8/11/2025
7+
---
8+
9+
# GitHub Advanced Security for Azure DevOps - Sprint 260 Update
10+
11+
## Features
12+
13+
[!INCLUDE [sprint-260-update-links](../includes/ghazdo/sprint-260-update-links.md)]
14+
15+
[!INCLUDE [sprint-260-update](../includes/ghazdo/sprint-260-update.md)]
16+
17+
[!INCLUDE [nextsteps](../includes/nextsteps.md)]

‎release-notes/2025/includes/boards/sprint-260-update-links.md‎

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,8 @@
1+
---
2+
author: gloridelmorales
3+
ms.author: glmorale
4+
ms.date: 8/11/2025
5+
ms.topic: include
6+
---
7+
8+
- [Azure Boards and Pipelines integration for GitHub Enterprise Cloud with Data Residency](#azure-boards-and-pipelines-integration-for-github-enterprise-cloud-with-data-residency)

‎release-notes/2025/includes/boards/sprint-260-update.md‎

Lines changed: 31 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,31 @@
1+
---
2+
author: gloridelmorales
3+
ms.author: glmorale
4+
ms.date: 8/11/2025
5+
ms.topic: include
6+
---
7+
8+
### Azure Boards and Pipelines integration for GitHub Enterprise Cloud with Data Residency
9+
10+
Azure Boards and Azure Pipelines now supports integration with GitHub Enterprise Cloud organizations that have data residency enabled. This update aligns with [GitHub’s September 2024 announcement](https://github.blog/engineering/engineering-principles/github-enterprise-cloud-with-data-residency/) introducing data residency for Enterprise Cloud customers.
11+
12+
**To connect an Azure Boards project:**
13+
14+
Create a new connection in Azure Boards. Then select the **GitHub Enterprise Cloud with data residency** option.
15+
16+
> [!div class="mx-imgBorder"]
17+
> ![Image to show Connect GitHub with Azure Boards.](../../media/260-boards-01.png "Image to show Connect GitHub with Azure Boards.")
18+
19+
**To connect an Azure Pipeline:**
20+
21+
Create a new Pipeline and select GitHub > More Options > GitHub Enterprise Cloud with data residency.
22+
23+
> [!div class="mx-imgBorder"]
24+
> ![Image to show GitHub Enterprise with data residency screen.](../../media/260-boards-02.png "Image to show GitHub Enterprise with data residency screen.")
25+
26+
Then enter the URL of your GitHub Enterprise Cloud organization.
27+
28+
> [!div class="mx-imgBorder"]
29+
> ![Image to show GitHub Enterprise with data residency.](../../media/260-boards-03.png "Image to show GitHub Enterprise with data residency.")
30+
31+
After your https://organization.ghe.com url is validated, the experience is same as it has always been, and you can select your GitHub repositories.

‎release-notes/2025/includes/general/sprint-260-update-links.md‎

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,10 @@
1+
---
2+
author: gloridelmorales
3+
ms.author: glmorale
4+
ms.date: 8/11/2025
5+
ms.topic: include
6+
---
7+
8+
- [Only organizations with existing public projects can create new ones](#only-organizations-with-existing-public-projects-can-create-new-ones)
9+
- [Azure DevOps login flow no longer relies on Azure Resource Manager audience](#azure-devops-login-flow-no-longer-relies-on-azure-resource-manager-audience)
10+
- [Continuous Access Evaluation on Azure DevOps](#continuous-access-evaluation-on-azure-devops)

‎release-notes/2025/includes/general/sprint-260-update.md‎

Lines changed: 27 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,27 @@
1+
---
2+
author: gloridelmorales
3+
ms.author: glmorale
4+
ms.date: 8/11/2025
5+
ms.topic: include
6+
---
7+
8+
### Only organizations with existing public projects can create new ones
9+
10+
Starting this sprint, only organizations that already have the [Allow public projects policy](/azure/devops/organizations/projects/make-project-public?view=azure-devops#1-enable-anonymous-access-to-projects) enabled can continue using it. The policy does not change for existing customers.
11+
12+
Microsoft recommends using [GitHub](https://github.com/) for all your public project needs.
13+
14+
### Azure DevOps login flow no longer relies on Azure Resource Manager audience
15+
16+
We've removed a dependency on the Azure Resource Manager (ARM) resource (https://management.azure.com) when logging in or refreshing Entra access tokens used to access Azure DevOps. The ARM resource is often associated with the Azure portal (https://portal.azure.com), and admins may want to restrict which users in their tenant can access the portal through Conditional Access policy (CAP) enforcement.
17+
18+
Due to Azure DevOps previous reliance on ARM, admins had to permit all Azure DevOps users to bypass the ARM CAPs in order to use Azure DevOps. This is no longer necessary as we've removed the ARM resource audience requirement during signin and refresh token flows.
19+
20+
There remain a couple of notable exceptions — the following ​user groups may need continued access to ARM:
21+
22+
1. Billing admins need access to ARM to setup billing and access subscriptions
23+
2. Service Connection creators require continued access to ARM for ARM role assignment and updates to MSIs
24+
25+
### Continuous Access Evaluation on Azure DevOps
26+
27+
Azure DevOps now supports [Continuous Access Evaluation (CAE)](https://learn.microsoft.com/entra/identity/conditional-access/concept-continuous-access-evaluation), enabling near real-time enforcement of Conditional Access policies through Microsoft Entra ID. This enhancement allows Azure DevOps to instantly revoke access when critical events occur—such as user disablement, password resets, or location/IP changes—without waiting for token expiration. Real-time enforcement means that compromised accounts or policy violations are addressed as soon as we learn of the event, reducing exposure windows and improving incident response. Developers using CAE-capable client libraries ([].NET now available](https://www.nuget.org/packages/Microsoft.TeamFoundationServer.Client/20.259.0-preview), Python and Go to come) must handle claims challenges and update sign-in flows accordingly. General availability begins August 2025 following phased rollout for all customers.

‎release-notes/2025/includes/ghazdo/sprint-260-update-links.md‎

Lines changed: 11 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,11 @@
1+
---
2+
author: gloridelmorales
3+
ms.author: glmorale
4+
ms.date: 8/11/2025
5+
ms.topic: include
6+
---
7+
8+
- [New secret patterns added to Advanced Security](#new-secret-patterns-added-to-advanced-security)
9+
- [Periodic repository re-scans performed for secret scanning](#periodic-repository-re-scans-performed-for-secret-scanning)
10+
- [Dismissals in Advanced Security now available in alert detail UI](#dismissals-in-advanced-security-now-available-in-alert-detail-ui)
11+
- [Validity checking for secrets now generally available](#validity-checking-for-secrets-now-generally-available)

‎release-notes/2025/includes/ghazdo/sprint-260-update.md‎

Lines changed: 28 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,28 @@
1+
---
2+
author: gloridelmorales
3+
ms.author: glmorale
4+
ms.date: 8/11/2025
5+
ms.topic: include
6+
---
7+
8+
### New secret patterns added to Advanced Security
9+
10+
New patterns have been added to Advanced Security's Secret Protection for both user alerts and push protection. View the updated list of supported secret patterns at [Secret scanning patterns](/azure/devops/repos/security/github-advanced-security-secret-scan-patterns?view=azure-devops#partner-provider-patterns).
11+
12+
### Periodic repository re-scans performed for secret scanning
13+
14+
For any stale repositories, without committing to the repository you may not receive alerts for new or updated secret patterns. To resolve this, we've added periodic, automatic re-scans performed on your behalf to raise new alerts for updated patterns.
15+
16+
### Dismissals in Advanced Security now available in alert detail UI
17+
Previously, dismissal information was only available via the alerts API. Now, information about the latest dismissal and the user identity shows up in the alert detail view.
18+
19+
> [!div class="mx-imgBorder"]
20+
> [![Image to show information about the latest dismissal.](../../media/260-ghazdo-01.png "Image to show information about the latest dismissal")](../../media/260-ghazdo-01.png#lightbox)
21+
22+
This address [Developer Community feedback](https://developercommunity.visualstudio.com/t/GHAzDO-closed-security-issues-misses-inf/10930119).
23+
24+
## Validity checking for secrets now generally available
25+
26+
Validity checking is a feature to determine if an exposed secret is active or inactive, helping you prioritize your remediation efforts. No opt-in is needed; once the feature is available in your organization, any patterns that support validity checking will automatically attempt a validity check. In an alert that supports validity checking, you can also manually re-validate the secret.
27+
28+
See all supported patterns with validity checking at [Secret scanning patterns](/azure/devops/repos/security/github-advanced-security-secret-scan-patterns?view=azure-devops#partner-provider-patterns).

‎release-notes/2025/includes/repos/sprint-260-update-links.md‎

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,8 @@
1+
---
2+
author: gloridelmorales
3+
ms.author: glmorale
4+
ms.date: 8/11/2025
5+
ms.topic: include
6+
---
7+
8+
- [Improved screen reader support for pull request experience](#improved-screen-reader-support-for-pull-request-experience)

0 commit comments

Comments
 (0)