AAD Authentication for Http trigger in LA Standard

[rubenaster]

When creating Http triggers LAs will generate a URL with secret strings. This has the following main disadvantages:

• you need to work with secrets, even so Azure more and more shifts to authentication via identity - which is geat!
• in your CI/CD pipeline you first need to deploy your LAs, then read the URLs of every Http workflow somehow which in return you then need to set in your e.g. APIM (using AAD authentication would make all of this obsolete)
• when you recreate the workflow or regenerate the secret you'd need to perform the previous steps again

So there really is a need for authentication via identity. This would make life so much easier and Azure Functions already support this feature.

There's a video about how to enable this feature on LA via REST (https://youtu.be/tawHXz6qGQI - it uses app registrations but identities work, too) but that's not transparent enough for our organization plus we only want to use GA features.

Several months ago I was told that it's in the pipeline and it should be ready first half of 2022 but I don't even see it in preview right now. So please, it's really embarrassing to use LA Standard for clients with such old-school auth-methods and the need to create such needless complicated pipelines.