more fixes

Author: chcomley

docs/pipelines/process/access-tokens.md

@@ -3,7 +3,6 @@ title: Understand job access tokens
 description: Access repositories, artifacts and other resources from pipelines
 ms.topic: reference
 ms.date: 06/30/2022
-monikerRange: '<= azure-devops'
 ---
 
 # Access repositories, artifacts, and other resources

docs/pipelines/process/variables.md

@@ -6,8 +6,6 @@ ms.topic: conceptual
 ms.assetid: 4751564b-aa99-41a0-97e9-3ef0c0fce32a
 ms.date: 10/03/2024
 ai-usage: ai-assisted
-
-monikerRange: '<= azure-devops'
 ---
 
 # Define variables

docs/test/run-automated-tests-from-test-hub.md

@@ -7,7 +7,6 @@ ms.custom: UpdateFrequency3
 ms.topic: conceptual 
 ms.author: jeom
 author: wisdeom
-monikerRange: '<= azure-devops'
 ms.date: 09/14/2021
 ms.update-cycle: 1095-days
 ---

release-notes/2025/testplans/sprint-258-update.md

@@ -12,6 +12,4 @@ ms.date: 6/30/2025
 
 [!INCLUDE [sprint-258-update-links](../includes/testplans/sprint-258-update-links.md)]
 
-[!INCLUDE [sprint-258-update](../includes/testplans/sprint-258-update.md)]
-
 [!INCLUDE [nextsteps](../includes/nextsteps.md)]

release-notes/roadmap/2025/new-service-connection.md

@@ -12,7 +12,7 @@ hide_comments: true
 
 # PAT-less authentication from pipeline tasks to Azure DevOps APIs
 
-Tasks in a pipeline use either a [job access token](../../../docs/pipelines/process/access-tokens.md), available via the built-in variable [System.AccessToken](../../../docs/pipelines/process/variables.md#system-variables), or a PAT to access Azure DevOps resources. For instance, a “checkout” task uses this token to authenticate to the repository. Similarly, a PowerShell script can use this token to access Azure DevOps REST APIs. However, the permissions of this token are based on the Project Build Service identity, meaning all job access tokens in a project have identical permissions. This grants excessive access across all pipelines within the project.
+Tasks in a pipelines use either a job access token, available via the built-in variable `System.AccessToken`, or a PAT to access Azure DevOps resources. For instance, a “checkout” task uses this token to authenticate to the repository. Similarly, a PowerShell script can use this token to access Azure DevOps REST APIs. However, the permissions of this token are based on the Project Build Service identity, meaning all job access tokens in a project have identical permissions. This grants excessive access across all pipelines within the project.
 
 Using PATs to access Azure DevOps resources is common, particularly when a task needs to access those resources across organization boundaries. For instance, a Nuget Authenticate task uses a PAT token to authenticate to a feed in another organization. PATs are an anti-pattern for security as they tend to be created with broad permissions and are held for a long time thereby increasing the risk of exfiltration.