Merge branch 'main' into release-migrate-agent-public-preview

Author: v-alje

articles/active-directory-b2c/customize-ui-with-html.md

@@ -6,7 +6,7 @@ author: kengaderdus
 manager: CelesteDG
 ms.service: azure-active-directory
 ms.topic: how-to
-ms.date: 02/17/2025
+ms.date: 03/04/2026
 ms.author: kengaderdus
 ms.subservice: b2c
 zone_pivot_groups: b2c-policy-type
@@ -440,6 +440,34 @@ To use the sample:
 1. Now modify the policy, pointing to your HTML file, as mentioned previously.
 1. If you see missing fonts, images, or CSS, check your references in the extensions policy and the `\*.html` files.
 
+
+### Bootstrap dependency in sample templates
+
+The [sample templates](https://github.com/azure-ad-b2c/html-templates) use **Bootstrap 3.3.5**, sourced from the official Bootstrap CDN. This version has been validated and tested with Azure AD B2C.
+
+The templates reference the following CDN URL for Bootstrap CSS:
+
+  ```
+  https://cdn.jsdelivr.net/npm/bootstrap@3.3.5/dist/css/bootstrap.min.css
+  ```
+
+The default configuration in the template HTML files includes a link element similar to the following example:
+
+  ```xml
+  <link href="https://cdn.jsdelivr.net/npm/bootstrap@3.3.5/dist/css/bootstrap.min.css" rel="stylesheet" type="text/css" />
+  ```
+
+For the official Bootstrap 3.3.5 download and CDN details, see [Bootstrap 3.3 Getting Started](https://getbootstrap.com/docs/3.3/getting-started/#download-cdn).
+
+#### Replace the CDN reference
+
+You can replace the CDN reference with your organization's internal CDN or a locally hosted copy to meet reliability, security, or compliance requirements.
+
+> [!IMPORTANT]
+> The templates are validated specifically against Bootstrap 3.3.5. Upgrading, downgrading, or otherwise modifying the Bootstrap version might introduce styling, layout, or component compatibility issues.
+
+If you change the Bootstrap version, you're responsible for completing regression testing to validate that your customized templates work correctly with Azure AD B2C. Retain the validated version unless you've completed appropriate testing.
+
 ## Use company branding assets in custom HTML
 
 To use [company branding](customize-ui.md#configure-company-branding) assets in a custom HTML, add the following tags outside the `<div id="api">` tag. The image source is replaced with that of the background image and banner logo.

articles/api-management/api-management-region-availability.md

@@ -33,7 +33,7 @@ Information in the following table is updated regularly. Capacity availability i
 | Brazil South | ✅ | ✅ | |  |
 | Canada Central  | ✅ | ✅ | ✅ |  |
 | Central India  | ✅ | ✅ | |  |
-| Central US  | ✅ | ✅ | |  |
+| Central US  | ✅ | ✅ | ✅ |  |
 | East Asia | ✅ | ✅ | | ✅ |
 | East US  | ✅ | ✅ |  |  |
 | East US 2 | ✅ | ✅ | ✅ | ✅ |

articles/application-gateway/for-containers/web-application-firewall.md

@@ -136,7 +136,7 @@ spec:
 The following functionality is not supported on an Azure Web Application Firewall policy that's associated with Application Gateway for Containers:
 
 - **Cross-region, cross-subscription policy**: Your WAF policy must be in the same subscription and region as your Application Gateway for Containers resource.
-- **Core Rule Set (CRS) managed rules**: An Application Gateway for Containers WAF supports only Default Rule Set (DRS) managed rule sets.
+- **Core Rule Set (CRS) managed rules**: An Application Gateway for Containers WAF supports only Default Rule Set (DRS) 2.1 managed rule set.
 - **Legacy Bot Manager Rule Set**: Bot Manager Ruleset 0.1 isn't supported, but Bot Manager Ruleset versions 1.0 and 1.1 are supported.
 - **JavaScript challenge actions on Bot Manager rules**: You can't set the action on a Bot Manager rule to JavaScript challenge.
 - **Captcha challenge actions on Bot Manager rules**: You can't set the action on a Bot Manager rule to Captcha.

articles/azure-functions/durable/durable-functions-azure-storage-provider.md

@@ -201,7 +201,7 @@ Durable Functions creates the queues, tables, and blobs it uses in a configured
 - The `durableTask/storageProvider/connectionStringName` setting (Durable Functions 2.x)
 - The `durableTask/azureStorageConnectionStringName` setting (in Durable Functions 1.x)
 
-# [Durable Functions 2.x](#tab/durable-2x)
+### [Durable Functions 2.x](#tab/durable-2x)
 
 ```json
 {
@@ -215,7 +215,7 @@ Durable Functions creates the queues, tables, and blobs it uses in a configured
 }
 ```
 
-# [Durable Functions 1.x](#tab/durable-1x)
+### [Durable Functions 1.x](#tab/durable-1x)
 
 ```json
 {
@@ -243,7 +243,7 @@ While you can scale out activity functions infinitely by adding more virtual mac
 
 You define the number of control queues in your `host.json` file. The following example `host.json` snippet sets the `durableTask/storageProvider/partitionCount` property (`durableTask/partitionCount` in Durable Functions 1.x) to `3`. You have as many control queues as you have partitions.
 
-# [Durable Functions 2.x](#tab/durable-2x)
+### [Durable Functions 2.x](#tab/durable-2x)
 
 ```json
 {
@@ -257,7 +257,7 @@ You define the number of control queues in your `host.json` file. The following
 }
 ```
 
-# [Durable Functions 1.x](#tab/durable-1x)
+### [Durable Functions 1.x](#tab/durable-1x)
 
 ```json
 {
@@ -310,7 +310,7 @@ Orchestration instances and entities are distributed across all control queue in
 
 You can enable extended sessions by setting `durableTask/extendedSessionsEnabled` to `true` in your `host.json` file. You can use the `durableTask/extendedSessionIdleTimeoutInSeconds` setting to control how long an idle session stays in memory:
 
-# [Durable Functions 2.x](#tab/durable-2x)
+### [Durable Functions 2.x](#tab/durable-2x)
 ```json
 {
   "extensions": {
@@ -322,7 +322,7 @@ You can enable extended sessions by setting `durableTask/extendedSessionsEnabled
 }
 ```
 
-# [Durable Functions 1.x](#tab/durable-1x)
+### [Durable Functions 1.x](#tab/durable-1x)
 ```json
 {
   "extensions": {

articles/azure-functions/durable/durable-functions-storage-providers.md

@@ -121,7 +121,7 @@ You can use the following table to understand the significant tradeoffs between
 | Price-performance configurable? | Coming soon! | ❌ No | ✅ Yes (SQL vCPUs) | ✅ Yes (Event Hubs TUs and CUs) | 
 | Disconnected environment support | ❌ Azure connectivity required | ❌ Azure connectivity required | ✅ Fully supported | ❌ Azure connectivity required |
 | Identity-based connections | ✅ Fully supported | ✅ Fully supported | ⚠️ Requires runtime-driven scaling | ❌ Not supported |
-| [Flex Consumption plan](../flex-consumption-plan.md) | ❌ Not supported | ✅ Fully supported ([see notes](./durable-functions-azure-storage-provider.md#flex-consumption-plan)) | ✅ Fully supported | ❌ Not supported |
+| [Flex Consumption plan](../flex-consumption-plan.md) | ✅ Fully supported | ✅ Fully supported ([see notes](./durable-functions-azure-storage-provider.md#flex-consumption-plan)) | ✅ Fully supported | ❌ Not supported |
 
 ::: zone-end
 

articles/azure-functions/durable/durable-task-scheduler/develop-with-durable-task-scheduler.md

@@ -132,9 +132,6 @@ The Durable Task Scheduler emulator is only available as a Docker image today.
 
    #### [Consumption SKU](#tab/consumption)
 
-   > [!NOTE]
-   > The Consumption SKU is currently in preview. [Learn more about the SKU and orchestration framework combinations recommended for production use.](./durable-task-scheduler-billing.md)
-
     ```azurecli
     az durabletask scheduler create --name "YOUR_SCHEDULER" --resource-group "YOUR_RESOURCE_GROUP" --location "LOCATION" --ip-allowlist "[0.0.0.0/0]" --sku-name "consumption"
     ```

articles/azure-functions/durable/durable-task-scheduler/durable-task-scheduler-billing.md

@@ -19,7 +19,7 @@ The Durable Task Scheduler is a managed backend service that persists orchestrat
 The [Durable Task Scheduler](./durable-task-scheduler.md) is a purpose-built backend as a service that persists orchestration state for your Durable Task SDK applications. The Durable Task Scheduler offers two pricing models to accommodate different service requirements, usage patterns, and preferred billing models:
 
 - [Dedicated](#dedicated-sku)
-- [Consumption (preview)](#consumption-sku)
+- [Consumption](#consumption-sku)
 
 ## What is an action?
 
@@ -106,9 +106,6 @@ A software as a service (SaaS) platform supports 800 million orchestrations mont
 
 ## Consumption SKU
 
-> [!NOTE]
-> The Consumption SKU is currently in preview. [Learn more about the SKU and orchestration framework recommended for production use.](../choose-orchestration-framework.md)
-
 The Consumption SKU offers a pay-as-you-use model, ideal for variable workloads and development scenarios. 
 
 Currently, you're limited to 10 schedulers and five task hubs per region per subscription when using the Consumption SKU. For more quota, [contact support](https://github.com/Azure/azure-functions-durable-extension/issues).

articles/azure-functions/durable/quickstart-mssql.md

@@ -299,7 +299,7 @@ az role assignment create --assignee "$clientId" --role "Storage Blob Data Owner
 
 #### Azure SQL Database
 >[!NOTE]
-> Authenticating to Azure SQL database using managed identity is _not_ supported when hosting a Durable Functions app in the Flex Consumption plan. If your app is hosted in the Flex Consumption plan, skip to the [set app settings](#set-required-app-settings) section. 
+> Authenticating to Azure SQL database using managed identity is _not_ supported when hosting a Durable Functions app in the Flex Consumption plan. If your app is hosted in the Flex Consumption plan, skip to the [set app settings](#set-required-app-settings) section. If you'd like to use it, the Flex Consumption plan is supported by Durable Task Scheduler.
 
 1. Start by setting your developer identity as the database's admin.
 

articles/cost-management-billing/manage/supported-payment-methods.md

@@ -34,7 +34,7 @@ For more information about payment methods, see [Add, update, or remove a paymen
 | Argentina | ✔   |     |     | ✔   | ✔   |     |     |     |
 | Armenia | ✔   |     |     | ✔   | ✔   |     |     |     |
 | Australia | ✔   |     |     | ✔   | ✔   |     |     |     |
-| Austria | ✔   |     |     | ✔   | ✔   |     |     |      |
+| Austria | ✔   |     |     | ✔   | ✔   |     |     | ✔     |
 | Azerbaijan | ✔   |     |     | ✔   | ✔   |     |     |     |
 | Bahamas | ✔   |     |     | ✔   | ✔   |     |     |     |
 | Bahrain | ✔   |     |     | ✔   | ✔   |     |     |     |
@@ -76,7 +76,7 @@ For more information about payment methods, see [Add, update, or remove a paymen
 | Finland | ✔   |     |     | ✔   | ✔   |     |     |     |
 | France | ✔   |     |     | ✔   | ✔   |     |     |     |
 | Georgia | ✔   |     |     | ✔   | ✔   |     |     |     |
-| Germany | ✔   |     |     | ✔   | ✔   |     |     |     |
+| Germany | ✔   |     |     | ✔   | ✔   |     |     | ✔   |
 | Ghana | ✔   |     |     | ✔   | ✔   |     |     |     |
 | Greece | ✔   |     |     | ✔   | ✔   |     |     |     |
 | Guatemala | ✔   |     |     | ✔   | ✔   |     |     |     |
@@ -116,7 +116,7 @@ For more information about payment methods, see [Add, update, or remove a paymen
 | Morocco |  ✔   |     |     | ✔   | ✔   |     |     |     |
 | Namibia | ✔   |     |     | ✔   | ✔   |     |     |     |
 | Nepal |     |     |     |  ✔   |   ✔  |     |     |     |
-| Netherlands | ✔   |     |     | ✔   | ✔   |     |     |     |
+| Netherlands | ✔   |     |     | ✔   | ✔   |     |     | ✔   |
 | New Zealand | ✔   |     |     | ✔   | ✔   |     |     |     |
 | Nicaragua | ✔   |     |     | ✔   | ✔   |     |     |     |
 | Nigeria | ✔   |     |     | ✔   | ✔   |     |     |     |

articles/network-watcher/vnet-flow-logs-overview.md

@@ -64,6 +64,18 @@ In addition to existing support to identify traffic that [network security group
 > 
 > If you enable network security group flow logs on the network security group of a subnet, then you enable virtual network flow logs on the same subnet or parent virtual network, you might get duplicate logging or only virtual network flow logs.
 
+## Platform Rules
+
+#### What is a platform rule in flow logs
+
+In flow logs, a platform rule represents network traffic that is processed by the Azure platform itself rather than by user‑configured rules, such as Network Security Groups (NSGs) or Azure Virtual Network Manager rules. This traffic is handled automatically by the platform and is not the result of an explicit allow or deny rule defined within a deployment. Platform rule entries provide visibility into system‑managed or infrastructure‑level traffic. If analysis is focused only on traffic evaluated by explicitly configured rules, these entries can be filtered out during log analysis.
+
+In some scenarios, traffic associated with you application or workload may appear under a platform rule. This can occur in a limited number of well‑understood cases, such as when load‑balanced connections are recreated as part of normal platform operations, or when return traffic does not require rule evaluation for the response path. In these cases, the traffic is processed as expected, but the flow log may associate it with a platform rule instead of a user‑defined rule.
+
+#### Does the presence of platform rules affect traffic?
+
+No. Platform rules do not change your traffic behavior, connectivity, security posture, or performance. They only affect how certain network flows are represented in flow logs. Platform rule entries are provided for informational purposes. Excluding them from analysis does not impact how traffic is handled. If traffic appears under a platform rule and does not align with the scenarios described above, the behavior can be investigated further. In such cases, reaching out through Azure support channels is recommended so the flow logs can be reviewed in detail.
+
 ## How logging works
 
 Key properties of virtual network flow logs include: