Merge pull request #304352 from MicrosoftDocs/main

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

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

articles/azure-cache-for-redis/cache-best-practices-performance.md

@@ -7,7 +7,7 @@ description: Learn how to test the performance of Azure Cache for Redis.
 ms.topic: conceptual
 ms.custom:
   - ignite-2024
-ms.date: 11/08/2024
+ms.date: 08/18/2025
 appliesto:
   - ✅ Azure Cache for Redis
 ---
@@ -16,7 +16,7 @@ appliesto:
 
 Testing the performance of a Redis instance can be a complicated task. The performance of a Redis instance can vary based on parameters such as the number of clients, the size of data values, and whether pipelining is being used. There also can be a tradeoff between optimizing throughput or latency.
 
-Fortunately, several tools exist to make benchmarking Redis easier. Two of the most popular tools are **[redis-benchmark](https://redis.io/docs/management/optimization/benchmarks/)** and **[memtier-benchmark](https://github.com/redislabs/memtier_benchmark)**. This article focuses on redis-benchmark.
+Fortunately, several tools exist to make benchmarking Redis easier. Two of the most popular tools are **[redis-benchmark](https://redis.io/docs/latest/operate/oss_and_stack/management/optimization/benchmarks/)** and **[memtier-benchmark](https://github.com/redislabs/memtier_benchmark)**. This article focuses on redis-benchmark.
 
 ## How to use the redis-benchmark utility
 
@@ -34,7 +34,7 @@ Fortunately, several tools exist to make benchmarking Redis easier. Two of the m
 
 1. If you're using an Azure Cache for Redis instance that uses [clustering](cache-how-to-scale.md), you need to add the `--cluster` parameter to your `redis-benchmark` command. Enterprise tier caches using the Enterprise [Clustering](../redis/architecture.md#clustering) can be treated as nonclustered caches and don't need this setting.
 
-1. Launch `redis-benchmark` from the CLI or shell of the VM. For instructions on how to configure and run the tool, see the [redis-benchmark documentation](https://redis.io/docs/management/optimization/benchmarks/) and the [redis-benchmark examples](#redis-benchmark-examples) sections.
+1. Launch `redis-benchmark` from the CLI or shell of the VM. For instructions on how to configure and run the tool, see the [redis-benchmark documentation](https://redis.io/docs/latest/operate/oss_and_stack/management/optimization/benchmarks/) and the [redis-benchmark examples](#redis-benchmark-examples) sections.
 
 ## Benchmarking recommendations
 
@@ -178,7 +178,7 @@ memtier_benchmark -h {your-cache-name}.{region}.redis.azure.net -p 10000 -a {you
 
 #### Enterprise & Enterprise Flash tiers
 
-The Enterprise and Enterprise Flash tiers offer 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 throughputs. We recommend using OSS cluster policy in most cases. For more information, see [Clustering](../redis/architecture.md#clustering) . Benchmarks for both cluster policies are shown in the following tables.
+The Enterprise and Enterprise Flash tiers offer 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/latest/operate/oss_and_stack/management/scaling/) to support higher throughputs. We recommend using OSS cluster policy in most cases. For more information, see [Clustering](../redis/architecture.md#clustering) . Benchgement/scalingmarks for both cluster policies are shown in the following tables.
 
 The following configuration was used to benchmark throughput for the Enterprise and Enterprise flash tiers:
 

articles/azure-cache-for-redis/cache-how-to-redis-cli-tool.md

@@ -5,21 +5,21 @@ description: Learn how to use redis-cli as a command-line tool for interacting w
 
 
 ms.topic: how-to
-ms.date: 04/04/2025
+ms.date: 08/18/2025
 appliesto:
   - ✅ Azure Cache for Redis
 ---
 # Use the Redis command-line tool with Azure Cache for Redis
 
-This article describes how to use the [redis-cli command-line interface](https://redis.io/docs/connect/cli/) to interact with Azure Cache for Redis as a client. You can use *redis-cli* to directly interact with your Azure Redis cache instance, and for debugging and troubleshooting.
+This article describes how to use the [redis-cli command-line interface](https://redis.io/docs/latest/operate/rs/references/cli-utilities/redis-cli/#connect-to-a-database) to interact with Azure Cache for Redis as a client. You can use *redis-cli* to directly interact with your Azure Redis cache instance, and for debugging and troubleshooting.
 
 ## Prerequisite
 
 Access to an Azure Cache for Redis server instance.
 
 ## Install redis-cli
 
-The redis-cli tool installs automatically with the Redis package, which is available for Linux, macOS, and Windows. For detailed installation instructions, see the open-source [Redis documentation](https://redis.io/docs).
+The redis-cli tool installs automatically with the Redis package, which is available for Linux, macOS, and Windows. For detailed installation instructions, see the open-source [Redis documentation](https://redis.io/docs/latest/operate/oss_and_stack/install/).
 
 ### Install on Linux
 

articles/migration/migrate-security-from-aws.md

@@ -3,7 +3,7 @@ title: Migrate security services from Amazon Web Services (AWS)
 description: Learn about replatforming security services from AWS to Microsoft Cloud to support the security requirements of the workload. Discover key similarities and differences between AWS and Microsoft.
 ms.author: joflore
 author: MicrosoftGuyJFlo
-ms.date: 05/01/2025
+ms.date: 07/30/2025
 ms.topic: conceptual
 ms.collection:
  - migration
@@ -15,13 +15,21 @@ This article describes scenarios that you can use to migrate Amazon Web Services
 
 These scenarios might cover tasks like migrating your security and information and event management (SIEM) solution to Azure.
 
+## Component comparison
+
+Start the migration process by comparing the AWS security and identity services used in the workload with the closest Azure counterpart. The goal is to identify the most suitable Azure services for your workload. For more information, see [Comparing AWS and Azure identity management solutions](/azure/architecture/aws-professional/security-identity).
+
+> [!NOTE]
+> This comparison isn't an exact representation of the functionality that these services provide in your workload.
+
 ## Migration scenarios
 
 Use the following migration guides as examples to help structure your migration strategy.
 
 | Scenario | Key services | Description |
 |--|--|--|
 | [Migrate your SIEM in AWS to Microsoft Sentinel](/azure/sentinel/migration) |  SIEM data in AWS -> Microsoft Sentinel | Plan the different phases of your SIEM data migration from AWS. |
+| [Migrate your customer facing tenant to Microsoft Entra External ID](/entra/external-id/customers/migrate-to-external-id) | Customer identities -> Microsoft Entra External ID | Plan the phases of your customer identity migration |
 
 ## Related workload components
 

articles/redis/architecture.md

@@ -1,7 +1,7 @@
 ---
 title: Azure Managed Redis Architecture
 description: Learn how Azure Managed Redis is architected
-ms.date: 05/18/2025
+ms.date: 08/18/2025
 ms.topic: conceptual
 ms.custom:
   - ignite-2024
@@ -44,7 +44,7 @@ Each Azure Managed Redis instance is internally configured to use clustering, ac
 
 Azure Managed Redis offers three clustering policies: _OSS_, _Enterprise_, and Non-Clustered (preview). _OSS_ cluster policy is recommended for most applications because it supports higher maximum throughput, but there are advantages and disadvantages to each version.
 
-The **OSS clustering policy** implements the same [Redis Cluster API](https://redis.io/docs/reference/cluster-spec/) as Azure Cache for Redis tiers. The Redis Cluster API allows the Redis client to connect directly to shards on each Redis node, minimizing latency and optimizing network throughput, allowing throughput to scale near-linearly as the number of shards and vCPUs increases. The OSS clustering policy generally provides the best latency and throughput performance. The OSS cluster policy, however, requires your client library to support the Redis Cluster API. Today, almost all Redis clients support the Redis Cluster API, but compatibility might be an issue for older client versions or specialized libraries.
+The **OSS clustering policy** implements the same [Redis Cluster API](https://redis.io/docs/latest/operate/oss_and_stack/reference/cluster-spec/) as Azure Cache for Redis tiers. The Redis Cluster API allows the Redis client to connect directly to shards on each Redis node, minimizing latency and optimizing network throughput, allowing throughput to scale near-linearly as the number of shards and vCPUs increases. The OSS clustering policy generally provides the best latency and throughput performance. The OSS cluster policy, however, requires your client library to support the Redis Cluster API. Today, almost all Redis clients support the Redis Cluster API, but compatibility might be an issue for older client versions or specialized libraries.
 
 OSS clustering policy can't be used with the [RediSearch module](redis-modules.md).
 

articles/redis/best-practices-performance.md

@@ -1,7 +1,7 @@
 ---
 title: Best practices for performance testing for Azure Managed Redis
 description: Learn how to test the performance of Azure Managed Redis.
-ms.date: 05/18/2025
+ms.date: 08/18/2025
 ms.topic: conceptual
 ms.custom:
   - ignite-2024
@@ -14,7 +14,7 @@ appliesto:
 
 Testing the performance of a Redis instance can be a complicated task. The performance of a Redis instance can vary based on parameters such as the number of clients, the size of data values, and whether pipelining is being used. There also can be a tradeoff between optimizing throughput or latency.
 
-Fortunately, several tools exist to make benchmarking Redis easier. Two of the most popular tools are **[redis-benchmark](https://redis.io/docs/management/optimization/benchmarks/)** and **[memtier-benchmark](https://github.com/redislabs/memtier_benchmark)**. This article focuses on memtier_benchmark, often called _memtier_.
+Fortunately, several tools exist to make benchmarking Redis easier. Two of the most popular tools are **[redis-benchmark](https://redis.io/docs/latest/operate/oss_and_stack/management/optimization/benchmarks/)** and **[memtier-benchmark](https://github.com/redislabs/memtier_benchmark)** . This article focuses on memtier_benchmark, often called _memtier_.
 
 ## How to use the memtier_benchmark utility
 
@@ -86,7 +86,7 @@ The table below shows optimal throughput that we observed while testing various
 >Microsoft periodically updates the underlying VM used in cache instances. This can change the performance characteristics from cache to cache and from region to region. The example benchmarking values on this page reflect a particular generation cache hardware in a single region. You may see different results in practice, especially with network bandwidth.
 >
 
-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).
+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/latest/operate/oss_and_stack/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 | GET requests per second for Memory Optimized | GET requests per second for Balanced | GET requests per second for Compute Optimized | 

articles/redis/how-to-redis-cli-tool.md

@@ -1,7 +1,7 @@
 ---
 title: Use redis-cli with Azure Managed Redis
 description: Learn how to use *redis-cli* as a command-line tool for interacting with an Azure Managed Redis as a client
-ms.date: 05/18/2025
+ms.date: 08/18/2025
 ms.topic: conceptual
 ms.custom:
   - ignite-2024
@@ -12,11 +12,11 @@ appliesto:
 ---
 # Use the Redis command-line tool with Azure Managed Redis
 
-Use the [redis-cli command-line tool](https://redis.io/docs/connect/cli/) to interact with an Azure Managed Redis as a client. Use this tool to directly interact with your Azure Managed Redis instance and for debugging and troubleshooting.
+Use the [redis-cli command-line tool](https://redis.io/docs/latest/operate/rs/references/cli-utilities/redis-cli/#connect-to-a-database) to interact with an Azure Managed Redis as a client. Use this tool to directly interact with your Azure Managed Redis instance and for debugging and troubleshooting.
 
 ## Install redis-cli
 
-The _redis-cli_ tool is installed automatically with the _Redis package_, which is available for multiple operating systems. See the open source [install Redis](https://redis.io/docs/install/install-redis/) guide for the most detailed documentation on your preferred operating system.
+The _redis-cli_ tool is installed automatically with the _Redis package_, which is available for multiple operating systems. See the open source [install Redis](https://redis.io/docs/latest/operate/oss_and_stack/install/) guide for the most detailed documentation on your preferred operating system.
 
 ### Linux
 

articles/storage/blobs/data-protection-overview.md

@@ -4,7 +4,7 @@ titleSuffix: Azure Storage
 description: The data protection options available for you're for Blob Storage and Azure Data Lake Storage data enable you to protect your data from being deleted or overwritten. If you should need to recover data that has been deleted or overwritten, this guide can help you to choose the recovery option that's best for your scenario.
 services: storage
 author: normesta
-
+ms.custom: copilot-scenario-highlight
 ms.service: azure-blob-storage
 ms.date: 07/29/2024
 ms.topic: overview
@@ -33,6 +33,9 @@ These options, as well as other data protection options for other scenarios, are
 
 For an overview of the costs involved with these features, see [Summary of cost considerations](#summary-of-cost-considerations).
 
+> [!TIP]
+> You can use Microsoft Copilot in Azure to get suggestions on enhancing your storage account's data resiliency. For more information, see [Manage and troubleshoot storage accounts using Microsoft Copilot in Azure](/azure/copilot/improve-storage-accounts#enhance-data-resiliency).
+
 ## Overview of data protection options
 
 The following table summarizes the options available in Azure Storage for common data protection scenarios. Choose the scenarios that are applicable to your situation to learn more about the options available to you. Not all features are available at this time for storage accounts with a hierarchical namespace enabled.

articles/storage/blobs/lifecycle-management-policy-configure.md

@@ -3,13 +3,12 @@ title: Configure a lifecycle management policy
 titleSuffix: Azure Blob Storage
 description: Configure a lifecycle management policy to automatically move data between hot, cool, cold, and archive tiers during the data lifecycle.
 author: normesta
-
 ms.author: normesta
 ms.date: 06/13/2025
 ms.service: azure-blob-storage
 ms.topic: concept-article
 ms.reviewer: yzheng
-ms.custom: "devx-track-azurepowershell, devx-track-azurecli" 
+ms.custom: devx-track-azurepowershell, devx-track-azurecli, copilot-scenario-highlight
 ms.devlang: azurecli
 # Customer intent: "As a cloud storage administrator, I want to configure lifecycle management policies for blob storage, so that I can automatically transition or delete data based on access patterns to optimize storage costs and improve data management."
 ---
@@ -23,6 +22,9 @@ You can use lifecycle management policies to transition blobs to cost-efficient
 > [!NOTE]
 > A lifecycle management policy must be read or written in full. Partial updates are not supported.
 
+> [!TIP]
+> You can use Microsoft Copilot in Azure to help author lifecycle management policies. For more information, see [Manage and troubleshoot storage accounts using Microsoft Copilot in Azure](/azure/copilot/improve-storage-accounts#reduce-storage-costs).
+
 ## Create or manage a policy
 
 ### [Portal](#tab/azure-portal)

articles/storage/common/storage-plan-manage-costs.md

@@ -8,7 +8,7 @@ ms.topic: concept-article
 ms.date: 06/12/2025
 ms.author: normesta
 ms.subservice: storage-common-concepts
-ms.custom: subject-cost-optimization
+ms.custom: subject-cost-optimization, copilot-scenario-highlight
 # Customer intent: As a cost manager, I want to analyze and manage Azure Blob Storage costs, so that I can optimize our cloud spending and avoid unexpected charges.
 ---
 
@@ -173,6 +173,9 @@ If you've been using Blob Storage for some time, you should periodically review
 - [Tutorial: Calculate container statistics by using Databricks](../blobs/storage-blob-calculate-container-statistics-databricks.md)
 - [Calculate blob count and total size per container using Azure Storage inventory](../blobs/calculate-blob-count-size.yml)
 
+> [!TIP]
+> You can use Microsoft Copilot in Azure to get suggestions on reducing the cost of your storage account. For more information, see [Manage and troubleshoot storage accounts using Microsoft Copilot in Azure](/azure/copilot/improve-storage-accounts#reduce-storage-costs).
+
 If you can model future capacity requirements, you can save money with Azure Storage reserved capacity. Azure Storage reserved capacity is available for most access tiers and offers you a discount on capacity for block blobs and for Azure Data Lake Storage data in standard storage accounts when you commit to a reservation for either one year or three years. A reservation provides a fixed amount of storage capacity for the term of the reservation. Azure Storage reserved capacity can significantly reduce your capacity costs for block blobs and Azure Data Lake Storage data. To learn more, see [Optimize costs for Blob Storage with reserved capacity](../blobs/storage-blob-reserved-capacity.md).
 
 You can also reduce costs by placing blob data into the most cost effective access tiers. Choose from three tiers that are designed to optimize your costs around data use. For example, the _hot_ tier has a higher storage cost but lower access cost. Therefore, if you plan to access data frequently, the hot tier might be the most cost-efficient choice. If you plan to access data less frequently, the _cold_ or _archive_ tier might make the most sense because it raises the cost of accessing data while reducing the cost of storing data. See any of these articles: