Skip to content

Commit 9635f25

Browse files
authored
Merge pull request #115282 from MicrosoftDocs/release-build-peering-service
Build 2020 Release Peering Service
2 parents 803b660 + 859d8b9 commit 9635f25

15 files changed

+159
-140
lines changed

articles/peering-service/TOC.yml

Lines changed: 8 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -4,6 +4,14 @@
44
items:
55
- name: About Peering Service
66
href: about.md
7+
- name: Tutorials
8+
items:
9+
- name: Register a Peering Service connection
10+
href: azure-portal.md
11+
- name: Create a Peering Service Connection
12+
href: create-connection.md
13+
- name: Measure Peering Service connection telemetry
14+
href: measure-connection-telemetry.md
715
- name: Concepts
816
items:
917
- name: Locations and partners
@@ -18,14 +26,10 @@
1826
items:
1927
- name: Register Peering Service
2028
items:
21-
- name: Azure portal
22-
href: azure-portal.md
2329
- name: Azure PowerShell
2430
href: powershell.md
2531
- name: Azure CLI
2632
href: cli.md
27-
- name: Measure connection telemetry
28-
href: measure-connection-telemetry.md
2933
- name: References
3034
items:
3135
- name: Azure PowerShell

articles/peering-service/about.md

Lines changed: 11 additions & 16 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
title: Azure Peering Service Preview overview
2+
title: Azure Peering Service overview
33
description: Learn about Azure Peering Service overview
44
services: peering-service
55
author: derekolo
@@ -8,11 +8,11 @@ ms.devlang: na
88
ms.topic: article
99
ms.tgt_pltfrm: na
1010
ms.workload: Infrastructure-services
11-
ms.date: 11/04/2019
11+
ms.date: 05/18/2020
1212
ms.author: derekol
1313
---
1414

15-
# Azure Peering Service Preview Overview
15+
# Azure Peering Service Overview
1616

1717
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.
1818

@@ -22,18 +22,13 @@ With Peering Service, customers can select a well-connected partner service prov
2222

2323
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.
2424

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.
2626

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).
2828

2929
> [!NOTE]
3030
> This article is intended for network architects in charge of enterprise connectivity to the cloud and to the internet.
3131
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/).
3732

3833
## What is Peering Service?
3934

@@ -50,9 +45,9 @@ Peering Service is not a private connectivity product like Azure ExpressRoute or
5045
5146
## Background
5247

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.
5449

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.
5651

5752
![Microsoft network and public connectivity](./media/peering-service-about/peering-service-background-final.png)
5853

@@ -76,15 +71,15 @@ Peering Service uses two types of redundancy:
7671

7772
- **Local redundancy**
7873

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.
8075

8176
Each peering location is provisioned with redundant and diverse peering links.
8277

8378
- **Geo-redundancy**
8479

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.
8681

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​.
8883

8984
![Geo-redundancy](./media/peering-service-about/peering-service-geo-shortest.png)
9085

@@ -112,7 +107,7 @@ The following routing technique is preferred:
112107

113108
This service monitors the routing performance between the customer's location and Microsoft.
114109

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.
116111

117112
Monitoring captures the events in case of any service degradation.
118113

articles/peering-service/azure-portal.md

Lines changed: 9 additions & 21 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
title: Register Azure Peering Service Preview - Azure portal
2+
title: Register Azure Peering Service - Azure portal
33
description: Learn how to register Azure Peering Service by using the Azure portal
44
services: peering-service
55
author: derekolo
@@ -8,22 +8,19 @@ ms.devlang: na
88
ms.topic: article
99
ms.tgt_pltfrm: na
1010
ms.workload: Infrastructure-services
11-
ms.date: 03/07/2020
11+
ms.date: 05/18/2020
1212
ms.author: derekol
1313
---
1414

15-
# Register Peering Service Preview by using the Azure portal
15+
# Register Peering Service by using the Azure portal
1616

1717
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.
1818

1919
In this article, you'll learn how to register a Peering Service connection by using the Azure portal.
2020

2121
If you don't have an Azure subscription, create an [account](https://azure.microsoft.com/free/?WT.mc_id=A261C142F) now.
2222

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+
>
2724
2825
## Prerequisites
2926

@@ -65,17 +62,12 @@ From a browser, go to the Azure portal and sign in with your Azure account.
6562
## Register a Peering Service connection
6663

