Azure AI Studio Tip: Deploying to an Existing Web App Generates a Newly Registered AAD App Every Time
Cleanup on Aisle 5
While adjusting and redeploying myRodBot a few times, I accidentally came upon somewhat of an issue. It’s probably more of an issue for me than most because it kindles a fire against my neatness and organization OCD.
Not familiar with myRodBot? See: Basic Steps to Create Your Own Simple Copilot
I had surmised (incorrectly) that when I updated my Web App from Azure AI Studio that it simply updated just the app so no additional resources were affected. It DOES update the Web App, but it also generates a new AAD App registration every single time I update the Web App.
I’m not sure that there’s a cost or a performance hit in having additional App registrations (if you know of something I’m missing, let me know) but, even though the App update date is recorded and shown, it does still make it much more difficult to manage the app because you have to hunt down the most recent one - and it’s possible that the most recent one could have been rolled back.
The other issue is if you’ve assigned a real domain to your Web App. Every time a new App is registered, you have to find it and add the proper Redirect URLs in Authentication (shown in the next image) for Auth Callback so your users can login.
So, my recommendation is to take the time (like I’ve done) to remove the ones that are no longer needed.
[Want to discuss this further? Hit me up on Twitter or LinkedIn]
[Subscribe to the RSS feed for this blog]
[Subscribe to the Weekly Microsoft Sentinel Newsletter]
[Subscribe to the Weekly Microsoft Defender Newsletter]
[Subscribe to the Weekly Azure OpenAI Newsletter]
[Learn KQL with the Must Learn KQL series and book]
[Learn AI Security with the Must Learn AI Security series and book]