Merge pull request #304007 from MicrosoftDocs/main

learn-build-service-prod[bot] · web-flow · commit 9a74eabf1329 · 2025-08-08T05:13:18.000Z
Auto Publish – main to live - 2025-08-08 05:00 UTC
diff --git a/articles/application-gateway/for-containers/understanding-pricing.md b/articles/application-gateway/for-containers/understanding-pricing.md
@@ -32,13 +32,8 @@ Application Gateway for Containers consists of four billable items:
 - Association resource 
 - Capacity units
 
-When Web Application Firewall is enabled two more billable items are added:
-
-- Web Application Firewall resource
-- Requests processed by WAF
-
->[!Note]
->The Web Application Firewall resource is only billed once per Application Gateway for Containers resource. For example, if you have five Web Application Firewall Policies assigned to five Application Gateway for Containers' security policies, only one Web Application Firewall resource will be metered.
+> [!NOTE]
+> Currently, there's no additional charge to enable Web Application Firewall (WAF) on Application Gateway for Containers beyond the added capacity units required to process requests.
 
 #### Application Gateway for Containers hour
 
@@ -180,51 +175,6 @@ Pricing calculation:
 * 3 Capacity Units x $0.008 x 730 hours = $17.52
 * Total = $124.83
 
-### Example 6 - Web Application Firewall
-
-This example assumes Application Gateway for Containers has load raising the number of capacity units and has a Web Application Firewall (WAF) policy reference to an Application Gateway for Containers' security policy. The WAF policy is configured with both DRS 2.1 and bot manager rulesets. This WAF policy also has four custom rules enabled which do not incur any additional charges
-
-*	1 Application Gateway for Containers resource
-*	1 frontend resource
-*	1 association resource
-*	1 security policy resources (non-billable)
-*	8 capacity units
-*	1 WAF policy running a default ruleset and a bot manager ruleset
-*	4 WAF custom rules
-*	10 million requests processed by WAF
-
-Pricing calculation:
-
-*	1 Application Gateway for Containers x $0.017 x 730 hours = $12.41
-*	1 Frontend x $0.01 x 730 hours = $7.30
-*	1 Association x $0.12 x 730 hours = $87.60
-*	8 Capacity Units x $0.008 x 730 hours = $46.72
-*	WAF enablement x $0.068 x 730 hours = $49.64
-*	10 one million requests (10) x $0.75 x 2 WAF rulesets (DRS 2.1 and Bot Manager) = $15
-*	Total = $218.67
-
-### Example 7 - Web Application Firewall - Multiple Policies
-
-This example assumes Application Gateway for Containers has load raising the number of capacity units and has three Web Application Firewall (WAF) policy reference to three corresponding Application Gateway for Containers' security policies. One policy is configured with both DRS 2.1, bot manager rulesets and 3 custom rules, the other two policies only have DRS 2.1 ruleset and no custom rules.
-
-*	1 Application Gateway for Containers resource
-*	1 frontend resource
-*	1 association resource
-*	3 security policy resources (non-billable)
-*	8 Capacity Units
-*	1 WAF policy running a default ruleset, a bot manager ruleset and three custom rules
-*	10 million requests processed by WAF
-
-Pricing calculation:
-
-*	1 Application Gateway for Containers x $0.017 x 730 hours = $12.41
-*	1 Frontend x $0.01 x 730 hours = $7.30
-*	1 Association x $0.12 x 730 hours = $87.60
-*	8 Capacity Units x $0.008 x 730 hours = $46.72
-*	WAF enablement x $0.068 x 730 hours = $49.64
-*	10 million requests (10) x $0.75 x 2 WAF rulesets (DRS 2.1 and Bot Manager) = $15
-*	Total = $218.67
-
 ## Next steps
 
 See the following articles to learn more about how pricing works in Application Gateway for Containers by visiting the Application Gateway pricing pages:
diff --git a/articles/cloud-services-extended-support/cloud-services-guestos-microsoft-security-response-center-releases.md b/articles/cloud-services-extended-support/cloud-services-guestos-microsoft-security-response-center-releases.md
@@ -3,12 +3,12 @@ title: List of updates applied to the Azure Guest OS | Microsoft Docs
 description: This article lists the Microsoft Security Response Center updates applied to different Azure Guest OS. See if an update applies to your Guest OS.
 services: cloud-services
 ms.subservice: guest-os-patching