6764
1. To register a Peering Service connection, select **Create a resource** > **Peering Service**.
65+
![Register Peering Service](./media/peering-service-portal/peering-servicecreate.png)
66+
1. Enter the following details on the **Basics** tab on the **Create a peering service connection** page.
6867

69-
> [!div class="mx-imgBorder"]
70-
> ![Register Peering Service](./media/peering-service-portal/peering-servicecreate.png)
71-
72-
1. Enter the following details on the **Basics** tab on the **Create a peering service connection** page.
7368

7469
1. Select the subscription and the resource group associated with the subscription.
75-
76-
> [!div class="mx-imgBorder"]
77-
> ![Register Peering basic tab](./media/peering-service-portal/peering-servicebasics.png)
78-
70+
![Register Peering basic tab](./media/peering-service-portal/peering-servicebasics.png)
7971

8072
1. Enter a **Name** to which the Peering Service instance should be registered.
8173

@@ -90,14 +82,10 @@ From a browser, go to the Azure portal and sign in with your Azure account.
9082
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.
9183

9284
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-
> ![Register Peering Service configuration tab](./media/peering-service-portal/peering-serviceconfiguration.png)
85+
> ![Register Peering Service configuration tab](./media/peering-service-portal/peering-serviceconfiguration.png)
9686
9787
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-
> ![Register Peering Service validation](./media/peering-service-portal/peering-service-validate.png)
88+
10189

10290
1. When you see the **Validation passed** message as shown, select **Create**.
10391

articles/peering-service/cli.md

Lines changed: 2 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -8,11 +8,11 @@ ms.devlang: na
88
ms.topic: article
99
ms.tgt_pltfrm: na
1010
ms.workload: Infrastructure-services
11-
ms.date: 11/04/2019
11+
ms.date: 05/2/2020
1212
ms.author: derekol
1313
---
1414

15-
# Register a Peering Service Preview connection by using the Azure CLI
15+
# Register a Peering Service connection by using the Azure CLI
1616

1717
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.
1818

@@ -22,11 +22,6 @@ If you don't have an Azure subscription, create an [account](https://azure.micro
2222

2323
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).
2424

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/).
29-
3025
## Prerequisites
3126

3227
You must have the following:

articles/peering-service/connection-telemetry.md

Lines changed: 5 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -1,32 +1,25 @@
11
---
2-
title: Azure Peering Service Preview connection telemetry
2+
title: Azure Peering Service connection telemetry
33
description: Learn about Microsoft Azure Peering Service connection telemetry
44
services: peering-service
55
author: derekolo
66
ms.service: peering-service
77
ms.devlang: na
88
ms.topic: article
99
ms.tgt_pltfrm: na
10-
ms.workload: Infrastructure-services
11-
ms.date: 11/04/2019
10+
ms.date: 05/18/2020
1211
ms.author: derekol
1312
---
14-
# Peering Service Preview connection telemetry
13+
# Peering Service connection telemetry
1514

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.
1716

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
2417

2518
Connection telemetry is composed of the following scopes:
2619

2720
### Latency measurement
2821

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.
3023

3124
### Route prefix monitoring and protection
3225

articles/peering-service/connection.md

Lines changed: 5 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
title: Azure Peering Service Preview connection
2+
title: Azure Peering Service connection
33
description: Learn about Microsoft Azure Peering Service connection
44
services: peering-service
55
author: derekolo
@@ -8,11 +8,11 @@ ms.devlang: na
88
ms.topic: article
99
ms.tgt_pltfrm: na
1010
ms.workload: Infrastructure-services
11-
ms.date: 11/04/2019
11+
ms.date: 05/18/2020
1212
ms.author: derekol
1313
---
1414

15-
# Peering Service Preview connection
15+
# Peering Service connection
1616

1717
A connection typically refers to a logical information set, identifying a Peering Service. It is defined by specifying the following attributes:
1818

@@ -28,19 +28,14 @@ Customer can establish a single connection or multiple connections as per the re
2828
>For more information about connection telemetry, refer to the [Peering Service connection telemetry](connection-telemetry.md).
2929
>
3030
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?
3732
3833
**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.
3934

4035
![Geo Redundant connections](./media/peering-service-connection/peering-service-connections.png)
4136

4237
> [!Note]
43-
> For a preview, State level-filtration is considered for the customer's physical location when the connection is geo-located in the United States.
38+
> State level-filtration is considered for the customer's physical location when the connection is geo-located in the United States.
4439
>
4540
4641
## Next steps

0 commit comments

Comments
 (0)