![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(240, 87%, 33%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EEC%3C/text%3E%3C/svg%3E)
Community Center | Not monitored
Tag not monitored by Microsoft.
Equinix and Microsoft support cannot safely request or receive a service key through this public forum. However, there are a few concrete checks and next steps that can be taken:
- Verify the ExpressRoute circuit state and service key
- In the Azure portal, open ExpressRoute circuits and select the relevant circuit.
- Confirm that the circuit is in a Provisioned or Enabled state on the Microsoft side and that the serviceKey value shown there is exactly what is being entered in the Equinix portal.
- If using automation/SDKs, the
serviceKey()method on theExpressRouteCircuitresource returns the same value that should be provided to Equinix.
- Confirm with the mutual customer
- Ensure the customer is providing the service key from the correct subscription and correct ExpressRoute circuit (not from a test or decommissioned circuit).
- Confirm that the circuit is configured for the correct peering location that matches the Equinix facility where the cross-connect is being ordered.
- Work through private support channels
- Since the service key is sensitive, share it only through secure, private channels:
- With Equinix: via their official ticketing system or portal (not in a public forum).
- With Microsoft: via an Azure support request from the customer’s subscription.
- The mutual customer (circuit owner) should open an Azure Support ticket under Networking → ExpressRoute, include the Equinix ticket number, and provide the service key in that private case so Microsoft can validate it end-to-end.
- Since the service key is sensitive, share it only through secure, private channels:
- Typical resolution path
- If Equinix still reports “invalid service key” after the above checks, Microsoft Support can verify:
- The service key format and status in Azure.
- That the key is associated with a circuit that is available for provisioning with the specified provider/location.
- Equinix Support and Microsoft Support then coordinate using the ticket references; no service key needs to be posted publicly.
- If Equinix still reports “invalid service key” after the above checks, Microsoft Support can verify:
References: