Deployment script produces poor logs when failing on Function only deployment about ipam HOT 4 CLOSED

Good morning @craigthackerx, and thank you so much for opening this issue!

At first glance, this doesn't appear per-se an Azure IPAM Deployment Script issue, but something within Azure is not allowing the deployment to complete. Can you try checking the Deployment results within the Azure portal?

You can find the Deployment details under the subscription like this:

I would expect you to see a failure here (mine shows success). Click on the failed deployment for additional details like so:

Here you should be able to see which component(s) failed, and perhaps a more clear reason as to why. It could be something like resource availability, quota limit, Azure Policy, etc.

I'm also more than happy to hop on a 1:1 session with you to drill down on the exact root cause at any time. Please feel free to reach out to me at [email protected], and we can get something scheduled.

I know we'll get this resolved soon, looking forward to driving this to closure with you!

from ipam.

Good morning @craigthackerx, I just wanted to circle back with you on this issue to see if you've been able to look a bit deeper into where the deployment failed in the Azure portal, or if you'd like to schedule some time for us to dive into this together.

Let me know how things are going, we're always here to help!

from ipam.

Good morning @craigthackerx, I just wanted to circle back with you on this issue to see if you've been able to look a bit deeper into where the deployment failed in the Azure portal, or if you'd like to schedule some time for us to dive into this together.

Let me know how things are going, we're always here to help!

Apologies for the slow reply, I haven't had a chance to reply over the holidays.

Oddly, I struggled to replicate the issue on another tenant I had. The tenant I was testing it in had more controls in place, so I find likely that something was interfering with the script, where as the Dev/Test tenant I have has little in the way of control.

You may wish to close this issue and I'll get back to you on here if I can replicate it, I can test what I wanted to test on my personal tenant.

from ipam.

Sounds great @craigthackerx! I've seen similar issues before where something like Azure Policy was preventing some portion of the Azure IPAM infrastructure from deploying.

In the future, you can add the "-Debug" flag to the Deploy.ps1 and it will produce EXTREMELY verbose logs (in the /logs folder). Generally we can parse through those to locate the more precise problem happening during the Bicep template deployment. As always, we're more than happy to assist with this once the Debug logs are generated.

For now I'll close this out, but we're here to help at any point in time!

from ipam.