Microsoft
Microsoftsrinipadala thanks for the article, nice feature although half baked.
Why?
🟡 Pool deployment available via Bicep / ARM, however when deployed to Azure you see nothing in the portal, just backend pool and the members. The backend recourse is not even visible in the Recourse Manage Explorer or query. It is a totally phantom resource.
🟡 Impossible to set headers (like in outbound policy) for the members of the pool, so we can't find out which backend endpoint the response came from.
That makes it difficult to implement in prod, as troubleshooting will be super hard.