-author: aschoksh
+author: jejackson
 ms.assetid: d0a272a9-ed01-4f4c-a0b3-bd5e841bdd77
 ms.service: azure-cloud-services-classic
 ms.topic: concept-article
-ms.date: 06/06/2025
-ms.author: aschoksh
+ms.date: 08/07/2025
+ms.author: jejackson
 ms.custom: compute-evergreen
 ---
 
@@ -19,6 +19,36 @@ ms.custom: compute-evergreen
 
 The following tables show the Microsoft Security Response Center (MSRC) updates applied to the Azure Guest OS. Search this article to determine if a particular update applies to your Guest OS. Updates always carry forward for the particular [family][family-explain] they were introduced in.
 
+## July 2025 Guest OS
+| Product Category | Parent KB Article | Vulnerability Description | Guest OS | Date First Introduced |
+| --- | --- | --- | --- | --- |
+| Rel 25-07 | [5062560] | Latest Cumulative Update(LCU) | [5.108] | 08-Jul-25
+| Rel 25-07 | [5062557] | Latest Cumulative Update(LCU) | [6.84] | 08-Jul-25
+| Rel 25-07 | [5062572] | Latest Cumulative Update(LCU) | [7.54] | 08-Jul-25
+| Rel 25-07 | [5049608] | .NET Framework DotNet | [6.84] | 14-Jan-25
+| Rel 25-07 | [5049614] | .NET Framework 4.8 Security and Quality Rollup LKG | [5.108] | 14-Jan-25
+| Rel 25-07 | [5049617] | .NET Framework 4.8 Security and Quality Rollup LKG | [7.54] | 14-Jan-25
+| Rel 25-07 | [5062799] | Servicing Stack Update | [5.108] | 08-Jul-25
+| Rel 25-07 | [5062557] | Servicing Stack Update | [6.84] | 08-Jul-25
+| Rel 25-07 | [5062572] | Servicing Stack Update | [7.54] | 08-Jul-25
+| Rel 25-07 | [4494175] | January '20 Microcode | [5.108] | 01-Sep-20
+| Rel 25-07 | [4494175] | January '20 Microcode | [6.84] | 01-Sep-20
+
+[5062560]: https://support.microsoft.com/kb/5062560
+[5062557]: https://support.microsoft.com/kb/5062557
+[5062572]: https://support.microsoft.com/kb/5062572
+[5049614]: https://support.microsoft.com/kb/5049614
+[5049608]: https://support.microsoft.com/kb/5049608
+[5049617]: https://support.microsoft.com/kb/5049617
+[5062799]: https://support.microsoft.com/kb/5062799
+[5062557]: https://support.microsoft.com/kb/5062557
+[5062572]: https://support.microsoft.com/kb/5062572
+[4494175]: https://support.microsoft.com/kb/4494175
+
+[5.108]: ./cloud-services-guestos-update-matrix.md#family-5-releases
+[6.84]: ./cloud-services-guestos-update-matrix.md#family-6-releases
+[7.54]: ./cloud-services-guestos-update-matrix.md#family-7-releases
+
 ## June 2025 Guest OS
 | Product Category | Parent KB Article | Vulnerability Description | Guest OS | Date First Introduced |
 | --- | --- | --- | --- | --- |
diff --git a/articles/cloud-services-extended-support/cloud-services-guestos-update-matrix.md b/articles/cloud-services-extended-support/cloud-services-guestos-update-matrix.md
@@ -3,12 +3,12 @@ title: Learn about the latest Azure Guest OS Releases | Microsoft Docs
 description: The latest release news and SDK compatibility for Azure Cloud Services Guest OS.
 services: cloud-services
 ms.subservice: guest-os-patching
-author: aschoksh
+author: jejackson
 ms.assetid: 6306cafe-1153-44c7-8554-623b03d59a34
 ms.service: azure-cloud-services-classic
 ms.topic: concept-article
-ms.date: 06/06/2025
-ms.author: aschoksh
+ms.date: 08/07/2025
+ms.author: jejackson
 ms.custom: compute-evergreen
 # Customer intent: As a cloud services administrator, I want to stay updated on the latest Guest OS releases and their compatibility, so that I can plan timely upgrades and ensure my applications remain secure and functional before any deprecation deadlines.
 ---
@@ -39,6 +39,9 @@ Unsure about how to update your Guest OS? Check [this][cloud updates] out.
 
 ## News updates
 
