Fix build link errors

Author: ggailey777

articles/azure-functions/configure-networking-how-to.md

@@ -3,7 +3,7 @@ title: How to use a secured storage account with Azure Functions
 description: Learn how to use a secured storage account in a virtual network as the default storage account for a function app in Azure Functions.
 ms-service: azure-functions
 ms.topic: how-to
-ms.date: 12/04/2024
+ms.date: 01/03/2025
 ms.custom: template-how-to, build-2024, ignite-2024
 # Customer intent: As a developer, I want to understand how to use a secured storage account in a virtual network as the default storage account for my function app, so that my function app can be secure.
 ---
@@ -18,7 +18,7 @@ When you create a function app, you either create a new storage account or link
 
 + To create a function app that uses an existing secured storage account as the default storage account, you must create your app either in the [Azure portal](https://portal.azure.com) or by using [ARM template](functions-infrastructure-as-code.md?tabs=json&pivots=premium-plan#secured-deployments) or [Bicep](functions-infrastructure-as-code.md?tabs=bicep&pivots=premium-plan#secured-deployments) deployments.
 + When using a secured storage account with a dynamic scale plan, you should host your functions in the [Flex Consumption plan](./flex-consumption-plan.md). This plan supports both secured storage accounts and managed identity-based connections to storage, which is the most secure connection option.    
-+ All tiers of both the [Dedicated (App Service) plan](./dedicated-plan.md) and the [Elastic Premium plan](./functions-premium-plan.md) also support secure storage accounts. However, there are trade-offs when using managed identities to connect from a Premium plan app. For more information, see <!---<<link here>>--->. 
++ All tiers of both the [Dedicated (App Service) plan](./dedicated-plan.md) and the [Elastic Premium plan](./functions-premium-plan.md) also support secure storage accounts. However, there are trade-offs when using managed identities to connect from a Premium plan app. For more information, see [Create an app without Azure Files](storage-considerations.md#create-an-app-without-azure-files). 
 + The [Consumption plan](consumption-plan.md) doesn't support virtual networks, so you can't connect to a secured storage account when running in the Consumption plan. To take advantage of serverless function hosting, you should instead recreate your app to run in Flex Consumption plan.
 + This article currently shows you how to create a function app in a Premium plan that connects to a secured storage account using the storage account connection string. To provide the best protection of storage account credentials, you should instead use managed identities when connecting to a storage account. Instead follow the [Quickstart: Create and deploy functions to Azure Functions using the Azure Developer CLI](create-first-function-azure-developer-cli.md) to create a function app in the Flex Consumption plan that connects to a new secured storage account using managed identities. 
 + For a list of all restrictions on storage accounts, see [Storage account requirements](storage-considerations.md#storage-account-requirements).

articles/azure-functions/functions-bindings-web-pubsub.md

@@ -72,7 +72,7 @@ The Web PubSub extension is part of an [extension bundle], which is specified in
 By default, an application setting named `WebPubSubConnectionString` is used to store your Web PubSub connection string. When you choose to use a different setting name for your connection, you must explicitly set that as the key name in your binding definitions. During local development, you must also add this setting to the `Values` collection in the the [_local.settings.json_ file](./functions-develop-local.md#local-settings-file).
 
 > [!IMPORTANT]
-> A connection string includes the authorization information required for your application to access Azure Web PubSub service. The access key inside the connection string is similar to a root password for your service. For optimal security, your function app should use managed idenities when connecting to the Web PubSub service instead of using a connection string. For more information, see [Authorize a managed identity request by using Microsoft Entra ID](../articles/azure-web-pubsub/howto-authorize-from-managed-identity.md). 
+> A connection string includes the authorization information required for your application to access Azure Web PubSub service. The access key inside the connection string is similar to a root password for your service. For optimal security, your function app should use managed idenities when connecting to the Web PubSub service instead of using a connection string. For more information, see [Authorize a managed identity request by using Microsoft Entra ID](../azure-web-pubsub/howto-authorize-from-managed-identity.md). 
 
 For details on how to configure and use Web PubSub and Azure Functions together, refer to [Tutorial: Create a serverless notification app with Azure Functions and Azure Web PubSub service](../azure-web-pubsub/tutorial-serverless-notification.md).
 

includes/functions-create-container-registry.md

@@ -4,7 +4,7 @@ ms.service: azure-functions
 ms.custom:
   - build-2024
 ms.topic: include
-ms.date: 12/29/2024
+ms.date: 01/03/2025
 ms.author: glenga
 ---
 
@@ -65,7 +65,7 @@ You should be all set.
 ---
 
 >[!IMPORTANT]
->This article currently shows how to connect to the container registry by using shared secret credentials. For the best security, you should instead use only a managed identity-based connection to Azure Container Registry using Microsoft Entra authentication. For more information, see the [Functions developer guide](./functions-reference.md#connections).
+>This article currently shows how to connect to the container registry by using shared secret credentials. For the best security, you should instead use only a managed identity-based connection to Azure Container Registry using Microsoft Entra authentication. For more information, see the [Functions developer guide](../articles/azure-functions/functions-reference.md#connections).
 
 [!INCLUDE [functions-cli-create-venv](functions-cli-create-venv.md)]
 

includes/functions-rabbitmq-managed-identity-note.md

@@ -3,7 +3,7 @@ author: ggailey777
 ms.author: glenga
 ms.service: azure-functions
 ms.topic: include
-ms.date: 12/09/2024
+ms.date: 01/03/2025
 ---
 > [!IMPORTANT]
-> The RabbitMQ binding doesn't support Microsoft Entra authentication and managed identities. You can use Azure Key Vault to centrally managed your RabbitMQ connection strings. To learn more, see [Manage Connections](./manage-connections.md). 
+> The RabbitMQ binding doesn't support Microsoft Entra authentication and managed identities. You can use Azure Key Vault to centrally managed your RabbitMQ connection strings. To learn more, see [Manage Connections](../articles/azure-functions/manage-connections.md). 

includes/functions-rabbitmq-plans-support-note.md

@@ -3,9 +3,9 @@ author: ggailey777
 ms.author: glenga
 ms.service: azure-functions
 ms.topic: include
-ms.date: 12/09/2024
+ms.date: 01/03/2025
 ---
 > [!NOTE]
-> The RabbitMQ bindings are only fully supported on [Elastic Premium](./functions-premium-plan.md) and [Dedicated (App Service)](./dedicated-plan.md) plans. [Flex Consumption](./flex-consumption-plan.md) and [Consumption](./consumption-plan.md) plans aren't yet supported.
+> The RabbitMQ bindings are only fully supported on [Elastic Premium](../articles/azure-functions/functions-premium-plan.md) and [Dedicated (App Service)](../articles/azure-functions/dedicated-plan.md) plans. [Flex Consumption](../articles/azure-functions/flex-consumption-plan.md) and [Consumption](../articles/azure-functions/consumption-plan.md) plans aren't yet supported.
 >
 > RabbitMQ bindings aren't supported by the Azure Functions v1.x runtime.

includes/functions-sql-database-authentication-note.md

@@ -2,9 +2,9 @@
 author: ggailey777
 ms.service: azure-functions
 ms.topic: include
-ms.date: 12/16/2024
+ms.date: 01/03/2025
 ms.author: glenga
 ---
 
 > [!IMPORTANT]
-> For optimal security, you should use Microsoft Entra ID with managed identities for connections between Functions and Azure SQL Database. Managed identities make your app more secure by eliminating secrets from your application deployments, such as credentials in the connection strings, server names, and ports being used. You can learn how to use managed identities in this tutorial, [Connect a function app to Azure SQL with managed identity and SQL bindings](../azure-functions/functions-identity-access-azure-sql-with-managed-identity.md).
+> For optimal security, you should use Microsoft Entra ID with managed identities for connections between Functions and Azure SQL Database. Managed identities make your app more secure by eliminating secrets from your application deployments, such as credentials in the connection strings, server names, and ports being used. You can learn how to use managed identities in this tutorial, [Connect a function app to Azure SQL with managed identity and SQL bindings](../articles/azure-functions/functions-identity-access-azure-sql-with-managed-identity.md).