Merge pull request #214461 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

@@ -70,56 +70,56 @@ To configure directory settings to disable automatic writeback of newly created
    import-module ADSync 
    $precedenceValue = Read-Host -Prompt "Enter a unique sync rule precedence value [0-99]" 
 
-   New-ADSyncRule  ` 
-   -Name 'In from AAD - Group SOAinAAD Delete WriteBackOutOfScope and SoftDelete' ` 
-   -Identifier 'cb871f2d-0f01-4c32-a333-ff809145b947' ` 
-   -Description 'Delete AD groups that fall out of scope of Group Writeback or get Soft Deleted in Azure AD' ` 
-   -Direction 'Inbound' ` 
-   -Precedence $precedenceValue ` 
-   -PrecedenceAfter '00000000-0000-0000-0000-000000000000' ` 
-   -PrecedenceBefore '00000000-0000-0000-0000-000000000000' ` 
-   -SourceObjectType 'group' ` 
-   -TargetObjectType 'group' ` 
-   -Connector 'b891884f-051e-4a83-95af-2544101c9083' ` 
-   -LinkType 'Join' ` 
-   -SoftDeleteExpiryInterval 0 ` 
-   -ImmutableTag '' ` 
-   -OutVariable syncRule 
-
-   Add-ADSyncAttributeFlowMapping  ` 
-   -SynchronizationRule $syncRule[0] ` 
-   -Destination 'reasonFiltered' ` 
-   -FlowType 'Expression' ` 
-   -ValueMergeType 'Update' ` 
-   -Expression 'IIF((IsPresent([reasonFiltered]) = True) && (InStr([reasonFiltered], "WriteBackOutOfScope") > 0 || InStr([reasonFiltered], "SoftDelete") > 0), "DeleteThisGroupInAD", [reasonFiltered])' ` 
-    -OutVariable syncRule 
-
-   New-Object  ` 
-   -TypeName 'Microsoft.IdentityManagement.PowerShell.ObjectModel.ScopeCondition' ` 
-   -ArgumentList 'cloudMastered','true','EQUAL' ` 
-   -OutVariable condition0 
-
-   Add-ADSyncScopeConditionGroup  ` 
-   -SynchronizationRule $syncRule[0] ` 
-   -ScopeConditions @($condition0[0]) ` 
-   -OutVariable syncRule 
+   New-ADSyncRule  `
+   -Name 'In from AAD - Group SOAinAAD Delete WriteBackOutOfScope and SoftDelete' `
+   -Identifier 'cb871f2d-0f01-4c32-a333-ff809145b947' `
+   -Description 'Delete AD groups that fall out of scope of Group Writeback or get Soft Deleted in Azure AD' `
+   -Direction 'Inbound' `
+   -Precedence $precedenceValue `
+   -PrecedenceAfter '00000000-0000-0000-0000-000000000000' `
+   -PrecedenceBefore '00000000-0000-0000-0000-000000000000' `
+   -SourceObjectType 'group' `
+   -TargetObjectType 'group' `
+   -Connector 'b891884f-051e-4a83-95af-2544101c9083' `
+   -LinkType 'Join' `
+   -SoftDeleteExpiryInterval 0 `
+   -ImmutableTag '' `
+   -OutVariable syncRule
+
+   Add-ADSyncAttributeFlowMapping  `
+   -SynchronizationRule $syncRule[0] `
+   -Destination 'reasonFiltered' `
+   -FlowType 'Expression' `
+   -ValueMergeType 'Update' `
+   -Expression 'IIF((IsPresent([reasonFiltered]) = True) && (InStr([reasonFiltered], "WriteBackOutOfScope") > 0 || InStr([reasonFiltered], "SoftDelete") > 0), "DeleteThisGroupInAD", [reasonFiltered])' `
+    -OutVariable syncRule
+
+   New-Object  `
+   -TypeName 'Microsoft.IdentityManagement.PowerShell.ObjectModel.ScopeCondition' `
+   -ArgumentList 'cloudMastered','true','EQUAL' `
+   -OutVariable condition0
+
+   Add-ADSyncScopeConditionGroup  `
+   -SynchronizationRule $syncRule[0] `
+   -ScopeConditions @($condition0[0]) `
+   -OutVariable syncRule
  
