Troubleshooting Azure Connections

Capacity errors when provisioning a Hosted connection

You might see the following error when provisioning a connection: No Azure port matching parameters found. This indicates a capacity issue.

Try provisioning the connection again while selecting a different availability zone.

If that is not possible, contact and we will work to either free up capacity or add more capacity to the site.

Change or update the VLAN ID on the PacketFabric side

When you created the Hosted connection, you specified a Private Peering VLAN and a Microsoft Peering VLAN. These same VLAN IDs are required when configuring peering in the Azure portal.

At this time, there is not an option to update the VLAN ID through the portal or API. Open a support ticket by emailing

When you open a ticket, provide the following information:

  • Circuit ID
  • Current VLAN ID
  • Requested VLAN ID

You can find this information in two places:

  • Go the the Hosted Clouds page. The circuit ID and VLAN ID are listed in the Hosted connections table. The private peering VLAN is followed by the Microsoft peering VLAN. If you did not specify a VLAN for both, a - appears in its place:

    Hosted clouds page

  • Go to the Virtual Circuits page and locate the virtual circuit associated with your Hosted connection. It will have the same name as the Hosted connection, followed by the peering type. Double-click the connection to go to its Details page. (If you set up both peering types when creating the Hosted connection, there will be one virtual circuit for each peering.)

    Azure hosted details page

Port is up but the connection to Azure is down

Check that your VLAN IDs match between PacketFabric and the Azure portal.

See the section above for information on finding the VLAN ID in the PacketFabric portal.

To find the VLAN ID in the Azure portal, go to the ExpressRoute circuits page and select your circuit. On the overview page, select the peering you are using:

Azure circuit overview page

From here you can confirm and/or update the VLAN ID:

Azure circuit peering page

TIP: It is easier to update the VLAN ID from the Azure side. If you want to change the PacketFabric side, email (see above).

If the problem persists even after ensuring the VLAN IDs match, email