Merge branch 'main' into release-esan-backup

Author: v-alje

articles/api-management/sap-api.md

@@ -116,7 +116,7 @@ Choose one of the following methods to import your API to API Management:
     |---------|---------| 
     |`HEAD /`     | Enables the client to exchange cross-site request forgery (CSRF) tokens with the SAP server when required.<br/><br/>SAP also allows CSRF token exchange via the GET verb.<br/><br/> CSRF token exchange isn’t covered in this article. See an [example API Management policy snippet](https://github.com/Azure/api-management-policy-snippets/blob/master/examples/Get%20X-CSRF%20token%20from%20SAP%20gateway%20using%20send%20request.policy.xml) to broker token exchange.     |
 
-    :::image type="content" source="media/sap-api/head-root-operation.png" alt-text="Sceenshot that shows the operation for fetching tokens.":::
+    :::image type="content" source="media/sap-api/head-root-operation.png" alt-text="Screenshot that shows the operation for fetching tokens.":::
 
 - `GET /`
 

articles/app-service/app-service-key-vault-references.md

@@ -95,6 +95,8 @@ If the secret version isn't specified in the reference, the app uses the latest
 
 The delay is because App Service caches the values of the Key Vault references and refetches them every 24 hours. Any configuration change to the app causes an app restart and an immediate refetch of all referenced secrets.
 
+To force resolution of your app's Key Vault references, make an authenticated POST request to the API endpoint `https://management.azure.com/[Resource ID]/config/configreferences/appsettings/refresh?api-version=2022-03-01`.
+
 ## <a name = "source-app-settings-from-key-vault"></a> Understand source app settings from Key Vault
 
 To use a Key Vault reference, set the reference as the value of the setting. Your app can reference the secret through its key as normal. No code changes are required.

articles/app-service/includes/tutorial-sidecar/common-faqs.md

@@ -18,3 +18,29 @@ No. App Service routes internet requests only to the main container. For code-ba
 
 For more information on configuring `IsMain`, see [Microsoft.Web sites/sitecontainers](/azure/templates/microsoft.web/sites/sitecontainers).
 
+### How do I use volume mounts?
+
+The Volume mounts feature enables you to share non-persistent files and directories between containers within your Web App.
+
+:::image type="content" source="../../media/tutorial-custom-container-sidecar/configure-volume-mounts.png" alt-text="Screenshot showing a volume mount configuration for a sidecar container.":::
+
+**Volume sub path:** This is a logical directory path that is automatically created, and is not referenced within the container. Containers that are configured with the same volume sub path can share files and directories with each other.
+
+**Container mount path:** This corresponds to a directory path that you reference within the container. The container mount path is mapped to the volume sub path.
+
+For example, suppose the following volume mounts are configured:
+
+| Sidecar name | Volume sub path | Container mount path | Read-only |
+| ------------ | --------------- | -------------------- | --------- |
+| Container1 | /directory1/directory2 | /container1Vol | False |
+| Container2 | /directory1/directory2 | /container2Vol | True |
+| Container3 | /directory1/directory2/directory3 | /container3Vol | False |
+| Container4 | /directory4 | /container1Vol | False |
+
+Based on these settings, the following conditions apply:
+-	If Container1 creates **/container1Vol/myfile.txt**, Container2 can read the file via **/container2Vol/myfile.txt**.
+-	If Container1 creates **/container1Vol/directory3/myfile.txt**, Container2 can read the file via **/container2Vol/directory3/myfile.txt**, and Container3 can read and write to the file via **/container3Vol/myfile.txt**.
+-	Container4 does not share a volume mount in common with any of the other containers.
+
+> [!Note]
+> For code-based Linux apps, the built-in Linux container cannot use volume mounts.

articles/app-service/media/tutorial-custom-container-sidecar/configure-volume-mounts.png

@@ -291,55 +291,35 @@
 
 - name: Reference
   items:
-    - name: Azure Managed Redis
-      items:
-        - name: .NET
-          href: /dotnet/api/overview/azure/resourcemanager.redisenterprise-readme
-        - name: Java
-          href: /java/api/overview/azure/resourcemanager-redisenterprise-readme
-        - name: Azure PowerShell
-          href: /powershell/module/az.redisenterprisecache
-        - name: Azure CLI
-          href: /cli/azure/redisenterprise
-        - name: REST
-          href: /rest/api/redis/redisenterprisecache/operation-groups
-        - name: Resource Manager template
-          href: /azure/templates/microsoft.cache/redisenterprise
-    - name: Azure Cache for Redis
-      items: 
-        - name: .NET
-          href: /dotnet/api/microsoft.azure.management.redis
-        - name: Java
-          href: /java/api/com.microsoft.azure.management.redis.rediscache
-        - name: Azure PowerShell
-          href: /powershell/module/az.rediscache
-        - name: Azure CLI
-          href: /cli/azure/redis
-        - name: REST
-          href: /rest/api/redis/
-        - name: Resource Manager template
-          href: /azure/templates/microsoft.cache/allversions
-        - name: Azure Policy built-ins
-          displayName: samples, policies, definitions
-          href: policy-reference.md
-        - name: Redis commands
-          href: https://redis.io/commands#
-        - name: Monitoring data reference
-          href: /azure/redis/monitor-cache-reference
-
+    - name: .NET
+      href: /dotnet/api/microsoft.azure.management.redis
+    - name: Java
+      href: /java/api/com.microsoft.azure.management.redis.rediscache
+    - name: Azure PowerShell
+      href: /powershell/module/az.rediscache
+    - name: Azure CLI
+      href: /cli/azure/redis
+    - name: REST
+      href: /rest/api/redis/
+    - name: Resource Manager template
+      href: /azure/templates/microsoft.cache/allversions
+    - name: Azure Policy built-ins
+      displayName: samples, policies, definitions
+      href: policy-reference.md
+    - name: Redis commands
+      href: https://redis.io/commands#
+    - name: Monitoring data reference
+      href: /azure/redis/monitor-cache-reference
 - name:  Resources
   items:
-  - name: Azure Cache for Redis FAQs
+  - name: Azure Redis FAQ
     href: /azure/redis/faq
   - name: Retirements from Azure Cache for Redis
     href: cache-retired-features.md
   - name: Videos
     href: https://www.youtube.com/results?search_query=azure+cache+redis
   - name: Microsoft Q&A question page
-    href: /answers/topics/azure-cache-redis.html
+    href: https://learn.microsoft.com/answers/tags/170/azure-cache-redis
   - name: Pricing
     href: https://azure.microsoft.com/pricing/details/cache/
-  - name: Build your skills with Microsoft Learn training
-    href: /training/browse/?products=azure-redis-cache
-  - name: Azure Roadmap
-    href: https://azure.microsoft.com/roadmap/?category=databases
+

articles/azure-cache-for-redis/TOC.yml

@@ -2,7 +2,7 @@
 title: Create a function in Go or Rust using Visual Studio Code - Azure Functions
 description: Learn how to create a Go function as an Azure Functions custom handler, then publish the local project to serverless hosting in Azure Functions using the Azure Functions extension in Visual Studio Code.
 ms.topic: quickstart
-ms.date: 06/03/2024
+ms.date: 05/20/2025
 ms.devlang: golang
 # ms.devlang: golang, rust
 ms.custom: mode-api, vscode-azure-extension-update-complete
@@ -16,7 +16,8 @@ In this article, you use Visual Studio Code to create a [custom handler](functio
 
 Custom handlers can be used to create functions in any language or runtime by running an HTTP server process. This article supports both [Go](create-first-function-vs-code-other.md?tabs=go) and [Rust](create-first-function-vs-code-other.md?tabs=rust).
 
-Completing this quickstart incurs a small cost of a few USD cents or less in your Azure account.
+>[!TIP]
+>Completing this quickstart creates an app that runs in an [Elastic Premium plan](functions-premium-plan.md), which can incur costs in your Azure account even when you're not using it. You should [Clean up resources](#clean-up-resources) to remove the function app, App Service plan, and related resources after you've completed the article.   
 
 ## Configure your environment
 
@@ -291,18 +292,24 @@ In this section, you publish your project to Azure in a function app running Lin
 
 In this section, you create a function app and related resources in your Azure subscription. 
 
-1. Choose the Azure icon in the Activity bar. Then in the **Resources** area, select the **+** icon and choose the **Create Function App in Azure** option.
+1. In the command palette, enter **Azure Functions: Create function app in Azure...(Advanced)**.
 
-    ![Create a resource in your Azure subscription](../../includes/media/functions-publish-project-vscode/function-app-create-resource.png)
+1. If you're not signed in, you're prompted to **Sign in to Azure**. You can also **Create a free Azure account**. After signing in from the browser, go back to Visual Studio Code.
 
-1. Provide the following information at the prompts:
+1. Following the prompts, provide this information:
 
-    |Prompt|Selection|
-    |--|--|
-    |**Select subscription**| Choose the subscription to use. You won't see this when you have only one subscription visible under **Resources**. |
-    |**Enter a globally unique name for the function app**| Type a name that is valid in a URL path. The name you type is validated to make sure that it's unique in Azure Functions.|
-    |**Select a runtime stack**| Choose **Custom Handler**. |
-    |**Select a location for new resources**| For better performance, choose a [region](https://azure.microsoft.com/regions/) near you.|
+   | Prompt |  Selection |
+   | ------ |  --------- |
+   | Enter a globally unique name for the new function app. | Type a globally unique name that identifies your new function app and then select Enter. Valid characters for a function app name are `a-z`, `0-9`, and `-`. |
+   | Select a hosting plan. | Choose the **Premium** [hosting plan](functions-scale.md), which provides serverless hosting on Linux that scales dynamically as needed. |
+   | Select a location for new resources. | Select a location in a [region](https://azure.microsoft.com/regions/) near you or near other services that your functions access. Only regions that support your chosen hosting plan are displayed. |
+   | Select a runtime stack. | Select **Custom handler**. |
+   | Select an OS. | Select **Linux** since the app was compiled to run on Linux. |
+   | Select a Linux App Service plan | For Elastic Premium plans, you must explicitly **Create a new app service plan**, enter the plan name, and select the **EP1** pricing tier. |
+   | Select resource authentication type | Select **Managed identity**, which is the most secure option for connecting to the [default host storage account](storage-considerations.md#storage-account-guidance). When using managed identities with an Elastic Premium plan, secret key access to the default host storage remains enabled for Azure Files access. For more information, see [run without Azure Files](storage-considerations.md#create-an-app-without-azure-files). |
+   | Select a storage account. | Choose **Create new storage account**, and at the prompt, enter a globally unique name for the new storage account used by your function app. Storage account names must be between 3 and 24 characters long and can contain only numbers and lowercase letters. |
+   | Select an Application Insights resource for your app. | Choose **Create new Application Insights resource**, and at the prompt, enter a name for the instance used to store runtime data from your functions. |
+   | Select a user assigned identity | Choose **Create a new user assigned identity**. This identity is used when accessing the default host storage account using Microsoft Entra ID authentication. | 
 
     The extension shows the status of individual resources as they are being created in Azure in the **Azure: Activity Log** panel.
 
@@ -312,6 +319,8 @@ In this section, you create a function app and related resources in your Azure s
 
     [!INCLUDE [functions-vs-code-created-resources](../../includes/functions-vs-code-created-resources.md)]
 
+    + A user-assigned managed identity that's added to the [Storage Blob Data Contributor](/azure/role-based-access-control/built-in-roles/storage#storage-blob-data-contributor) role in the new default host storage account.
+
     A notification is displayed after your function app is created and the deployment package is applied.
 
     [!INCLUDE [functions-vs-code-create-tip](../../includes/functions-vs-code-create-tip.md)]

articles/azure-functions/create-first-function-vs-code-other.md

@@ -9,6 +9,8 @@ ms.custom: build-2024, linux-related-content
 
 # Azure Container Apps hosting of Azure Functions 
 
+[!INCLUDE [functions-aca-v2-note](../../includes/functions-aca-v2-note.md)]
+
 Azure Functions provides integrated support for developing, deploying, and managing containerized function apps on [Azure Container Apps](../container-apps/overview.md). Use Azure Container Apps to host your function app containers when you need to run your event-driven functions in Azure in the same environment as other microservices, APIs, websites, workflows, or any container hosted programs. Container Apps hosting lets you run your functions in a fully managed, Kubernetes-based environment with built-in support for open-source monitoring, mTLS, Dapr, and Kubernetes Event-driven Autoscaling (KEDA).
 
 You can write your function code in any [language stack supported by Functions](supported-languages.md). You can use the same Functions triggers and bindings with event-driven scaling. You can also use existing Functions client tools and the Azure portal to create containers, deploy function app containers to Container Apps, and configure continuous deployment. 
@@ -140,3 +142,5 @@ Keep in mind the following considerations when deploying your function app conta
 
 + [Hosting and scale](./functions-scale.md)
 + [Create your first containerized functions on Container Apps](./functions-deploy-container-apps.md)
++ [Native Azure Functions Support in Azure Container Apps](../../articles/container-apps/functions-overview.md)
++ [Create your Native Azure Functions on Azure Container Apps](../../articles/container-apps/functions-usage.md)

articles/azure-functions/functions-container-apps-hosting.md

@@ -11,6 +11,8 @@ zone_pivot_groups: programming-languages-set-functions
 
 In this article, you create a function app running in a Linux container and deploy it to an Azure Container Apps environment from a container registry. By deploying to Container Apps, you're able to integrate your function apps into cloud-native microservices. For more information, see [Azure Container Apps hosting of Azure Functions](functions-container-apps-hosting.md).
 
+[!INCLUDE [functions-aca-v2-note](../../includes/functions-aca-v2-note.md)]
+
 This article shows you how to create functions running in a Linux container and deploy the container to a Container Apps environment. 
 
 Completing this quickstart incurs a small cost of a few USD cents or less in your Azure account, which you can minimize by [cleaning-up resources](#clean-up-resources) when you're done.
@@ -189,7 +191,11 @@ az group delete --name AzureFunctionsContainers-rg
 ## Next steps
 
 > [!div class="nextstepaction"]  
-> [Azure Container Apps hosting of Azure Functions](./functions-container-apps-hosting.md)   
+> [Azure Container Apps hosting of Azure Functions](./functions-container-apps-hosting.md)  
+> [!div class="nextstepaction"]  
+> [Native Azure Functions Support in Azure Container Apps](../../articles/container-apps/functions-overview.md)  
+> [!div class="nextstepaction"]  
+> [Create your Native Azure Functions on Azure Container Apps](../../articles/container-apps/functions-usage.md)  
 > [!div class="nextstepaction"]  
 > [Working with containers and Azure Functions](./functions-how-to-custom-container.md)  
 > [!div class="nextstepaction"]  

articles/azure-functions/functions-deploy-container-apps.md

@@ -11,6 +11,9 @@ zone_pivot_groups: functions-container-hosting
 
 :::zone pivot="container-apps"
 This article demonstrates the support that Azure Functions provides for working with containerized function apps running in an Azure Container Apps environment. For more information, see [Azure Container Apps hosting of Azure Functions](functions-container-apps-hosting.md). 
+
+[!INCLUDE [functions-aca-v2-note](../../includes/functions-aca-v2-note.md)]
+
 ::: zone-end
 :::zone pivot="azure-functions,azure-arc"
 This article demonstrates the support that Azure Functions provides for working with function apps running in Linux containers. 
@@ -407,8 +410,10 @@ SSH enables secure communication between a container and a client. With SSH enab
 The following articles provide more information about deploying and managing containers:
 
 + [Azure Container Apps hosting of Azure Functions](./functions-container-apps-hosting.md)
++ [Native Azure Functions Support in Azure Container Apps](../../articles/container-apps/functions-overview.md)
++ [Create your Native Azure Functions on Azure Container Apps](../../articles/container-apps/functions-usage.md)
 + [Scale and hosting options](functions-scale.md)
 + [Kubernetes-based serverless hosting](functions-kubernetes-keda.md)
 
 
-[Azure portal]: https://portal.azure.com
+[Azure portal]: https://portal.azure.com

articles/azure-functions/functions-how-to-custom-container.md

@@ -1,7 +1,7 @@
 ---
 author: JanSchietse
 ms.author: janschietse
-ms.date: 01/25/2024
+ms.date: 03/17/2025
 ms.topic: include
 ms.service: azure-health-insights
 ---