Networking
The Networking forum covers all aspects of Networking in Azure, including endpoints, load-balancing, network security, DNS, Traffic Manager, virtual networks, and external connectivity.
Virtual Network:
Traffic Manager:
Network Watcher:
If you have any feedback on any aspect of Azure relating to Networking, we’d love to hear it.
-
To know what IP Addresses are used by NAT on Public Peering
Currently we know that the Microsoft Edge Routers are doing NAT translation for the packets coming from Public Peering.
Sometimes we need to know what IP addresses are used for that, but there is no way to know that without contacting Microsoft Support.
We want to know which addresses are used on Portal or PowerShell.24 votesThank you for the feedback on this functionality. At this time, we are not implementing new functionality for the public peering feature of ExpressRoute.
We recommend customers utilize Microsoft peering, which provides the same capabilities as public peering and allows additional controls, bidirectionality, and where our development will continue moving forward. The NAT IP addresses with Microsoft peering are supplied by the customer or by the service provider.
https://docs.microsoft.com/en-us/azure/expressroute/how-to-move-peering
Please contact support if you require the NAT IP addresses of the current circuits that have public peering. The IPs do not change for the life cycle of the public peering.
-
stop letting non-Azure Microsoft networks use BGP routes that Azure learns through ExpressRoute. This easily leads to asymmetric routing.
stop letting non-Azure Microsoft networks use the BGP routes that Azure learns through ExpressRoute. This leads to asymmetry in many cases.
Also, the current behavior lets bandwidth hungry Microsoft services like Windows Update consume the bandwidth and metered data of ExpressRoute.
As of today, companies using ExpressRoute need to set up their network in an unnecessary complicated way to avoid this problem.
One way to do it is to only announce a small prefix, and use that prefix for NAT'ing all the traffic destined for Azure services over ExpressRoute.
Then one has to make sure that all traffic destined for…12 votesHi!
Can you please refer to our NAT guidance (docs.microsoft.com/en-us/azure/expressroute..)It clearly calls out the following:
The NAT IP pool advertised to Microsoft must not be advertised to the Internet. This will break connectivity to other Microsoft services.
-
Provide a non-redundant ExpressRoute connection offer
Microsoft should consider providing a cheap ExpressRoute connection with non-redundant connection to Microsoft Azure and Service Providers.
Customers can than choice to upgrade to redundant connection and get the 99.9% SLA for connection or as an alternative choice to add a Site-to-Site VPN connection as a failover connection
This offer is only attended to target customers with the need to access to Azure VNets.
7 votes -
Provide real-life price comparisons of ExpressRoute vs. AWS Direct Connect
During numerous conversations with customers, it has surfaced that ExpressRoute seems to be at least 10x the cost of AWS' Direct Connect. However, my understanding is that the real difference is much more negligible, but I can't find any true price comparisons anywhere. This has been a point of contention repeatedly, and it would be great to direct customers to a real-life cost comparison.
4 votesThank you for the question. We regret but unfortunately we cannot publish AWS prices.
-
manually add route to expressroute
It would be great if you could manually add routes through the Azure portal for ranges that our ExpressRoute ISP doesn't know dynamically. That way we don't need to contact them to add a new subnet.
4 votesThank you for your suggestion, unfortunately this is something we will not pursue.
-
ExpressRoute between Azure datacenters without any connection to on premises
There is now ExpressRoute Premium Add-on which allows to bind VNETs in several datacenters to same ExpressRoute. This basically allows to handle routing between various azure VNETs via BGP. There is no need to connect various Azure VNETs via IPSEC VPNs then. We want this ExpressRoute networking/routing for our Azure VNETs but without creating leased line to Azure from on premises because we moved whole system to cloud and don't need dedicated connection to Azure at all.
So basically we want ExpressRoute Premium Add-on without ExpressRoute and manage our networking via virtual router appliance inside Azure completely separated from on…
1 voteHi!
You can have the same experience using vnet to vnet connectivity across regions. you can choose to use null encryption to enhance throughput and manage security in the application layer.Thanks,
- Don't see your idea?