Skip to content

Commit 11d3d14

Browse files
committed
tweak
1 parent 5f7ff9c commit 11d3d14

File tree

1 file changed

+1
-7
lines changed

1 file changed

+1
-7
lines changed

articles/internet-peering/service-faqs.yml

Lines changed: 1 addition & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@ title: Peering Service frequently asked questions (FAQ)
1414
summary: |
1515
1616
sections:
17-
- name:
17+
- name: Ignored
1818
questions:
1919
- question: |
2020
Can a carrier use existing direct peering connections with Microsoft to support Peering Service?
@@ -36,9 +36,3 @@ sections:
3636
answer: |
3737
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're 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).
3838
39-
- name: Next steps
40-
questions:
41-
- question:
42-
answer: |
43-
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).
44-

0 commit comments

Comments
 (0)