Today I tried to move one of my PowerShell scripts that I was running as a scheduled task to my Azure Functions. Remembering how I did this a while back with some PnP PowerShell scripts I knew that Azure Functions could do this. I found quite quickly that the preview functionality looked like turning into deprecated options.
My PowerApps friend Paul Culmsee pointed me in the direction of the Experimental Language Support toggle, however in my environment I did not find this option. This is however documented in the Azure Functions runtime versions overview. Ok, I’m running version 2 and I need to run runtime version 1.
I had to create a new Azure Function first as you can’t change this version number once you have a few functions inside the app. With the new app I changed my runtime version as shown above.
And the experimental Language support option appeared!
I switched the Experimental Language Support on and the PowerShell options appeared!
Pieter Veenstra
Is your business still running on paper trails, sprawling Excel files, or ageing Access databases? There’s a better way — and I can show you exactly what it looks like. I’m the Technical Director of Vantage 365, a Microsoft solutions consultancy working with clients across the UK, the Netherlands, and worldwide. For over 30 years I’ve been turning messy, manual business processes into clean, automated systems that save time, reduce errors, and give teams the visibility they need to make better decisions. SharePains is not just any blog run by a Microsoft MVP. Have you ever used Try-Catch in Power Automate? The original post about Try-Catch in Power Automate can still be found on this site, https://staging.sharepains.com/2018/02/07/try-catch-finally-in-power-automate-flow/ Or have you ever used the Pieter’s method to avoid variables and speed up your flows? https://staging.sharepains.com/2020/03/11/pieters-method-for-advanced-in-flows/ You can contact me using contact@staging.sharepains.com
Leave a Reply
You must be logged in to post a comment.