Improving network performance between Azure virtual machines in different subscriptions

Luc Dallaire 0 Reputation points
2024-08-20T18:19:29.0133333+00:00

Is there a way to improve network performance between two Azure virtual machines that are in different subscriptions but in the same tenant and Azure location? Proximity Groups cannot cross subscription boundaries, so I am looking for alternative solutions.

Azure Virtual Network
Azure Virtual Network
An Azure networking service that is used to provision private networks and optionally to connect to on-premises datacenters.
2,762 questions
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. ChaitanyaNaykodi-MSFT 27,476 Reputation points Microsoft Employee Moderator
    2024-08-22T03:31:28.07+00:00

    @Luc Dallaire

    Thank you for reaching out.

    I understand you wish to know about how to improve network performance between Azure Virtual machines. You cannot use Proximity Groups as the VM's as they are in different subscriptions.

    Apart from Proximity placement groups. You can use following options to help optimize the network latency

    • Use the latest version of Windows or Linux.
    • Enable Accelerated Networking for increased performance.
    • Create larger VMs for better performance.

    The recommended approach to help reduce latency is documented here.

    Use the following best practices to test and analyze network latency:

    1. As soon as you finish deploying, configuring, and optimizing network VMs, take baseline network latency measurements between deployed VMs to establish benchmarks.
    2. Test the effects on network latency of changing any of the following components:
      • Operating system (OS) or network stack software, including configuration changes.
      • VM deployment method, such as deploying to an availability zone or proximity placement group (PPG).
      • VM properties, such as Accelerated Networking or size changes.
      • Virtual network configuration, such as routing or filtering changes.
    3. Always compare new test results to the baseline or to the latest test results before controlled changes.
    4. Repeat tests whenever you observe or deploy changes.

    You can do a latency test using Latte or SockPerf to set the benchmark.

    You can also test the latency difference when

    • The VM's are communicating with each other via their Public IP's
    • The VM's are communicating with each other via their private IP's where the Virtual Network they reside in are connected via Vnet peering (You can peer virtual networks in different subscriptions and these roles are required to establish vnet peering).

    Please let me know if you have any additional questions. Thank you!


    Please "Accept the answer" if the information helped you. This will help us and others in the community as well.

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.