Add a job to refresh assets so if an asset is added in another browser tab you don't have to leave the editing blade to see the assets in the editor blade1 vote
Thanks for posting this feedback.
Add a button to create Service Principal for accounts that don't have a SP or to replace/update current cert used buy SP runas Account.1 vote
Thanks for posting this idea. The team is looking into this. I’ll update when we start working on this feature.
Connection types are defined as a file in the module file. Is there a reason that you want to created them via cmdlets instead?
As a side note, you can do this through our API today as a workaround.
When adding a new Connection, it would be nice to have descriptions or more information for the various required fields - Application, Tenant, Certificate - and possibly a dropdown box for the subscription.1 vote
Thanks for posting this! We had considered something similar a while back, but it fell off our backlog. We’ll take another look.
Please make it possible to add labels on links in graphical runbooks, otherwise I can be hard to understand logic of the runbook. (Was one of the great features of SCO Classic).1 vote
Thanks for the feedback. We will investigate and update here if we can get this done as I agree it makes understanding the flow easier.
The blades on the portal are very poor in performance and navigation controls. Please improve the blade navigation by adding sizing controls. The technologies and solutions are great, but the portal experience leaves the users abandoning the idea.1 vote
Thanks for the feedback. We are looking to improve the performance and navigation across the automation experience.
You can define inconsistent types between runbook parameter type and the type of the parameter associated with a schedule. For example, if you have a runbook RB0, it has a parameter P0 of type Boolean.
You can actually use Register-AzureRmAutomationScheduledRunbook cmdlet to associate a schedule with parameter P0 of a string type.1 vote
Thanks for reporting this. We will look to address in a future cmdlet release.
Currently there is no alerting mechanism to alert when jobs in automation accounts get Completed with errors. The job shows completed, which means the runbook script has executed ok, but when we go inside the job we can see errors. There should be some alerting configured to know that the Automation job has completed with errors.1 vote
Thanks for your suggestion. This is under review.
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.
Use "Script Center" tags "ASM" or "ARM" to filter which runbooks within the Azure Portal is supported for ARM. This will make it easier for end users to find the right runbooks for the job
Thanks for posting this. Our team is taking this into consideration.
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>,
provide an option to allow users to unhide the runbooks that sync AA and Github to allow users to modify the process, with their custom process.
Use case would be adding an email notification or integrating with a ticketing system so their is a record of who preformed the sync and when in other system than the Azure Audit log.0 votes
Thanks for posting this! You can actually overwrite these scripts with your own content today just by importing a runbook with the same name as the script (just like global modules, these are global runbooks). So for example, you can name a script Sync-MicrosoftAzureAutomationAccountFromGithubV1 and your script will run when you click the “Sync” button.
In order for us to make these scripts public, we need to remove some proprietary code so this isn’t just as simple as releasing them. I’ll discuss with the team to see what we can do though.
- Don't see your idea?