-   New-Object  ` 
-   -TypeName 'Microsoft.IdentityManagement.PowerShell.ObjectModel.JoinCondition' ` 
-   -ArgumentList 'cloudAnchor','cloudAnchor',$false ` 
-   -OutVariable condition0 
-
-   Add-ADSyncJoinConditionGroup  ` 
-   -SynchronizationRule $syncRule[0] ` 
-   -JoinConditions @($condition0[0]) ` 
-   -OutVariable syncRule 
-
-   Add-ADSyncRule  ` 
-   -SynchronizationRule $syncRule[0] 
-
-   Get-ADSyncRule  ` 
-   -Identifier 'cb871f2d-0f01-4c32-a333-ff809145b947' 
-   ``` 
+   New-Object  `
+   -TypeName 'Microsoft.IdentityManagement.PowerShell.ObjectModel.JoinCondition' `
+   -ArgumentList 'cloudAnchor','cloudAnchor',$false `
+   -OutVariable condition0
+
+   Add-ADSyncJoinConditionGroup  `
+   -SynchronizationRule $syncRule[0] `
+   -JoinConditions @($condition0[0]) `
+   -OutVariable syncRule
+
+   Add-ADSyncRule  `
+   -SynchronizationRule $syncRule[0]
+
+   Get-ADSyncRule  `
+   -Identifier 'cb871f2d-0f01-4c32-a333-ff809145b947'
+   ```
 
 4. [Enable group writeback](how-to-connect-group-writeback-enable.md). 
 5. Enable the Azure AD Connect sync scheduler: 

articles/active-directory/saas-apps/confluencemicrosoft-tutorial.md

@@ -211,7 +211,7 @@ In this section, you'll enable B.Simon to use Azure single sign-on by granting a
        > To enable the default login form for admin login on the login page when the force azure login is enabled, add the query parameter in the browser URL.
        > `https://<DOMAIN:PORT>/login.action?force_azure_login=false`
 
-    1. **Enable Use of Application Proxy** checkbox, if you have configured your on-premise atlassian application in an App Proxy setup. For App proxy setup , follow the steps on the [Azure AD App Proxy Documentation](/articles/active-directory/app-proxy/what-is-application-proxy.md).
+    1. **Enable Use of Application Proxy** checkbox, if you have configured your on-premise atlassian application in an App Proxy setup. For App proxy setup , follow the steps on the [Azure AD App Proxy Documentation](../app-proxy/what-is-application-proxy.md).
 
     1. Click **Save** button to save the settings.
 

articles/active-directory/saas-apps/github-enterprise-managed-user-oidc-provisioning-tutorial.md

@@ -106,6 +106,12 @@ This section guides you through the steps to configure the Azure AD provisioning
 
 5. Under the **Admin Credentials** section, input your GitHub Enterprise Managed User (OIDC) Tenant URL and Secret Token. Click **Test Connection** to ensure Azure AD can connect to GitHub Enterprise Managed User (OIDC). If the connection fails, ensure your GitHub Enterprise Managed User (OIDC) account has created the secret token as an enterprise owner and try again.
 
+   For "Tenant URL", type https://api.github.com/scim/v2/enterprises/YOUR_ENTERPRISE, replacing YOUR_ENTERPRISE with the name of your enterprise account.
+   
+   For example, if your enterprise account's URL is https://github.com/enterprises/octo-corp, the name of the enterprise account is octo-corp.
+   
+   For "Secret token", paste the personal access token with the admin:enterprise scope that  you created earlier.
+   
      ![Token](common/provisioning-testconnection-tenanturltoken.png)
 
 6. In the **Notification Email** field, enter the email address of a person or group who should receive the provisioning error notifications and select the **Send an email notification when a failure occurs** check box.
@@ -172,4 +178,4 @@ Once you've configured provisioning, use the following resources to monitor your
 
 ## Next steps
 
-* [Learn how to review logs and get reports on provisioning activity](../app-provisioning/check-status-user-account-provisioning.md)
+* [Learn how to review logs and get reports on provisioning activity](../app-provisioning/check-status-user-account-provisioning.md)

articles/active-directory/saas-apps/jiramicrosoft-tutorial.md

@@ -237,7 +237,7 @@ In this section, you'll enable B.Simon to use Azure single sign-on by granting a
 
 	k. **Enable Use of Application Proxy** checkbox, if you have configured your on-premise atlassian application in an App Proxy setup.
 
-	* For App proxy setup , follow the steps on the [Azure AD App Proxy Documentation](/articles/active-directory/app-proxy/what-is-application-proxy.md).
+	* For App proxy setup , follow the steps on the [Azure AD App Proxy Documentation](../app-proxy/what-is-application-proxy.md).
 
 	l. Click **Save** button to save the settings.
 

articles/azure-vmware/concepts-storage.md

