If a VM is longer than 15 chars, unable to see which VM at a glance. This is troublesome in large production environments.6 votes
When running job in runbook, input parameters (Input Name and Value) are displayed in job windows.
I can imagine there can be use cases such as multiple users using one runbook and the job input parameters are displayed to every users.
As a workaround, currently there are Runbook assets , variable which can encrypt the values, but these are made for automation account level.
I believe there should be straight forward way to hide or mask input parameters for runbook job from runbook itself.26 votes
Just like the Automation resource page, a circle graph that demonstrates degree of compliance.1 vote
Thanks for the feedback. This is something we’ve been planning to add to the service. Monitoring\compliance for Automation. Please share if you have any specifc area you’d want to have captured that will impact your overall Automation Compliance.
Ability to rename automation runbooks and schedules. Typos and naming standards changes happen, please help your customers out with this little change. Thanks.4 votes
When vieweing "Jobs" in Azure Automation, only the columns "Status", "Created" and "Last updated" is visible.
It would be useful to be able to view columns for "Schedule" in this view.
A runbook may be linked to several schedules and thus may run with different parameters.
With that in mind it would make sense to be able to see what linked schedule each job was triggered by.19 votes
We need more than 15 tags to identify our resources. Unfortunately, the automation account is one of the few that does not yet support 50 tags. Please change that.3 votes
The job run page with the Input and Output has no deep link or at least the portal does not update the URL and I found no documentation how to build a deep link. For working on errors it would be easier to send a link directly to a co worker10 votes
Currently, the self-signed certificate that you created for the Run As account expires one year from the date of creation and the certificate won’t be automatically updated. Although you can set your certificate to expire a very long time by using Azure PowerShell, some users wonder that it will be a security issue if such a long certificate leaks. Such users are required to update the certificate every year before it expired. It would be great if the operations to update a certificate could be flexible as follows so that the uses can omit the troublesome procedure, which is updating the certificate every year.
- Any expiration date can be set from Azure portal
- Add an option of automatic update
Currently, the self-signed certificate that you created for the Run As account expires one year from the date of creation and the certificate won’t be automatically updated. Although you can set your certificate to expire a very long time by using Azure PowerShell, some users wonder that it will be a security issue if such a long certificate leaks. Such users are required to update the certificate every year before it expired. It would be great if the operations to update a certificate could be flexible as follows so that the uses can omit the troublesome procedure, which is updating…57 votes
We are bringing in support for Managed identity in Azure Automation which would be the recommended way going forward for authentication & get over the issues\overhead associated with managing RunAs cert.
ETA :March-End\Early April CY21.
Add the ability to organize runbooks into folder / categories in the Runbooks view under automation accounts.2 votes
I'm currently having issues using the mouse wheel to scroll, in firefox, while editing a PowerShell-based runbook. I've not tried it with any other runbook types, but I presume the issue would persist.3 votes
In runbook designer, the label for each activity is too small in length, only allows 11-15 characters, could you please make it allow more characters showing. This will help to know what each activity does at a glance in runbook designer.
Currently the words wrapped and cut off. it is hard to read especially when calling child runbook, we want to know what child runbook name is , but it wrapped and cut off, we will have to click it to display the whole label.1 vote
Thanks for the valid suggestion. Your feedback is now open for the user community to upvote & comment on. This allows us to effectively prioritize your request against our existing feature backlog and also gives us insight into the potential impact of implementing the suggested feature
I'm in the middle of automation and deploying runbooks/schedules via ARM templates but couldn't find the option to link schedule to runbook.
i tried with "type": "Microsoft.Automation/automationAccounts/jobSchedules", but didn't work
could you please check and provide some suggestions?
In my case i must to change the name of parameter 'name' from template.json and parameters.json.
I downloaded a Service Plan Automatetion Script and changed the parameter name from 'name' to 'servicePlanName' to make it works, else PowerShell prompt this...
Currently there is a 500 custom field limit to Log types. Turning on diagnostics for Data factory V2 quickly fills this limit to the maximum on AzureDiagnostics which is used by multiple services / providers.
Can we have the limit raised, or suffix the log type with the service / provider or resource name to help overcome this. If the limit is reached, critical diagnostic events can be lost.17 votes
It would be nice to remove the old entries for Update Deployments in update management solution for presentation purposes
It would be nice to remove the old entries for Update Deployments in update management solution for presentation purposes.6 votes
It's nice to have the powershell editor and see how it supports useful capabilities like code comments through keyboard shortcuts. (Ctrl + k c), however, it would be even better if it supports Ctrl + s to save the script (currently it opens a window to save the whole webpage...), that would make the editor even more intuitive.1 vote
change tracking "Manage Machines" is grayed out after onboarding.7 votes
For auditing purposes, it would be helpful to be able to view who started a job in the Azure Portal. It would be nice to show the StartedBy property in the Essentials section on the job details screen. Currently we need to use the Get-AzureRmAutomationJob PowerShell cmdlet to view the StartedBy property by providing the JobId.11 votes
Currently just "Completed" and "Failed" state is shown in job list.
If the script throws warnings, this is just visible if I go directly the job / Job overview.
E.g. in my script that assign SPE E3 licenses I throw warning messages if we are running low on licenses .. but if it's not in the dashboard the Administrator don't cares ..17 votes
Would be nice to be able to assign multiple DCS node configurations to a DCS node, i.e. the same way we can have multiple GPO assigned to an OU.12 votes
Thanks for submitting this feedback. We will investigate and update the status here.
- Don't see your idea?