Update: Microsoft will be moving away from UserVoice sites on a product-by-product basis throughout the 2021 calendar year. We will leverage 1st party solutions for customer feedback. Learn more here.

Automation

Azure Automation allows you to automate the creation, monitoring, deployment, and maintenance of resources in your Azure environment using a highly-available workflow execution engine. Orchestrate time-consuming, error-prone, and frequently repeated tasks against Azure and third party systems to decrease time to value for your cloud operations.

Visit the Automation page to learn more about Automation and how to get started.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. Powershell Cmdlets to manage Automation Patch Management

    Create Powershell Cmdlets to manage Azure Automation Patch Management

    12 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  PowerShell cmdlets  ·  Flag idea as inappropriate…  ·  Admin →
  2. PowerShell Cmdlets for Watcher Tasks

    No cmdlets are available to interact with watcher tasks (creating, starting, stopping, getting job status, job details, etc.).

    There is no way to monitor watcher tasks to check status to ensure the watcher sandbox is running.

    21 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  PowerShell cmdlets  ·  Flag idea as inappropriate…  ·  Admin →
  3. Update Azure PowerShell Modules In New Azure Automation Accounts

    When provisioning a new Azure Automation I would like to see an option where you can tell the service that you want all the Azure modules updated to their latest version. I believe this would save new users to the service pain when attempting to author Runbooks for the first time. This personally caused me 3 hours of pain. https://jacobbenson.io/index.php/2018/05/16/set-azurermvmcustomscriptextension-object-reference-not-set-to-an-instance-of-an-object/

    13 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  PowerShell cmdlets  ·  Flag idea as inappropriate…  ·  Admin →
  4. User Context

    Can you please help me extract the Login ID that is currently running the Run Book .As we do not have a Runbook level restriction within a Azure Automation account ,idea is to check if the current user would login to Azure Portal to execute the Runbook .Before user can execute a the script we need to check if the user is part of a AD Group .

    2 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  PowerShell cmdlets  ·  Flag idea as inappropriate…  ·  Admin →
  5. Update-AzureRmVM not supports try-catch.

    Update-AzureRmVM not supports try-catch.

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  PowerShell cmdlets  ·  Flag idea as inappropriate…  ·  Admin →
  6. Make it easier to update tag values

    Please provide an easier way to update the value of a single tag, on a single resource. ie. a VM

    Current Method:

    The current method requires you to obtain the entire hash table of tags on a resource (in my case a VM), update the value in the hash table, and then write the entire table back to the resource.

    Proposed:
    New TAG cmdlets allowing simple adding, removing and updating of tags.

    Benefit:
    Simplified dynamic manipulation of tags, allowing for simplified automation scripts. The challenge was that all suggestions online pointed to the tags being in an array, which we…

    10 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  PowerShell cmdlets  ·  Flag idea as inappropriate…  ·  Admin →
  7. Add Get-AzureRmAutomationJob status filters for "active" and "inactive" runbooks

    Currently the Get-AzureRmAutomationJob cmdlet provides the ability to filter on a specific status of jobs (e.g. "Running" or "Suspended" etc.). I would like to see two additional status options that represent a grouping of status selections such as "Active" which would encompass all the status selections where the job has not yet completed execution and perhaps something like "Inactive" that would represent all selections where the job has finished executing (e.g. "Completed", "Failed" or "Stopped").

    Currently to achieve this I have to query for each of the status options that would make up an "active" job individually which then requires…

    2 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  PowerShell cmdlets  ·  Flag idea as inappropriate…  ·  Admin →
  8. set-AzureRmAutomationSchedule set start time

    I would like to have the option to set the start time of a schedule in Azure Automation with the CMDlet set-AzureRmAutomationSchedule.
    If you create a schedule in OMS Update Management this sets a schedule in Azure Automation, I like to have control over the start time so I can set the date based on input of my script.
    This gives me more control when I want to update my environments.

    8 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  PowerShell cmdlets  ·  Flag idea as inappropriate…  ·  Admin →
  9. 61 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  PowerShell cmdlets  ·  Flag idea as inappropriate…  ·  Admin →
  10. PowerShell cmdlet to get Runbook context.

    It would be great if you could use in runbook code something like Get-RunbookContext to retrieve the current ResourceGroup and/or Automation Account the runbook is executing in. Then it would be much easier to locate Automation Account Assets like connections and variables without the need to hard-code them into your Runbook. The PowerShell commands available to retrieve and use assets require you to specify the ResourceGroup and Automation Account the asset is stored under.

    137 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  PowerShell cmdlets  ·  Flag idea as inappropriate…  ·  Admin →
  11. Support the Get-AzureRmVmss Cmdlet

    It seems the *-AzureRmVmss cmdlets are not supported in Automation. Specifically Get-AzureRmVmss, Update-AzureRmVmss and other cmdlets in the family. This is especially annoying since they are actually used in the "Scale Down Virtual Machine Scale Set Instances", "Scale Up Virtual Machine Scale Set Instances" Gallery runbooks.

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  PowerShell cmdlets  ·  Flag idea as inappropriate…  ·  Admin →
  12. 1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  PowerShell cmdlets  ·  Flag idea as inappropriate…  ·  Admin →
    under review  ·  Beth Cooper responded

    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.

  13. Show PowerShell command line for creating any Resource when you select the resource

    Showing PowerShell command line for creating a Resource when you select a similar resource from Azure Portal will help those who are working on automating the Azure tasks.

    This is similar to how you show the downloadable template for any resource. You can show the PowerShell command line for achieving similar results.

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  PowerShell cmdlets  ·  Flag idea as inappropriate…  ·  Admin →
  14. Enable Publish-AzureWebsiteProject command in Runbooks

    Please add this feature "Publish-AzureWebsiteProject" in future so that we can publish content to website from Runbooks using the package which is in azure storage container or by downloading package from storage container to Worker process locally temporary folder and then execute the command .Currently getting error while performing the option

    9 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  PowerShell cmdlets  ·  Flag idea as inappropriate…  ·  Admin →
  15. Increase 5MB limit for CheckPoint

    Many cmdlets need to be run as InlineScript. And as Checkpoint are not available in InlineScript trying to assign the returned values from an InlineScript to a variable is a solution.... sometimes.
    When dealing with larger data sets, e.g. Get-MsolUser with +1000 users this no longer works because of a 5 MB limit for a Checkpoint.

    4 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  PowerShell cmdlets  ·  Flag idea as inappropriate…  ·  Admin →
    under review  ·  Beth Cooper responded

    Thanks for posting this! How large does the data set get with you are working with a function like Get-MsolUser with 1000 users? Also, how frequently do you rely one PowerShell Workflow functionality in your scripts vs. using PowerShell and making the script idempotent?

  16. Status on Module Import

    I would really like to be able to get a status for when a module has been fully uploaded and all cmdlets have been extracted.
    Currently I have to make my script sleep for a random time and not be able to extract information whether it has been fully uploaded or not.

    Either build a -wait property on the new-azurermautomationModule or some other thing.

    10 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  PowerShell cmdlets  ·  Flag idea as inappropriate…  ·  Admin →
    under review  ·  Beth Cooper responded

    Why can’t you use the ProvisioningState property from the Get-AzureRmAutomationModule cmdlet? ProvisioningState should show as “Creating” until all the cmdlets are extracted.

    As a side note since it is somewhat related. We are currently working on providing more detailed feedback in the UX on module import status so it is more apparent that the module is still extracting activities. We are also working on bubbling up underlying errors that caused activities to fail to extract.

  17. Start/Stop Cloud Services Web/Worker Role using Azure Automation and RunBook

    We have many Cloud Service Worker roles running on Dev environment. Dev team does not need them at night and on weekends. It will be awesome to have a RunBook which i could schedule to run at day end to to Stop these Worker Roles. can have another RunBook scheduled early morning to spin them back up.

    4 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  PowerShell cmdlets  ·  Flag idea as inappropriate…  ·  Admin →
    under review  ·  Beth Cooper responded

    Right now, you can stop an entire service using Stop-AzureService and start it using Start-AzureService. If you are looking for a more granular solution, you can delete a role instance (see msdn.microsoft.com/library/azure/dn469418.a..) and wrap this call in PS.

    Can you let me know if you are looking for one of these solutions? If you are looking for a specific cmdlet that does not exist either as an Azure cmdlet or in the REST API, then I’ll move this request over to cloud services since they own adding this functionality.

  18. Get-AzureAutomationJob output has JobParameters as empty. Output doesnt contain the JobContextID , and the HybridWorker property is empty.

    Get-AzureAutomationJob output has JobParameters as empty. Output doesnt contain the JobContextID , and the HybridWorker property is empty.

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  PowerShell cmdlets  ·  Flag idea as inappropriate…  ·  Admin →
    under review  ·  Beth Cooper responded

    Thanks for reporting this! Our team will investigate adding a fix for these issues.

  19. View or export Modules

    The use of modules is very important in PowerShell authoring. Currently in Azure Automation, once you import a module, there is no way to view the current code that is implemented. This is challenging when you want to update a module or are troubleshooting an existing one. You can refer to source control but there is no guarantee that is what's implemented in Prod. Being able to see what is contained in a module or at least export out the zip would be helpful.

    Thanks!

    Christopher

    16 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  PowerShell cmdlets  ·  Flag idea as inappropriate…  ·  Admin →
    under review  ·  Beth Cooper responded

    Thanks for the feedback Christopher! Are you interesting in the global modules or modules that you have imported yourself to Automation?

2 Next →
  • Don't see your idea?

Feedback and Knowledge Base