You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/expressroute/about-upgrade-circuit-bandwidth.md
+13-8Lines changed: 13 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,35 +5,40 @@ services: expressroute
5
5
author: duongau
6
6
ms.service: azure-expressroute
7
7
ms.topic: concept-article
8
-
ms.date: 10/16/2023
8
+
ms.date: 01/31/2025
9
9
ms.author: duau
10
10
---
11
11
12
12
# About upgrading ExpressRoute circuit bandwidth
13
13
14
-
ExpressRoute is a dedicated and private connection to Microsoft's global network. Connectivity is facilitated through an ExpressRoute partner's network, or a direct connection to the Microsoft Enterprise Edge (MSEE) devices. Once physical connectivity has been configured and tested, you can enable layer-2 and layer-3 connectivity by creating an ExpressRoute circuit and configuring peering.
14
+
ExpressRoute provides a dedicated, private connection to Microsoft's global network. You can establish this connectivity through an ExpressRoute partner's network or directly to the Microsoft Enterprise Edge (MSEE) devices. After setting up and testing the physical connection, you can enable layer-2 and layer-3 connectivity by creating an ExpressRoute circuit and configuring peering.
An ExpressRoute circuit is created on a physical connection between Microsoft and a ExpressRoute Partner. The physical connection has a fixed capacity. If you're unable to increase your circuit size that means that the underlying physical connection for your existing circuit doesn’t have capacity for the upgrade. You need to create a new circuit if you want to change the circuit size. For more information, see [Migrate to a new ExpressRoute circuit](circuit-migration.md).
20
+
If you're unable to increase your circuit size, it means the underlying physical connection for your existing circuit lacks the capacity for the upgrade. In this case, you need to create a new circuit. For more information, see [Migrate to a new ExpressRoute circuit](circuit-migration.md).
21
21
22
-
After you've successfully created the new ExpressRoute circuit, you should link your existing virtual networks to this circuit. You can then test and validate the connectivity of the new ExpressRoute circuit before you deprovision the old circuit. These recommended migration steps minimize down time and disruption to your production work load.
22
+
After creating the new ExpressRoute circuit, link your existing virtual networks to it. Test and validate the connectivity of the new circuit before deprovisioning the old one. These steps help minimize downtime and disruption to your production workload.
If you're unable to create a new ExpressRoute circuit because of a capacity error. It means this ExpressRoute partner doesn’t have capacity to connect to Microsoft at this peering location. Contact your ExpressRoute partner to request for more capacity.
26
+
If you're unable to create a new ExpressRoute circuit due to a capacity error, it means the ExpressRoute partner doesn’t have sufficient capacity at the peering location to connect to Microsoft. Contact your ExpressRoute partner to request additional capacity.
27
27
28
-
Once the new capacity gets provisioned, you can use the methods contained in the [Upgrade circuit bandwidth](#upgrade) section to create a new circuit, configure connectivity, and delete the old circuit.
28
+
Once the new capacity is provisioned, you can follow the methods in the [Upgrade circuit bandwidth](#upgrade) section to create a new circuit, configure connectivity, and delete the old circuit.
29
29
30
30
### <aname="bandwidth"></a>Insufficient ExpressRoute Direct bandwidth
31
31
32
-
If the ExpressRoute Direct doesn't have sufficient capacity, you have two options. You can either delete circuits that are associated to the ExpressRoute Direct resource that you no longer need, or create a new ExpressRoute Direct resource. For guidance on managing the ExpressRoute Direct resource, refer to [How to configure ExpressRoute Direct](how-to-expressroute-direct-portal.md).
32
+
If ExpressRoute Direct lacks sufficient capacity, you have two options:
33
+
34
+
- Delete any unnecessary circuits associated with the ExpressRoute Direct resource.
35
+
- Create a new ExpressRoute Direct resource.
36
+
37
+
For detailed guidance on managing ExpressRoute Direct resources, see [How to configure ExpressRoute Direct](how-to-expressroute-direct-portal.md).
33
38
34
39
## <aname="upgrade"></a>Upgrade circuit bandwidth
35
40
36
-
To upgrade circuit bandwidth, the ExpressRoute Direct, or ExpressRoute partner needs to have[sufficient available bandwidth](#considerations) for the upgrade to succeed.
41
+
To upgrade circuit bandwidth, ensure that the ExpressRoute Direct or ExpressRoute partner has[sufficient available bandwidth](#considerations) for the upgrade to succeed.
37
42
38
43
If capacity is available, you can upgrade the circuit using the following methods:
Copy file name to clipboardExpand all lines: articles/expressroute/configure-expressroute-private-peering.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@ author: duongau
6
6
ms.author: duau
7
7
ms.service: azure-expressroute
8
8
ms.topic: tutorial
9
-
ms.date: 01/02/2024
9
+
ms.date: 01/31/2025
10
10
# Customer intent: As a network engineer, I want to establish a private connection from my on-premises network to my Azure virtual network using ExpressRoute.
Copy file name to clipboardExpand all lines: articles/expressroute/expressroute-about-encryption.md
+22-21Lines changed: 22 additions & 21 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,46 +1,47 @@
1
1
---
2
-
title: 'Azure ExpressRoute: About Encryption'
3
-
description: Learn about ExpressRoute encryption.
2
+
title: 'About encryption for Azure ExpressRoute'
3
+
description: Learn about the use of encryption with Azure ExpressRoute.
4
4
services: expressroute
5
5
author: duongau
6
6
ms.service: azure-expressroute
7
7
ms.custom:
8
8
- ignite-2023
9
9
ms.topic: concept-article
10
-
ms.date: 11/15/2023
10
+
ms.date: 01/31/2025
11
11
ms.author: duau
12
12
---
13
-
# ExpressRoute encryption
13
+
14
+
# About encryption for Azure ExpressRoute
14
15
15
-
ExpressRoute supports a couple of encryption technologies to ensure confidentiality and integrity of the data traversing between your network and Microsoft's network. By default traffic over an ExpressRoute connection isn't encrypted.
16
+
ExpressRoute supports encryption technologies to ensure the confidentiality and integrity of data between your network and Microsoft's network. By default, traffic over an ExpressRoute connection isn't encrypted.
16
17
17
18
## Point-to-point encryption by MACsec FAQ
18
19
19
-
MACsec is an [IEEE standard](https://1.ieee802.org/security/802-1ae/). It encrypts data at the Media Access control (MAC) level or Network Layer 2. You can use MACsec to encrypt the physical links between your network devices and Microsoft's network devices when you connect to Microsoft via [ExpressRoute Direct](expressroute-erdirect-about.md). MACsec is disabled on ExpressRoute Direct ports by default. You bring your own MACsec key for encryption and store it in [Azure Key Vault](/azure/key-vault/general/overview). You decide when to rotate the key.
20
+
MACsec is an [IEEE standard](https://1.ieee802.org/security/802-1ae/) that encrypts data at the Media Access Control (MAC) level (Network Layer 2). You can use MACsec to encrypt the physical links between your network devices and Microsoft's network devices when connecting via [ExpressRoute Direct](expressroute-erdirect-about.md). MACsec is disabled on ExpressRoute Direct ports by default. You must bring your own MACsec key for encryption and store it in [Azure Key Vault](/azure/key-vault/general/overview). You decide when to rotate the key.
20
21
21
22
### Can I enable Azure Key Vault firewall policies when storing MACsec keys?
22
-
23
-
Yes, ExpressRoute is a trusted Microsoft service. You can configure Azure Key Vault firewall policies and allow trusted services to bypass the firewall. For more information, see [Configure Azure Key Vault firewalls and virtual networks](/azure/key-vault/general/network-security).
23
+
24
+
Yes, ExpressRoute is a trusted Microsoft service. You can configure Azure Key Vault firewall policies to allow trusted services to bypass the firewall. For more information, see [Configure Azure Key Vault firewalls and virtual networks](/azure/key-vault/general/network-security).
24
25
25
26
### Can I enable MACsec on my ExpressRoute circuit provisioned by an ExpressRoute provider?
26
27
27
-
No. MACsec encrypts all traffic on a physical link with a key owned by one entity (for example, customer). Therefore, it's available on ExpressRoute Direct only.
28
+
No. MACsec encrypts all traffic on a physical link with a key owned by one entity (for example, the customer). Therefore, it's available only on ExpressRoute Direct.
28
29
29
-
### Can I encrypt some of the ExpressRoute circuits on my ExpressRoute Direct ports and leave other circuits on the same ports unencrypted?
30
+
### Can I encrypt some ExpressRoute circuits on my ExpressRoute Direct ports and leave others unencrypted?
30
31
31
-
No. Once MACsec is enabled all network control traffic, for example, the BGP data traffic, and customer data traffic are encrypted.
32
+
No. Once MACsec is enabled, all network control traffic (for example, BGP data traffic) and customer data traffic are encrypted.
32
33
33
-
### When I enable/disable MACsec or update MACsec key will my on-premises network lose connectivity to Microsoft over ExpressRoute?
34
+
### Will my on-premises network lose connectivity to Microsoft over ExpressRoute when I enable/disable MACsec or update the MACsec key?
34
35
35
-
Yes. For the MACsec configuration, we support the preshared key mode only. It means you need to update the key on both your devices and on Microsoft's (via our API). This change isn't atomic, so you lose connectivity when there's a key mismatch between the two sides. We strongly recommend that you schedule a maintenance window for the configuration change. To minimize the downtime, we suggest you update the configuration on one link of ExpressRoute Direct at a time after you switch your network traffic to the other link.
36
+
Yes. We support the preshared key mode only for MACsec configuration, meaning you need to update the key on both your devices and Microsoft's (via our API). This change isn't atomic, so you lose connectivity when there's a key mismatch. We strongly recommend scheduling a maintenance window for the configuration change. To minimize downtime, update the configuration on one link of ExpressRoute Direct at a time after switching your network traffic to the other link.
36
37
37
-
### Does traffic continue to flow if there's a mismatch in MACsec key between my devices and Microsoft's?
38
+
### Does traffic continue to flow if there's a MACsec key mismatch between my devices and Microsoft's?
38
39
39
-
No. If MACsec is configured and a key mismatch occurs, you lose connectivity to Microsoft. In other words, traffic doesn't fall back to an unencrypted connection, exposing your data.
40
+
No. If MACsec is configured and a key mismatch occurs, you lose connectivity to Microsoft. Traffic doesn't fall back to an unencrypted connection, ensuring your data remains protected.
40
41
41
42
### Does enabling MACsec on ExpressRoute Direct degrade network performance?
42
43
43
-
MACsec encryption and decryption occur in hardware on the routers we use. There's no performance degradation on our side. However, you should check with the network vendor for the devices you use and see if MACsec has any performance implication.
44
+
MACsec encryption and decryption occur in hardware on the routers we use, so there's no performance degradation on our side. However, check with your network vendor to see if MACsec has any performance implications for your devices.
44
45
45
46
### Which cipher suites are supported for encryption?
46
47
@@ -56,19 +57,19 @@ Yes, you can set [Secure Channel Identifier (SCI)](https://en.wikipedia.org/wiki
56
57
57
58
## End-to-end encryption by IPsec FAQ
58
59
59
-
IPsec is an [IETF standard](https://tools.ietf.org/html/rfc6071). It encrypts data at the Internet Protocol (IP) level or Network Layer 3. You can use IPsec to encrypt an end-to-end connection between your on-premises network and your virtual network on Azure.
60
+
IPsec is an [IETF standard](https://tools.ietf.org/html/rfc6071) that encrypts data at the Internet Protocol (IP) level (Network Layer 3). You can use IPsec to encrypt an end-to-end connection between your on-premises network and your virtual network on Azure.
60
61
61
62
### Can I enable IPsec in addition to MACsec on my ExpressRoute Direct ports?
62
63
63
-
Yes. MACsec secures the physical connections between you and Microsoft. IPsec secures the end-to-end connection between you and your virtual networks on Azure. You can enable them independently.
64
+
Yes. MACsec secures the physical connections between you and Microsoft, while IPsec secures the end-to-end connection between you and your virtual networks on Azure. You can enable them independently.
64
65
65
66
### Can I use Azure VPN gateway to set up the IPsec tunnel over Azure Private Peering?
66
67
67
-
Yes. If you adopt Azure Virtual WAN, you can follow steps in [VPN over ExpressRoute for Virtual WAN](../virtual-wan/vpn-over-expressroute.md) to encrypt your end-to-end connection. If you have regular Azure virtual network, you can follow [site-to-site VPN connection over Private peering](../vpn-gateway/site-to-site-vpn-private-peering.md) to establish an IPsec tunnel between Azure VPN gateway and your on-premises VPN gateway.
68
+
Yes. If you use Azure Virtual WAN, follow the steps in [VPN over ExpressRoute for Virtual WAN](../virtual-wan/vpn-over-expressroute.md) to encrypt your end-to-end connection. If you have a regular Azure virtual network, follow [site-to-site VPN connection over Private peering](../vpn-gateway/site-to-site-vpn-private-peering.md) to establish an IPsec tunnel between Azure VPN gateway and your on-premises VPN gateway.
68
69
69
-
### What is the throughput I'll get after enabling IPsec on my ExpressRoute connection?
70
+
### What is the throughput after enabling IPsec on my ExpressRoute connection?
70
71
71
-
If Azure VPN gateway is used, review these [performance numbers](../vpn-gateway/vpn-gateway-about-vpngateways.md) to see if they match your expected throughput. If a third-party VPN gateway is used, check with the vendor for their performance numbers.
72
+
If you use Azure VPN gateway, review these [performance numbers](../vpn-gateway/vpn-gateway-about-vpngateways.md) to see if they match your expected throughput. If you use a third-party VPN gateway, check with the vendor for their performance numbers.
0 commit comments