Skip to content

Commit cf6f4a5

Browse files
committed
freshness
1 parent a6c561e commit cf6f4a5

File tree

1 file changed

+14
-13
lines changed

1 file changed

+14
-13
lines changed

articles/peering-service/about.md

Lines changed: 14 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -6,23 +6,24 @@ author: halkazwini
66
ms.service: peering-service
77
ms.topic: overview
88
ms.workload: Infrastructure-services
9-
ms.date: 06/30/2022
9+
ms.date: 01/15/2023
1010
ms.author: halkazwini
11+
ms.custom: template-overview, engagement-fy23
1112
---
1213

1314
# Azure Peering Service overview
1415

15-
Azure Peering Service is a networking service that enhances customer 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.
16+
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.
1617

1718
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.
1819

19-
![Distributed connectivity to Microsoft cloud](./media/peering-service-about/peering-service-what.png)
20+
:::image type="content" source="./media/peering-service-about/peering-service-what.png" alt-text="Diagram showing distributed connectivity to Microsoft cloud.":::
2021

2122
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.
2223

2324
To use Peering Service, customers aren't required to register with Microsoft. The only requirement is to contact a [Peering Service partner](location-partners.md) to get the service. To opt in for Peering Service telemetry, customers must register for it in the Azure portal.
2425

25-
For instructions on how to register Peering Service, see [Register Peering Service by using the Azure portal](azure-portal.md).
26+
For instructions on how to register a Peering Service, see [Create, change, or delete a Peering Service connection using the Azure portal](azure-portal.md).
2627

2728
> [!NOTE]
2829
> This article is intended for network architects in charge of enterprise connectivity to the cloud and to the internet.
@@ -34,18 +35,18 @@ Peering Service is:
3435
- An IP service that uses the public internet.
3536
- A collaboration platform with service providers and a value-added service that's intended to offer optimal and reliable routing via service provider partners to the Microsoft cloud over the public network.
3637

37-
Peering Service is not a private connectivity product like Azure ExpressRoute or a VPN product.
38-
3938
> [!NOTE]
40-
> For more information about ExpressRoute, see [ExpressRoute documentation](../expressroute/expressroute-introduction.md).
39+
> Peering Service isn't a private connectivity product like Azure ExpressRoute or Azure VPN. For more information, see:
40+
> - [What is Azure ExpressRoute?](../expressroute/expressroute-introduction.md)
41+
> - [What is Azure VPN Gateway?](../vpn-gateway/vpn-gateway-about-vpngateways.md)
4142
4243
## Background
4344

4445
Microsoft 365, Dynamics 365, and any other Microsoft SaaS services are hosted in multiple Microsoft datacenters and can be accessed from any geographic location. The Microsoft global network has Microsoft Edge point-of-presence (PoP) locations around the world where it can connect to an end user via their service providers.
4546

4647
Microsoft and partner service providers ensure that the traffic for the prefixes registered with a Peering Service connection enters and exits the nearest Microsoft Edge PoP locations on the Microsoft global network. Microsoft ensures that the networking traffic egressing from the prefixes registered with Peering Service connections takes the nearest Microsoft Edge PoP locations on the Microsoft global network.
4748

48-
![Microsoft network and public connectivity](./media/peering-service-about/peering-service-background-final.png)
49+
:::image type="content" source="./media/peering-service-about/peering-service-background-final.png" alt-text="Diagram showing Microsoft network and public connectivity.":::
4950

5051
> [!NOTE]
5152
> For more information about the Microsoft global network, see [Microsoft global network](../networking/microsoft-global-network.md).
@@ -77,7 +78,7 @@ Peering Service uses two types of redundancy:
7778

7879
This type of redundancy uses the shortest routing path by always choosing the nearest Microsoft Edge PoP to the end user and ensures that the customer is one network hop (AS hops) away from Microsoft​.
7980

80-
![Geo-redundancy](./media/peering-service-about/peering-service-geo-shortest.png)
81+
:::image type="content" source="./media/peering-service-about/peering-service-geo-shortest.png" alt-text="Diagram showing geo-redundancy.":::
8182

8283
### Optimal routing
8384

@@ -89,7 +90,7 @@ The following routing technique is preferred:
8990

9091
Routing that doesn't use the cold-potato technique is referred to as hot-potato routing. With hot-potato routing, traffic that originates from the Microsoft cloud then goes over the internet.
9192

92-
![Cold-potato routing](./media/peering-service-about/peering-service-cold-potato.png)
93+
:::image type="content" source="./media/peering-service-about/peering-service-cold-potato.png" alt-text="Diagram showing cold-potato routing.":::
9394

9495
### Monitoring platform
9596

@@ -105,9 +106,9 @@ The following routing technique is preferred:
105106

106107
Routing performance is measured by validating the round-trip time taken from the client to reach the Microsoft Edge PoP. Customers can view the latency reports for different geographic locations.
107108

108-
Monitoring captures the events in case of any service degradation.
109+
Monitoring captures the events if there's any service degradation.
109110

110-
![Monitoring platform for Peering Service](media/peering-service-about/peering-service-latency-report.png)
111+
:::image type="content" source="./media/peering-service-about/peering-service-latency-report.png" alt-text="Diagram showing monitoring platform for Peering Service.":::
111112

112113
### Traffic protection
113114

@@ -123,5 +124,5 @@ BGP route anomalies are reported in the Azure portal, if any.
123124
- To learn about Peering Service connection telemetry, see [Peering Service connection telemetry](connection-telemetry.md).
124125
- To find a service provider partner, see [Peering Service partners and locations](location-partners.md).
125126
- To onboard a Peering Service connection, see [Onboarding Peering Service model](onboarding-model.md).
126-
- To register a connection by using the Azure portal, see [Register a Peering Service connection by using the Azure portal](azure-portal.md).
127+
- To register Peering Service, see [Create, change, or delete a Peering Service connection using the Azure portal](azure-portal.md).
127128
- To measure telemetry, see [Measure connection telemetry](measure-connection-telemetry.md).

0 commit comments

Comments
 (0)