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. Remove quid requirement for jobs resource types in ARM templates

    CompilationJob and Job resource types require a guid for the resource name. Because of this PowerShell is needed to prevent inserting a guid manually. Which makes template more complex and prevents template only deployment. (Deploy to Azure button)
    Resource Types
    Microsoft.Automation/AutomationAccounts/jobs
    Microsoft.Automation/AutomationAccounts/Compilationjobs
    Please remove the requirement of the guid in the resource name. The job identifier/name of the underlying job can still be a guid.

    93 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    closed  ·  3 comments  ·  Other  ·  Flag idea as inappropriate…  ·  Admin →
  2. Allow custom integration modules to be automatically pushed out to the Hybrid Runbook Workers

    Currently, when imported a custom integration module into Azure Automation account, it does not get pushed out to hybrid runbook workers. One of the great feature about SMA is that integration modules are automatically distributed to runbook workers. It would be very nice if this feature is enabled on Azure automation hybrid runbook workers.

    78 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    6 comments  ·  Hybrid  ·  Flag idea as inappropriate…  ·  Admin →
  3. Scheduling a Runbook multiple times with different parameters

    It would be nice, if one runbook could be sceduled multiple times. Its need with runbooks are parameterized (eg, delete resources with this tag at this time and with that tag once a week).

    70 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    22 comments  ·  Scheduling  ·  Flag idea as inappropriate…  ·  Admin →
  4. BitBucket integration

    Can you please add BitBucket integration into the roadmap?

    66 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Source control integration  ·  Flag idea as inappropriate…  ·  Admin →
  5. Add Folder Views

    The list of runbooks can get quite long. It would be nice to be able to organize these into multiple folders to aid in finding the correct runbook quicker. It may also be a good idea to implement folder structures with the Role-Based Access Control request.

    61 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  User Experience  ·  Flag idea as inappropriate…  ·  Admin →
  6. Ability to schedule a run every minute or Integrate with Azure scheduler

    We have a requirement to execute an SP every 2,3 minutes and were planning to consider automation. But having 1 hour schedule will not work. Any suggestions ?

    55 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Scheduling  ·  Flag idea as inappropriate…  ·  Admin →
  7. Add-AzureRmAccount doesn't work with service principal accounts

    Scenario
    - define an Automation Account based on Azure AD Service Principal (without any certificate)
    - when the account is used to login to an azure subscription it is successful but any other call to azure fails (if run on Azure, it works if run on an hybrid worker)

    code snippet
    $credentials= Get-AutomationPSCredential -Name $AutomationCredentialName

            Add-AzureRmAccount -ServicePrincipal -TenantId $TenantId -Credential $credentials -SubscriptionId $SubscriptionId -EnvironmentName AzureCloud 
    

    the following statement fails with WARNING: Unable to acquire token for tenant <tenant name>

    Get-AzureRmSubscription

    The same runbook works if run from an Hybrid Worker.

    Using Azure powershell module 2.1.0
    Automation account id /subscriptions/fd9e0192-37d2-4e28-9c42-6ae6a768813a/resourceGroups/OpsManagement-WEU-RG01/providers/Microsoft.Automation/automationAccounts/OSMAutomation

    In…

    43 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    closed  ·  6 comments  ·  Bug  ·  Flag idea as inappropriate…  ·  Admin →
  8. Provide configuration data management for DSC

    Currently, it is not possible to handle configuration data in the Azure Automation portal. The only option is to create a hash table or psd1-file in PowerShell and use with the ConfigurationData parameter of Start-AzureRmAutomationDscCompilationJob.

    It would be very useful if the Azure Automation portal could provide a “configuration data editor” where it`s possible to define an environment with properties applicable to all nodes (‘*’), define properties for individual nodes as well as custom properties needed in the environment (“NonNodeData”). The data structure created would then be converted into a hash table which can be selected as an option when…

    34 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Desired State Configuration  ·  Flag idea as inappropriate…  ·  Admin →

    We investigated this area in depth, including what solutions already exist. The DSC community has an active project that addresses this need. Rather than duplicate the functionality, we are planning to include reference material in our documentation for how to use the community solution with our platform. Until the docs have been updated, you can read details of the community solution at the link below. Thank you!

    https://github.com/gaelcolas/datum

  9. Utilise Automation runbooks within DSC configurations

    Pulling assets information and data into the deployment using any of the Orchestrator.AssetManagement.Cmdlets is already available for Azure DSC Configuration.

    I haven’t been able to find this functionality and I am not sure if this already exist but It would be a good idea if you could Utilise Automation runbooks within DSC configurations by adding a functionality on top of Azure DSC Pull server where it could pull Runbook and PowerShell script from Azure Runbook stack and run them as part of the DSC deployment, (Same topology as Custom script extension)

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Desired State Configuration  ·  Flag idea as inappropriate…  ·  Admin →

    This should work in the current environment without requiring new features. It looks like Beth asked for more information, and I agree. Since the discussion on this item has not continued for some time, I will mark it as closed. Please reach out or comment here if we should research this area further.

    Thank you!
    Michael Greene
    @migreene

  10. 1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  User Experience  ·  Flag idea as inappropriate…  ·  Admin →
  11. azurerm.network is missing. why?

    azurerm.network is missing. Why?

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  PowerShell cmdlets  ·  Flag idea as inappropriate…  ·  Admin →
  12. Version control integration for DSC

    Integrate DSC to Azure DevOps Repo to allow versioning of configuration state. This will allow the product to compete with commercial configuration management tools.

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Desired State Configuration  ·  Flag idea as inappropriate…  ·  Admin →

    We have investigated this area in depth. It is possible to publish configuration scripts or compiled MOF files from CICD platforms such as Azure DevOps but as you have pointed out, there currently is no source control integration. A major benefit to integration with Azure DevOps is using the Test capabilities to lint/unit test configurations before deployment. If we integrated with source control, the only way to still follow the same pattern would be a branch strategy where merging to master means deploy to production. This would also limit the ability to use features such as defining multiple environments and releasing in stages or with approvals. For now, I am closing this item but I will continue to look at how we should be integrating with CI platforms.

  • Don't see your idea?

Feedback and Knowledge Base