build warning fixes

Author: chcomley

docs/integrate/get-started/authentication/service-principal-managed-identity.md

@@ -331,7 +331,7 @@ A: Service principals and managed identities offer significant security advantag
 - **Conditional access**: Apply policies based on location, device, and risk factors
 - **No service accounts**: Eliminates dependency on individual user accounts for automation
 
-For migration examples, see [Replace PATs with Microsoft Entra tokens](entra.md#replace-pats-with-microsoft-entra-tokens).
+For migration examples, see [Replace PATs with Microsoft Entra tokens](entra.md#migration-from-legacy-authentication).
 
 #### Q: What are the rate limits on service principals and managed identities?
 

docs/integrate/get-started/client-libraries/samples.md

@@ -29,7 +29,7 @@ Learn how to extend and integrate with Azure DevOps using the [.NET client libra
 - **Azure-hosted applications**: Use [managed identities](../authentication/service-principal-managed-identity.md)
 - **CI/CD pipelines**: Use [service principals](../authentication/service-principal-managed-identity.md) 
 - **Interactive applications**: Use [Microsoft Entra authentication](../authentication/entra.md)
-- **Legacy scenarios only**: Use [personal access tokens](../authentication/authentication-guidance.md#personal-access-tokens-pats)
+- **Legacy scenarios only**: Use [personal access tokens](../authentication/authentication-guidance.md)
 
 > [!IMPORTANT]
 > This article shows multiple authentication methods for different scenarios. Choose the most appropriate method based on your deployment environment and security requirements.
@@ -525,7 +525,7 @@ private static bool IsTransientError(Exception ex)
 - Deploy incrementally to production
 - Monitor for authentication issues
 
-For detailed migration guidance, see [Replace PATs with Microsoft Entra tokens](../authentication/entra.md#replace-pats-with-microsoft-entra-tokens).
+For detailed migration guidance, see [Replace PATs with Microsoft Entra tokens](../authentication/entra.md#migration-from-legacy-authentication).
 
 ## Related resources
 

docs/integrate/index.md

@@ -49,12 +49,12 @@ Azure DevOps integration enables you to:
 **Choose the right authentication method:**
 
 **✅ Recommended for production:**
-- **[Managed Identity](./get-started/authentication/authentication-guidance.md#managed-identity)** - For Azure-hosted applications (most secure)
-- **[Service Principal](./get-started/authentication/authentication-guidance.md#service-principal)** - For CI/CD pipelines and automated services
+- **[Managed Identity](./get-started/authentication/service-principal-managed-identity.md)** - For Azure-hosted applications (most secure)
+- **[Service Principal](./get-started/authentication/service-principal-managed-identity.md)** - For CI/CD pipelines and automated services
 - **[Microsoft Entra ID](./get-started/authentication/entra.md)** - For user-facing applications requiring OAuth flows
 
 **⚡ Quick development:**
-- **[Personal Access Tokens (PATs)](./get-started/authentication/authentication-guidance.md#personal-access-tokens)** - For testing and personal automation only
+- **[Personal Access Tokens (PATs)](./get-started/authentication/authentication-guidance.md)** - For testing and personal automation only
 
 **❌ Avoid for production:**
 - Username/password authentication (deprecated)