Following circular nested profile path identified

If you’re getting the following error:

Circular nested profile definitions are not allowed. Following circular nested profile path identified: example.trafficmanager.net -> example.trafficmanager.net.

Then very likely you got an ARM template like this:

{
  "type": "Microsoft.Network/trafficManagerProfiles/nestedEndpoints",
  "apiVersion": "[variables('tmApiVersion')]",
  "name": "[concat(variables('tmName'), '/', parameters('location'))]",
  "properties": {
    "endpointStatus": "Enabled",
    "targetResourceId": "[resourceId('Microsoft.Network/trafficManagerProfiles', variables('tmName'))]",
    "weight": 1,
    "minChildEndpoints": 1,
    "geoMapping": [
      "GEO-NA"
    ]
  }
}

What means you created a Geographic traffic-routing based Traffic Manager that references itself. Hence the error.

This entry was posted in Infrastructure and tagged , . Bookmark the permalink.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.