Merge pull request #283671 from MicrosoftDocs/main

8/6 11:00 AM IST Publish

Author: PhilKang0704

.openpublishing.redirection.azure-functions.json

@@ -0,0 +1,9 @@
+{
+    "redirections": [
+        {
+            "source_path_from_root": "/articles/azure-functions/durable/durable-functions-configure-durable-functions-with-credentials.md",
+            "redirect_url": "/azure/azure-functions/durable/durable-functions-configure-managed-identity",
+            "redirect_document_id": false
+        }
+    ]
+}

articles/azure-arc/resource-bridge/system-requirements.md

@@ -31,15 +31,16 @@ Arc Appliance CLI extension, `arcappliance`, needs to be installed on the CLI. T
 
 Arc resource bridge has the following minimum resource requirements:
 
-- 50 GB disk space
+- 200 GB disk space
 - 4 vCPUs
 - 8 GB memory
+- supported storage configuration - hybrid storage (flash and HDD) or all-flash storage (SSDs or NVMe)
 
-These minimum requirements enable most scenarios. However, a partner product may support a higher resource connection count to Arc resource bridge, which requires the bridge to have higher resource requirements. Failure to provide sufficient resources may cause errors during deployment, such as disk copy errors. Review the partner product's documentation for specific resource requirements.
+These minimum requirements enable most scenarios for products that use Arc resource bridge. Review the product's documentation for specific resource requirements. Failure to provide sufficient resources may cause errors during deployment or upgrade. 
 
 ## IP address prefix (subnet) requirements
 
-The IP address prefix (subnet) where Arc resource bridge will be deployed requires a minimum prefix of /29. The IP address prefix must have enough available IP addresses for the gateway IP, control plane IP, appliance VM IP, and reserved appliance VM IP. Arc resource bridge only uses the IP addresses assigned to the IP pool range (Start IP, End IP) and the Control Plane IP. We recommend that the End IP immediately follow the Start IP. Ex: Start IP =192.168.0.2, End IP = 192.168.0.3. Please work with your network engineer to ensure that there is an available subnet with the required available IP addresses and IP address prefix for Arc resource bridge.
+The IP address prefix (subnet) where Arc resource bridge will be deployed requires a minimum prefix of /29. The IP address prefix must have enough available IP addresses for the gateway IP, control plane IP, appliance VM IP, and reserved appliance VM IP. Arc resource bridge only uses the IP addresses assigned to the IP pool range (Start IP, End IP) and the Control Plane IP. We recommend that the End IP immediately follow the Start IP. Ex: Start IP = 192.168.0.2, End IP = 192.168.0.3. Please work with your network engineer to ensure that there is an available subnet with the required available IP addresses and IP address prefix for Arc resource bridge.
 
 The IP address prefix is the subnet's IP address range for the virtual network and subnet mask (IP Mask) in CIDR notation, for example `192.168.7.1/29`. You provide the IP address prefix (in CIDR notation) during the creation of the configuration files for Arc resource bridge. 
 

articles/azure-cache-for-redis/cache-how-to-scale.md

@@ -71,7 +71,7 @@ You can scale up/down to a different pricing tier with the following restriction
   - You can't scale from a **Standard** cache down to a **Basic** cache.
 - You can scale from a **Basic** cache to a **Standard** cache but you can't change the size at the same time. If you need a different size, you can later do a scaling operation to the wanted size.
 - You can't scale from a **Basic** cache directly to a **Premium** cache. First, scale from **Basic** to **Standard** in one scaling operation, and then from **Standard** to **Premium** in the next scaling operation.
-- You can't scale from a larger size down to the **C0 (250 MB)** size. However, you can scale down to any other size within the same pricing tier. For example, you can scale down from C5 Standard to C1 Standard.
+- You can't scale from a larger size in to the **C0 (250 MB)** size. However, you can scale in to any other size within the same pricing tier. For example, you can scale in from C5 Standard to C1 Standard.
 - You can't scale from a **Premium**, **Standard**, or **Basic** cache up to an **Enterprise** or **Enterprise Flash** cache.
 - You can't scale between **Enterprise** and **Enterprise Flash**.
 

articles/azure-functions/durable/TOC.yml

@@ -39,8 +39,8 @@
     href: quickstart-netherite.md
   - name: Configure a storage provider - MSSQL
     href: quickstart-mssql.md
-  - name: Authenticate a Durable Functions app
-    href: durable-functions-configure-durable-functions-with-credentials.md   
+  - name: Configure Durable Functions app with managed identity
+    href: durable-functions-configure-managed-identity.md   
 - name: Tutorials
   items:
   - name: Function chaining