Merge pull request #225954 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/privileged-identity-management/pim-email-notifications.md

@@ -59,9 +59,9 @@ Who receives these emails for Azure AD roles depends on your role, the event, an
 
 | User | Role activation is pending approval | Role activation request is completed | PIM is enabled |
 | --- | --- | --- | --- |
-| Privileged Role Administrator</br>(Activated/Eligible) | Yes</br>(only if no explicit approvers are specified) | Yes* | Yes |
-| Security Administrator</br>(Activated/Eligible) | No | Yes* | Yes |
-| Global Administrator</br>(Activated/Eligible) | No | Yes* | Yes |
+| Privileged Role Administrator</br>(Activated) | Yes</br>(only if no explicit approvers are specified) | Yes* | Yes |
+| Security Administrator</br>(Activated) | No | Yes* | Yes |
+| Global Administrator</br>(Activated) | No | Yes* | Yes |
 
 \* If the [**Notifications** setting](pim-how-to-change-default-settings.md) is set to **Enable**.
 

articles/aks/configure-azure-cni-dynamic-ip-allocation.md

@@ -28,7 +28,6 @@ This article shows you how to use Azure CNI networking for dynamic allocation of
 
 * Review the [prerequisites](/configure-azure-cni.md#prerequisites) for configuring basic Azure CNI networking in AKS, as the same prerequisites apply to this article.
 * Review the [deployment parameters](/configure-azure-cni.md#deployment-parameters) for configuring basic Azure CNI networking in AKS, as the same parameters apply.
-* Only linux node clusters and node pools are supported.
 * AKS Engine and DIY clusters aren't supported.
 * Azure CLI version `2.37.0` or later.
 

articles/azure-functions/functions-run-local.md

@@ -252,7 +252,7 @@ There are no additional considerations for PowerShell.
 
 # [TypeScript](#tab/ts)
 
-+ To use a `--worker-runtime` value of `node`, specify the `--language` as `javascript`.
++ To use a `--worker-runtime` value of `node`, specify the `--language` as `typescript`.
 
 + See the [TypeScript section in the JavaScript developer reference](functions-reference-node.md#typescript) for `func init` behaviors specific to TypeScript. 
 

articles/container-apps/azure-arc-create-container-app.md

@@ -43,7 +43,8 @@ az extension add -s https://download.microsoft.com/download/5/c/2/5c2ec3fc-bd2a-
 Create a resource group for the services created in this tutorial.
 
 ```azurecli-interactive
-az group create --name myResourceGroup --location eastus 
+myResourceGroup="my-container-apps-resource-group"
+az group create --name $myResourceGroup --location eastus 
 ```
 
 ## Get custom location information
@@ -75,7 +76,8 @@ Now that you have the custom location ID, you can query for the connected enviro
 A connected environment is largely the same as a standard Container Apps environment, but network restrictions are controlled by the underlying Arc-enabled Kubernetes cluster.
 
 ```azure-interactive
-myConnectedEnvironment = az containerapp connected-env list --custom-location customLocationId -o tsv --query '[].id'
+myContainerApp="my-container-app"
+myConnectedEnvironment=$(az containerapp connected-env list --custom-location $customLocationId -o tsv --query '[].id')
 ```
 
 ## Create an app
@@ -84,16 +86,15 @@ The following example creates a Node.js app.
 
 ```azurecli-interactive
  az containerapp create \
-    --resource-group myResourceGroup \
-    --name myContainerApp \
-    --environment myConnectedEnvironment \
+    --resource-group $myResourceGroup \
+    --name $myContainerApp \
+    --environment $myConnectedEnvironment \
     --environment-type connected \
-    --image mcr.microsoft.com/azuredocs/container-apps-helloworld:latest \
+    --image mcr.microsoft.com/azuredocs/containerapps-helloworld:latest \
     --target-port 80 \
     --ingress 'external'
 
-az containerapp browse --resource-group myResourceGroup \
-    --name myContainerApp
+az containerapp browse --resource-group $myResourceGroup --name $myContainerApp
 ```
 
 ## Get diagnostic logs using Log Analytics
@@ -112,7 +113,7 @@ let StartTime = ago(72h);
 let EndTime = now();
 ContainerAppsConsoleLogs_CL
 | where TimeGenerated between (StartTime .. EndTime)
-| where AppName_s =~ "myContainerApp"
+| where AppName_s =~ "my-container-app"
 ```
 
 The application logs for all the apps hosted in your Kubernetes cluster are logged to the Log Analytics workspace in the custom log table named `ContainerAppsConsoleLogs_CL`.

articles/container-apps/azure-arc-enable-cluster.md

@@ -91,7 +91,6 @@ Set environment variables based on your Kubernetes cluster deployment.
 
 ```bash
 GROUP_NAME="my-arc-cluster-group"
-CLUSTER_NAME="my-arc-cluster"
 AKS_CLUSTER_GROUP_NAME="my-aks-cluster-group"
 AKS_NAME="my-aks-cluster" 
 LOCATION="eastus" 
@@ -101,7 +100,6 @@ LOCATION="eastus"
 
 ```azurepowershell
 $GROUP_NAME="my-arc-cluster-group"
-$CLUSTER_NAME="my-arc-cluster"
 $AKS_CLUSTER_GROUP_NAME="my-aks-cluster-group"
 $AKS_NAME="my-aks-cluster" 
 $LOCATION="eastus" 
@@ -121,7 +119,7 @@ The following steps help you get started understanding the service, but for prod
     az group create --name $AKS_CLUSTER_GROUP_NAME --location $LOCATION
     az aks create \
        --resource-group $AKS_CLUSTER_GROUP_NAME \
-       --name $AKS_NAME \ 
+       --name $AKS_NAME \
        --enable-aad \
        --generate-ssh-keys
     ```
@@ -212,7 +210,7 @@ A [Log Analytics workspace](../azure-monitor/logs/quick-create-workspace.md) pro
 
     az monitor log-analytics workspace create `
         --resource-group $GROUP_NAME `
-        --workspace-name $wORKSPACE_NAME
+        --workspace-name $WORKSPACE_NAME
     ```
 
     ---
@@ -224,13 +222,13 @@ A [Log Analytics workspace](../azure-monitor/logs/quick-create-workspace.md) pro
     ```azurecli
     LOG_ANALYTICS_WORKSPACE_ID=$(az monitor log-analytics workspace show \
         --resource-group $GROUP_NAME \
-        --workspace-name $wORKSPACE_NAME \
+        --workspace-name $WORKSPACE_NAME \
         --query customerId \
         --output tsv)
     LOG_ANALYTICS_WORKSPACE_ID_ENC=$(printf %s $LOG_ANALYTICS_WORKSPACE_ID | base64 -w0) # Needed for the next step
     lOG_ANALYTICS_KEY=$(az monitor log-analytics workspace get-shared-keys \
         --resource-group $GROUP_NAME \
-        --workspace-name $wORKSPACE_NAME \
+        --workspace-name $WORKSPACE_NAME \
         --query primarySharedKey \
         --output tsv)
     lOG_ANALYTICS_KEY_ENC=$(printf %s $lOG_ANALYTICS_KEY | base64 -w0) # Needed for the next step
@@ -241,13 +239,13 @@ A [Log Analytics workspace](../azure-monitor/logs/quick-create-workspace.md) pro
     ```azurepowershell
     $LOG_ANALYTICS_WORKSPACE_ID=$(az monitor log-analytics workspace show `
         --resource-group $GROUP_NAME `
-        --workspace-name $wORKSPACE_NAME `
+        --workspace-name $WORKSPACE_NAME `
         --query customerId `
         --output tsv)
     $LOG_ANALYTICS_WORKSPACE_ID_ENC=[Convert]::ToBase64String([System.Text.Encoding]::UTF8.GetBytes($LOG_ANALYTICS_WORKSPACE_ID))# Needed for the next step
     $lOG_ANALYTICS_KEY=$(az monitor log-analytics workspace get-shared-keys `
         --resource-group $GROUP_NAME `
-        --workspace-name $wORKSPACE_NAME `
+        --workspace-name $WORKSPACE_NAME `
         --query primarySharedKey `
         --output tsv)
     $lOG_ANALYTICS_KEY_ENC=[Convert]::ToBase64String([System.Text.Encoding]::UTF8.GetBytes($lOG_ANALYTICS_KEY))
@@ -294,7 +292,7 @@ A [Log Analytics workspace](../azure-monitor/logs/quick-create-workspace.md) pro
         --release-namespace $NAMESPACE \
         --configuration-settings "Microsoft.CustomLocation.ServiceAccount=default" \
         --configuration-settings "appsNamespace=${NAMESPACE}" \
-        --configuration-settings "CLUSTER_NAME=${CONNECTED_ENVIRONMENT_NAME}" \
+        --configuration-settings "clusterName=${CONNECTED_ENVIRONMENT_NAME}" \
         --configuration-settings "envoy.annotations.service.beta.kubernetes.io/azure-load-balancer-resource-group=${AKS_CLUSTER_GROUP_NAME}" \
         --configuration-settings "logProcessor.appLogs.destination=log-analytics" \
         --configuration-protected-settings "logProcessor.appLogs.logAnalyticsConfig.customerId=${LOG_ANALYTICS_WORKSPACE_ID_ENC}" \
@@ -316,7 +314,7 @@ A [Log Analytics workspace](../azure-monitor/logs/quick-create-workspace.md) pro
         --release-namespace $NAMESPACE `
         --configuration-settings "Microsoft.CustomLocation.ServiceAccount=default" `
         --configuration-settings "appsNamespace=${NAMESPACE}" `
-        --configuration-settings "CLUSTER_NAME=${CONNECTED_ENVIRONMENT_NAME}" `
+        --configuration-settings "clusterName=${CONNECTED_ENVIRONMENT_NAME}" `
         --configuration-settings "envoy.annotations.service.beta.kubernetes.io/azure-load-balancer-resource-group=${AKS_CLUSTER_GROUP_NAME}" `
         --configuration-settings "logProcessor.appLogs.destination=log-analytics" `
         --configuration-protected-settings "logProcessor.appLogs.logAnalyticsConfig.customerId=${LOG_ANALYTICS_WORKSPACE_ID_ENC}" `
@@ -335,7 +333,7 @@ A [Log Analytics workspace](../azure-monitor/logs/quick-create-workspace.md) pro
     | - | - |
     | `Microsoft.CustomLocation.ServiceAccount` | The service account created for the custom location. It's recommended that it 's set to the value `default`. |
     | `appsNamespace` | The namespace used to create the app definitions and revisions. It **must** match that of the extension release namespace. |
-    | `CLUSTER_NAME` | The name of the Container Apps extension Kubernetes environment that will be created against this extension. |
+    | `clusterName` | The name of the Container Apps extension Kubernetes environment that will be created against this extension. |
     | `logProcessor.appLogs.destination` | Optional. Destination for application logs. Accepts `log-analytics` or `none`, choosing none disables platform logs. |
     | `logProcessor.appLogs.logAnalyticsConfig.customerId` | Required only when `logProcessor.appLogs.destination` is set to `log-analytics`. The base64-encoded Log analytics workspace ID. This parameter should be configured as a protected setting. |
     | `logProcessor.appLogs.logAnalyticsConfig.sharedKey` | Required only when `logProcessor.appLogs.destination` is set to `log-analytics`. The base64-encoded Log analytics workspace shared key. This parameter should be configured as a protected setting. |4
@@ -474,7 +472,8 @@ Before you can start creating apps in the custom location, you need an [Azure Co
     az containerapp connected-env create \
         --resource-group $GROUP_NAME \
         --name $CONNECTED_ENVIRONMENT_NAME \
-        --custom-location $CUSTOM_LOCATION_ID 
+        --custom-location $CUSTOM_LOCATION_ID \
+        --location $LOCATION
     ```
 
     # [PowerShell](#tab/azure-powershell)
@@ -483,7 +482,8 @@ Before you can start creating apps in the custom location, you need an [Azure Co
     az containerapp connected-env create `
         --resource-group $GROUP_NAME `
         --name $CONNECTED_ENVIRONMENT_NAME `
-        --custom-location $CUSTOM_LOCATION_ID       
+        --custom-location $CUSTOM_LOCATION_ID `
+        --location $LOCATION
     ```
 
     ---

articles/cosmos-db/nosql/how-to-delete-by-partition-key.md

@@ -22,7 +22,7 @@ This article explains how to use the Azure Cosmos DB SDKs to delete all items by
 
 ## Feature overview
 
-The delete by partition key feature is an asynchronous, background operation that allows you to delete all documents with the same logical partition key value, using the Comsos SDK.
+The delete by partition key feature is an asynchronous, background operation that allows you to delete all documents with the same logical partition key value, using the Cosmos SDK.
 
 Because the number of documents to be deleted may be large, the operation runs in the background. Though the physical deletion operation runs in the background, the effects will be available immediately, as the documents to be deleted won't appear in the results of queries or read operations. 
 

articles/openshift/howto-create-a-storageclass.md

@@ -86,6 +86,15 @@ apiVersion: storage.k8s.io/v1
 metadata:
   name: azure-file
 provisioner: kubernetes.io/azure-file
+mountOptions:
+  - dir_mode=0777
+  - file_mode=0777
+  - uid=0
+  - gid=0
+  - mfsymlinks
+  - cache=strict
+  - actimeo=30
+  - noperm
 parameters:
   location: $LOCATION
   secretNamespace: kube-system
@@ -99,6 +108,17 @@ EOF
 oc create -f azure-storageclass-azure-file.yaml
 ```
 
+Mount options for Azure Files will generally be dependent on the workload that you are deploying and the requirements of the application. Specifically for Azure files, there are additional parameters that you should consider using.
+
+Mandatory parameters: 
+- "mfsymlinks" to map symlinks to a form the client can use
+- "noperm" to disable permission checks on the client side
+
+Recommended parameters: 
+- "nossharesock" to disable reusing sockets if the client is already connected via an existing mount point
+- "actimeo=30" (or higher) to increase the time the CIFS client caches file and directory attributes
+- "nobrl" to disable sending byte range lock requests to the server and for applications which have challenges with posix locks
+
 ## Change the default StorageClass (optional)
 
 The default StorageClass on ARO is called managed-premium and uses the azure-disk provisioner. Change this by issuing patch commands against the StorageClass manifests.

articles/openshift/tutorial-create-cluster.md

@@ -70,14 +70,6 @@ You will also need sufficient Azure Active Directory permissions (either a membe
     az provider register -n Microsoft.Authorization --wait
     ```
     
-    1. Azure Red Hat Openshift is now available as a public preview in Azure government. If you are looking to deploy there, please follow these instructions: 
-
-> [!IMPORTANT]
-> ARO preview features are available on a self-service, opt-in basis. Preview features are provided "as is" and "as available," and they are excluded from the service-level agreements and limited warranty. Preview features are partially covered by customer support on a best-effort basis. As such, these features are not meant for production use.
-
-```azurecli-interactive
-az feature register --namespace Microsoft.RedHatOpenShift --name preview
-```
 
 ### Get a Red Hat pull secret (optional)
 

articles/synapse-analytics/sql-data-warehouse/load-data-from-azure-blob-storage-using-copy.md

@@ -78,7 +78,7 @@ The first step toward loading data is to login as LoaderRC20.
 
 3. Select **Connect**.
 
-4. When your connection is ready, you will see two server connections in Object Explorer. One connection as ServerAdmin and one connection as MedRCLogin.
+4. When your connection is ready, you will see two server connections in Object Explorer. One connection as ServerAdmin and one connection as LoaderRC20.
 
     ![Connection is successful](./media/load-data-from-azure-blob-storage-using-polybase/connected-as-new-login.png)