500 Internal Server Error

[cata008]

@DCMattyG I have deployed the IPAM solution using Azure Web Apps instead (one for the UI and one for the Engine), but I am running into some ugly errors.

If I click on any of the tabs - spaces, blocks, vnets etc - I end up with a loading screen. While checking the engine logs, I can see many errors, but I am not sure where to start looking for the problem.

The only thing that I did different is, I deployed the solution using an Application Admin role (I don't have a Global Admin role), but everything was successfully deployed nonetheless and all permissions seem to be in place.

Any idea what I got wrong?

[DCMattyG]

Hey @cata008, the Global Admin requirement is really for the ability to grant Admin Consent for the App Registration. For the Engine Service Principal, does it have Reader at the Root Management Group?

I'm guessing that you're not using the provided deploy.ps1 script, so how are you creating the App Registrations and assigning their permissions for your deployment? Are you doing that manually?

[cata008]

@DCMattyG Thanks so much for your quick reply.

I have tried multiple things:
a. Deployed the solution in a multi-container app service using .\deploy.ps1 - still got the described behavior and no errors - maybe it is worth looking into error handling?
b. Started as "a." and then made the app service a single container app; deployed an additional app service for the engine - set all environment variables accordingly - the same behavior
c. Just managed to get hold of a test tenant and with a Global Admin everything works

This is how the app registrations look with an Application Admin role only:
ipam-ui-app

ipam-ui-engine

I compared this with the way it looks for the Global admin deployment and I do not spot a difference.

And to answer to your questions, the engine spn has Reader on the root mg.

[DCMattyG]

Thank you @cata008, for the incredible level of detail. It seems you're doing everything as expected, so I'm curious to explore this with you on our upcoming Teams call together later this week.