+###### **July 30, 2025**
+The July 2025 Guest OS released.
+
 ###### **July 6, 2025**
 The June 2025 Guest OS released.
 
@@ -294,10 +297,11 @@ The September Guest OS released.
 
 | Configuration string | Release date | Disable date |
 | --- | --- | --- |
+|  WA-GUEST-OS-7.54_202507-01 |  July 30, 2025  |  Post 7.57  |
 |  WA-GUEST-OS-7.53_202506-01 |  July 6, 2025  |  Post 7.56  |
 |  WA-GUEST-OS-7.52_202505-01 |  June 4, 2025  |  Post 7.55  |
-|  WA-GUEST-OS-7.51_202504-01 |  May 1, 2025  |  Post 7.54  |
-|~~WA-GUEST-OS-7.50_202503-01~~|  March 28, 2025  |  Post 7.53  |
+|~~WA-GUEST-OS-7.51_202504-01~~|  May 1, 2025  |  July 30, 2025  |
+|~~WA-GUEST-OS-7.50_202503-01~~|  March 28, 2025  |  July 6, 2025  |
 |~~WA-GUEST-OS-7.49_202502-01~~|  February 26, 2025  |  June 4, 2025  |
 |~~WA-GUEST-OS-7.48_202501-01~~|  February 5, 2025  |  May 1, 2025  |
 |~~WA-GUEST-OS-7.47_202411-01~~|  January 17, 2025  |  March 28, 2025  |
@@ -352,10 +356,11 @@ The September Guest OS released.
 
 | Configuration string | Release date | Disable date |
 | --- | --- | --- |
+|  WA-GUEST-OS-6.84_202507-01 |  July 30, 2025  |  Post 6.87  |
 |  WA-GUEST-OS-6.83_202506-01 |  July 6, 2025  |  Post 6.86  |
 |  WA-GUEST-OS-6.82_202505-01 |  June 4, 2025  |  Post 6.85  |
-|  WA-GUEST-OS-6.81_202504-01 |  May 1, 2025  |  Post 6.84  |
-|~~WA-GUEST-OS-6.80_202503-01~~|  March 28, 2025  |  Post 6.83  |
+|~~WA-GUEST-OS-6.81_202504-01~~|  May 1, 2025  |  July 30, 2025  |
+|~~WA-GUEST-OS-6.80_202503-01~~|  March 28, 2025  |  July 6, 2025  |
 |~~WA-GUEST-OS-6.79_202502-01~~|  February 26, 2025  |  June 4, 2025  |
 |~~WA-GUEST-OS-6.78_202501-01~~|  February 5, 2025  |  May 1, 2025  |
 |~~WA-GUEST-OS-6.77_202411-01~~|  January 17, 2025  |  March 28, 2025  |
@@ -444,10 +449,11 @@ The September Guest OS released.
 
 | Configuration string | Release date | Disable date |
 | --- | --- | --- |
+|  WA-GUEST-OS-5.108_202507-01 |  July 30, 2025  |  Post 5.110  |
 |  WA-GUEST-OS-5.107_202506-01 |  July 6, 2025  |  Post 5.109  |
 |  WA-GUEST-OS-5.106_202505-01 |  June 4, 2025  |  Post 5.108  |
-|  WA-GUEST-OS-5.105_202504-01 |  May 1, 2025  |  Post 5.107  |
-|~~WA-GUEST-OS-5.104_202503-01~~|  March 28, 2025  |  Post 5.107  |
+|~~WA-GUEST-OS-5.105_202504-01~~|  May 1, 2025  |  July 30, 2025  |
+|~~WA-GUEST-OS-5.104_202503-01~~|  March 28, 2025  |  July 6, 2025  |
 |~~WA-GUEST-OS-5.103_202502-01~~|  February 26, 2025  |  June 4, 2025  |
 |~~WA-GUEST-OS-5.102_202501-01~~|  February 5, 2025  |  May 1, 2025  |
 |~~WA-GUEST-OS-5.101_202411-01~~|  January 17, 2025  |  March 28, 2025  |
