Azure Express Route

  • Author: Ronald Fung

  • Creation Date: 17 May 2023

  • Next Modified Date: 17 May 2024

A. Introduction

ExpressRoute is an Azure service that lets you create private connections between Microsoft datacenters and infrastructure that’s on your premises or in a colocation facility. ExpressRoute connections don’t go over the public Internet, and offer higher security, reliability, and speeds with lower latencies than typical connections over the Internet.

B. How is it used at Seagen

As a biopharma research company using Microsoft Azure, you can use Azure ExpressRoute to establish a dedicated and private network connection between your on-premises infrastructure and Azure. Here are some ways you can use Azure ExpressRoute:

  1. High-speed connectivity: Azure ExpressRoute can help you to establish a high-speed, low-latency network connection between your on-premises infrastructure and Azure, with bandwidths up to 100 Gbps.

  2. Private and dedicated connection: Azure ExpressRoute provides a private and dedicated connection between your on-premises infrastructure and Azure, which can help you to improve security, reliability, and performance.

  3. Hybrid cloud integration: Azure ExpressRoute can help you to integrate your on-premises infrastructure with Azure, creating a hybrid cloud environment that can help you to leverage the benefits of both cloud and on-premises infrastructure.

  4. Global connectivity: Azure ExpressRoute provides global connectivity, with connectivity options available in multiple regions around the world.

  5. Integration with other Azure services: Azure ExpressRoute can integrate with other Azure services such as Azure Virtual Machines, Azure Storage, and Azure SQL Database. This can help you to extend the functionality of your hybrid cloud environment and create more complex workflows.

  6. Security and compliance: Azure ExpressRoute provides security features such as encryption and access control. It also complies with regulatory requirements such as GDPR and HIPAA.

Overall, Azure ExpressRoute can help your biopharma research company to establish a dedicated and private network connection between your on-premises infrastructure and Azure, with high-speed connectivity, hybrid cloud integration, global connectivity, integration with other Azure services, security and compliance. With Azure ExpressRoute, you can improve the performance, reliability, and security of your hybrid cloud environment, and leverage the benefits of both cloud and on-premises infrastructure.

C. Features

ExpressRoute supports three routing domains for various types of services: private peering, Microsoft peering, and public peering (deprecated).

Private peering

Supported:

Microsoft peering

If your ExpressRoute circuit is enabled for Azure Microsoft peering, you can access the public IP address ranges used in Azure over the circuit. Azure Microsoft peering will provide access to services currently hosted on Azure (with geo-restrictions depending on your circuit’s SKU). To validate availability for a specific service, you can check the documentation for that service to see if there’s a reserved range published for that service. Then, look up the IP ranges of the target service and compare with the ranges listed in the Azure IP Ranges and Service Tags – Public Cloud XML file. Alternatively, you can open a support ticket for the service in question for clarification.

Supported:

  • Microsoft 365

  • Power BI - Available via an Azure Regional Community, see here for how to find out the region of your Power BI tenant.

  • Azure Active Directory

  • Azure DevOps (Azure Global Services community)

  • Azure Public IP addresses for IaaS (Virtual Machines, Virtual Network Gateways, Load Balancers, etc.)

  • Most of the other Azure services are also supported. Check directly with the service that you want to use to verify support.

Not supported:

  • CDN

  • Azure Front Door

  • Multi-factor Authentication Server (legacy)

  • Traffic Manager

  • Logic Apps

Public peering

Public peering is no longer available on new ExpressRoute circuits and is scheduled for retirement on March 31, 2024. Access to Azure services can be done through Microsoft peering. To avoid disruption to your services, you should migrate to Microsoft peering before the retirement date.

For more information, see Migrate from public peering to Microsoft peering. For a comparison between the different peering types, see Peering comparison.

D. Where Implemented

LeanIX

E. How it is tested

