Skip to content

Commit 69728c6

Browse files
Merge pull request #228484 from halkazwini/ip-faq
Internet Peering: Freshness: Internet peering - FAQ
2 parents 5fb0ef5 + 914a972 commit 69728c6

File tree

2 files changed

+16
-16
lines changed

2 files changed

+16
-16
lines changed

articles/internet-peering/faqs.md

Lines changed: 14 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -1,30 +1,30 @@
11
---
2-
title: Internet peering - FAQs
3-
description: Internet peering - FAQs
2+
title: Internet peering - FAQ
3+
description: Internet peering frequently asked questions (FAQ)
44
services: internet-peering
55
author: halkazwini
66
ms.service: internet-peering
7-
ms.topic: reference
8-
ms.date: 11/27/2019
7+
ms.topic: conceptual
8+
ms.date: 02/24/2023
99
ms.author: halkazwini
10+
ms.custom: engagement-fy23, template-concept
1011
---
1112

12-
# Internet peering - FAQs
13+
# Internet peering frequently asked questions (FAQ)
1314

14-
You may review information below for general questions.
1515

16-
**What is the difference between Internet peering and Peering Service?**
16+
## 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 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.
1919

20-
**What is legacy peering?**
20+
## What is legacy peering?
2121

22-
Peering connection set up using Azure PowerShell is managed as an Azure resource. 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.
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.
2323

24-
**When New-AzPeeringDirectConnectionObject is called, what IP addresses are given to Microsoft and Peer devices?**
24+
## When New-AzPeeringDirectConnectionObject is called, what IP addresses are given to Microsoft and Peer devices?
2525

26-
When calling New-AzPeeringDirectConnectionObject cmdlet, a `/31` address (`a.b.c.d/31`) or a `/30` address (`a.b.c.d/30`) is entered. The first IP address (`a.b.c.d+0`) is given to Peer's device and second IP address (`a.b.c.d+1`) is given to Microsoft device.
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.
2727

28-
**What is MaxPrefixesAdvertisedIPv4 and MaxPrefixesAdvertisedIPv6 parameters in New-AzPeeringDirectConnectionObject cmdlet?**
28+
## What is MaxPrefixesAdvertisedIPv4 and MaxPrefixesAdvertisedIPv6 parameters in New-AzPeeringDirectConnectionObject cmdlet?
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+
`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.

articles/internet-peering/toc.yml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -84,7 +84,7 @@
8484
href: https://azure.microsoft.com/blog/topics/networking
8585
- name: Networking feedback
8686
href: https://feedback.azure.com/d365community/forum/8ae9bf04-8326-ec11-b6e6-000d3a4f0789
87-
- name: Internet peering FAQs
87+
- name: Internet peering FAQ
8888
href: faqs.md
89-
- name: Peering Service FAQs
89+
- name: Peering Service FAQ
9090
href: service-faqs.yml

0 commit comments

Comments
 (0)