diff --git a/articles/communication-services/concepts/service-limits.md b/articles/communication-services/concepts/service-limits.md
@@ -321,7 +321,11 @@ When you send or receive a high volume of requests, you might receive a ```Throt
 
 | Operation | Scope | Time frame (seconds) | Limit (number of requests) | Timeout in seconds |
 | --- | --- | --- | --- | --- |
-| General requests | Per resource | 10 | 1,000 | 10 |
+| General requests | Per resource | 10 | 3,000 | 5 |
+| Get Jobs (Route-Level Throttling) | Per resource | 10 | 332 | 5 |
+| Get Queue Statistics (Route-Level Throttling) | Per resource | 10 | 166 | 5 |
+| Get In-Queue Position (Route-Level Throttling) | Per resource | 10 | 166 | 5 |
+| Get Workers (Route-Level Throttling) | Per resource | 10 | 332 | 5 |
 
 ### Action to take
 
diff --git a/articles/cost-management-billing/manage/mca-setup-account.md b/articles/cost-management-billing/manage/mca-setup-account.md
@@ -6,7 +6,7 @@ ms.reviewer: jkinma
 ms.service: cost-management-billing
 ms.subservice: billing
 ms.topic: how-to
-ms.date: 05/22/2025
+ms.date: 08/06/2025
 ms.author: jkinma
 ---
 
@@ -239,7 +239,7 @@ Access to Azure resources that was set using Azure role-based access control (Az
 
 ### Azure reservations and savings plans
 
-Any Azure reservations and savings plan in your Enterprise Agreement enrollment are moved to your new billing account. During the transition, there are no changes to the reservation discounts that are being applied to your subscriptions. If you have a savings plan that's getting transferred and it was purchased in USD, there are no changes to the saving plan discounts.
+Any Azure reservations and savings plan in your Enterprise Agreement enrollment are moved to your new billing account. During the transition, there are no changes to the reservation discounts that are being applied to your subscriptions. If you have a savings plan that's getting transferred and it was purchased in USD, there are no changes to the saving plan discounts. For more details, refer to the **Changes after migration** section below. 
 
 ### Savings plan transfers with a non-USD billing currency
 
@@ -262,7 +262,16 @@ Close the Exchange savings plan page and then select the **I have viewed and agr
 
 ### Azure Marketplace products
 
-Any Azure Marketplace consumption-based products in your Enterprise agreement enrollment are moved along with the subscriptions. There are no changes to the service access of the Marketplace products during the transition. Purchases continue to remain in the source agreement.
+When you transfer a subscription from an Enterprise Agreement to a Microsoft Customer Agreement, Marketplace purchases transfer with it when the following conditions are met: 
+
+- The Marketplace purchase in the EA subscription must be active. 
+
+- The Marketplace purchase must pass all eligibility checks before transfer. For example, the purchase must be available for use in the target agreement. 
+    - Marketplace private offer purchased under EA in Netherland cannot be transferred to the MCA-E billing account in US, as the eligibility check fails for this scenario. 
+
+- All other assets in the source subscription must also be able to successfully be transferred. Otherwise, the transfer fails. 
+
+- Please note Marketplace purchased through AppSource is not associated with any subscription, and cannot be transferred with this method. 
 
 ### Support plan
 
@@ -400,7 +409,7 @@ Enterprise administrators and department administrators are listed as invoice se
 - Cost Management using third-party providers like Cloud health and Cloud easier - Organizations transitioning to MCA need to update their provider that they're transitioning to MCA. Most of them have a documented process to pull the MCA cost data.
 - Historical data – It isn’t available to account owners or users with the Subscription owner Azure role-based access control (RBAC) role after migration. Access for existing users, groups, or service principals that was assigned using [Azure role-based access control (Azure RBAC)](../../role-based-access-control/overview.md) isn't affected during the transition.
     - Cost data transition - Cost data before the transition remains in the EA scope. It doesn't move to the MCA scope. You can access the data by switching scopes.
-- Reservations - When there's a currency change during or after an enrollment transfer, reservations paid for monthly are canceled for the source enrollment. Cancellation happens at the time of the next monthly payment for an individual reservation. The cancellation is intentional and only affects monthly reservation purchases. You can repurchase them after migration.
+- Reservations - When there's a currency change during or after an enrollment transfer, reservations paid for monthly are canceled for the source enrollment. Cancellation happens at the time of the next monthly payment for an individual reservation. The cancellation is intentional and only affects monthly reservation purchases. You can repurchase them after migration. **Reservations cancellations triggered by this migration do not count toward the cancellation threshold of USD 50,000 within a rolling 12-month window**. For the cancellation policy, please refer to [Self-service exchanges and refunds for Azure Reservations](../reservations/exchange-and-refund-azure-reservations.md) 
 - Savings Plans - If they were purchased in a non-USD currency, they get canceled during migration. You can repurchase them after migration.
 - API changes - API endpoints differ between EA and MCA. Existing EA API calls don't work with MCA. You need to use Microsoft Cost Management APIs instead if using consumption APIs. For more information, see:
     - [Migrate EA to Microsoft Customer Agreement APIs](../costs/migrate-cost-management-api.md)
diff --git a/articles/redis/best-practices-performance.md b/articles/redis/best-practices-performance.md
@@ -61,7 +61,7 @@ Fortunately, several tools exist to make benchmarking Redis easier. Two of the m
 Prepare the cache instance with data required for the testing. Loading the instance with data ensures that the results more accurately reflect real-world conditions. The `{number-of-keys}` parameter should be determined by the size of your AMR instance and the size of each key. A good rule of thumb is to fill up the instance roughly 75% full, accounting for buffers. You can use this formula: `numberOfKeysToSet = (<TotalCacheSizeInBytes> * 0.75) / (1024 + 300)`. For example, if you're benchmarking on a Compute Optimized X3 instance, using 1,024-byte key sizes, as shown previously, that implies `{number-of-keys} = (3 * 1000000000 * 0.75) / (1024 + 300)`. The result equals approximately 1,699,396 keys.
 
 ```bash
