azure-managed-redis-articles

lisalozano · lisalozano · commit 323166301ac1 · 2026-03-20T15:59:23.000-06:00
diff --git a/articles/redis/how-to-upgrade.md b/articles/redis/how-to-upgrade.md
@@ -1,5 +1,5 @@
 ---
-title: Upgrade your Redis Version in Azure Managed Redis
+title: Upgrade Your Redis Version in Azure Managed Redis
 description: Learn how to upgrade your Redis version in Azure Managed Redis.
 ms.date: 05/18/2025
 ms.topic: how-to
@@ -12,7 +12,7 @@ appliesto:
 
 # Upgrade the Redis version of your Azure Managed Redis instance
 
-There are frequent releases of new versions of Redis server software that include new features, more commands, and stability improvements. By maintaining your Azure Managed Redis instance with the latest version of Redis, you can ensure the best possible experience.
+New versions of Redis server software are frequently released with new features, more commands, and stability improvements. By maintaining your Azure Managed Redis instance with the latest version of Redis, you can ensure the best possible experience.
 
 This article details how to upgrade your Redis instance in Azure Managed Redis to the latest available version.
 
@@ -31,13 +31,13 @@ These Redis versions are available for each tier.
 
 ## Upgrade options
 
-You can choose from automatic or manual upgrades. Automatic upgrades are part of the standard patching process. You can use the manual process to start upgrades that are available outside the normal automatic process.
+You can choose from automatic or manual upgrades. Automatic upgrades are part of the standard patching process. With the manual process, you can start upgrades that are available outside of the normal automatic process.
 
 ### Automatic upgrades
 
 Redis server version upgrades are made automatically as a part of the standard monthly patching process. Upgrades to the latest version of Redis occur when that Redis version reaches general availability (GA) on Azure.
 
