Skip to content

Commit 3aa5df7

Browse files
Merge pull request #308724 from cfields475/patch-51
Revise prefix limit details for Azure Peering Service
2 parents 462285d + c0930c6 commit 3aa5df7

1 file changed

Lines changed: 2 additions & 2 deletions

File tree

articles/internet-peering/walkthrough-communications-services-partner.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -253,7 +253,7 @@ Get answers to frequently asked questions.
253253

254254
**A.** Currently, there's no API support. You can configure your service only by using the Azure portal.
255255

256-
**Q.** Setting the Prefix Limit: Recommended Max Prefix Limits for Voice service peering.
256+
**Setting the Prefix Limit: Recommended Max Prefix Limits for Microsoft Azure Peering Service.**
257257

258-
**A.** Microsoft generally announces up to 300 voice-enabled service IP prefixes on the internet, and this number may increase over time. To maintain stability and prevent session drops, it is recommended to set your Max Prefix Count to 500. This provides a safe buffer above current announcements and allows for future growth.
258+
Microsoft currently announces up to 2000 IPv4 prefixes on the internet, and this number may increase over time. To maintain stability and prevent session drops, it is recommended to set your Max Prefix Count according to the peeringdb.com entry for ASN 8075. This provides a safe buffer above current announcements and allows for future growth.
259259

0 commit comments

Comments
 (0)