-memtier_benchmark -h {your-cache-name}.{region}.redis.azure.net -p 10000 -a {your-access-key} --hide-histogram --pipeline=10 -clients=50 -threads=6 --key-maximum=1699396 -n allkeys --key-pattern=P:P --ratio=1:0 -data-size=1024 --tls --cluster-mode
+memtier_benchmark -h {your-cache-name}.{region}.redis.azure.net -p 10000 -a {your-access-key} --hide-histogram --pipeline=10 --clients=50 --threads=6 --key-maximum=1699396 -n allkeys --key-pattern=P:P --ratio=1:0 --data-size=1024 --tls --cluster-mode
 ```
 
 >[!NOTE]
@@ -71,7 +71,7 @@ memtier_benchmark -h {your-cache-name}.{region}.redis.azure.net -p 10000 -a {you
 This command tests pipelined GET requests with 1k payload. Use this command to test how much read throughput to expect from your cache instance. This example assumes you're using TLS and the OSS cluster policy. The `--key-pattern=R:R` parameter ensures that keys are randomly accessed, increasing the realism of the benchmark. This test runs for five minutes.
 
 ```bash
-memtier_benchmark -h {your-cache-name}.{region}.redis.azure.net -p 10000 -a {your-access-key} --hide-histogram --pipeline=10 -clients=50 -threads=6 -d 1024 --key-maximum=1699396 --key-pattern=R:R --ratio=0:1 --distinct-client-seed --test-time=300 --json-out-file=test_results.json --tls --tls-skip-verify --cluster-mode
+memtier_benchmark -h {your-cache-name}.{region}.redis.azure.net -p 10000 -a {your-access-key} --hide-histogram --pipeline=10 --clients=50 --threads=6 -d 1024 --key-maximum=1699396 --key-pattern=R:R --ratio=0:1 --distinct-client-seed --test-time=300 --json-out-file=test_results.json --tls --tls-skip-verify --cluster-mode
 ```
 
 ## Example performance benchmark data
@@ -90,7 +90,7 @@ The table below shows optimal throughput that we observed while testing various
 Azure Managed Redis offers a choice of cluster policy: _Enterprise_ and _OSS_. Enterprise cluster policy is a simpler configuration that doesn't require the client to support clustering. OSS cluster policy, on the other hand, uses the [Redis cluster protocol](https://redis.io/docs/management/scaling) to support higher throughput. We recommend using OSS cluster policy in most cases, especially when you require high performance. For more information, see [Clustering](architecture.md#clustering).
 
 
-| Size in GB | Memory Optimized | Balanced| Compute Optimized| 
+| Size in GB | GET requests per second for Memory Optimized | GET requests per second for Balanced | GET requests per second for Compute Optimized | 
 |--|--|--|--|
 |0.5| - | 120,000| - |
 |1| - | 120,000| - | 
diff --git a/articles/reliability/availability-zones-service-support.md b/articles/reliability/availability-zones-service-support.md
