Merge pull request #304257 from MicrosoftDocs/main

Auto Publish – main to live - 2025-08-15 05:00 UTC

Author: learn-build-service-prod[bot]

articles/app-service/environment/overview.md

@@ -3,7 +3,7 @@ title: App Service Environment Overview
 description: Learn about App Service Environments, which are fully isolated and single-tenant App Service deployments that provide high-scale, network-secured hosting.
 author: seligj95
 ms.topic: overview
-ms.date: 07/25/2025
+ms.date: 08/14/2025
 ms.update-cycle: 1095-days
 ms.author: jordanselig
 ms.custom:
@@ -233,7 +233,7 @@ The following sections list the regional pricing tiers, or SKUs, availability fo
 | Canada Central       | ✅          | ✅          | ✅               |
 | Canada East          | ✅          | ✅          | ✅               | 
 | Central India        | ✅          | ✅          | ✅               | 
-| Central US           | ✅          | ✅ *        |                   | 
+| Central US           | ✅          | ✅*         | ✅**             | 
 | East Asia            | ✅          | ✅          | ✅               |
 | East US              | ✅          | ✅          |                   | 
 | East US 2            | ✅          | ✅          | ✅               |
@@ -273,14 +273,15 @@ The following sections list the regional pricing tiers, or SKUs, availability fo
 | UAE North            | ✅          | ✅          | ✅               | 
 | UK South             | ✅          | ✅          | ✅               | 
 | UK West              | ✅          | ✅          | ✅               | 
-| West Central US      | ✅          | ✅ *        |                   | 
-| West Europe          | ✅          | ✅ *        |                   | 
+| West Central US      | ✅          | ✅*         |                   | 
+| West Europe          | ✅          | ✅*         |                   | 
 | West India           | ✅          | ✅          |                   | 
 | West US              | ✅          | ✅          | ✅               | 
 | West US 2            | ✅          | ✅          | ✅               | 
 | West US 3            | ✅          | ✅          | ✅               | 
 
 \* Windows containers don't support large SKUs in this region.
+\** Limited availability. Create a support ticket if you run into issues deploying this SKU.
 
 ### Azure Government regions
 

articles/azure-netapp-files/whats-new.md

@@ -19,7 +19,7 @@ Azure NetApp Files is updated regularly. This article provides a summary about t
 
 ## August 2025
 
