Missing resource; Automation Accounts?

[sanderkl]

Hi, I find this extension and come from Azure Automation extension, which is deprecated.
I used it to edit runbook scripts in Automation accounts, it was able to save scripts in draft and publish them.

In the Azure Resource extension I see lot more resources, but no Automation Accounts. Am I missing something or is not supported in the extension? cheers, Sander

[alexweininger]

Hi Sander,

Unfortunately, Automation Accounts are not supported in the Azure Resources extension. Although deprecated feel free to continue using the Azure Automation extension.

[JMDirksen]

Is this ever going to be added to the Azure Resources extension? Can this maybe be marked as a feature request? I hate to have to work with deprecated (not updated) things and especially having a yellow exclamation mark.

⚠️ This extension is deprecated. Use the Azure Resources extension instead.

[r3dpan]

I would also like to know, if there are any plans to add this feature in the future.

Currently there is the problem, that the only VSCode extension, that allows to edit and test azure runbooks inside VSCode, is 'Azure automation'. This extension however still depends on the deprecated extension 'Azure Account'. Sadly, there is currently no communication whatsoever from the devs from the 'Azure Automation' extension (official microsoft extension) what the future plans for this extension are (e. g. implementing their own Sign-In logic or also deprecating their extension). Instead there is only a recommendation to keep using the deprecated (and also official microsoft) extension 'Azure Account' (-> https://github.com/microsoft/vscode-azureAutomation/issues/60#issuecomment-2628426922). The 'Azure Account' extension however points to using the 'Azure Resource' extension instead in it's deprecation message.

From a user point of view i find this behavior extremely concerning and also a bit confusing. On the one side, there is the recommendation to keep using an outdated and unsupported version of an extension (which in turn could lead to {security} problems in the future) and on the other side there seems to be no official communication from microsoft on what's the plan to solve this issue at all (e. g. 'Azure Resources' extension will get the feature added in the future, 'Azure Automation' extension will be updated, no update on any extension and instead relying on the azure build-in editor, ... etc.). Keep in mind that the 'Azure Account' extension made it's deprecation date public mid last year already and those are all VSCode extensions developed and provided by microsoft itself.