Merge pull request #211497 from MicrosoftDocs/repo_sync_working_branch

Confirm merge from repo_sync_working_branch to main to sync with https://github.com/MicrosoftDocs/azure-docs (branch main)

Author: huypub

articles/active-directory/develop/msal-node-migration.md

@@ -71,7 +71,7 @@ const msal = require('@azure/msal-node');
 
 const pca = new msal.PublicClientApplication({
         auth: {
-            clientId = "YOUR_CLIENT_ID"
+            clientId: "YOUR_CLIENT_ID"
         }
     });
 ```
@@ -86,8 +86,8 @@ const msal = require('@azure/msal-node');
 
 const cca = new msal.ConfidentialClientApplication({
         auth: {
-            clientId = "YOUR_CLIENT_ID",
-            clientSecret = "YOUR_CLIENT_SECRET"
+            clientId: "YOUR_CLIENT_ID",
+            clientSecret: "YOUR_CLIENT_SECRET"
         }
     });
 ```

articles/azure-vmware/includes/azure-vmware-solutions-limits.md

@@ -22,7 +22,7 @@ The following table describes the maximum limits for Azure VMware Solution.
 | HCX site pairings | 25 (any edition) |
 | Azure VMware Solution ExpressRoute max linked private clouds | 4<br />The virtual network gateway used determines the actual max linked private clouds.  For more details, see [About ExpressRoute virtual network gateways](../../expressroute/expressroute-about-virtual-network-gateways.md) | 
 | Azure VMware Solution ExpressRoute port speed | 10 Gbps<br />The virtual network gateway used determines the actual bandwidth. For more details, see [About ExpressRoute virtual network gateways](../../expressroute/expressroute-about-virtual-network-gateways.md) | 
-| Public IPs exposed via vWAN | 100 |
+| Public IPs down to NSX-T | 2000 |
 | vSAN capacity limits | 75% of total usable (keep 25% available for SLA)  |
 | VMware Site Recovery Manager - Number of protected Virtual Machines  | 3,000  |
 | VMware Site Recovery Manager - Number of Virtual Machines per recovery plan  | 2,000  |

articles/machine-learning/how-to-create-manage-compute-instance.md

@@ -210,6 +210,61 @@ This setting can be configured during CI creation or for existing CIs via the fo
     }
     ```
 
+### Azure policy support
+Administrators can use a built-in [Azure Policy](./../governance/policy/overview.md) definition to enfore auto-stop on all compute instances in a given subscription/resource-group. 
+
+1. Navigate to Azure Policy in the Azure portal.
+2. Under "Definitions", look for the idle shutdown policy.
+
+      :::image type="content" source="media/how-to-create-attach-studio/idle-shutdown-policy.png" alt-text="Screenshot for the idle shutdown policy in Azure Portal.":::
+
+3. Assign policy to the necessary scope.
+
+You can also create your own custom Azure policy. For example, if the below policy is assigned, all new compute instances will have auto-stop configured with a 60 minute inactivity period. 
+
+```json
+{
+  "mode": "All",
+  "policyRule": {
+    "if": {
+      "allOf": [
+        {
+          "field": "type",
+          "equals": "Microsoft.MachineLearningServices/workspaces/computes"
+        },
+        {
+          "field": "Microsoft.MachineLearningServices/workspaces/computes/computeType",
+          "equals": "ComputeInstance"
+        },
+        {
+          "anyOf": [
+            {
+              "field": "Microsoft.MachineLearningServices/workspaces/computes/idleTimeBeforeShutdown",
+              "exists": false
+            },
+            {
+              "value": "[empty(field('Microsoft.MachineLearningServices/workspaces/computes/idleTimeBeforeShutdown'))]",
+              "equals": true
+            }
+          ]
+        }
+      ]
+    },
+    "then": {
+      "effect": "append",
+      "details": [
+        {
+          "field": "Microsoft.MachineLearningServices/workspaces/computes/idleTimeBeforeShutdown",
+          "value": "PT60M"
+        }
+      ]
+    }
+  },
+  "parameters": {}
+}
+```
+
+
 ## Create on behalf of (preview)
 
 As an administrator, you can create a compute instance on behalf of a data scientist and assign the instance to them with:

articles/machine-learning/media/how-to-create-attach-studio/idle-shutdown-policy.png

@@ -35,7 +35,7 @@ Use the following pattern as you configure your account to use Blob storage feat
 
 #### Understand the terms used in documentation
 
-As you move between content sets, you'll notice some slight terminology differences. For example, content featured in the [Blob storage documentation](storage-blobs-introduction.md), will use the term *blob* instead of *file*. Technically, the files that you ingest to your storage account become blobs in your account. Therefore, the term is correct. However, this can cause confusion if you're use to the term *file*. You'll also see the term *container* used to refer to a *file system*. Consider these terms as synonymous.
+As you move between content sets, you'll notice some slight terminology differences. For example, content featured in the [Blob storage documentation](storage-blobs-introduction.md), will use the term *blob* instead of *file*. Technically, the files that you ingest to your storage account become blobs in your account. Therefore, the term is correct. However, this can cause confusion if you're used to the term *file*. You'll also see the term *container* used to refer to a *file system*. Consider these terms as synonymous.
 
 ## Consider premium