Add title and overview

gloridelmorales · gloridelmorales · commit 4132e588b273 · 2025-08-06T11:51:26.000-07:00
diff --git a/release-notes/2025/includes/boards/sprint-260-update-links.md b/release-notes/2025/includes/boards/sprint-260-update-links.md
@@ -5,4 +5,4 @@ ms.date: 8/11/2025
 ms.topic: include
 ---
 
-- [Azure Boards and Pipelines Integration with GitHub Enterprise Cloud with Data Residency](#azure-boards-and-pipelines-integration-with-github-enterprise-cloud-with-data-residency)
+- [Azure Boards and Azure Pipelines integration with GitHub Enterprise Cloud (data residency enabled)](#azure-boards-and-azure-pipelines-integration-with-github-enterprise-cloud-data-residency-enabled)
diff --git a/release-notes/2025/includes/boards/sprint-260-update.md b/release-notes/2025/includes/boards/sprint-260-update.md
@@ -5,7 +5,7 @@ ms.date: 8/11/2025
 ms.topic: include
 ---
 
-### Azure Boards and Pipelines Integration with GitHub Enterprise Cloud with Data Residency
+### Azure Boards and Azure Pipelines integration with GitHub Enterprise Cloud (data residency enabled)
 
 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.
 
@@ -23,9 +23,9 @@ Create a new Pipeline and select GitHub > More Options > GitHub Enterprise Cloud
 > [!div class="mx-imgBorder"]
 > ![Image to show GitHub Enterprise with data residency screen.](../../media/260-boards-02.png "Image to show GitHub Enterprise with data residency screen.")
 
-Then enter the URL of your GitHub Enterprise Cloud organization.
+    Then enter the URL of your GitHub Enterprise Cloud organization.
 
 > [!div class="mx-imgBorder"]
 > ![Image to show GitHub Enterprise with data residency.](../../media/260-boards-03.png "Image to show GitHub Enterprise with data residency.")
 
-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.
+    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.
diff --git a/release-notes/2025/includes/general/sprint-260-update.md b/release-notes/2025/includes/general/sprint-260-update.md
@@ -7,15 +7,17 @@ ms.topic: include
 
 ### Only organizations with existing public projects can create new ones
 
-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. Microsoft recommends using [GitHub](https://github.com/) for all your public project needs.
+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. 
+
+Microsoft recommends using [GitHub](https://github.com/) for all your public project needs.
 
 ### Azure DevOps login flow no longer relies on Azure Resource Manager audience
 
 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.
 
-Due to ADO's previous reliance on ARM, admins had to permit all ADO users to bypass the ARM CAPs in order to use ADO. This is no longer necessary as we've removed the ARM resource audience requirement during signin and refresh token flows. 
+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. 
 
 There remain a couple of notable exceptions  — the following ​user groups may need continued access to ARM:
 
 1. Billing admins need access to ARM to setup billing and access subscriptions
-2. Service Connection creators require continued access to ARM for ARM role assignment and updates to MSIs.
+2. Service Connection creators require continued access to ARM for ARM role assignment and updates to MSIs
diff --git a/release-notes/2025/includes/repos/sprint-260-update.md b/release-notes/2025/includes/repos/sprint-260-update.md
@@ -7,20 +7,20 @@ ms.topic: include
 
 ### Improved screen reader support for pull request experience
 
-We improved support for screen readers in Pull Request experience.
-The new option in built-in code editor will allow to enable announcements for line changes and comments.
+We improved support for screen readers in the pull request experience.
+The new option in built-in code editor will let you enable announcements for line changes and comments.
 
-To enable new option, on Pull Request page click "File" tab:
+To enable the new option, from the pull request page click on the **File** tab. 
 
 > [!div class="mx-imgBorder"]
 > [![Image to show file tab.](../../media/260-repos-01.png "Image to show file tab.")](../../media/260-repos-01.png#lightbox) 
 
-After that, click on "Editor preferences" button:
+Then, click on the **Editor preferences** button.
 
 > [!div class="mx-imgBorder"]
 > [![Image to Editor preferences button.](../../media/260-repos-02.png "Image to Editor preferences button.")](../../media/260-repos-02.png#lightbox)
 
-In opened popup menu enable "Enable announcements for line changes and comments to enhance screen reader accessibility" option and click on "Save" button:
+On the popup menu, select the **Enable announcements for line changes and comments to enhance screen reader accessibility** option and **Save**.
 
 > [!div class="mx-imgBorder"]
 > [![Image to Editor preferences.](../../media/260-repos-03.png "Image to Editor preferences.")](../../media/260-repos-03.png#lightbox)
diff --git a/release-notes/2025/media/260-repos-03.png b/release-notes/2025/media/260-repos-03.png
diff --git a/release-notes/2025/sprint-260-update.md b/release-notes/2025/sprint-260-update.md
@@ -1,14 +1,16 @@
 ---
-title: TBD
+title: Azure Boards and Azure Pipelines GitHub Enterprise Cloud Integration
 author: gloridelmorales
 ms.author: glmorale
 ms.date: 8/11/2025
-description: TBC
+description: Azure Boards and Azure Pipelines GitHub Enterprise Cloud Integration
 ---
 
-# TBD
+# Azure Boards and Azure Pipelines GitHub Enterprise Cloud Integration
 
-Placeholder 
+Azure Boards and Azure Pipelines now support integration with GitHub Enterprise Cloud organizations with data residency enabled. You can learn more about how to create a new connection for Azure Boards and a new pipeline form the release notes. 
+
+In addition, with this release we are no longer allowing organizations to create public projects. This change won't impact organizations that already have the Allow public policy enabled. 
 
 Check out the release notes for details.
 
