Fix links

ecfan · ecfan · commit 6c0f00f81cf7 · 2024-08-06T14:59:23.000-07:00
diff --git a/articles/logic-apps/create-custom-built-in-connector-standard.md b/articles/logic-apps/create-custom-built-in-connector-standard.md
@@ -113,11 +113,11 @@ The following sections describe the methods that the example connector implement
 >
 > When you have sensitive information, such as connection strings that include usernames and passwords, 
 > make sure to use the most secure authentication flow available. For example, Microsoft recommends that 
-> you authenticate access to Azure resources with a [managed identity](entra/identity/managed-identities-azure-resources/overview) 
+> you authenticate access to Azure resources with a [managed identity](/entra/identity/managed-identities-azure-resources/overview) 
 > when support is available, and assign a role that has the least required privilege.
 >
 > If this capability is unavailable, make sure to secure connection strings through other measures, such as 
-> [Azure Key Vault](../key-vault/general/overview), which you can use with [app settings](edit-app-settings-host-settings.md). 
+> [Azure Key Vault](../key-vault/general/overview.md), which you can use with [app settings](edit-app-settings-host-settings.md). 
 > You can then [directly reference secure strings](../app-service/app-service-key-vault-references.md), such as connection 
 > strings and keys. Similar to ARM templates, where you can define environment variables at deployment time, you can define 
 > app settings within your [logic app workflow definition](/azure/templates/microsoft.logic/workflows). 
diff --git a/articles/logic-apps/create-parameters-workflows.md b/articles/logic-apps/create-parameters-workflows.md
@@ -45,11 +45,11 @@ In single-tenant Standard logic app workflows, you can work with environment var
 > When you have sensitive information, such as connection strings that include usernames and passwords, 
 > make sure to use the most secure authentication flow available. For example, in Standard logic app workflows, 
 > secure data types, such as `securestring` and `secureobject`, aren't supported. Microsoft recommends that you 
-> authenticate access to Azure resources with a [managed identity](entra/identity/managed-identities-azure-resources/overview) 
+> authenticate access to Azure resources with a [managed identity](/entra/identity/managed-identities-azure-resources/overview) 
 > when possible, and assign a role that has the least privilege necessary.
 >
 > If this capability is unavailable, make sure to secure connection strings through other measures, such as 
-> [Azure Key Vault](../key-vault/general/overview), which you can use with [app settings](edit-app-settings-host-settings.md). 
+> [Azure Key Vault](../key-vault/general/overview.md), which you can use with [app settings](edit-app-settings-host-settings.md). 
 > You can then [directly reference secure strings](../app-service/app-service-key-vault-references.md), such as connection 
 > strings and keys. Similar to ARM templates, where you can define environment variables at deployment time, you can define 
 > app settings within your [logic app workflow definition](/azure/templates/microsoft.logic/workflows). 
diff --git a/articles/logic-apps/custom-connector-overview.md b/articles/logic-apps/custom-connector-overview.md
@@ -118,11 +118,11 @@ The following sections provide more information about the methods that your conn
 >
 > When you have sensitive information, such as connection strings that include usernames and passwords, 
 > make sure to use the most secure authentication flow available. For example, Microsoft recommends that 
-> you authenticate access to Azure resources with a [managed identity](entra/identity/managed-identities-azure-resources/overview) 
+> you authenticate access to Azure resources with a [managed identity](/entra/identity/managed-identities-azure-resources/overview) 
 > when support is available, and assign a role that has the least required privilege.
 >
 > If this capability is unavailable, make sure to secure connection strings through other measures, such as 
-> [Azure Key Vault](../key-vault/general/overview), which you can use with [app settings](edit-app-settings-host-settings.md). 
+> [Azure Key Vault](../key-vault/general/overview.md), which you can use with [app settings](edit-app-settings-host-settings.md). 
 > You can then [directly reference secure strings](../app-service/app-service-key-vault-references.md), such as connection 
 > strings and keys. Similar to ARM templates, where you can define environment variables at deployment time, you can define 
 > app settings within your [logic app workflow definition](/azure/templates/microsoft.logic/workflows). 
