Highlight
I’m sorry, what?
Intro
Ha! This one is a good one.
Here is my short story…
Situation
In one of our data platforms we’ve been deploying a lot of logic apps, for now it’s over 160 deployments, but we plan to have 300 by the end of the year.
Recently our deployments started failing because one of Azure policies which checks if Logic App Standard is using an app service plan with Virtual Network integration enabled. After investigation, we’ve checked and concluded that it’s not on our side and raised a support request to Microsoft asking for help.
Microsoft’s support engineer came, and after an investigation said that Terraform AzureRM makes non-supported calls for Logic App standard. And we should move our deployments to Azure Bicep.
?!??!
Obviously you can imagine our surprise. It’s not like we will abandon our entire Terraform IaC strategy because of a single issue. We temporarily disabled the policy and continued as-is. But our surprise knew no bounds.
Solution
When I reached out to Microsoft’s product team for AzureRM and TF, they said that this is an often misalignment between support engineering teams and Microsoft’s strategy.
Microsoft’s official response was that AzureRM is fully supported by Microsoft.
So, what is the solution? If you ever hear this, then push back, and don’t let your team change the approach. Push back the support team to assist you and escalate your issues inside of MS product teams if necessary.
Summary
This one wasn’t really a technological issue, it’s a business alignment issue. These ahppen as well, so I wanted to share a story here, to ensure you always use logic, and sometimes you will need to push back.
