You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/peering-service/about.md
+11-16Lines changed: 11 additions & 16 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,5 @@
1
1
---
2
-
title: Azure Peering Service Preview overview
2
+
title: Azure Peering Service overview
3
3
description: Learn about Azure Peering Service overview
4
4
services: peering-service
5
5
author: derekolo
@@ -8,11 +8,11 @@ ms.devlang: na
8
8
ms.topic: article
9
9
ms.tgt_pltfrm: na
10
10
ms.workload: Infrastructure-services
11
-
ms.date: 11/04/2019
11
+
ms.date: 05/18/2020
12
12
ms.author: derekol
13
13
---
14
14
15
-
# Azure Peering Service Preview Overview
15
+
# Azure Peering Service Overview
16
16
17
17
Azure Peering Service is a networking service that enhances customer connectivity to Microsoft cloud services such as Office 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.
18
18
@@ -22,18 +22,13 @@ With Peering Service, customers can select a well-connected partner service prov
22
22
23
23
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.
24
24
25
-
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 for Peering Service telemetry, customers must register for it in the Azure portal.
25
+
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.
26
26
27
-
For instructions on how to register Peering Service, see [Register Peering Service Preview by using the Azure portal](azure-portal.md).
27
+
For instructions on how to register Peering Service, see [Register Peering Service by using the Azure portal](azure-portal.md).
28
28
29
29
> [!NOTE]
30
30
> This article is intended for network architects in charge of enterprise connectivity to the cloud and to the internet.
31
31
32
-
>
33
-
> [!IMPORTANT]
34
-
> Peering Service is currently in public preview.
35
-
> This preview version is provided without a service level agreement. We don't recommend it for production workloads. Certain features might not be supported or might have constrained capabilities.
36
-
> For more information, see [Supplemental terms of use for Microsoft Azure previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/).
37
32
38
33
## What is Peering Service?
39
34
@@ -50,9 +45,9 @@ Peering Service is not a private connectivity product like Azure ExpressRoute or
50
45
51
46
## Background
52
47
53
-
Office 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.
48
+
Office 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.
54
49
55
-
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.
50
+
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.
56
51
57
52

