Merge pull request #198195 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/manage-apps/migrate-okta-sync-provisioning-to-azure-active-directory.md

@@ -79,11 +79,11 @@ The example will grab *all* on-premises Azure AD users and export a list of thei
 1. Run these commands in PowerShell on a domain controller on-premises:
 
    ```PowerShell
-   Get-ADUser -Filter * -Properties objectGUID | Select-Object
+   Get-ADUser -Filter * -Properties objectGUID | Select -Object
    UserPrincipalName, Name, objectGUID, @{Name = 'ImmutableID';
    Expression = {
-   [system.convert\]::ToBase64String(([GUID\]\$_.objectGUID).ToByteArray())
-   } } | export-csv C:\\Temp\\OnPremIDs.csv
+   [system.convert]::ToBase64String((GUID).tobytearray())
+   } } | export-csv C:\Temp\OnPremIDs.csv
    ```
 
    ![Screenshot that shows domain controller on-premises commands.](./media/migrate-okta-sync-provisioning-to-azure-active-directory-connect-based-synchronization/domain-controller.png)

includes/azure-virtual-network-limits.md

@@ -74,9 +74,10 @@ The following limits apply only for networking resources managed through Azure R
 | Backend resources per Load Balancer <sup>1<sup> | 1,200                 |
 | High-availability ports rule            | 1 per internal frontend       |
 | Outbound rules per Load Balancer        | 600                           |
-| Load Balancers per VM                   | 2 (1 Public and 1 internal)   |
+| Load Balancers per VM <sup>2<sup>       | 2 (1 Public and 1 internal)   |
 
 <sup>1</sup> The limit is up to 1,200 resources, in any combination of standalone virtual machine resources, availability set resources, and virtual machine scale-set placement groups.
+<sup>2</sup> An exception to this limit is that 2 public load balancers can be in front of a VM if an IPv4 address config is used for one load balancer and IPv6 address config is used for the second.
 
 **Basic Load Balancer**
 
@@ -85,12 +86,12 @@ The following limits apply only for networking resources managed through Azure R
 | Load balancers                          | 1,000                        |
 | Rules per resource                      | 250                          |
 | Rules per NIC (across all IPs on a NIC) | 300                          |
-| Frontend IP configurations <sup>2<sup>  | 200                          |
+| Frontend IP configurations <sup>3<sup>  | 200                          |
 | Backend pool size                       | 300 IP configurations, single availability set |
 | Availability sets per Load Balancer     | 1                            |
 | Load Balancers per VM                   | 2 (1 Public and 1 internal)  |
 
-<sup>2</sup> The limit for a single discrete resource in a backend pool (standalone virtual machine, availability set, or virtual machine scale-set placement group) is to have up to 250 Frontend IP configurations across a single Basic Public Load Balancer and Basic Internal Load Balancer.
+<sup>3</sup> The limit for a single discrete resource in a backend pool (standalone virtual machine, availability set, or virtual machine scale-set placement group) is to have up to 250 Frontend IP configurations across a single Basic Public Load Balancer and Basic Internal Load Balancer.
 
 <a name="virtual-networking-limits-classic"></a>The following limits apply only for networking resources managed through the **classic** deployment model per subscription. Learn how to [view your current resource usage against your subscription limits](../articles/networking/check-usage-against-limits.md).