We are rolling support for Functions V4, and for the most part customers will not require any action, as they will be migrated automatically. There are some edge cases, and the team will be publishing guidance for those case next week.
cc: @nikolaiblackie, @logicappsio
@wearsy@michael_stephen@WSilveiraNZ@sandro_asp@Azure@egrootenboer Update!
I believe there is a break-in period for Service Bus, because the memory hike is only during initial use. Over period of time, the peaks are not that high, as matter of fact there are no peaks.
Why is Service Bus being clingy, was expecting a clean break once the ingress activities are over, but the memory is retained for long even after the connection are closed. Any pointer, the egress activity is through Azure Function?
@345Technology If you have patience and systematically approach it, you can tame them all. You know how they start calling it[Integration work] your baby once you put enough effort into it, that is so true, if you give enough attention it will grow to handle the toughest of challenges.
Key contrast to designing on-prem Integration solution compared to building one in Azure, is that every interfacing team that comes for Demo goes back with goodie bag of Azure artifact that they can host and test however they want.
#Azure#CloudComputing
@WSilveiraNZ@BizTalkBill@AzureFunctions#Azure
The issue was resolved, once I stopped "Cisco AnyConnect Umbrella Roaming Security Agent" service, as suspected, that was the one blocking the call.