diff --git a/articles/logic-apps/devops-deployment-single-tenant-azure-logic-apps.md b/articles/logic-apps/devops-deployment-single-tenant-azure-logic-apps.md
@@ -101,11 +101,11 @@ When you use a built-in operation for a service such as Azure Service Bus or Azu
 >
 > When you have sensitive information, such as connection strings that include usernames and passwords, 
 > make sure to use the most secure authentication flow available. For example, Microsoft recommends that 
-> you authenticate access to Azure resources with a [managed identity](entra/identity/managed-identities-azure-resources/overview) 
+> you authenticate access to Azure resources with a [managed identity](/entra/identity/managed-identities-azure-resources/overview) 
 > when support is available, and assign a role that has the least required privilege.
 >
 > If this capability is unavailable, make sure to secure connection strings through other measures, such as 
-> [Azure Key Vault](../key-vault/general/overview), which you can use with [app settings](edit-app-settings-host-settings.md). 
+> [Azure Key Vault](../key-vault/general/overview.md), which you can use with [app settings](edit-app-settings-host-settings.md). 
 > You can then [directly reference secure strings](../app-service/app-service-key-vault-references.md), such as connection 
 > strings and keys. Similar to ARM templates, where you can define environment variables at deployment time, you can define 
 > app settings within your [logic app workflow definition](/azure/templates/microsoft.logic/workflows). 
diff --git a/articles/logic-apps/logic-apps-diagnosing-failures.md b/articles/logic-apps/logic-apps-diagnosing-failures.md
@@ -176,11 +176,11 @@ The following list includes possible causes for these errors and steps to help t
   > When you have sensitive information, such as connection strings that include usernames and passwords, 
   > make sure to use the most secure authentication flow available. For example, in Standard logic app workflows, 
   > secure data types, such as `securestring` and `secureobject`, aren't supported. Microsoft recommends that you 
-  > authenticate access to Azure resources with a [managed identity](entra/identity/managed-identities-azure-resources/overview) 
+  > authenticate access to Azure resources with a [managed identity](/entra/identity/managed-identities-azure-resources/overview) 
   > when possible, and assign a role that has the least privilege necessary.
   >
   > If this capability is unavailable, make sure to secure connection strings through other measures, such as 
- > [Azure Key Vault](../key-vault/general/overview), which you can use with [app settings](edit-app-settings-host-settings.md). 
+ > [Azure Key Vault](../key-vault/general/overview.md), which you can use with [app settings](edit-app-settings-host-settings.md). 
   > You can then [directly reference secure strings](../app-service/app-service-key-vault-references.md), such as connection 
   > strings and keys. Similar to ARM templates, where you can define environment variables at deployment time, you can define 
   > app settings within your [logic app workflow definition](/azure/templates/microsoft.logic/workflows). 
diff --git a/articles/logic-apps/logic-apps-limits-and-config.md b/articles/logic-apps/logic-apps-limits-and-config.md
@@ -271,11 +271,11 @@ The following recommendations apply to scaling Standard logic app workflows:
      > When you have sensitive information, such as connection strings that include usernames and passwords, 
      > make sure to use the most secure authentication flow available. For example, in Standard logic app workflows, 
      > secure data types, such as `securestring` and `secureobject`, aren't supported. Microsoft recommends that you 
-     > authenticate access to Azure resources with a [managed identity](entra/identity/managed-identities-azure-resources/overview) 
+     > authenticate access to Azure resources with a [managed identity](/entra/identity/managed-identities-azure-resources/overview) 
      > when possible, and assign a role that has the least privilege necessary.
      >
      > If this capability is unavailable, make sure to secure connection strings through other measures, such as 
-     > [Azure Key Vault](../key-vault/general/overview), which you can use with [app settings](edit-app-settings-host-settings.md). 
+     > [Azure Key Vault](../key-vault/general/overview.md), which you can use with [app settings](edit-app-settings-host-settings.md). 
      > You can then [directly reference secure strings](../app-service/app-service-key-vault-references.md), such as connection 
      > strings and keys. Similar to ARM templates, where you can define environment variables at deployment time, you can define 
      > app settings within your [logic app workflow definition](/azure/templates/microsoft.logic/workflows). 
