bookmark fix

Author: chcomley

docs/integrate/get-started/authentication/azure-devops-oauth.md

@@ -23,7 +23,7 @@ Azure DevOps is an identity provider for OAuth 2.0 apps. Our implementation of O
 
 1. Go to `https://app.vsaex.visualstudio.com/app/register` to register your app.
 
-2. Select the [scopes](./oauth.md#scopes) that your application needs, and then use the same scopes when you [authorize your app](#2-authorize-your-app). If you registered your app using the preview APIs, re-register because the scopes that you used are now deprecated.
+2. Select the [scopes](./oauth.md#available-scopes) that your application needs, and then use the same scopes when you [authorize your app](#2-authorize-your-app). If you registered your app using the preview APIs, re-register because the scopes that you used are now deprecated.
 
 3. Select **Create application**.
 
@@ -61,7 +61,7 @@ Parameter     | Type   | Notes
 client_id     | GUID   | The ID assigned to your app when it was registered.
 response_type | string | `Assertion`
 state         | string | Can be any value. Typically a generated string value that correlates the callback with its associated authorization request.
-scope         | string | Scopes registered with the app. Space separated. See [available scopes](oauth.md#scopes).
+scope         | string | Scopes registered with the app. Space separated. See [available scopes](oauth.md#available-scopes).
 redirect_uri  | URL    | Callback URL for your app. **Must exactly match the URL registered with the app**.
 
 2. Add a link or button to your site that takes the user to the Azure DevOps Services authorization endpoint:
@@ -216,7 +216,7 @@ You can find a C# sample that implements OAuth to call Azure DevOps Services RES
 
 ## Regenerate client secret
 
-Application secrets regularly expire every 60 days (as of March 2025). You may have two secrets at any time. Continue to create and use access tokens and refresh tokens by rotating your soon-to-expire app secret with a new application secret. This can be done on the app's registration page on the [Visual Studio profile](https://aex.dev.azure.com/me) or through the [Registration Secret APIs](/rest/api/azure/devops/delegatedauth/registration-secret). To use the APIs, you must use an [Entra access token](entra-oauth.md) with the `vso.tokens` [scope](oauth.md#scopes).
+Application secrets regularly expire every 60 days (as of March 2025). You may have two secrets at any time. Continue to create and use access tokens and refresh tokens by rotating your soon-to-expire app secret with a new application secret. This can be done on the app's registration page on the [Visual Studio profile](https://aex.dev.azure.com/me) or through the [Registration Secret APIs](/rest/api/azure/devops/delegatedauth/registration-secret). To use the APIs, you must use an [Entra access token](entra-oauth.md) with the `vso.tokens` [scope](oauth.md#available-scopes).
 
 1. Create a secondary secret by selecting **"Generate Secret"** for "Secret 2". (Use the [Create Registration Secret API](/rest/api/azure/devops/delegatedauth/registration-secret/create).)
 

docs/integrate/get-started/authentication/entra-oauth.md

@@ -22,7 +22,7 @@ This differs from apps that perform actions on-behalf-of themselves. For that, y
 
 * [Register an application with the Microsoft identity platform](/entra/identity-platform/quickstart-register-app)
 * [Add permissions for access to Microsoft Graph](/entra/identity-platform/quickstart-configure-app-access-web-apis#add-permissions-to-access-microsoft-graph): Learn how to add delegated permissions from an Azure resource. Instead of Microsoft Graph, select `Azure DevOps` from the list of resources.
-* [Read about scopes and permissions in the Microsoft identity platform](/entra/identity-platform/scopes-oidc): Understand the `.default` scope. See the scopes available for Azure DevOps in [our list of scopes](oauth.md#scopes).
+* [Read about scopes and permissions in the Microsoft identity platform](/entra/identity-platform/scopes-oidc): Understand the `.default` scope. See the scopes available for Azure DevOps in [our list of scopes](oauth.md#available-scopes).
 * [Request permissions through consent](/entra/identity-platform/consent-types-developer)
 * [Use authentication libraries](/entra/identity-platform/reference-v2-libraries) and [code samples](/entra/identity-platform/sample-v2-code?tabs=apptype)
 * [Explore support and help options for developers](/entra/identity-platform/developer-support-help-options)

docs/organizations/accounts/use-personal-access-tokens-to-authenticate.md

@@ -47,7 +47,7 @@ When you use Microsoft tools, your Microsoft account (MSA) or Microsoft Entra ID
 
    :::image type="content" source="media/pats/create-new-pat.png" alt-text="Screenshot showing entry of basic token information.":::
 
-5. Select the [scopes](../../integrate/get-started/authentication/oauth.md#scopes)
+5. Select the [scopes](../../integrate/get-started/authentication/oauth.md#available-scopes)
    for this token to authorize for *your specific tasks*.
 
       For example, to create a token for a [build and release agent](../../pipelines/agents/agents.md) to authenticate to Azure DevOps, set the token's scope to **Agent Pools (Read & manage)**. To read audit log events and manage or delete streams, select **Read Audit Log**, and then select **Create**.
@@ -132,7 +132,7 @@ Do the following steps to:
 
 - Regenerate a PAT to create a new token, which invalidates the previous one.
 - Extend a PAT to increase its validity period.
-- Alter the [scope](../../integrate/get-started/authentication/oauth.md#scopes) of a PAT to change its permissions.
+- Alter the [scope](../../integrate/get-started/authentication/oauth.md#available-scopes) of a PAT to change its permissions.
 
 1. From your home page, open user settings :::image type="icon" source="../../media/icons/user-settings-gear.png" border="false"::: and select **Personal access tokens**.
 

docs/repos/git/create-pr-status-server-with-azure-functions.md

@@ -140,7 +140,7 @@ Now that your server can receive service hook events when new PRs are created, u
 
 Update the code of your Azure function, similar to the following example.
 
-Make sure to update the code with your organization name, project name, repository name, and Microsoft Entra ID token. In order to have permission to change PR status, the token requires [vso.code_status](../../integrate/get-started/authentication/oauth.md#scopes) scope, which you can obtain through Microsoft Entra authentication.
+Make sure to update the code with your organization name, project name, repository name, and Microsoft Entra ID token. In order to have permission to change PR status, the token requires [vso.code_status](../../integrate/get-started/authentication/oauth.md#available-scopes) scope, which you can obtain through Microsoft Entra authentication.
 
 >[!Important]
 >This sample code stores the token in code, simplifying the sample. It is recommended to store secrets in Azure Key Vault and retrieve them from there using managed identity for enhanced security.

docs/repos/git/go-install.md

@@ -104,7 +104,7 @@ The `<user>` part can be any nonempty string; we suggest using `entra` or your u
 
 #### Personal Access Tokens (alternative)
 
-If you prefer to use PATs, create a PAT as described in [Authenticate access with personal access tokens](../../organizations/accounts/use-personal-access-tokens-to-authenticate.md). This PAT requires only the **Code (read)** [scope](../../integrate/get-started/authentication/oauth.md#scopes).
+If you prefer to use PATs, create a PAT as described in [Authenticate access with personal access tokens](../../organizations/accounts/use-personal-access-tokens-to-authenticate.md). This PAT requires only the **Code (read)** [scope](../../integrate/get-started/authentication/oauth.md#available-scopes).
 
 After you create the PAT, add this entry to your `.gitconfig` file: