Support PowerShell Core as Runbook Type
I develop on OSX and so use PowerShell Core heavily.
It's frustrating when Azure Automation Runbooks don't work the same way as they do locally because they run PowerShell 5.
For example, Invoke-RestMethod in PowerShell Core supports the following parameter:
The product team is aware of this need and while we are not immediately able to work on this, we will consider it if resourcing allows in future.
So it was announced today that Azure Functions now support PowerShell 7. This really feels like the death knell for PowerShell's future in Azure Automation, especially given the complete silence on basically any new features for the Azure Automation platform in over a year and a half now. Extremely disappointing. Azure Functions is not a direct replacement for Automation.
Any updates on this?
Ken Knight commented
Frustrated with Automation as well - what the heck actually works here?
I'm forced to reverse engineer by reading automation library modules.
Get-Variable # doesn't work
How does my powershell code know its in a runbook or interactive? I there some context variable i can check?
Can you please let us know the roadmap for Azure Automation?
Justin Grote commented
Azure Automation seems like pretty much a dead end, time to start moving to Azure Functions since it is GA for powershell...
Honestly, what development resourcing constraints are there for Azure Automation? The last new feature you added was nearly a year ago on 02/11/19 with Az module support. Is Azure Automation a dead product now? It is extremely frustrating that what is supposed to be Microsoft's premier task scheduling solution doesn't support Microsoft's own premier scripting language, especially when said language had been GA for over two years.
Nicholas Hatch commented
PowerShell 7 will be GA very soon as well. At this point, you might as well just jump to 7.
I have a Powershell tools library that I need to call from Azure Automation and from Azure Functions. I'm being pushed to Function App v2 which is Core... but Automation is stuck against 5. Considering how much Core is being pushed it is unacceptable that it is not supported in Automation.
Rich Lewis commented
This is really frustrating. Powershell Core has been in GA for over 18 months now and is being pushed by Microsoft everywhere, not just Linux/OSX, but Windows too (I'm primarily a Windows user). Why is AA so far behind the curve on this?
I'm super frustrated about this. Is there any update?
Yeah, I do all my dev work on Windows and I still agree that this is important. After all, new functionality is only being added in PWSH 6+, and we can't take advantage of any of it in Automation currently.