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.
Alexander Batishchev's Blog 