address accumulated build suggestion fixes

Author: chcomley

release-notes/2023/includes/ghazdo/sprint-228-update.md

@@ -7,7 +7,7 @@ ms.topic: include
 
 ### Changes to Code Scanning (CodeQL) user input task and variables
 
-All user-provided inputs are now specified in the CodeQL Initialize task, which is responsible for configuring the CodeQL analysis environment used for code analysis with CodeQL `AdvancedSecurity-Codeql-Init@1``. See the [configure GitHub Advanced Security for Azure DevOps features documentation](/azure/devops/repos/security/configure-github-advanced-security-features?view=azure-devops&tabs=yaml) for more information on configuring GitHub Advanced Security for Azure DevOps. 
+All user-provided inputs are now specified in the CodeQL Initialize task, which is responsible for configuring the CodeQL analysis environment used for code analysis with CodeQL `AdvancedSecurity-Codeql-Init@1``. See the [configure GitHub Advanced Security for Azure DevOps features documentation](/azure/devops/repos/security/configure-github-advanced-security-features?view=azure-devops&tabs=yaml&preserve-view=true) for more information on configuring GitHub Advanced Security for Azure DevOps. 
 
 In addition, user inputs take precedence over any values set by variables. For instance, if you establish the language variable as `advancedsecurity.codeql.language: Java` and subsequently, during the CodeQL initialization phase, you specify the language as an input with `Language: cpp,` the input `cpp` will override the variable `Java` for the language. Please ensure that your inputs are configured accurately.
 
@@ -21,13 +21,13 @@ Below are the require task for code scanning.
 > ![Screenshot of required code scanning tasks.](../../media/228-general-01.png "Screenshot of required code scanning tasks")
 
 