-* [Flexible service level](manage-cool-access.md#register-the-feature) now supports storage with cool access (Preview)
+* [Flexible service level](manage-cool-access.md?tabs=flexible#register-the-feature) now supports storage with cool access (Preview)
 
     Azure NetApp Files now supports cool access for the Flexible service level, enabling you to further optimize performance and cost by automatically tiering infrequently accessed data to lower-cost Azure storage accounts. This enhancement builds on the Flexible service level's ability to decouple storage capacity and throughput, allowing precise resource alignment for diverse workloads while maintaining configured throughput levels—even with cool access enabled. These features help organizations reduce total cost of ownership without compromising performance. You must be registered for the [Flexible service level](azure-netapp-files-set-up-capacity-pool.md) before enrolling in [the preview for the Flexible service level with cool access](manage-cool-access.md#register-the-feature). 
 

articles/container-apps/functions-overview.md

@@ -48,7 +48,7 @@ The following steps show you how to use a sample container image to create your
 
 1. Next to *Optimize for Azure Functions* check the checkbox.
 
-![fnonacaportal](https://github.com/user-attachments/assets/78bc6b15-462a-48a4-8243-91aa92c0bcbc)
+    :::image type="content" source="media/functions-overview/functions-create-container-app.png" alt-text="Screenshot of the Azure portal when you create a container app pre-configured for Azure Functions.":::
 
 1. Under *Container Apps environment* enter:
 

articles/container-apps/functions-usage.md

@@ -7,7 +7,7 @@ ms.suite: integration
 ms.reviewer: estfan, azla
 ms.collection: ce-skilling-ai-copilot
 ms.topic: how-to
-ms.date: 02/07/2025
+ms.date: 08/06/2025
 ms.update-cycle: 180-days
 # Customer intent: As a developer, I want to create my first example Standard logic app workflow that runs in single-tenant Azure Logic Apps using the Azure portal.
 ---
@@ -195,6 +195,21 @@ For optimal designer responsiveness and performance, review and follow these gui
    1. On the **Monitoring** tab, under **Application Insights**, set **Enable Application Insights** to **Yes**.
 
    1. For the **Application Insights** setting, either select an existing Application Insights instance, or if you want to create a new instance, select **Create new** and provide the name that you want to use.
+  
+1. On the **Authentication** tab, under **Authentication type**, select the authentication to use for connecting to the host storage account resource (**Host storage (AzureWebJobsStorage)**).
+
+   > [!IMPORTANT]
+   >
+   > If you select **Managed identity** for authentication, you must specify the managed identity to use. Choose one of the following options:
+   >
+   > - If you select **Create new managed identity**, the portal creates this identity and automatically assigns the correct role-based access
+   > permissions to the identity on the host storage account for your logic app. After you create your logic app, you might have to wait a few
+   > minutes for the permissions to propagate onto your new managed identity. You can then restart your logic app. If no option exists to create
+   > a managed identity, you need the lowest level of permissions that permits you to complete this task.
+   >
+   > - If you select an existing managed identity, you must manually assign the roles in the **Minimum roles required column** to the managed
+   > identity on the host storage account resource. Consider completing this assignment before you deploy your logic app. Otherwise, you get 
+   > errors when you open your new logic app resource. For more information, see [Assign Azure roles using the Azure portal](/azure/role-based-access-control/role-assignments-portal).
 
 1. After Azure validates your logic app settings, on the **Review + create** tab, select **Create**, for example:
 

articles/container-apps/media/functions-overview/functions-create-container-app.png

@@ -434,3 +434,39 @@ The following bug fixes, defect resolutions, or usability improvements are deliv
 * NFO - [SFI] A total of 15 CVEs are addressed in this release.
 * RP - [606065291] Fixes conflict scenarios during SNS delete operations by preventing duplicate requests.
 * RP - [600962417] Populate Chart Details in DeploymentProfile when ConfigurationType is "Secret"
+
+## Release 3.0.3131-220
+
+Document Revision 1.0
+
+### Release Summary
+Azure Operator Service Manager is a cloud orchestration service that enables automation of operator network-intensive workloads, and mission critical applications hosted on Azure Operator Nexus. Azure Operator Service Manager unifies infrastructure, software, and configuration management with a common model into a single interface, both based on trusted Azure industry standards. This August 8, 2025 Azure Operator Service Manager release includes updating the NFO version to 3.0.3131-220 and the RP version to 1.0.03134.469, the details of which are further outlined in the remainder of this document.
+
+### Release Details
+* Release Version: NFO version 3.0.3131-220, RP version 1.0.03134.469
+* Release Date: August 8, 2025
+* Is NFO update required: YES, Update only
+* Dependency Versions: Go/1.24.3 - Helm/3.17.3 - Base Image/AzureLinux 3.0
+
+#### Release Updates
+The following bug fixes, defect resolutions, or usability improvements are delivered with this release, for either Network Function Operator (NFO) or resource provider (RP) components.
+
+* NFO - [1041747] Improves support for publisher cleanup feature, fixing stability issues and addressing corner-cases such as disconnected mode.
+* NFO - [2217456] Migrates AOSM extension images to MCR source, including cluster registry and geneva images.
+* NFO - [2209250] Fixes cluster registry file corruption in broken manifest link, NFO now handles such failures and auto-recovers so that deletes can succeed.
+* NFO - [2278364] Fixes behavior where upgrade fails due to a pre-upgrade hook stuck on bad node, removing the hook which is no longer needed.
+* NFO - [2196085] Remediates file system security vulnerability with TLS-Daemonset by allowing only ReadOnlyRootFilesystem access.
+* RP - [2236853] 1ES Operation Vulnerabilities.
+* RP - [2034803] Clean up of RP resources and unused files for decom'ed regions.
+* RP - [2217454] Clean up of redundant and old runners.
+* RP - [2217437] Fixes NFO component rollback timeout issue.
+* RP - [2217439] Fixes SNS retry policy on workload forbidden error.
+* RP - [2275730] Fixes batch scope token provisioning timeout.
+* RP - [2278044] Fixes NF DTF scheduling failure where timeout now exceeds 7 days.
+
+#### Security Related Updates
+* NFO - [CVE] A total of 2 CVEs are addressed in this release.
+* NFO - [SFI] Helm version upgraded from 3.17.2 to 3.17.3
+* RP - [SFI] 2236914: MISE Upgrade
+* RP - [SFI] 2120797: Migrate to MISE/SNI
+* RP - [SFI] 2154940: Security Code Bugs