Professional Documents
Culture Documents
In this article, you'll learn how to register a Peering Service connection by using the
Azure portal.
Important
Peering Service is currently in public preview. This preview version is provided without a
service level agreement. We don't recommend it for production workloads. Certain
features might not be supported or might have constrained capabilities. For more
information, see Supplemental terms of use for Microsoft Azure previews.
Prerequisites
You must have the following:
Azure account
You must have a valid and active Microsoft Azure account. This account is required to
set up the Peering Service connection. Peering Service is a resource within Azure
subscriptions. This cannot be a trial account.
Connectivity provider
You can work with an internet service provider (ISP) or internet exchange partner (IXP)
to obtain Peering Service to connect your network with the Microsoft network.
Make sure the connectivity providers are partnered with Microsoft for Peering Service.
Register your subscription with the resource provider and feature flag
Before you proceed to the steps of registering the Peering Service, you need to register
your subscription with the resource provider and feature flag either via Azure
PowerShell or the Azure CLI.
Azure PowerShell
Azure PowerShell Copy
Try It
Register-AzProviderFeature -FeatureName AllowPeeringService -ProviderNamespace
Microsoft.Peering
Azure CLI
Azure CLI Copy
Try It
az feature register --namespace Microsoft.Peering --name AllowPeeringService
5. Select the Review + create button at the lower left of the page. The Review +
create page appears, and Azure validates your configuration.
6. When you see the Validation passed message as shown, select Create.
7. After you register a Peering Service connection, additional validation is
performed on the included prefixes. You can review the validation status under the
Prefixes section of the resource name. If the validation fails, one of the following
error messages is displayed:
o Invalid Peering Service prefix, the prefix should be valid format, only Ipv4
prefix is supported.
o Prefix was not received from Peering Service provider.
o Prefix announcement does not have a valid BGP community, please
contact Peering Service provider.
o Backup route not found, please contact Peering Service provider.
o Prefix received with longer AS path, please contact Peering Service
provider.
o Prefix received with private AS in the path, please contact Peering Service
provider.
Select the ellipsis (...) next to the listed prefix, and select the Delete option.
On the All Resources page, select the check box on the Peering Service and select the
Delete option at the top of the page.
Next steps
To learn about Peering Service connection, see Peering Service connection.
To learn about Peering Service connection telemetry, see Peering Service
connection telemetry.
To measure telemetry, see Measure connection telemetry.
To register the connection by using Azure PowerShell, see Register a Peering
Service connection - Azure PowerShell.
To register the connection by using the Azure CLI, see Register a Peering Service
connection - Azure CLI.