Skip to content

Commit 0d7824c

Browse files
committed
link to peering service docs
1 parent b2df99a commit 0d7824c

File tree

1 file changed

+8
-1
lines changed

1 file changed

+8
-1
lines changed

articles/internet-peering/service-faqs.yml

Lines changed: 8 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ metadata:
77
author: halkazwini
88
ms.service: internet-peering
99
ms.topic: faq
10-
ms.date: 03/29/2023
10+
ms.date: 04/20/2023
1111
ms.author: halkazwini
1212
ms.custom: engagement-fy23
1313
title: Peering Service frequently asked questions (FAQ)
@@ -36,4 +36,11 @@ sections:
3636
If a service provider already peers with Microsoft, what kind of changes are required to support Peering Service?
3737
answer: |
3838
Peering Service partners must have an Azure subscription and manage the Peering Service connections using the Azure Portal as this is where customer prefixes are registered, performance metrics are viewed, and support tickets are logged, among other features. If a provider has existing peering with Microsoft but no Azure subscription, the resources must be added to your subscription before you will be able to convert these to the Peering Service configuration. During the configuration change, Microsoft changes the policy group during a hard restart of the BGP session. No configuration changes are required on the partner’s side, unless the telco partner is supporting Peering Service for voice then BFD configuration is required. For more information, see [Azure Internet peering for Communications Services walkthrough](walkthrough-communications-services-partner.md)
39+
40+
- name: Ignored
41+
questions:
42+
- question: |
43+
Next steps
44+
answer: |
45+
For more Peering Service frequently asked questions, see [Peering Service frequently asked questions (FAQ)](../peering-service/faq.yml). <br> For more information about Peering Service, see [Azure Peering Service overview](../peering-service/about.md).
3946

0 commit comments

Comments
 (0)