Azure Peering Service

  • Author: Ronald Fung

  • Creation Date: 26 May 2023

  • Next Modified Date: 26 May 2024


A. Introduction

Azure Peering Service is a networking service that enhances the connectivity to Microsoft cloud services such as Microsoft 365, Dynamics 365, software as a service (SaaS) services, Azure, or any Microsoft services accessible via the public internet. Microsoft has partnered with internet service providers (ISPs), internet exchange partners (IXPs), and software-defined cloud interconnect (SDCI) providers worldwide to provide reliable and high-performing public connectivity with optimal routing from the customer to the Microsoft network.

With Peering Service, customers can select a well-connected partner service provider in a given region. Public connectivity is optimized for high reliability and minimal latency from cloud services to the end-user location.

Diagram showing distributed connectivity to Microsoft cloud.

Peering Service

Customers can also opt for Peering Service telemetry such as user latency measures to the Microsoft network, BGP route monitoring, and alerts against leaks and hijacks by registering the Peering Service connection in the Azure portal.

To use Peering Service, customers aren’t required to register with Microsoft. The only requirement is to contact a Peering Service partner to get the service. To opt in for Peering Service telemetry, customers must register for it in the Azure portal.

For instructions on how to register a Peering Service, see Create, change, or delete a Peering Service connection using the Azure portal.


B. How is it used at Seagen

As a biopharma research company using Microsoft Azure, Seagen could use Azure Peering service to optimize its network connectivity and improve the performance of its cloud-based applications and workloads. Here are some ways Seagen could use Azure Peering service:

  1. Improved network performance: Azure Peering service provides a dedicated, private connection between Seagen’s network and Microsoft Azure. This can improve network performance by reducing latency and improving network reliability.

  2. Reduced costs: Azure Peering service can help Seagen reduce costs associated with network traffic by providing a direct, private connection to Microsoft Azure. This can reduce the need for expensive public internet connections or dedicated network circuits.

  3. Improved security: Azure Peering service provides a more secure connection to Microsoft Azure by using dedicated, private connections. This can help protect Seagen’s sensitive data and applications from potential security threats.

  4. Better application performance: Azure Peering service can improve the performance of Seagen’s cloud-based applications and workloads by reducing latency and improving network reliability. This can help Seagen to deliver a better user experience and improve overall productivity.

  5. Access to Microsoft services: Azure Peering service can provide Seagen with direct access to Microsoft services, such as Azure ExpressRoute, which can further enhance network performance and reliability.

Overall, Azure Peering service provides a powerful tool for optimizing network connectivity and improving the performance of cloud-based applications and workloads on Microsoft Azure. Its ability to improve network performance, reduce costs, improve security, and provide access to Microsoft services makes it a valuable tool for organizations, such as Seagen, that require high-performance network connectivity for their enterprise applications and workloads.


C. Features

Azure Peering service is a networking service that provides a dedicated, private connection between an organization’s network and Microsoft Azure. Here are some of the key features of Azure Peering service:

  1. Private connectivity: Azure Peering service provides a dedicated, private connection between an organization’s network and Microsoft Azure. This can improve network performance by reducing latency and improving network reliability.

  2. Reduced costs: Azure Peering service can help organizations reduce costs associated with network traffic by providing a direct, private connection to Microsoft Azure. This can reduce the need for expensive public internet connections or dedicated network circuits.

  3. Improved security: Azure Peering service provides a more secure connection to Microsoft Azure by using dedicated, private connections. This can help protect an organization’s sensitive data and applications from potential security threats.

  4. Better application performance: Azure Peering service can improve the performance of cloud-based applications and workloads by reducing latency and improving network reliability. This can help organizations to deliver a better user experience and improve overall productivity.

  5. Integration with Azure services: Azure Peering service is integrated with other Azure services, such as Azure ExpressRoute, which can further enhance network performance and reliability.

  6. Global coverage: Azure Peering service is available globally, which enables organizations to connect to Microsoft Azure from anywhere in the world.

  7. Easy to set up and manage: Azure Peering service is easy to set up and manage, with intuitive management tools and APIs that simplify network configuration and deployment.

Overall, Azure Peering service provides a powerful tool for optimizing network connectivity and improving the performance of cloud-based applications and workloads on Microsoft Azure. Its ability to improve network performance, reduce costs, improve security, and provide access to Microsoft services makes it a valuable tool for organizations that require high-performance network connectivity for their enterprise applications and workloads.


D. Where Implemented

LeanIX


E. How it is tested

Testing Azure Peering service involves several steps that include:

  1. Setting up a testing environment: The first step is to set up a testing environment that is separate from the production environment. This ensures that any issues or bugs discovered during testing do not affect the live system.

  2. Creating test cases: The next step is to create test cases that cover all the functionalities of Azure Peering service. Test cases should include positive and negative scenarios, edge cases, and stress tests.

  3. Running tests: Once the test cases are created, the next step is to run the tests. This involves executing the test cases and recording the results.

  4. Debugging and fixing issues: If any issues or bugs are discovered during testing, they must be debugged and fixed before proceeding with further testing.

  5. Repeat testing: After fixing the issues, the tests must be run again to ensure that the fixes have been successful and there are no further issues.

  6. Integration testing: Once Azure Peering service has been tested, it must be integrated with other systems and applications to ensure that it works seamlessly with other components.

  7. User acceptance testing: Finally, Azure Peering service must undergo user acceptance testing to ensure that it meets the requirements of the end-users.

Overall, testing Azure Peering service involves a comprehensive testing approach that covers all the functionalities of the solution and ensures that it meets the requirements of the end-users. Testing should include both functional and non-functional testing, such as performance testing, security testing, and scalability testing. It is also important to test the integration of Azure Peering service with other systems and applications to ensure that it works seamlessly with other components.


F. 2023 Roadmap

????


G. 2024 Roadmap

????


H. Known Issues

Like all software products, Azure Peering service may have some known issues. Here are some of the known issues for Azure Peering service:

  1. Latency issues: There may be latency issues when using Azure Peering service, which can impact the performance of applications and workloads.

  2. Network connectivity issues: Organizations may experience network connectivity issues when using Azure Peering service, which can result in disrupted or slow network connections.

  3. Cost management issues: Organizations must carefully manage the costs associated with Azure Peering service, as costs can quickly add up when using dedicated, private connections to Microsoft Azure.

  4. Integration issues: Azure Peering service may have integration issues when integrating with other systems and applications, which can impact the ability of organizations to use Azure Peering service for their enterprise applications and workloads.

  5. Limited geographic availability: Azure Peering service may have limited geographic availability, which can impact organizations that require high-performance network connectivity in regions that are not covered by Azure Peering service.

Overall, while Azure Peering service is a powerful solution for optimizing network connectivity and improving the performance of cloud-based applications and workloads on Microsoft Azure, users must be aware of these known issues and take steps to mitigate their impact. This may include addressing latency and network connectivity issues, carefully managing costs, and ensuring compatibility and integration with other systems and applications. It is also important to carefully plan and test the use of Azure Peering service to minimize the risk of issues during production use.


[x] Reviewed by Enterprise Architecture

[x] Reviewed by Application Development

[x] Reviewed by Data Architecture