update service-endpoints.md

Author: cebundy

docs/organizations/settings/about-settings.md

@@ -500,7 +500,7 @@ From the administrative **Project settings** page, you can configure settings av
       **Service connections**
    :::column-end:::
    :::column span="2":::
-      - [Manage service connections in Azure Pipelines](../../pipelines/library/service-endpoints.md#project-level-permissions)
+      - [Manage service connections in Azure Pipelines](../../pipelines/policies/permissions.md#set-service-connection-project-permissions)
    :::column-end:::
    :::column span="2":::
       For more information, see a [list of common service connection types](../../pipelines/library/service-endpoints.md#common-service-connection-types).

docs/pipelines/library/connect-to-azure.md

@@ -175,7 +175,7 @@ To deploy to a specific Azure resource, the task needs more data about that reso
 You can quickly convert an existing Azure Resource Manager service connection to use workload identity federation for authentication instead of a service principal. You can use the service connection conversion tool in Azure DevOps if your service connection meets these requirements:
 
 * Azure DevOps originally created the service connection. If you manually create your service connection, you can't convert the service connection by using the service connection conversion tool because Azure DevOps doesn't have permissions to modify its own credentials.
-* Only one project uses the service connection. You can't convert [cross-project service connections](service-endpoints.md#project-permissions---cross-project-sharing-of-service-connections).
+* Only one project uses the service connection. You can't convert [cross-project service connections](../policies/permissions.md#set-service-connection-project-permissions).
 
 To convert a service connection: