Merge pull request #307548 from MicrosoftDocs/main

Auto Publish – main to live - 2025-10-30 05:00 UTC

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

.openpublishing.redirection.json

@@ -6029,8 +6029,11 @@
       "source_path": "articles/iot-hub-device-update/device-update-azure-real-time-operating-system.md",
       "redirect_url": "/azure/iot-hub-device-update/",
       "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/storage/container-storage/container-storage-aks-quickstart.md",
+      "redirect_url": "/azure/storage/container-storage/install-container-storage-aks",
+      "redirect_document_id": true
     }
- 
-
   ]
 }

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

@@ -39,16 +39,13 @@
         href: /azure/redis/dotnet-how-to-use-azure-redis-cache
       - name: Java app
         href: /azure/redis/java-get-started
-      - name: Java app with JCache
-        href: /azure/redis/java-redisson-get-started
       - name: Node.js app
         href: /azure/redis/nodejs-get-started
       - name: Python app
         href: /azure/redis/python-get-started
       - name: Go app
         href: /azure/redis/go-get-started
-      - name: Rust app
-        href: /azure/redis/rust-get-started
+
 
 - name: Migration 
   expanded: true
@@ -113,10 +110,7 @@
       href: /azure/redis/overview-vector-similarity
     - name: Connection resilience best practices
       href: cache-best-practices-connection.md
-    # - name: Use Azure Functions triggers and bindings
-    #   items:
-    #   - name: Create a simple Function app for Redis triggers 
-    #     href: /azure/redis/tutorial-functions-getting-started
+
 
   - name: Logs and monitoring
     items:
@@ -250,10 +244,7 @@
     items:
       - name: Vector search concepts
         href: /azure/redis/overview-vector-similarity
-      - name: Vector similarity search
-        href: /azure/redis/tutorial-vector-similarity
-      - name: Semantic caching
-        href: /azure/redis/tutorial-semantic-cache
+
   - name: ASP.NET
     items:
     - name: Use ASP.NET core output cache

articles/azure-functions/flex-consumption-how-to.md

@@ -291,7 +291,7 @@ You can use Maven to create a Flex Consumption hosted function app and required
 
 1. (Optional) Customize the Flex Consumption plan in your Maven deployment by also including these elements in the `<plugin>.<configuration>` section:             .
 
-    + `<instanceSize>` - sets the [instance memory](./flex-consumption-plan.md#instance-memory) size for the function app. The default value is `2048`.  
+    + `<instanceSize>` - sets the [instance memory](./flex-consumption-plan.md#instance-sizes) size for the function app. The default value is `2048`.  
     + `<maximumInstances>` - sets the highest value for the maximum instances count of the function app.  
     + `<alwaysReadyInstances>` - sets the [always ready instance counts](flex-consumption-plan.md#always-ready-instances) with child elements for HTTP trigger groups (`<http>`), Durable Functions groups (`<durable>`), and other specific triggers (`<my_function>`). When you set any instance count greater than zero, you're charged for these instances whether your functions execute or not. For more information, see [Billing](flex-consumption-plan.md#billing).  
 
@@ -437,7 +437,7 @@ To configure deployment settings when you create your function app in the Flex C
 Use the [`az functionapp create`] command and supply these extra options that customize deployment storage:  
 
 | Parameter | Description |
-|--|--|--|
+|--|--|
 | `--deployment-storage-name` | The name of the deployment storage account. | 
 | `--deployment-storage-container-name` | The name of the container in the account to contain your app's deployment package. | 
 | `--deployment-storage-auth-type`| The authentication type to use for connecting to the deployment storage account. Accepted values include `StorageAccountConnectionString`, `UserAssignedIdentity`, and `SystemAssignedIdentity`. |
@@ -494,7 +494,7 @@ You can't currently configure deployment storage for your app in Azure using Vis
 
 ## Configure instance memory
 
-The instance memory size used by your Flex Consumption plan can be explicitly set when you create your app. For more information about supported sizes, see [Instance memory](flex-consumption-plan.md#instance-memory).  
+The instance memory size used by your Flex Consumption plan can be explicitly set when you create your app. For more information about supported sizes, see [Instance sizes](flex-consumption-plan.md#instance-sizes).  
 
 To set an instance memory size that's different from the default when creating your app:
 
@@ -731,15 +731,29 @@ When your app is connected to Application Insights, you can better analyze your
 
    + Use "Performance" to analyze response times and dependencies
    + Use "Failures" to identify any errors occurring after migration
-   + Create custom queries in "Logs" to analyze function behavior:
+   + Create custom queries in "Logs" to analyze function behavior. For example:
 
-     ```kusto
-     // Compare success rates by instance
-     requests
-     | where timestamp > ago(7d)
-     | summarize successCount=countif(success == true), failureCount=countif(success == false) by bin(timestamp, 1h), cloud_RoleName
-     | render timechart
-     ```
+Use this query to compare success rates by instance:
+
+```kusto
+requests
+| where timestamp > ago(7d)
+| summarize successCount=countif(success == true), failureCount=countif(success == false) by bin(timestamp, 1h), cloud_RoleName
+| render timechart
+```
+
+Use this query to analyze the number of instances that were actively processing your function:
+
+```kusto
+let _startTime = ago(20m); //Adjust start time as needed
+let _endTime = now(); //Adjust end time as needed
+let bins = 1s; //Adjust bin as needed - this will give per second results
+requests 
+| where operation_Name == 'EventHubsTrigger' //Replace with the name of the function in the function app that you are analyzing
+| where timestamp between(_startTime .. _endTime)
+| make-series dcount(cloud_RoleInstance) default=0 on timestamp from _startTime to _endTime step bins
+| render columnchart
+```
 
 ### View costs
 
@@ -757,7 +771,7 @@ To view the current costs:
 
 ## Fine-tune your app
 
-The Flex Consumption plan provides several settings that you can tune to refine the performance of your app. Actual performance and costs can vary based on your app-specific workload patterns and configuration. For example, higher [memory instance sizes](./flex-consumption-plan.md#instance-memory) can improve performance for memory-intensive operations but at a higher cost per active period. 
+The Flex Consumption plan provides several settings that you can tune to refine the performance of your app. Actual performance and costs can vary based on your app-specific workload patterns and configuration. For example, higher [memory instance sizes](./flex-consumption-plan.md#instance-sizes) can improve performance for memory-intensive operations but at a higher cost per active period. 
 
 Here are some adjustments you can make to fine-tune performance versus cost:
 

articles/azure-functions/flex-consumption-plan.md

@@ -26,7 +26,7 @@ The Flex Consumption plan builds on the strengths of the serverless Consumption
 + **Virtual network support**: [Virtual network integration](#virtual-network-integration) enables your serverless app to run in a virtual network.
 + **Per-Function Scaling**: Each function in your app [scales independently based on its workload](#per-function-scaling), potentially resulting in more efficient resource allocation.
 + **Improved Concurrency Handling**: Better handling of concurrent executions with configurable concurrency settings per function.
-+ **Flexible Memory Configuration**: Flex Consumption offers multiple [instance memory](#instance-memory) size options, allowing you to optimize for your specific workload requirements.
++ **Flexible Memory Configuration**: Flex Consumption offers multiple [instance sizes](#instance-sizes) size options, allowing you to optimize for your specific workload requirements.
 
 This table helps you directly compare the features of Flex Consumption with the Consumption hosting plan:
 
@@ -45,11 +45,21 @@ For a complete comparison of the Flex Consumption plan against the Consumption p
 
 Flex Consumption expands on the traditional benefits of Consumption plan by adding support for [virtual network integration](./functions-networking-options.md#virtual-network-integration). When your apps run in a Flex Consumption plan, they can connect to other Azure services secured inside a virtual network. All while still allowing you to take advantage of serverless billing and scale, together with the scale and throughput benefits of the Flex Consumption plan. For more information, see [Enable virtual network integration](./flex-consumption-how-to.md#enable-virtual-network-integration).
 
-## Instance memory
+## Instance sizes
 
 When you create your function app in a Flex Consumption plan, you can select the memory size of the instances on which your app runs. See [Billing](#billing) to learn how instance memory sizes affect the costs of your function app. 
 
-Currently, Flex Consumption offers these instance memory size options: 512 MB, 2,048 MB, and 4,096 MB.
+Currently, Flex Consumption offers these instance size options:
+
+| Instance Memory (MB) | CPU Cores |
+|-----------------|-----------|
+| 512           | 0.25      |
+| 2048         | 1         |
+| 4096        | 2         |
+
+
+> [!NOTE]
+> The CPU core values shown are typical allocations for instances with the specified memory size. However, initial instances might be granted slightly different core allocations to improve performance.
 
 When deciding on which instance memory size to use with your apps, here are some things to consider:
 
@@ -102,7 +112,7 @@ Deployments in the Flex Consumption plan follow a single path, and there's no lo
 
 The minimum billable execution period for both execution modes is 1,000 ms. Past that, the billable activity period is rounded up to the nearest 100 ms. You can find details on the Flex Consumption plan billing meters in the [Monitoring reference](monitor-functions-reference.md?tab=flex-consumption-plan#metrics).
 
-For details about how costs are calculated when you run in a Flex Consumption plan, including examples, see [Consumption-based costs](functions-consumption-costs.md?tabs=flex-consumtion-plan#consumption-based-costs).   
+For details about how costs are calculated when you run in a Flex Consumption plan, including examples, see [Consumption-based costs](functions-consumption-costs.md?tabs=flex-consumption-plan#consumption-based-costs) and [Viewing cost-related data](functions-consumption-costs.md?tabs=flex-consumption-plan#viewing-and-estimating-costs-from-metrics).
 
 ## Supported language stack versions
 
@@ -122,9 +132,9 @@ This table shows the language stack versions that are currently supported for Fl
 
 ## Regional subscription memory quotas
 
-The Flex Consumption plan has a memory-based quota that limits how much compute all your Flex Consumption apps can use at the same time in a specific region and subscription. Imagine you have a bucket of memory measured in GB for your entire subscription in a region. All your Flex Consumption apps in that region share this bucket. If your Flex Consumption apps try to use more than the quota allows, some executions may be delayed or throttled from scaling, but you won’t be blocked from creating or deploying apps.
+The Flex Consumption plan has a memory-based quota that limits how much compute all your Flex Consumption apps can use at the same time in a specific region and subscription. Imagine you have a bucket of memory measured in GB or CPU cores for your entire subscription in a region. All your Flex Consumption apps in that region share this bucket. If your Flex Consumption apps try to use more than the quota allows, some executions may be delayed or throttled from scaling, but you won’t be blocked from creating or deploying apps.
 
-Currently, each region in a given subscription has a default memory limit quota of `512,000 MB` for all instances of apps running on Flex Consumption plans. This quota means that, in a given subscription and region, you could have any combination of instance memory sizes and counts, as long as they stay under the quota limit. For example, each the following examples would mean the quota is reached and the apps would stop scaling:
+Currently, each region in a given subscription has a default quota of the lesser of either `512,000 MB` or 250 cores for all instances of apps running on Flex Consumption plans. These quotas mean that, in a given subscription and region, you could have any combination of instance memory sizes and counts, as long as they stay under the quota limits. For example, in each of these scenarios the quota is reached, and apps in the region stops scaling:
 
 + You have one 512-MB app scaled to 250 instances and a second 512-MB app scaled to 750 instances. 
 + You have one 512-MB app scaled to 1,000 instances.

articles/azure-functions/functions-concurrency.md

@@ -50,7 +50,7 @@ For trigger types that support concurrency configuration, the concurrency settin
 
 _Applies only to the Flex Consumption plan_ 
 
-HTTP trigger concurrency is a special type of fixed per-instance concurrency. In HTTP trigger concurrency, the default concurrency also depends on the [instance memory size](./flex-consumption-plan.md#instance-memory).
+HTTP trigger concurrency is a special type of fixed per-instance concurrency. In HTTP trigger concurrency, the default concurrency also depends on the [instance size](./flex-consumption-plan.md#instance-sizes).
 
 The Flex Consumption plan scales all HTTP trigger functions together as a group. For more information, see [Per-function scaling](event-driven-scaling.md#per-function-scaling).