Merge pull request #224456 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/hybrid/how-to-connect-modify-group-writeback.md

@@ -36,13 +36,28 @@ To configure directory settings to disable automatic writeback of newly created
 - PowerShell: Use the [Microsoft Graph PowerShell SDK](/powershell/microsoftgraph/installation?view=graph-powershell-1.0&preserve-view=true). For example: 
 
   ```PowerShell 
-    # Import Module
-    Import-Module Microsoft.Graph.Identity.DirectoryManagement
-
-    #Connect to MgGraph with necessary scope and select the Beta API Version
-    Connect-MgGraph -Scopes Directory.ReadWrite.All
-    Select-MgProfile -Name beta
-
+  # Import Module
+  Import-Module Microsoft.Graph.Identity.DirectoryManagement
+
+  #Connect to MgGraph with necessary scope and select the Beta API Version
+  Connect-MgGraph -Scopes Directory.ReadWrite.All
+  Select-MgProfile -Name beta
+
+  # Verify if "Group.Unified" directory settings exist
+  $DirectorySetting = Get-MgDirectorySetting | Where-Object {$_.DisplayName -eq "Group.Unified"}
+
+  # If "Group.Unified" directory settings exist, update the value for new unified group writeback default
+  if ($DirectorySetting) {
+    $DirectorySetting.Values | ForEach-Object {
+        if ($_.Name -eq "NewUnifiedGroupWritebackDefault") {
+            $_.Value = "false"
+        }
+    }
+    Update-MgDirectorySetting -DirectorySettingId $DirectorySetting.Id -BodyParameter $DirectorySetting
+  }
+  else
+  {
+    # In case the directory setting doesn't exist, create a new "Group.Unified" directory setting
     # Import "Group.Unified" template values to a hashtable
     $Template = Get-MgDirectorySettingTemplate | Where-Object {$_.DisplayName -eq "Group.Unified"}
     $TemplateValues = @{}
@@ -52,6 +67,7 @@ To configure directory settings to disable automatic writeback of newly created
 
     # Update the value for new unified group writeback default
     $TemplateValues["NewUnifiedGroupWritebackDefault"] = "false"
+    
     # Create a directory setting using the Template values hashtable including the updated value
     $params = @{}
     $params.Add("TemplateId", $Template.Id)
@@ -60,6 +76,7 @@ To configure directory settings to disable automatic writeback of newly created
         $params.Values += @(@{Name = $_; Value = $TemplateValues[$_]})
     }
     New-MgDirectorySetting -BodyParameter $params
+  }
   ``` 
 
 > [!NOTE]     

articles/aks/azure-cni-overlay.md

@@ -41,7 +41,7 @@ Ingress connectivity to the cluster can be achieved using an ingress controller
 Like Azure CNI Overlay, Kubenet assigns IP addresses to pods from an address space logically different from the VNet but has scaling and other limitations. The below table provides a detailed comparison between Kubenet and Azure CNI Overlay. If you do not want to assign VNet IP addresses to pods due to IP shortage, then Azure CNI Overlay is the recommended solution.
 
 | Area | Azure CNI Overlay | Kubenet |
-| -- | :--: | -- |
+| -- | -- | -- |
 | Cluster scale | 1000 nodes and 250 pods/node | 400 nodes and 250 pods/node |
 | Network configuration | Simple - no additional configuration required for pod networking | Complex - requires route tables and UDRs on cluster subnet for pod networking |
 | Pod connectivity performance | Performance on par with VMs in a VNet | Additional hop adds minor latency |

articles/azure-monitor/essentials/prometheus-metrics-enable.md

@@ -114,6 +114,7 @@ The output will be similar to the following:
 ### Prerequisites
 
 - Register the `AKS-PrometheusAddonPreview` feature flag in the Azure Kubernetes clusters subscription with the following command in Azure CLI: `az feature register --namespace Microsoft.ContainerService --name AKS-PrometheusAddonPreview`.
+- If the Azure Managed Grafana instance is in a subscription other than the Azure Monitor Workspaces subscription, then please register the Azure Monitor Workspace subscription with the `Microsoft.Dashboard` resource provider following this [documentation](/azure-resource-manager/management/resource-providers-and-types#register-resource-provider.md#register-resource-provider).
 - The Azure Monitor workspace and Azure Managed Grafana workspace must already be created.
 - The template needs to be deployed in the same resource group as the Azure Managed Grafana workspace.