Merge pull request #262044 from MicrosoftDocs/main

12/28/2023 PM Publish

Author: Taojunshen

articles/ddos-protection/ddos-switch-ddos-protection-tier.md

@@ -61,7 +61,7 @@ You can switch from Network Protection to IP Protection using the Azure portal.
 The DDoS protection plan must be disassociated from the protected resources before you can delete the plan. 
 
 >[!WARNING]
->To maintain DDoS Protection during migration, ensure IP protection is enabled on all pubic IPs protected by Network Protection.
+>To maintain DDoS Protection during migration, ensure IP protection is enabled on all public IPs protected by Network Protection.
 
 1. In the search box at the top of the portal, enter **DDoS protection plans**. Select your DDoS protection plan.
 1. In the **Settings** page, select the **Protected Resources** tab, then select the **Dissociate** icon next to the virtual network that contains the resources you are protecting. When prompted, select **Yes** to confirm.

articles/ddos-protection/manage-ddos-protection-powershell-ip.md

@@ -69,7 +69,7 @@ $publicIp = Get-AzPublicIpAddress -Name myStandardPublicIP -ResourceGroupName My
 #Checks the status of the public IP address
 $protectionMode = $publicIp.DdosSettings.ProtectionMode
 
-#Returns the status of the pubic IP address
+#Returns the status of the public IP address
 $protectionMode
 
 ```

articles/expressroute/expressroute-connectivity-models.md

@@ -5,20 +5,20 @@ services: expressroute
 author: duongau
 ms.service: expressroute
 ms.topic: conceptual
-ms.date: 10/31/2022
+ms.date: 12/28/2023
 ms.author: duau
 ---
 
 # ExpressRoute connectivity models
 
-ExpressRoute allows you to create a connection between your on-premises network and the Microsoft cloud in four different ways, [CloudExchange Co-location](#CloudExchange), [Point-to-point Ethernet Connection](#Ethernet), [Any-to-any (IPVPN) Connection](#IPVPN), and [ExpressRoute Direct](#Direct). Connectivity providers may offer more than one connectivity models. You can work with your connectivity provider to pick the model that works best for you.
+ExpressRoute allows you to create a connection between your on-premises network and the Microsoft cloud in four different ways, [CloudExchange Colocation](#CloudExchange), [Point-to-point Ethernet Connection](#Ethernet), [Any-to-any (IPVPN) Connection](#IPVPN), and [ExpressRoute Direct](#Direct). Connectivity providers might offer more than one connectivity models. You can work with your connectivity provider to pick the model that works best for you.
 <br><br>
 
 :::image type="content" source="./media/expressroute-connectivity-models/expressroute-connectivity-models-diagram.png" alt-text="ExpressRoute connectivity model diagram":::
 
-## <a name="CloudExchange"></a>Co-located at a cloud exchange
+## <a name="CloudExchange"></a>Colocated at a cloud exchange
 
-If you're co-located in a facility with a cloud exchange, you can request for virtual cross-connections to the Microsoft cloud through the co-location provider’s Ethernet exchange. Co-location providers can offer either Layer 2 cross-connections, or managed Layer 3 cross-connections between your infrastructure in the co-location facility and the Microsoft cloud.
+If you're colocated in a facility with a cloud exchange, you can request for virtual cross-connections to the Microsoft cloud through the colocation provider’s Ethernet exchange. Colocation providers can offer either Layer 2 cross-connections, or managed Layer 3 cross-connections between your infrastructure in the colocation facility and the Microsoft cloud.
 
 ## <a name="Ethernet"></a>Point-to-point Ethernet connections
 
@@ -41,4 +41,4 @@ You can connect directly into the Microsoft global network at a peering location
 * Configure your ExpressRoute connection.
   * [Create an ExpressRoute circuit](expressroute-howto-circuit-portal-resource-manager.md)
   * [Configure routing](expressroute-howto-routing-portal-resource-manager.md)
-  * [Link a VNet to an ExpressRoute circuit](expressroute-howto-linkvnet-portal-resource-manager.md)
+  * [Link a virtual network to an ExpressRoute circuit](expressroute-howto-linkvnet-portal-resource-manager.md)

articles/expressroute/expressroute-howto-circuit-arm.md

@@ -4,7 +4,7 @@ description: This quickstart shows you how to create, provision, verify, update,
 services: expressroute
 author: duongau
 ms.author: duau
-ms.date: 12/27/2022
+ms.date: 12/28/2023
 ms.topic: quickstart
 ms.service: expressroute
 ms.custom: devx-track-azurepowershell, mode-api
@@ -34,7 +34,7 @@ This quickstart shows you how to create an ExpressRoute circuit using PowerShell
 
 Before you create an ExpressRoute circuit, you need the list of supported connectivity providers, locations, and bandwidth options.
 
-The PowerShell cmdlet **Get-AzExpressRouteServiceProvider** returns this information, which you’ll use in later steps:
+The PowerShell cmdlet **Get-AzExpressRouteServiceProvider** returns this information, which you use in later steps:
 
 ```azurepowershell-interactive
 Get-AzExpressRouteServiceProvider
@@ -145,7 +145,7 @@ Peerings                         : []
 
 ### Send the service key to your connectivity provider for provisioning
 
-*ServiceProviderProvisioningState* provides you information about the current state of provisioning on the service-provider side. *CircuitProvisioningState* provides you the status on the Microsoft side. For more information about circuit provisioning states, see [Workflows](expressroute-workflows.md#expressroute-circuit-provisioning-states).
+*ServiceProviderProvisioningState* provides you with information about the current state of provisioning on the service-provider side. *CircuitProvisioningState* provides you with the status on the Microsoft side. For more information about circuit provisioning states, see [Workflows](expressroute-workflows.md#expressroute-circuit-provisioning-states).
 
 When you create a new ExpressRoute circuit, the circuit is in the following state:
 
@@ -170,7 +170,7 @@ CircuitProvisioningState         : Enabled
 
 ### Periodically check the status and the state of the circuit key
 
-Checking the status and the state of the service key will let you know when your provider has provisioned your circuit. After the circuit has been configured, *ServiceProviderProvisioningState* appears as *Provisioned*, as shown in the following example:
+Checking the status and the state of the service key lets you know when your provider provisioned your circuit. After the circuit gets configured, *ServiceProviderProvisioningState* appears as *Provisioned*, as shown in the following example:
 
 ```azurepowershell-interactive
 Get-AzExpressRouteCircuit -Name "ExpressRouteARMCircuit" -ResourceGroupName "ExpressRouteResourceGroup"
@@ -312,7 +312,7 @@ $ckt.sku.Name = "Premium_MeteredData"
 Set-AzExpressRouteCircuit -ExpressRouteCircuit $ckt
 ```
 
-The circuit now has the ExpressRoute premium add-on features enabled. We begin billing you for the premium add-on capability as soon as the command has successfully run.
+The circuit now has the ExpressRoute premium add-on features enabled. We begin billing you for the premium add-on capability as soon as the command successfully ran.
 
 ### To disable the ExpressRoute premium add-on
 
@@ -323,8 +323,8 @@ The circuit now has the ExpressRoute premium add-on features enabled. We begin b
 Note the following information:
 
 * Before you downgrade from premium to standard, you must ensure that the number of virtual networks that are linked to the circuit is less than 10. If you don't, your update request fails, and we bill you at premium rates.
-* All virtual networks in other geopolitical regions must be first unlinked. If you don't remove the link, your update request will fail and we continue to bill you at premium rates.
-* Your route table must be less than 4,000 routes for private peering. If your route table size is greater than 4,000 routes, the BGP session will drop. The BGP session won't be re-enabled until the number of advertised prefixes is under 4,000.
+* All virtual networks in other geopolitical regions must be first unlinked. If you don't remove the link, your update request fails and we continue to bill you at premium rates.
+* Your route table must be less than 4,000 routes for private peering. If your route table size is greater than 4,000 routes, the BGP session drops. The BGP session doesn't re-establish until the number of advertised prefixes is under 4,000.
 
 You can disable the ExpressRoute premium add-on for the existing circuit by using the following PowerShell cmdlet:
 
@@ -357,7 +357,7 @@ $ckt.ServiceProviderProperties.BandwidthInMbps = 1000
 Set-AzExpressRouteCircuit -ExpressRouteCircuit $ckt
 ```
 
-Your circuit will be upgraded on the Microsoft side. Then you must contact your connectivity provider to update configurations on their side to match this change. After you make this notification, we'll begin billing you for the updated bandwidth option.
+Your circuit is upgraded on the Microsoft side. Then you must contact your connectivity provider to update configurations on their side to match this change. After you make this notification, we'll begin billing you for the updated bandwidth option.
 
 ### To move the SKU from metered to unlimited
 
@@ -382,7 +382,7 @@ Note the following information:
 
 * All virtual networks must be unlinked from the ExpressRoute circuit. If this operation fails, check to see if any virtual networks are linked to the circuit.
 * If the ExpressRoute circuit service provider provisioning state is **Provisioning** or **Provisioned** you must work with your service provider to deprovision the circuit on their side. We continue to reserve resources and bill you until the service provider completes deprovisioning the circuit and notifies us.
-* If the service provider has deprovisioned the circuit meaning the service provider provisioning state gets set to **Not provisioned**, you can delete the circuit. The billing for the circuit will then stop.
+* If the service provider deprovisioned the circuit, meaning the service provider provisioning state gets set to **Not provisioned**, you can delete the circuit. The billing for the circuit stops.
 
 ## Clean up resources
 

articles/expressroute/expressroute-howto-macsec.md

@@ -5,7 +5,7 @@ services: expressroute
 author: duongau
 ms.service: expressroute
 ms.topic: how-to
-ms.date: 12/05/2023
+ms.date: 12/28/2023
 ms.author: duau 
 ms.custom: devx-track-azurepowershell
 
@@ -94,7 +94,7 @@ Follow these steps to begin the configuration:
     > * For GcmAes128 and GcmAesXpn128, the CAK must be an even-length string with 32 hexadecimal digits (0-9, A-F).
     > * For GcmAes256 and GcmAesXpn256, the CAK must be an even-length string with 64 hexadecimal digits (0-9, A-F).
 
-1. Grant the user identity the authorization to perform the GET operation.
+1. Grant the user identity the authorization to perform the `GET` operation.
 
     ```azurepowershell-interactive
     Set-AzKeyVaultAccessPolicy -VaultName "your_key_vault_name" -PermissionsToSecrets get -ObjectId $identity.PrincipalId

articles/expressroute/expressroute-introduction.md

@@ -4,9 +4,8 @@ description: The ExpressRoute Technical Overview explains how an ExpressRoute co
 services: expressroute
 author: duongau
 ms.service: expressroute
-ms.custom: ignite-2022
 ms.topic: overview
-ms.date: 12/22/2022
+ms.date: 12/28/2023
 ms.author: duau
 ---
 
@@ -17,7 +16,7 @@ ms.author: duau
 
 ExpressRoute lets you extend your on-premises networks into the Microsoft cloud over a private connection with the help of a connectivity provider. With ExpressRoute, you can establish connections to Microsoft cloud services, such as Microsoft Azure and Microsoft 365.
 
-Connectivity can be from an any-to-any (IP VPN) network, a point-to-point Ethernet network, or a virtual cross-connection through a connectivity provider at a colocation facility. ExpressRoute connections don't go over the public Internet. This allows ExpressRoute connections to offer more reliability, faster speeds, consistent latencies, and higher security than typical connections over the Internet. For information on how to connect your network to Microsoft using ExpressRoute, see [ExpressRoute connectivity models](expressroute-connectivity-models.md).
+Connectivity can be from an any-to-any (IP VPN) network, a point-to-point Ethernet network, or a virtual cross-connection through a connectivity provider at a colocation facility. ExpressRoute connections offer more reliability, faster speeds, consistent latencies, and higher security than typical connections over the Internet, because they don’t go over the public Internet. For information on how to connect your network to Microsoft using ExpressRoute, see [ExpressRoute connectivity models](expressroute-connectivity-models.md).
 
 ![ExpressRoute connection overview](./media/expressroute-introduction/expressroute-connection-overview.png)
 
@@ -45,7 +44,7 @@ Microsoft uses BGP, an industry standard dynamic routing protocol, to exchange r
 
 ### Redundancy
 
-Each ExpressRoute circuit consists of two connections to two Microsoft Enterprise edge routers (MSEEs) at an [ExpressRoute Location](./expressroute-locations.md#expressroute-locations) from the connectivity provider or your network edge. Microsoft requires dual BGP connections from the connectivity provider or your network edge – one to each MSEE. You may choose not to deploy redundant devices/Ethernet circuits at your end. However, connectivity providers use redundant devices to ensure that your connections are handed off to Microsoft in a redundant manner.
+Each ExpressRoute circuit consists of two connections to two Microsoft Enterprise edge routers (MSEEs) at an [ExpressRoute Location](./expressroute-locations.md#expressroute-locations) from the connectivity provider or your network edge. Microsoft requires dual BGP connections from the connectivity provider or your network edge – one to each MSEE. You might choose not to deploy redundant devices/Ethernet circuits at your end. However, connectivity providers use redundant devices to ensure that your connections are handed off to Microsoft in a redundant manner.
 
 ### Connectivity to Microsoft cloud services
 
@@ -63,11 +62,11 @@ For a detailed list of services supported over ExpressRoute, visit the [ExpressR
 
 You can connect to Microsoft from one of our [peering locations](expressroute-locations.md) and access regions within the same geopolitical region.
 
-For example, if you connect to Microsoft in Amsterdam through ExpressRoute. You'll have access to all of  Microsoft cloud services hosted in North and West Europe. For an overview of the geopolitical regions, the associated Microsoft cloud regions, and corresponding ExpressRoute peering locations, see the [ExpressRoute partners and peering locations](expressroute-locations.md) article.
+For example, if you connect to Microsoft in Amsterdam through ExpressRoute. You have access to all of  Microsoft cloud services hosted in North and West Europe. For an overview of the geopolitical regions, the associated Microsoft cloud regions, and corresponding ExpressRoute peering locations, see the [ExpressRoute partners and peering locations](expressroute-locations.md) article.
 
 ### Global connectivity with ExpressRoute Premium
 
-You can enable [ExpressRoute Premium](expressroute-faqs.md#expressroute-premium) to extend connectivity across geopolitical boundaries. If you connect to Microsoft in Amsterdam through ExpressRoute, you'll have access to all of Microsoft cloud services hosted in every region across the globe. For example, you'll have access to services deployed in West US or Australian East the same way you access North and West Europe regions. National clouds are excluded.
+You can enable [ExpressRoute Premium](expressroute-faqs.md#expressroute-premium) to extend connectivity across geopolitical boundaries. If you connect to Microsoft in Amsterdam through ExpressRoute, you have access to all of Microsoft cloud services hosted in every region across the globe. For example, you have access to services deployed in West US or Australian East the same way you access North and West Europe regions. National clouds are excluded.
 
 ### Local connectivity with ExpressRoute Local
 
@@ -77,7 +76,7 @@ For peering location and supported Azure local region, see [providers by locatio
 
 ### Across on-premises connectivity with ExpressRoute Global Reach
 
-You can enable ExpressRoute Global Reach to exchange data across your on-premises sites by connecting your ExpressRoute circuits. For example, if you have a private data center in California connected to an ExpressRoute circuit in Silicon Valley and another private data center in Texas connected to an ExpressRoute circuit in Dallas. With ExpressRoute Global Reach, you can connect your private data centers together through these two ExpressRoute circuits. Your cross data-center traffic will traverse through the Microsoft network.
+By enabling ExpressRoute Global Reach, you can exchange data across your on-premises sites through your ExpressRoute circuits. For instance, suppose you have two private data centers, one in California and one in Texas, each connected to an ExpressRoute circuit in their respective regions. You can use ExpressRoute Global Reach to link your data centers with these circuits, and your cross data-center traffic uses the Microsoft network.
 
 For more information, see [ExpressRoute Global Reach](expressroute-global-reach.md).
 
@@ -128,8 +127,8 @@ You can select a billing model that works best for you:
 * **Metered data**. Billing is based on a monthly fee; all inbound data transfer is free of charge. Outbound data transfer is charged per GB of data transfer. Data transfer rates vary by region.
 * **ExpressRoute premium add-on**. ExpressRoute premium is an add-on to the ExpressRoute circuit. The ExpressRoute premium add-on provides the following capabilities: 
   * Increased route limits for Azure public and Azure private peering from 4,000 routes to 10,000 routes.
-  * Global connectivity for services. An ExpressRoute circuit created in any region (excluding national clouds) will have access to resources across every other region in the world. For example, a virtual network created in West Europe can be accessed through an ExpressRoute circuit provisioned in Silicon Valley.
-  * Increased number of VNet links per ExpressRoute circuit from 10 to a larger limit, depending on the bandwidth of the circuit.
+  * Global connectivity for services. An ExpressRoute circuit created in any region (excluding national clouds) has access to resources across every other region in the world. For example, a virtual network created in West Europe can be accessed through an ExpressRoute circuit provisioned in Silicon Valley.
+  * Increased number of virtual network links per ExpressRoute circuit from 10 to a larger limit, depending on the bandwidth of the circuit.
 
 ## FAQ