Skip to content

Commit 74fcdd0

Browse files
committed
updates
1 parent b5b64d2 commit 74fcdd0

File tree

1 file changed

+11
-7
lines changed

1 file changed

+11
-7
lines changed

articles/internet-peering/faqs.md

Lines changed: 11 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ services: internet-peering
55
author: halkazwini
66
ms.service: internet-peering
77
ms.topic: conceptual
8-
ms.date: 02/24/2023
8+
ms.date: 03/29/2023
99
ms.author: halkazwini
1010
ms.custom: engagement-fy23, template-concept
1111
---
@@ -15,16 +15,20 @@ ms.custom: engagement-fy23, template-concept
1515

1616
## What is the difference between Internet peering and Peering Service?
1717

18-
Peering Service is a service that intends to provide enterprise grade public IP connectivity to Microsoft for its enterprise customers. Enterprise grade internet includes connectivity through ISPs that have high throughput connectivity to Microsoft and redundancy for a HA connectivity. Additionally, user traffic is optimized for latency to the nearest Microsoft Edge. Peering Service builds on peering connectivity with partner carrier. The peering connectivity with partner must be Direct peering as opposed to Exchange peering. Direct peering must have local and geo-redundancy.
18+
Peering Service provides enterprise-grade public IP connectivity to Microsoft for customers. Enterprise grade Internet includes connectivity through partner ISPs that have high throughput capacity to Microsoft and redundancy for reliable connectivity. Peering Service providers receive a customer’s registered traffic directly from Microsoft at locations that are selected by the customer.
1919

2020
## What is legacy peering?
2121

22-
Peering connections set up in the past are stored in our system as legacy peering which you may choose to convert to manage as an Azure resource. Any new peering connection set up using Azure PowerShell is managed as an Azure resource.
22+
Peering connections that were set up outside of the automated portal process and aren't shown as resources in your Azure subscription are considered legacy peerings. It's encouraged but not required to set up all peering connections in the Azure portal and to convert legacy peerings to Azure resources so that a peer can view and manage all of their peering connections to the Microsoft network. By utilizing the Azure portal, peers can also view performance metrics and submit support tickets. If a peer is interested in becoming a MAPS partner, then converting legacy peerings to Azure Resources is a requirement.
2323

24-
## When New-AzPeeringDirectConnectionObject is called, what IP addresses are given to Microsoft and Peer devices?
24+
## What is the minimum link speed for an interconnect?
2525

26-
When you use `New-AzPeeringDirectConnectionObject` cmdlet, you enter a `/31` prefix (`a.b.c.d/31`) or a `/30` prefix (`a.b.c.d/30`). The first IP address (`a.b.c.d+0`) is given to the peer device and second IP address (`a.b.c.d+1`) is given to Microsoft device.
26+
10 Gbps.
2727

28-
## What is MaxPrefixesAdvertisedIPv4 and MaxPrefixesAdvertisedIPv6 parameters in New-AzPeeringDirectConnectionObject cmdlet?
28+
## When will peering IP addresses be allocated and displayed in the Azure portal?
2929

30-
`MaxPrefixesAdvertisedIPv4` and `MaxPrefixesAdvertisedIPv6` parameters represent the maximum number of IPv4 and IPv6 prefixes a Peer wants Microsoft to accept. These parameters can be modified anytime.
30+
Our automated process allocates IP addresses and sends the information via email to the PNI requestor after the port is configured on our side. This may take up to a week after the request has been submitted as the port has been cabled before it can be configured.
31+
32+
## What Microsoft routes will we receive over these interconnects?
33+
34+
Microsoft announces all of Microsoft's public service prefixes over these interconnects. This ensures not only communications, but other cloud services are accessible from the same interconnect.

0 commit comments

Comments
 (0)