-When a new version becomes generally available, your Redis instance is automatically upgraded to the new version unless you defer it ahead of time. For more information on deferring an upgrade, go to [Upgrade deferment](#defer-upgrades).
+When a new version becomes generally available, your Redis instance is automatically upgraded to the new version unless you defer it ahead of time. For more information on deferring an upgrade, see [Upgrade deferment](#defer-upgrades) in this article.
 
 ### Manual upgrades
 
@@ -46,20 +46,21 @@ You can also choose to manually upgrade to the latest Redis version. Manual upgr
 - You control when the upgrade occurs.
 - You can upgrade to preview releases of Redis.
 
-1. In the portal, use the **Resource** menu to go to **Overview**. Select **Upgrade**.
-
    > [!WARNING]
    > After you upgrade your Redis instance, you can't downgrade it to the previous version.
-   >
+
+1. In the portal, use the **Resource** menu to go to **Overview**. Select **Upgrade**.
 
    :::image type="content" source="media/how-to-upgrade/managed-redis-upgrade-overview.png" alt-text="Screenshot that shows the Upgrade pane, the current version, and the available version." :::
 
-1. You see an **Upgrading Redis** pane that displays the current Redis version, and the versions that you can upgrade to. To confirm and begin the upgrade process, select **Start upgrade**. (If you're already running the latest available version of Redis software, the **Start upgrade** button is disabled.)
+1. An **Upgrading Redis** pane displays the current Redis version and the versions that you can upgrade to. To confirm and begin the upgrade process, select **Start upgrade**. (If you're already running the latest available version of Redis software, the **Start upgrade** button is unavailable.)
 
    :::image type="content" source="media/how-to-upgrade/managed-redis-upgrade-pane.png" alt-text="Screenshot that shows Overview on the Resource menu and the Upgrade Redis pane.":::
 
 ### <a name = "defer-upgrades"></a> Upgrade deferment
 
+You can defer an automatic upgrade of a new version of Redis software for up to 90 days. This option gives you time to test new versions and ensure that everything works as expected. The cache is upgraded either 90 days after the new Redis version reaches GA, or whenever you manually trigger the upgrade.
+
 To prevent an automatic upgrade, select the deferral option before a new Redis version reaches GA.
 
 Go to **Advanced settings** on the **Resource** menu, and select the box for **Defer Redis DB version updates**.
@@ -71,14 +72,12 @@ Go to **Advanced settings** on the **Resource** menu, and select the box for **D
 
 ## Pre-upgrade considerations
 
-We intend for each new Redis version to be a seamless upgrade from previous versions and we design for backwards compatibility. However, small changes and bug fixes do occur, which can cause application changes. You should keep these changes in mind.
+Each new Redis version is intended to be a seamless upgrade from previous versions with backward compatibility as a design principle. However, small changes and bug fixes do occur, which can cause application changes. You should keep these changes in mind.
 
 ### Client version
 
-When you use an outdated Redis client, new commands or Redis features aren't properly supported. We always recommend that you update to the latest stable version of your Redis client, as newer versions often have stability and performance improvements. For more information on configuring your client library, see [Best practices using client libraries](best-practices-client-libraries.md).
+When you use an outdated Redis client, new commands or Redis features aren't properly supported. We always recommend that you update to the latest stable version of your Redis client, because newer versions often have stability and performance improvements. For more information on configuring your client library, see [Best practices using client libraries](best-practices-client-libraries.md).
 
 ### Breaking changes
 
-Each version of Redis often has a few minor bug fixes that can present breaking changes. If you have concerns, we recommend reviewing the Redis 7.4 release notes before you upgrade your Redis version:
-
-- [Redis 7.4 release notes](https://raw.githubusercontent.com/redis/redis/7.4/00-RELEASENOTES)
+Each version of Redis often has a few minor bug fixes that can present breaking changes. If you have concerns, we recommend reviewing the [Redis 7.4 release notes](https://raw.githubusercontent.com/redis/redis/7.4/00-RELEASENOTES) before you upgrade your Redis version.
diff --git a/articles/redis/reserved-pricing.md b/articles/redis/reserved-pricing.md
@@ -104,33 +104,41 @@ To buy a reservation:
 ### Use the Azure portal to buy reservations
 
 1. In the Azure portal, search for and select **Reservations** > **Add**. You can also go to the [Purchase reservations](https://portal.azure.com/#blade/Microsoft_Azure_Reservations/CreateBlade/) page.
+
 1. On the **Purchase reservations** page, select **Azure Cache for Redis and Managed Redis**.
+
 1. On the **Select the product you want to purchase** pane, select your chosen options for **Scope** and **Subscription**.
+
 1. Select your chosen values from the dropdown menus for **Region**, **Term**, and **Billing frequency**.
 
 The following list describes the form fields in detail.
 
-- **Subscription**: The subscription you use to pay for the reservation. The subscription type must be either:
+- **Subscription**: The subscription that you use to pay for the reservation. The subscription type must be either:
   - **EA**: Offer numbers MS-AZR-0017P or MS-AZR-0148P. The charges are deducted from the enrollment's Azure prepayment balance or charged as overage.
   - **An individual agreement with pay-as-you-go pricing**: Offer numbers MS-AZR-0003P or MS-AZR-0023P. The charges are billed to the subscription's credit card or invoice.
 - **Scope**: The reservation's scope, one of the following options:
-  - **Shared**: This applies the reservation discount to cache instances in any subscriptions in your billing context. For EA, the shared scope is the enrollment and includes subscriptions within the enrollment. For pay-as-you-go, the shared scope is all of the pay-as-you-go subscriptions created by the account administrator.
-  - **Single subscription**: This applies the reservation discount to cache instances in this subscription.
-  - **Single resource group**: This applies the reservation discount to instances in the selected resource group within the subscription.
-  - **Management group**: This applies the reservation discount to matching resources in subscriptions that are a part of both the management group and billing scope.
+  - **Shared**: Applies the reservation discount to cache instances in any subscriptions in your billing context. For EA, the shared scope is the enrollment and includes subscriptions within the enrollment. For pay-as-you-go, the shared scope is all of the pay-as-you-go subscriptions that the account administrator created.
+  - **Single subscription**: Applies the reservation discount to cache instances in this subscription.
+  - **Single resource group**: Applies the reservation discount to instances in the selected resource group within the subscription.
+  - **Management group**: Applies the reservation discount to matching resources in subscriptions that are a part of both the management group and billing scope.
 - **Region**: The Azure region for the reservation.
-- **Term**: You can select **1 year** or **3 years**.
-- **Billing frequency**: You can select **Monthly** or **Upfront**.
-- **Recommended quantity**: The number of nodes that we recommend you reserve in the selected Azure region, tier, and scope. Select **See details** for details about recommended quantities.
+- **Term**: **1 year** or **3 years**.
+- **Billing frequency**: **Monthly** or **Upfront**.
+- **Recommended quantity**: The recommended number of nodes to reserve in the selected Azure region, tier, and scope. For information about the recommended quantities, select **See details**.
 
-The reservation discount is applied to existing or new caches that match the attributes you select. The actual number of instances that get the discount depends on the scope and quantity you select.
+Existing or new caches that match the attributes that you select get the reservation discount. The actual number of instances that get the discount depends on the scope and quantity you select.
 
 1. Select the reservation you want. Note the amount for **Monthly price per node** and the estimated savings.
+
 1. Select **Add to cart**, and then select **View cart** to close the product list pane.
+
 1. On the **Purchase reservations** page, review the reservation details.
+
 1. **Auto-renew** is set to **On** by default, and automatically renews your reservation at the end of the term. You can change it to **Off** at any time before the end of the term.
+
 1. Select **Next: Review + buy**.
-1. Review the details of the following fields: **Additional notes**, **Today's charge**, and **Total cost**. Then select **Buy now**.
+
+1. Review the details for **Additional notes**, **Today's charge**, and **Total cost**. Then select **Buy now**.
 
 You can update the scope of the reservation through the Azure portal, PowerShell, the Azure CLI, or the API.
 
