Azure / Enterprise-Scale

The Azure Landing Zones (Enterprise-Scale) architecture provides prescriptive guidance coupled with Azure best practices, and it follows design principles across the critical design areas for organizations to define their Azure architecture
https://aka.ms/alz
MIT License
1.73k stars 979 forks source link

Bug Report - InternalServerError using ALZ Portal Accelerator #1775

Closed SeanKelly35 closed 2 months ago

SeanKelly35 commented 2 months ago

Note from ALZ Core Team:

[!IMPORTANT] Known issue in ARM, being resolved as we speak: see https://github.com/Azure/Enterprise-Scale/issues/1775#issuecomment-2374537416


Landing zone accelerator from the Microsoft Azure Training for AZ-305 is having issues completing the template correctly. I am getting an internal server error message. I followed the instructions precisely on this page: https://learn.microsoft.com/en-us/training/modules/cloud-adoption-framework-ready/6-deploy-blueprint

Yet I still get the error. image

Explain with Copilot says to select a resource from the select a resource pane, I find a hidden resource and then it errors out saying there was still an internal server error.

image

Hoping to get some help so that I can continue my studies. Thanks.

SeanKelly35 commented 2 months ago

Here are the settings of my attempted landing zone accelerator deployment image image image image

jdrepo commented 2 months ago

Same problem here, tried it in different tenants and with different settings and I always get after review + create validate the above mentioned "internal server error"

{"code":"InternalServerError","message":"Encountered internal server error. Diagnostic information: timestamp '20240925T062626Z', subscription id '', tracking id '8a909214-2339-43d2-8622-c7227ab8ce56', request correlation id '4e2ffe5b-98d9-447b-9466-502aaaa8b4e6'."}

image

image

Are there any further logs available where I can see what the problem for the internal server error is ?

jtracey93 commented 2 months ago

Hey @SeanKelly35 & @jdrepo,

Thanks for reporting. We also noticed this to and have tracked this down to a bug in ARM that we are working closely with the engineering team to resolve.

We have identified the cause and are working out steps to remediate the rollout the changes to ARM ASAP.

For clarity this is not an issue with ALZ, and is impacting many other ARM/Bicep templates that use a particular nested deployment feature in a certain way. We understand this may be frustrating but we are working closely between the two teams to resolve as fast as possible.

Thanks for understanding

Jack

jensdiedrich commented 2 months ago

Hey @jtracey93

no problem at all, so I know that it has nothing to do with my tenant or subscription. So I will go the ALZ-Bicep path

Regards

SeanKelly35 commented 2 months ago

Thanks so much for getting back to me. I can wait for a bit. Cheers!

jtracey93 commented 2 months ago

Hey @jensdiedrich @SeanKelly35 @jdrepo

This has now been fixed and rollout was made overnight, and we have tested and all working :)

jdrepo commented 2 months ago

Hey @jtracey93 , thanks for the notification, yes now it seem that I can get over the review + create step and the deployment starts now. But now I have an issue with the single subscription scenario. Will open another issue

SeanKelly35 commented 1 month ago

@jtracey93 Thanks a bunch will give it a try later today.