Template analyzer action considers lack of managed identity to be error (even if not used)

[pamelafox]

I am trying out the template-analyzer app on a simple project that deploys a Web App with no database, storage, etc. The only resources are App Service Plan, App Service, Log Analytics.

Here's the PR where I try out template analyzer:
pamelafox/simple-flask-server-example#3

My Bicep code originally did not use a managed identity, as it wasn't needed for this app. However, that resulted in "Error"-severity level alerts.

So I changed it to create a managed identity, and it's happy now. But I'm wondering if it's actually necessary, and if there are any drawbacks to creating managed identities before they are needed.
I have potentially quite a few templates which would be affected by this, so I'm trying to understand it fully before making the change.