diff --git a/articles/logic-apps/manage-logic-apps-with-azure-portal.md b/articles/logic-apps/manage-logic-apps-with-azure-portal.md
@@ -373,11 +373,11 @@ Before you try to recover your deleted logic app, review the following considera
    > When you have sensitive information, such as connection strings that include usernames and passwords, 
    > make sure to use the most secure authentication flow available. For example, in Standard logic app workflows, 
    > secure data types, such as `securestring` and `secureobject`, aren't supported. Microsoft recommends that you 
-   > authenticate access to Azure resources with a [managed identity](entra/identity/managed-identities-azure-resources/overview) 
+   > authenticate access to Azure resources with a [managed identity](/entra/identity/managed-identities-azure-resources/overview) 
    > when possible, and assign a role that has the least privilege necessary.
    >
    > If this capability is unavailable, make sure to secure connection strings through other measures, such as 
-   > [Azure Key Vault](../key-vault/general/overview), which you can use with [app settings](edit-app-settings-host-settings.md). 
+   > [Azure Key Vault](../key-vault/general/overview.md), which you can use with [app settings](edit-app-settings-host-settings.md). 
    > You can then [directly reference secure strings](../app-service/app-service-key-vault-references.md), such as connection 
    > strings and keys. Similar to ARM templates, where you can define environment variables at deployment time, you can define 
    > app settings within your [logic app workflow definition](/azure/templates/microsoft.logic/workflows). 
diff --git a/articles/logic-apps/set-up-sql-db-storage-single-tenant-standard-workflows.md b/articles/logic-apps/set-up-sql-db-storage-single-tenant-standard-workflows.md
@@ -112,11 +112,11 @@ The following table describes some reasons why you might want to use SQL:
    >
    > When you have sensitive information, such as connection strings that include usernames and passwords, 
    > make sure to use the most secure authentication flow available. Microsoft recommends that you 
-   > authenticate access to Azure resources with a [managed identity](entra/identity/managed-identities-azure-resources/overview) 
+   > authenticate access to Azure resources with a [managed identity](/entra/identity/managed-identities-azure-resources/overview) 
    > when possible, and assign a role that has the least privilege necessary.
    >
    > If this capability is unavailable, make sure to secure connection strings through other measures, such as 
-   > [Azure Key Vault](../key-vault/general/overview), which you can use with [app settings](edit-app-settings-host-settings.md). 
+   > [Azure Key Vault](../key-vault/general/overview.md), which you can use with [app settings](edit-app-settings-host-settings.md). 
    > You can then [directly reference secure strings](../app-service/app-service-key-vault-references.md), such as connection 
    > strings and keys. Similar to ARM templates, where you can define environment variables at deployment time, you can define 
    > app settings within your [logic app workflow definition](/azure/templates/microsoft.logic/workflows). 

Original file line number	Diff line number	Diff line change
`@@ -113,11 +113,11 @@ The following sections describe the methods that the example connector implement`
`113`	`113`	`>`
`114`	`114`	`> When you have sensitive information, such as connection strings that include usernames and passwords,`
`115`	`115`	`> make sure to use the most secure authentication flow available. For example, Microsoft recommends that`
`116`		`-> you authenticate access to Azure resources with a [managed identity](entra/identity/managed-identities-azure-resources/overview)`
	`116`	`+> you authenticate access to Azure resources with a [managed identity](/entra/identity/managed-identities-azure-resources/overview)`
`117`	`117`	`> when support is available, and assign a role that has the least required privilege.`
`118`	`118`	`>`
`119`	`119`	`> If this capability is unavailable, make sure to secure connection strings through other measures, such as`
`120`		`-> [Azure Key Vault](../key-vault/general/overview), which you can use with [app settings](edit-app-settings-host-settings.md).`
	`120`	`+> [Azure Key Vault](../key-vault/general/overview.md), which you can use with [app settings](edit-app-settings-host-settings.md).`
`121`	`121`	`> You can then [directly reference secure strings](../app-service/app-service-key-vault-references.md), such as connection`
`122`	`122`	`> strings and keys. Similar to ARM templates, where you can define environment variables at deployment time, you can define`
`123`	`123`	`> app settings within your [logic app workflow definition](/azure/templates/microsoft.logic/workflows).`
Original file line number	Diff line number	Diff line change
`@@ -118,11 +118,11 @@ The following sections provide more information about the methods that your conn`
`118`	`118`	`>`
`119`	`119`	`> When you have sensitive information, such as connection strings that include usernames and passwords,`
`120`	`120`	`> make sure to use the most secure authentication flow available. For example, Microsoft recommends that`
`121`		`-> you authenticate access to Azure resources with a [managed identity](entra/identity/managed-identities-azure-resources/overview)`
	`121`	`+> you authenticate access to Azure resources with a [managed identity](/entra/identity/managed-identities-azure-resources/overview)`