@@ -49,7 +49,7 @@ vSAN datastores use data-at-rest encryption by default using keys stored in Azur
 
 ## Datastore capacity expansion options
 
-The vSAN datastore capacity can be expanded by connecting Azure storage resources such as [Azure NetApp Files volumes as datastores](/azure/azure-vmware/attach-azure-netapp-files-to-azure-vmware-solution-hosts). Virtual machines can be migrated between vSAN and Azure NetApp Files datastores using storage vMotion. Azure NetApp Files datastores can be replicated to other regions using storage based [Cross-region replication](/azure/azure-netapp-files/cross-region-replication-introduction) for testing, development and failover purposes.
+The vSAN datastore capacity can be expanded by connecting Azure storage resources such as [Azure NetApp Files volumes as datastores](/azure/azure-vmware/attach-azure-netapp-files-to-azure-vmware-solution-hosts). Virtual machines can be migrated between vSAN and Azure NetApp Files datastores using storage vMotion.
 Azure NetApp Files is available in [Ultra, Premium and Standard performance tiers](/azure/azure-netapp-files/azure-netapp-files-service-levels) to allow for adjusting performance and cost to the requirements of the workloads. 
 
 ## Azure storage integration

articles/azure-vmware/configure-vmware-hcx.md

@@ -75,6 +75,12 @@ VMware HCX Connector deploys a subset of virtual appliances (automated) that req
    - vMotion
    - Replication
    - Uplink
+   
+   > [!NOTE]
+   > * Azure VMware Solution connected via VPN should set Uplink Network Profile MTU's to 1350 to account for IPSec overhead.
+   > * Azure VMWare Solution defaults to 1500 MTU and is sufficient for most ExpressRoute implementations.
+   >   * If your ExpressRoute provider does not support jumbo frame, MTU may need to be lowered in ExpressRoute setups as well.
+   >   * Changes to MTU should be performed on both HCX Connector (on-premises) and HCX Cloud Manager (Azure VMware Solution) network profiles.
 
 1. Under **Infrastructure**, select **Interconnect** > **Multi-Site Service Mesh** > **Network Profiles** > **Create Network Profile**.
 

articles/container-apps/communicate-between-microservices.md

@@ -163,13 +163,15 @@ Output from the `az acr build` command shows the upload progress of the source c
     # [Bash](#tab/bash)
 
     ```azurecli
-     docker push $ACR_NAME.azurecr.io/albumapp-ui 
+
+     docker push "$ACR_NAME.azurecr.io/albumapp-ui" 
     ```
 
     # [PowerShell](#tab/powershell)
 
     ```powershell
-    docker push $ACR_NAME.azurecr.io/albumapp-ui 
+
+    docker push "$ACR_NAME.azurecr.io/albumapp-ui"
     ```
 
     ---

articles/dev-box/concept-dev-box-concepts.md

@@ -21,12 +21,10 @@ This article describes the key concepts and components of Microsoft Dev Box.
 
 ## Dev center
 
-A dev center is a collection of projects that require similar settings. Dev centers enable dev infrastructure managers to manage the images and SKUs available to the projects using [dev box definitions](concept-dev-box-concepts.md#dev-box-definition), and configure the networks the development teams consume using [network connections](./concept-dev-box-concepts.md#network-connection).  
-
+A dev center is a collection of projects that require similar settings. Dev centers enable dev infrastructure managers to manage the images and SKUs available to the projects using [dev box definitions](concept-dev-box-concepts.md#dev-box-definition) and configure the networks the development teams consume using [network connections](./concept-dev-box-concepts.md#network-connection).  
 ## Projects
 
-A project is the point of access for the development team members. When you associate a project with a dev center, all the settings at the dev center level will be applied to the project automatically. Each project can be associated with only one dev center. Dev managers can configure the dev boxes available for the project by  specifying the [dev box definitions](./concept-dev-box-concepts.md#dev-box-definition) appropriate for their workloads.
-
+A project is the point of access for the development team members. When you associate a project with a dev center, all the settings at the dev center level will be applied to the project automatically. Each project can be associated with only one dev center. Dev managers can configure the dev boxes available for the project by specifying the [dev box definitions](./concept-dev-box-concepts.md#dev-box-definition) appropriate for their workloads.
 ## Dev box definition
 
 A dev box definition specifies a source image and size, including compute size and storage size. You can use a source image from the marketplace, or a custom image from your own [Azure Compute Gallery](./how-to-configure-azure-compute-gallery.md). You can use dev box definitions across multiple projects in a dev center. 
@@ -35,12 +33,10 @@ A dev box definition specifies a source image and size, including compute size a
 
 IT administrators and dev infrastructure managers configure the network used for dev box creation in accordance with their organizational policies. Network connections store configuration information like Active Directory join type and virtual network that dev boxes use to connect to network resources. 
 
-When creating a network connection, you must choose whether to use a native Azure Active Directory (Azure AD) join or a hybrid Azure AD join. If your dev boxes need to connect exclusively to cloud-based resources, use a native Azure AD join. Use a hybrid Azure AD join if your dev boxes need to connect to on-premises resources and cloud-based resources. To learn more about Azure AD and hybrid Azure AD joined  devices, [Plan your Azure Active Directory device deployment](/azure/active-directory/devices/plan-device-deployment).
-
+When creating a network connection, you must choose whether to use a native Azure Active Directory (Azure AD) join or a hybrid Azure AD join. If your dev boxes need to connect exclusively to cloud-based resources, use a native Azure AD join. Use a hybrid Azure AD join if your dev boxes need to connect to on-premises resources and cloud-based resources. To learn more about Azure AD and hybrid Azure AD joined devices, [Plan your Azure Active Directory device deployment](/azure/active-directory/devices/plan-device-deployment).
 The virtual network specified in a network connection also determines the region for the dev box. You can create multiple network connections based on the regions where you support developers and use them when creating different dev box pools to ensure dev box users create a dev box in a region close to them. Using a region close to the dev box user provides the best experience. 
 
 ## Dev box pool 
-A dev box pool is a collection of dev boxes that you manage together that you manage together and to which you apply similar settings. You can create multiple dev box pools to support the needs of hybrid teams working in different regions or on different workloads.
-
+A dev box pool is a collection of dev boxes that you manage together and to which you apply similar settings. You can create multiple dev box pools to support the needs of hybrid teams working in different regions or on different workloads.
 ## Dev box 
-A dev box is a preconfigured ready-to-code workstation that you create through the self-service developer portal. The new dev box has all the tools, binaries, and configuration required for a dev box user to be productive immediately. You can create and manage multiple dev boxes to work on multiple work streams. As a dev box user you have control over your own dev boxes - you can create more as you need them, and delete them when you have finished using them.
+A dev box is a preconfigured ready-to-code workstation that you create through the self-service developer portal. The new dev box has all the tools, binaries, and configuration required for a dev box user to be productive immediately. You can create and manage multiple dev boxes to work on multiple work streams. As a dev box user, you have control over your own dev boxes - you can create more as you need them and delete them when you have finished using them.

articles/openshift/support-policies-v4.md

@@ -25,7 +25,7 @@ Certain configurations for Azure Red Hat OpenShift 4 clusters can affect your cl
 * Don't remove or modify the cluster Prometheus service.
 * Don't remove or modify the cluster Alertmanager service or Default receiver. It *is* supported to create additional receivers to notify external systems.
 * Don't remove Service Alertmanager rules.
-* Security groups can't be modified. Any attempt to modify security groups will be reverted.
+* The ARO-provided Network Security Group can't be modified or replaced. Any attempt to modify or replace it will be reverted.
 * Don't remove or modify Azure Red Hat OpenShift service logging (mdsd pods).
 * Don't remove or modify the 'arosvc.azurecr.io' cluster pull secret.
 * All cluster virtual machines must have direct outbound internet access, at least to the Azure Resource Manager (ARM) and service logging (Geneva) endpoints.  No form of HTTPS proxying is supported.

articles/service-bus-messaging/service-bus-messages-payloads.md

@@ -67,10 +67,12 @@ While this hidden serialization magic is convenient, applications should take ex
 
 The .NET Standard and Java API variants only accept byte arrays, which means that the application must handle object serialization control. 
 
+If the payload of a message can't be deserialized, then it is recommended to [dead-letter the message](/azure/service-bus-messaging/service-bus-dead-letter-queues?source=recommendations#application-level-dead-lettering).
+
 ## Next steps
 
 To learn more about Service Bus messaging, see the following topics:
 
 * [Service Bus queues, topics, and subscriptions](service-bus-queues-topics-subscriptions.md)
 * [Get started with Service Bus queues](service-bus-dotnet-get-started-with-queues.md)
-* [How to use Service Bus topics and subscriptions](service-bus-dotnet-how-to-use-topics-subscriptions.md)
+* [How to use Service Bus topics and subscriptions](service-bus-dotnet-how-to-use-topics-subscriptions.md)