In the testing console, the inputs are remembered when the testing console is opened again, but the Run Settings already reset to "Azure" even if it had been tested on "hybrid worker" the last time it was open1 vote
Thanks for this suggestion! We will investigate remembering the last run on setting for hybrid.
In the runbook test experience and production jobs for graphical runbooks enable tracing of the input objects, output objects, streams, exceptions, start and end times for each activity. This will enable much more efficient troubleshooting.1 vote
Azure Automation / UserVoice users – we would appreciate your feedback on this suggestion!
In the dialog to enter parameter values when starting a runbook, it would be convenient to offer validated values where those can be inferred by type or otherwise. For example, if the parameter type is "System.Management.Automation.PSCredential", give me an intellisense-like dropdown of the credential assets I've defined in the automation account to choose from. I think this would help make testing faster and easier to avoid trial and error when possible.4 votes
Thanks Noah! We can investigate selecting assets as input parameters to runbooks.
When using "Insert" to insert a setting or activity, it would be nice to have a full-text search filter to quickly narrow down results. Given that the Azure module has hundreds of activities already, will become increasingly tedious to locate what you want. This also fits with requests for intellisense and authoring tooling in VS or ISE.1 vote
Thanks again! This is great feedback.
Allow to enter an AAD user account when manually start a runbook, or allow to use the credentials of the signed-in user (AAD token)
Allow to enter an AAD user account when manually start a runbook (instead of store it as Asset), or allow to use the credentials of the signed-in user (reuse the AAD issued access token)12 votes
Thanks for the feedback! We will look into making authentication to Azure easier and will take this suggestion into consideration.
In general the "Operation status" pane is a good idea, but it gets really tiresome that you have to close and close and re-close succeeded operations etc.
It should definately be togglable weather you want to see running/completed operations or not.3 votes
You are talking about the notifications that show up as you create/delete runbooks, start jobs, etc.? Let me know if I’m misunderstanding the request.
This is really how the framework works, but I could definitely see adding a configuration step to turn off notifications, especially when you are editing and testing runbooks.
Display historic runbook executions like a calendar appointment to visualise runbook executions that might occur at the same time. Future executions could be displayed using historic average runtime or default values to illustrate possible future scheduling conflicts.3 votes
Thanks for the feedback. This would be a nice addition.
Currently the requirements including setting azure resources is pretty convoluted (and currently does not work). A way to interact directly from automation with the websites and change common features would be very beneficial.3 votes
Thanks for the feedback. Can you describe some specific scenarios that you would like to use this for?
Right now, you would write PowerShell cmdlets against the website that you want to automate against.
Do you want to be able to send the website or website properties as parameters to a runbook to automate it? Or are you looking for similar functionality to that provided in web jobs?
I ran into an issue where I had no idea how to fix nor was the error message correct. I called CopyItemtoVM runbook and got an error saying Connect-Azure runbook could not be found. that was only because I had imported the child CA after the parent CITVM. Error message needs to be updated and more importantly this bug is very hard to figure out.7 votes
We are currently investigating how we can fix this issue so that it does not matter what order you publish your runbooks in.
But better error messages to explain the actual issue would definitely help too. I’ll keep you posted. :)
Description : Until granular permissions for items becomes available per administrator, allow critical RunBooks to be marked as protected and with a password requirement.
Reason : Critical runbooks need to be protected as much as possible from accidental deleted or editing. Mitigate possibility of human error.9 votes
Would role based access control solve this problem for you?
Also, are you interested in protecting runbooks from being started or just edited and deleted?
Allow, from the management console, to execute a Powershell command (with elevated permissions) on every instance in the hosted service (or role). There should also be an option to do a rolling run or a brute force run.
Output from the script, obviously, needs to be displayed at the end of the run.1 vote
With the current Connection Type extensibility, giving 'friendly' names to the properties within the type is not possible, resulting in unfriendly names displayed to the user when creating a new Connection. Supporting Text Hints would also be nice, though less necessary.
"DisplayName": "Service Bus Namespace URL",
"Hint": "ie: <a rel="nofollow noreferrer" href="https://[namespace].servicebus.windows.net"">https://[namespace].servicebus.windows.net"</a>,
- Don't see your idea?