`122`	`122`	`> when support is available, and assign a role that has the least required privilege.`
`123`	`123`	`>`
`124`	`124`	`> If this capability is unavailable, make sure to secure connection strings through other measures, such as`
`125`		`-> [Azure Key Vault](../key-vault/general/overview), which you can use with [app settings](edit-app-settings-host-settings.md).`
	`125`	`+> [Azure Key Vault](../key-vault/general/overview.md), which you can use with [app settings](edit-app-settings-host-settings.md).`
`126`	`126`	`> You can then [directly reference secure strings](../app-service/app-service-key-vault-references.md), such as connection`
`127`	`127`	`> strings and keys. Similar to ARM templates, where you can define environment variables at deployment time, you can define`
`128`	`128`	`> app settings within your [logic app workflow definition](/azure/templates/microsoft.logic/workflows).`
Original file line number	Diff line number	Diff line change
`@@ -101,11 +101,11 @@ When you use a built-in operation for a service such as Azure Service Bus or Azu`
`101`	`101`	`>`
`102`	`102`	`> When you have sensitive information, such as connection strings that include usernames and passwords,`
`103`	`103`	`> make sure to use the most secure authentication flow available. For example, Microsoft recommends that`
`104`		`-> you authenticate access to Azure resources with a [managed identity](entra/identity/managed-identities-azure-resources/overview)`
	`104`	`+> you authenticate access to Azure resources with a [managed identity](/entra/identity/managed-identities-azure-resources/overview)`
`105`	`105`	`> when support is available, and assign a role that has the least required privilege.`
`106`	`106`	`>`
`107`	`107`	`> If this capability is unavailable, make sure to secure connection strings through other measures, such as`
`108`		`-> [Azure Key Vault](../key-vault/general/overview), which you can use with [app settings](edit-app-settings-host-settings.md).`
	`108`	`+> [Azure Key Vault](../key-vault/general/overview.md), which you can use with [app settings](edit-app-settings-host-settings.md).`
`109`	`109`	`> You can then [directly reference secure strings](../app-service/app-service-key-vault-references.md), such as connection`
`110`	`110`	`> strings and keys. Similar to ARM templates, where you can define environment variables at deployment time, you can define`
`111`	`111`	`> app settings within your [logic app workflow definition](/azure/templates/microsoft.logic/workflows).`
Original file line number	Diff line number	Diff line change
`@@ -112,11 +112,11 @@ The following table describes some reasons why you might want to use SQL:`
`112`	`112`	`>`
`113`	`113`	`> When you have sensitive information, such as connection strings that include usernames and passwords,`
`114`	`114`	`> make sure to use the most secure authentication flow available. Microsoft recommends that you`
`115`		`- > authenticate access to Azure resources with a [managed identity](entra/identity/managed-identities-azure-resources/overview)`
	`115`	`+ > authenticate access to Azure resources with a [managed identity](/entra/identity/managed-identities-azure-resources/overview)`
`116`	`116`	`> when possible, and assign a role that has the least privilege necessary.`
`117`	`117`	`>`
`118`	`118`	`> If this capability is unavailable, make sure to secure connection strings through other measures, such as`
`119`		`- > [Azure Key Vault](../key-vault/general/overview), which you can use with [app settings](edit-app-settings-host-settings.md).`
	`119`	`+ > [Azure Key Vault](../key-vault/general/overview.md), which you can use with [app settings](edit-app-settings-host-settings.md).`
`120`	`120`	`> You can then [directly reference secure strings](../app-service/app-service-key-vault-references.md), such as connection`
`121`	`121`	`> strings and keys. Similar to ARM templates, where you can define environment variables at deployment time, you can define`
`122`	`122`	`> app settings within your [logic app workflow definition](/azure/templates/microsoft.logic/workflows).`