58
53
@@ -76,15 +71,15 @@ Peering Service uses two types of redundancy:
76
71
77
72
-**Local redundancy**
78
73
79
-
Microsoft and service providers interconnect across multiple Microsoft edge PoP locations to deliver Peering Service. In each location, interconnection must support failover across two routers.
74
+
Microsoft and service providers interconnect across multiple Microsoft Edge PoP locations to deliver Peering Service. In each location, interconnection must support failover across two routers.
80
75
81
76
Each peering location is provisioned with redundant and diverse peering links.
82
77
83
78
-**Geo-redundancy**
84
79
85
-
Microsoft has interconnected with service providers at multiple metro locations so that if one of the edge nodes has degraded performance, the traffic routes to and from Microsoft via alternate sites. Microsoft routes traffic in its global network by using SDN-based routing policies for optimal performance.
80
+
Microsoft has interconnected with service providers at multiple metro locations so that if one of the Edge nodes has degraded performance, the traffic routes to and from Microsoft via alternate sites. Microsoft routes traffic in its global network by using SDN-based routing policies for optimal performance.
86
81
87
-
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.
82
+
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.
@@ -112,7 +107,7 @@ The following routing technique is preferred:
112
107
113
108
This service monitors the routing performance between the customer's location and Microsoft.
114
109
115
-
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.
110
+
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.
116
111
117
112
Monitoring captures the events in case of any service degradation.
Copy file name to clipboardExpand all lines: articles/peering-service/azure-portal.md
+9-21Lines changed: 9 additions & 21 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,5 @@
1
1
---
2
-
title: Register Azure Peering Service Preview - Azure portal
2
+
title: Register Azure Peering Service - Azure portal
3
3
description: Learn how to register Azure Peering Service by using the Azure portal
4
4
services: peering-service
5
5
author: derekolo
@@ -8,22 +8,19 @@ ms.devlang: na
8
8
ms.topic: article
9
9
ms.tgt_pltfrm: na
10
10
ms.workload: Infrastructure-services
11
-
ms.date: 03/07/2020
11
+
ms.date: 05/18/2020
12
12
ms.author: derekol
13
13
---
14
14
15
-
# Register Peering Service Preview by using the Azure portal
15
+
# Register Peering Service by using the Azure portal
16
16
17
17
Azure Peering Service is a networking service that enhances customer connectivity to Microsoft cloud services such as Office 365, Dynamics 365, software as a service (SaaS) services, Azure, or any Microsoft services accessible via the public internet.
18
18
19
19
In this article, you'll learn how to register a Peering Service connection by using the Azure portal.
20
20
21
21
If you don't have an Azure subscription, create an [account](https://azure.microsoft.com/free/?WT.mc_id=A261C142F) now.
22
22
23
-
> [!IMPORTANT]
24
-
> Peering Service is currently in public preview.
25
-
> This preview version is provided without a service level agreement. We don't recommend it for production workloads. Certain features might not be supported or might have constrained capabilities.
26
-
> For more information, see [Supplemental terms of use for Microsoft Azure previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/).
23
+
>
27
24
28
25
## Prerequisites
29
26
@@ -65,17 +62,12 @@ From a browser, go to the Azure portal and sign in with your Azure account.
65
62
## Register a Peering Service connection
66
63
67
64
1. To register a Peering Service connection, select **Create a resource** > **Peering Service**.
1. Enter a **Name** to which the Peering Service instance should be registered.
81
73
@@ -90,14 +82,10 @@ From a browser, go to the Azure portal and sign in with your Azure account.
90
82
1. Select **Create new prefix** at the bottom of the **Prefixes** section, and text boxes appear. Now, enter the name of the prefix resource and the prefixes that are associated with the service provider.
91
83
92
84
1. Select **Prefix Key** and add the Prefix Key that has been given to you by your provider (ISP or IXP). This key allows MS to validate the prefix and provider who have allocated your IP prefix.
93
-
94
-
> [!div class="mx-imgBorder"]
95
-
> 
85
+
> 
96
86
97
87
1. Select the **Review + create** button at the lower left of the page. The **Review + create** page appears, and Azure validates your configuration.
98
-
99
-
> [!div class="mx-imgBorder"]
100
-
> 
88
+
101
89
102
90
1. When you see the **Validation passed** message as shown, select **Create**.
Copy file name to clipboardExpand all lines: articles/peering-service/cli.md
+2-7Lines changed: 2 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,11 +8,11 @@ ms.devlang: na
8
8
ms.topic: article
9
9
ms.tgt_pltfrm: na
10
10
ms.workload: Infrastructure-services
11
-
ms.date: 11/04/2019
11
+
ms.date: 05/2/2020
12
12
ms.author: derekol
13
13
---
14
14
15
-
# Register a Peering Service Preview connection by using the Azure CLI
15
+
# Register a Peering Service connection by using the Azure CLI
16
16
17
17
Azure Peering Service is a networking service that enhances customer connectivity to Microsoft cloud services such as Office 365, Dynamics 365, software as a service (SaaS) services, Azure, or any Microsoft services accessible via the public internet. In this article, you'll learn how to register a Peering Service connection by using the Azure CLI.
18
18
@@ -22,11 +22,6 @@ If you don't have an Azure subscription, create an [account](https://azure.micro
22
22
23
23
If you choose to install and use the CLI locally, this article requires the Azure CLI version 2.0.28 or later. To find the version, run `az --version`. If you need to install or upgrade, see [Install the Azure CLI](/cli/azure/install-azure-cli).
24
24
25
-
> [!IMPORTANT]
26
-
> Peering Service is currently in public preview.
27
-
> This preview version is provided without a service level agreement. We don't recommend it for production workloads. Certain features might not be supported or might have constrained capabilities.
28
-
> For more information, see [Supplemental terms of use for Microsoft Azure previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/).
Copy file name to clipboardExpand all lines: articles/peering-service/connection-telemetry.md
+5-12Lines changed: 5 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,32 +1,25 @@
1
1
---
2
-
title: Azure Peering Service Preview connection telemetry
2
+
title: Azure Peering Service connection telemetry
3
3
description: Learn about Microsoft Azure Peering Service connection telemetry
4
4
services: peering-service
5
5
author: derekolo
6
6
ms.service: peering-service
7
7
ms.devlang: na
8
8
ms.topic: article
9
9
ms.tgt_pltfrm: na
10
-
ms.workload: Infrastructure-services
11
-
ms.date: 11/04/2019
10
+
ms.date: 05/18/2020
12
11
ms.author: derekol
13
12
---
14
-
# Peering Service Preview connection telemetry
13
+
# Peering Service connection telemetry
15
14
16
-
Connection telemetry provides insights collected for the connectivity between the customer's location and the Microsoft network. Customers can obtain telemetry for Azure Peering Service connection by registering the connection in the Azure portal. This feature provides prefix security and insights into the network latency.
15
+
Connection telemetry provides insights collected for the connectivity between the customer's location and the Microsoft network. Customers can obtain telemetry for Azure Peering Service connection by registering the connection in the Azure portal. This feature provides prefix security and insights into the network performance.
17
16
18
-
> [!IMPORTANT]
19
-
> Peering Service is currently in public preview.
20
-
> This preview version is provided without a service level agreement. We don't recommend it for production workloads. Certain features might not be supported or might have constrained capabilities.
21
-
> For more information, see [Supplemental terms of use for Microsoft Azure previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/).
22
-
23
-
## Preview scope
24
17
25
18
Connection telemetry is composed of the following scopes:
26
19
27
20
### Latency measurement
28
21
29
-
Latency is measured from the client to the Microsoft edge PoP for the registered prefixes.
22
+
Latency is measured from the client to the Microsoft Edge PoP for the registered prefixes within Peering Service.
Copy file name to clipboardExpand all lines: articles/peering-service/connection.md
+5-10Lines changed: 5 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,5 @@
1
1
---
2
-
title: Azure Peering Service Preview connection
2
+
title: Azure Peering Service connection
3
3
description: Learn about Microsoft Azure Peering Service connection
4
4
services: peering-service
5
5
author: derekolo
@@ -8,11 +8,11 @@ ms.devlang: na
8
8
ms.topic: article
9
9
ms.tgt_pltfrm: na
10
10
ms.workload: Infrastructure-services
11
-
ms.date: 11/04/2019
11
+
ms.date: 05/18/2020
12
12
ms.author: derekol
13
13
---
14
14
15
-
# Peering Service Preview connection
15
+
# Peering Service connection
16
16
17
17
A connection typically refers to a logical information set, identifying a Peering Service. It is defined by specifying the following attributes:
18
18
@@ -28,19 +28,14 @@ Customer can establish a single connection or multiple connections as per the re
28
28
>For more information about connection telemetry, refer to the [Peering Service connection telemetry](connection-telemetry.md).
29
29
>
30
30
31
-
> [!IMPORTANT]
32
-
> "Peering Service" is currently in public preview.
33
-
> This preview version is provided without a service level agreement, and it's not recommended for production workloads. Certain features might not be supported or might have constrained capabilities.
34
-
> For more information, see [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/).
35
-
36
-
## How to register a connection?
31
+
>## How to register a connection?
37
32
38
33
**Scenario** - Let's say a branch office is spread across different geographic locations as shown in the figure below. Here, the customer is required to provide a logical name, Service Provider(SP) name, customer's physical location, and IP prefixes that are (owned by the customer or allocated by the Service Provider) associated with a single connection. This process must be repeated to register Peering Service for separate Geo-redundant connections.
0 commit comments