Testing Azure ExpressRoute involves ensuring that the service is functioning correctly and securely, and meeting the needs of all stakeholders involved in the project. Here are some steps to follow to test Azure ExpressRoute:

  1. Define the scope and requirements: Define the scope of the project and the requirements of all stakeholders involved in the project. This will help ensure that Azure ExpressRoute is designed to meet the needs of all stakeholders.

  2. Develop test cases: Develop test cases that cover all aspects of Azure ExpressRoute functionality, including connectivity, bandwidth, and security. The test cases should be designed to meet the needs of the organization, including scalability and resilience.

  3. Conduct unit testing: Test the individual components of Azure ExpressRoute to ensure that they are functioning correctly. This may involve using tools like PowerShell or Azure CLI for automated testing.

  4. Conduct integration testing: Test Azure ExpressRoute in an integrated environment to ensure that it works correctly with other systems and applications. This may involve testing Azure ExpressRoute with different operating systems, browsers, and devices.

  5. Conduct user acceptance testing: Test Azure ExpressRoute with end-users to ensure that it meets their needs and is easy to use. This may involve conducting surveys, interviews, or focus groups to gather feedback from users.

  6. Automate testing: Automate testing of Azure ExpressRoute to ensure that it is functioning correctly and meeting the needs of all stakeholders. This may involve using tools like Azure DevOps Pipelines to set up automated testing pipelines.

  7. Monitor performance: Monitor the performance of Azure ExpressRoute in production to ensure that it is meeting the needs of all stakeholders. This may involve setting up monitoring tools, such as Azure Monitor, to track usage and identify performance issues.

  8. Address issues: Address any issues that are identified during testing and make necessary changes to ensure that Azure ExpressRoute is functioning correctly and meeting the needs of all stakeholders.

By following these steps, you can ensure that Azure ExpressRoute is tested thoroughly and meets the needs of all stakeholders involved in the project. This can help improve the quality of Azure ExpressRoute and ensure that it functions correctly in a production environment.

F. 2023 Roadmap

????

G. 2024 Roadmap

Public peering is no longer available on new ExpressRoute circuits and is scheduled for retirement on March 31, 2024.

H. Known Issues

There are several known issues that can impact Azure ExpressRoute. Here are some of the most common issues to be aware of:

  1. Connectivity issues: Connectivity issues can arise when establishing and maintaining a connection to Azure ExpressRoute. It is important to ensure that the service is properly sized and configured to avoid these issues.

  2. Security issues: Security is a critical concern when it comes to Azure ExpressRoute. It is important to ensure that Azure ExpressRoute is secured and that access to the solution is restricted to authorized personnel.

  3. Compatibility issues: Azure ExpressRoute may not be compatible with all platforms, devices, or languages. It is important to ensure that Azure ExpressRoute is compatible with the organization’s existing infrastructure before implementation.

  4. Scalability issues: Scalability issues can arise when scaling up or down the service. It is important to ensure that the service can scale to meet the needs of the organization.

  5. Integration issues: Integration issues can arise when integrating Azure ExpressRoute with other systems and applications. It is important to ensure that Azure ExpressRoute is designed to work seamlessly with other systems and applications to avoid integration issues.

  6. Testing issues: Testing issues can arise when testing Azure ExpressRoute. It is important to ensure that testing is carried out thoroughly and that all aspects of Azure ExpressRoute functionality are tested.

  7. Performance issues: Performance issues can impact the speed and reliability of Azure ExpressRoute. It is important to monitor performance and address any issues that arise.

  8. Licensing issues: Licensing issues can arise when using Azure ExpressRoute. It is important to ensure that the appropriate licensing is in place to avoid any legal issues.

Overall, Azure ExpressRoute requires careful planning and management to ensure that it is functioning correctly and meeting the needs of all stakeholders involved in the project. By being aware of these known issues and taking steps to address them, you can improve the quality of Azure ExpressRoute and ensure the success of your project.

[x] Reviewed by Enterprise Architecture

[x] Reviewed by Application Development

[x] Reviewed by Data Architecture