-For more information, please refer to the set up code scanning [documentation](/azure/devops/repos/security/configure-github-advanced-security-features?view=azure-devops&tabs=yaml#set-up-code-scanning).
+For more information, please refer to the set up code scanning [documentation](/azure/devops/repos/security/configure-github-advanced-security-features?view=azure-devops&tabs=yaml#set-up-code-scanning&preserve-view=true).
 
 ### CodeQL code scanning now supports Swift
 
 We're expanding our support for CodeQL code scanning to include Swift! This means that developers working on Swift libraries and applications for Apple platforms can now take advantage of our top-notch code security analysis. Our current capabilities include the detection of issues such as path injection, risky web view fetches, various cryptographic misuses, and other forms of unsafe handling or processing of unfiltered user data.
 
 Swift is now part of our roster of supported programming languages, which includes C/C++, Java/Kotlin, JavaScript/TypeScript, Python, Ruby, C#, and Go. Altogether, these languages enable us to perform nearly 400 comprehensive checks on your code, all while maintaining a low rate of false positives and ensuring high precision.
 
-See the [configure GitHub Advanced Security for Azure DevOps features documentation](/azure/devops/repos/security/configure-github-advanced-security-features?view=azure-devops&tabs=yaml) for more information on configuring GitHub Advanced Security for Azure DevOps for your repositories.
+See the [configure GitHub Advanced Security for Azure DevOps features documentation](/azure/devops/repos/security/configure-github-advanced-security-features?view=azure-devops&tabs=yaml&preserve-view=true) for more information on configuring GitHub Advanced Security for Azure DevOps for your repositories.
 

release-notes/2024/general/sprint-233-update.md

@@ -1,6 +1,6 @@
 ---
 title: Azure DevOps release notes - Azure DevOps Sprint 233 Update
-description: See the Sprint 233 feature updates for Azure DevOps, including next steps.
+description: See Sprint 233 feature updates for Azure DevOps, including next steps.
 author: ckanyika
 ms.author: glmorale
 ms.date: 1/19/2024

release-notes/2024/includes/artifacts/sprint-246-update.md

@@ -7,9 +7,9 @@ ms.topic: include
 
 ### Authentication to Azure Artifacts using a public feed and Cargo
 
-Due to a limitation with the Cargo client, authentication was all-or-nothing. For private feeds, authentication would be sent, but for [public feeds](/azure/devops/artifacts/tutorials/share-packages-publicly?view=azure-devops&tabs=nuget), which need to allow for anonymous users, no authentication would be sent, even if it was available or needed.
+Due to a limitation with the Cargo client, authentication was all-or-nothing. For private feeds, authentication would be sent, but for [public feeds](/azure/devops/artifacts/tutorials/share-packages-publicly?view=azure-devops&tabs=nuget&preserve-view=true), which need to allow for anonymous users, no authentication would be sent, even if it was available or needed.
 
-Now, authenticated users can connect to a public Azure Artifacts feed, just as they would a private feed. If you or your pipeline agent have [permission to save packages from upstream sources](/azure/devops/artifacts/feeds/feed-permissions?view=azure-devops#permissions-table), you can access packages from crates.io through the feed. This change gives control of what packages can come into a feed back in the hands of feed administrators. Once packages are brought into the feed from an upstream source, anonymous users will have access to them.
+Now, authenticated users can connect to a public Azure Artifacts feed, just as they would a private feed. If you or your pipeline agent have [permission to save packages from upstream sources](/azure/devops/artifacts/feeds/feed-permissions?view=azure-devops#permissions-table&preserve-view=true), you can access packages from crates.io through the feed. This change gives control of what packages can come into a feed back in the hands of feed administrators. Once packages are brought into the feed from an upstream source, anonymous users will have access to them.
 
-To ensure authentication, append  `~force-auth` to the feed name in your registry URL. You can find out more details through [our public documentation](/azure/devops/artifacts/cargo/cargo-upstream-source?view=azure-devops&tabs=publicfeed%2CWindows%2CPowerShell#connect-to-your-feed).
+To ensure authentication, append  `~force-auth` to the feed name in your registry URL. You can find out more details through [our public documentation](/azure/devops/artifacts/cargo/cargo-upstream-source?view=azure-devops&tabs=publicfeed%2CWindows%2CPowerShell#connect-to-your-feed&preserve-view=true).
 

release-notes/2024/includes/boards/sprint-234-update.md

@@ -42,7 +42,7 @@ When you go to the work item, the corresponding Development and Deployment contr
 > [!div class="mx-imgBorder"]
 > ![Screenshots of related work.](../../media/234-boards-02.png "Screenshots of related work.")
 
-If you decide to [connect a GitHub repo to Azure Boards](/azure/devops/boards/github/?view=azure-devops&preserve-view=true ), the Development control for GitHub repos will be displayed.
+If you decide to [connect a GitHub repo to Azure Boards](/azure/devops/boards/github/?view=azure-devops&preserve-view=true), the Development control for GitHub repos will be displayed.
 
 > [!div class="mx-imgBorder"]
 > ![Screenshots of development control .](../../media/234-boards-03.png "Screenshots of development control .")

release-notes/2024/includes/general/sprint-234-update.md

@@ -17,4 +17,4 @@ Every five years, it's essential to update the **Client Secret** for your Azure
 > [!div class="mx-imgBorder"]
 > ![Screenshot of Select a geography.](../../media/234-general-01.png "Screenshot of Select a geography")
 
-Look for this new functionality in each of your Azure DevOps app pages that can be accessible through [your profile here](https://app.vssps.visualstudio.com/_signin?realm=app.vssps.visualstudio.com&reply_to=https%3A%2F%2Fapp.vssps.visualstudio.com%2Fprofile%2Fview&redirect=1&context=eyJodCI6MywiaGlkIjoiYTVjYTM1ZWItMTQ4ZS00Y2NkLWJiYjMtZDMxNTc2ZDc1OTU4IiwicXMiOnt9LCJyciI6IiIsInZoIjoiIiwiY3YiOiIiLCJjcyI6IiJ90#ctx=eyJTaWduSW5Db29raWVEb21haW5zIjpbImh0dHBzOi8vbG9naW4ubWljcm9zb2Z0b25saW5lLmNvbSIsImh0dHBzOi8vbG9naW4ubWljcm9zb2Z0b25saW5lLmNvbSJdfQ2). Learn more about this new step in our [Azure DevOps OAuth guide](/azure/devops/integrate/get-started/authentication/azure-devops-oauth?view=azure-devops&preserve-view=tru).
+Look for this new functionality in each of your Azure DevOps app pages that can be accessible through [your profile here](https://app.vssps.visualstudio.com/_signin?realm=app.vssps.visualstudio.com&reply_to=https%3A%2F%2Fapp.vssps.visualstudio.com%2Fprofile%2Fview&redirect=1&context=eyJodCI6MywiaGlkIjoiYTVjYTM1ZWItMTQ4ZS00Y2NkLWJiYjMtZDMxNTc2ZDc1OTU4IiwicXMiOnt9LCJyciI6IiIsInZoIjoiIiwiY3YiOiIiLCJjcyI6IiJ90#ctx=eyJTaWduSW5Db29raWVEb21haW5zIjpbImh0dHBzOi8vbG9naW4ubWljcm9zb2Z0b25saW5lLmNvbSIsImh0dHBzOi8vbG9naW4ubWljcm9zb2Z0b25saW5lLmNvbSJdfQ2). Learn more about this new step in our [Azure DevOps OAuth guide](/azure/devops/integrate/get-started/authentication/azure-devops-oauth?view=azure-devops&preserve-view=true).

release-notes/2024/includes/general/sprint-246-update.md

@@ -14,9 +14,9 @@ In response to your feedback in the  [developer community](https://developercomm
 
 ### Microsoft Entra profile information (preview)
 
-We’re excited to introduce the integration of Microsoft Entra profile information in Azure DevOps, removing the need for separate profile updates. To try the preview, enable Microsoft Entra profile information in [Preview Features](/azure/devops/project/navigation/preview-features?view=azure-devops).
+We’re excited to introduce the integration of Microsoft Entra profile information in Azure DevOps, removing the need for separate profile updates. To try the preview, enable Microsoft Entra profile information in [Preview Features](/azure/devops/project/navigation/preview-features?view=azure-devops&preserve-view=true).
 
 > [!div class="mx-imgBorder"]
 > ![Screenshot of turn on Microsoft Entra Profile Information.](../../media/246-general-02.png "Screenshot of turn on Microsoft Entra Profile Information")
 
-Once enabled, your [profile settings](/azure/devops/organizations/settings/set-your-preferences?view=azure-devops#set-preferences) are read-only and automatically populated from Microsoft Entra. To revert to your previous settings or provide feedback, turn off the preview and share your comments.
+Once enabled, your [profile settings](/azure/devops/organizations/settings/set-your-preferences?view=azure-devops&preserve-view=true#set-preferences) are read-only and automatically populated from Microsoft Entra. To revert to your previous settings or provide feedback, turn off the preview and share your comments.

release-notes/2024/includes/ghazdo/sprint-234-update.md

@@ -30,7 +30,7 @@ New alert severities now exist for alert results from the CodeQL `quality` queri
 
 ### Linked Azure subscription required for GitHub Advanced Security for Azure DevOps enablement
 
-If you previously enabled Advanced Security for repositories in an Azure DevOps organization without a linked Azure subscription, you may notice Advanced Security automatically disabled itself on those repositories. To re-enable Advanced Security, add an associated Azure subscription to the organization. For more information on how to add or change your subscription, see [Change Azure subscription](/azure/devops/organizations/billing/change-azure-subscription?view=azure-devopsthe&preserve-view=true).
+If you previously enabled Advanced Security for repositories in an Azure DevOps organization without a linked Azure subscription, you may notice Advanced Security automatically disabled itself on those repositories. To re-enable Advanced Security, add an associated Azure subscription to the organization. For more information on how to add or change your subscription, see [Change Azure subscription](/azure/devops/organizations/billing/change-azure-subscription?view=azure-devops&preserve-view=true).
 
 ### Advanced Security API updates 
 

release-notes/2024/includes/ghazdo/sprint-238-update.md

@@ -16,4 +16,4 @@ The security overview risk page now links directly to each repository's individu
 
 The **AdvancedSecurity-Publish@1** task allows you to easily retrieve results from third-party providers, enhancing the integration with GitHub advanced security for AzureDevOps. These providers can include both open-source and commercial security analysis pipeline tasks that generate results in the conforming SARIF format. By leveraging this, you can now view the results within the Advanced Security Code Scanning alerts hub, providing a unified view of code security alerts from currently supported analysis tools directly within Azure DevOps. This integration supports SARIF 2.1, offering you a comprehensive overview of their security posture.
 
-For detailed instructions on configuring code scanning in GitHub Advanced Security with Azure DevOps, see [Set up code scanning](/azure/devops/repos/security/configure-github-advanced-security-features?view=azure-devops&tabs=yaml#set-up-code-scanning). 
+For detailed instructions on configuring code scanning in GitHub Advanced Security with Azure DevOps, see [Set up code scanning](/azure/devops/repos/security/configure-github-advanced-security-features?view=azure-devops&tabs=yaml#set-up-code-scanning&preserve-view=true). 

release-notes/2024/includes/ghazdo/sprint-243-update.md

@@ -21,7 +21,7 @@ However, CodeQL, the static analysis engine behind GitHub Advanced Security for
 
 For all compiled languages, the default build mode is **"manual."** However, for C# and Java, you can change the build mode to **"none."** 
 
-You can configure the build mode during the AdvancedSecurity-Codeql-Init@1 setup. For detailed instructions on configuring code scanning in GitHub Advanced Security with Azure DevOps, see Set up [code scanning](/azure/devops/repos/security/configure-github-advanced-security-features?view=azure-devops&tabs=yaml#set-up-code-scanning)
+You can configure the build mode during the AdvancedSecurity-Codeql-Init@1 setup. For detailed instructions on configuring code scanning in GitHub Advanced Security with Azure DevOps, see Set up [code scanning](/azure/devops/repos/security/configure-github-advanced-security-features?view=azure-devops&tabs=yaml#set-up-code-scanning&preserve-view=true)
 
 Consideration:
 - If **"none"** is selected and a language other than supported complied languages C# or Java, the pipeline task may not work as expected. 

release-notes/2025/includes/general/sprint-251-update.md

@@ -14,7 +14,7 @@ The **Generate Git Credentials** button has been removed from the **Clone Reposi
 > [![Screenshot of deactivated generate git credentials button.](../../media/251-general-01.png "Screenshot of deactivated generate git credentials button")](../../media/251-general-01.png#lightbox)
 
 
-To enhance security and streamline authentication, consider using Entra tokens for ad-hoc Git clone operations in Repos and Wiki. Documentation is available to help you configure authentication via the  [command line](/azure/devops/repos/git/auth-overview?view=azure-devops&tabs=Windows) or within the [Git Credential Manager](/azure/devops/repos/git/set-up-credential-managers?view=azure-devops) (GCM).
+To enhance security and streamline authentication, consider using Entra tokens for ad-hoc Git clone operations in Repos and Wiki. Documentation is available to help you configure authentication via the  [command line](/azure/devops/repos/git/auth-overview?view=azure-devops&tabs=Windows&preserve-view=true) or within the [Git Credential Manager](/azure/devops/repos/git/set-up-credential-managers?view=azure-devop&preserve-view=trues) (GCM).
 
 While PATs remain available for Git operations, they must now be manually created with the appropriate `vso.code` scope from the Personal Access Token page. Ensure that PATs are only active as long as needed and revoked when no longer in use. As a best practice, store PATs securely in a secret management service such as Azure Key Vault (AKV) and rotate them regularly.