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. 60 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  PowerShell cmdlets  ·  Flag idea as inappropriate…  ·  Admin →
  2. Ability to rerun a job with same parameters of the last job

    The feature I propose is a 'Rerun Command’. I have a ‘crude’ mockup attached. Clicking on Rerun would bring up the Start Runbook blade; but with the parameter values prepopulated with the same values from the previous execution. I can now modify any value, if necessary, or just click OK, to start the job quickly.

    I see myself rerunning my runbook with mostly the same values. When I have many input parameters, I have to be very careful not to mess up any values, and what I do now is open two browser windows. Open the previous job’s Input blade…

    59 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  User Experience  ·  Flag idea as inappropriate…  ·  Admin →
  3. Please allow for versioned configurations in Azure Automation

    It would be great to have multiple versions of DSC configurations compiled into Azure Automation, simultaneously.

    Currently, a server, or other resource, could be provisioned with one version of a configuration, but if an updated version is compiled during pipeline transitions, they could receive a different configuration than tested in a lower environment, invalidating their tests.

    This would allow someone to target a v1.1.0 configuration, even though the latest is v1.1.3 in Azure Automation, for example.

    It would be doubly nice if this could be derived from Git tags or other versioning mechanism in TFS/VSTS, as well.

    58 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Desired State Configuration  ·  Flag idea as inappropriate…  ·  Admin →
  4. The way updating the certificate for Run As account should be more flexible

    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…

    53 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  User Experience  ·  Flag idea as inappropriate…  ·  Admin →

    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.

  5. Azure Automation should support using pre-existing Service Principals for RunAs connections

    Currently the only supported method for adding a RunAs connection to an Azure Automation account is to create a new Service Principal. By default the SP is created with Contributor access to the entire subscription.

    This is not ideal for several reasons:
    * Contributor access to a subscription is a relatively high level of access. I would like to ensure that my automation accounts are more tightly constrained.
    * The auto-generated name for the SP can cause problems in accounts that have applied a naming standard/governance model to SP accounts.
    * Since we are unable to reuse our existing SPs…

    52 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Role Based Access Control  ·  Flag idea as inappropriate…  ·  Admin →
  6. Provide better exception messages in Azure Automation

    Exceptions are currently only surfaced by the exception message string. Please give us richer exception messages for Powershell-based runbooks, such as file name, line number, etc. Ideally I'd like to get a "regular" exception object back using Azure Powershell.

    51 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Debugging and troubleshooting  ·  Flag idea as inappropriate…  ·  Admin →
  7. Fixed IP for Automation PowerShell sandbox in order to fit ACL requirements for public endpoints

    If VM has external endpoints (WinRM, SSH) protected by ACL, the Azure Automation doesn't able to connect for such VMs.

    51 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Hybrid  ·  Flag idea as inappropriate…  ·  Admin →
  8. CSP Subscription cannot create Azure Classic Run as Account

    When creating Automation Account in Azure portal, if we use CSP subscription, creating Classic Run as Account is failure.

    Because CSP can access ARM resource only.
    But error message is very unclear.


    • Message
      Azure Classic Run As account creation error

    An error occurred while creating the Azure Classic Run As account for account 'AutomationTest'. Error details: ForbiddenError: The server failed to authenticate the request. Verify that the certificate is valid and is associated with this subscription..

    <Request>
    For resources not available in CSP, please output error including CSP string.

    50 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Other  ·  Flag idea as inappropriate…  ·  Admin →
  9. CORS support for Azure Automation Webhooks

    It would be great to have the ability to enable CORS on Azure Automation Webhooks to enable quick testing from client-side javascript code. At present, client-side javascript will not be able to make a valid POST call to an Azure Automation Webhook due to the call being across origins. This would also allow lightweight apps to be developed without server-side code, for non-technical interfaces that could front-end complex Azure Automation workflows.

    50 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    5 comments  ·  Webhooks  ·  Flag idea as inappropriate…  ·  Admin →
  10. Link Azure Automation Account to OMS Workspace using Powershell

    I am trying to generate an OMS Solution using Log Analytics and Azure Automation. However, after I create an Azure Automation account i observe that there is no way to link the Azure Automation account to the Log Analytics workspace. It would be great if this option is available.

    49 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  Other  ·  Flag idea as inappropriate…  ·  Admin →
  11. Change behavior when sandbox runs out of memory (1MB max to one stream limit)

    There is currently a maximum limit of 1MB when outputting values to the any stream (Serialized size per object in pipeline).
    I understand why this limit is there, but I don't think the current behavior is the right way to go.

    Current behavior is that the runbook restarts, and runs 3 times until it is stopped with the following error:

    Suspended
    The job action 'Activate' cannot be run, because the process stopped unexpectedly. The job action was attempted 3 times.

    If we run it on look at the eventlog on a hybrid worker (this error also happens in Azure workers),…

    47 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Bug  ·  Flag idea as inappropriate…  ·  Admin →
    under review  ·  Beth Cooper responded

    Thanks for posting this feedback! I’m checking with our team to see if there is anything that we can do about this in the short term. We’ll definitely take this into consideration in our longer term plans.

  12. Add Python 3 runbook support in Azure Automation

    Add Python 3 runbook support in Azure Automation. Right now, only python2 is supported.

    46 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Flag idea as inappropriate…  ·  Admin →
  13. Add bitbucket support to Azure Automation

    Add bitbucket as a supported source for Azure automation under the 'source control' pane. Currently only TFS and GitHub are supported.

    46 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  14. Azure Automation PowerShell version 7.0

    Anyone know if or when this will be released, or if it will be?

    46 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  15. Continuous Deployment of runbooks

    I have runbooks that are stored in source control which then get deployed to Azure Automation. The process of deploying them is rather cumbersome (basically a bunch of hand crafted Powershell scripts that call the Azure Automation cmdlets). It seems to me that there are going to be lots of people crafting the same kind of scripts - that's a lot of wheel-reinvention going on.
    I'd like to see some features introduced that support quick and easy Continuous Deployment of runbooks (i.e. I check them into source control and they automatically get deployed to Azure Automation).

    Some ideas:
    -Support Continuous…

    46 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Source control integration  ·  Flag idea as inappropriate…  ·  Admin →
  16. Support populating and displaying arrays for account-level Variables

    While it's possible to set arrays with Set-AutomationVariable, they cannot be displayed or edited from UI.
    It makes them a bit inconvenient - if I have a job that I need to execute against a set of something, I need to have separate jobs to validate and change that set.

    45 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  User Experience  ·  Flag idea as inappropriate…  ·  Admin →
  17. Increase 1MB Size Limit for DSC Node Configurations (MOF files)

    Azure DSC node configuration (MOF files) are currently limited to 1 MB in size. This limitation does not allow for significantly detailed or complex configurations.

    In my specific scenario, we have several IIS websites in a our web farm and we've hit the limit of how many unique websites we can configure per server because the MOF file is larger than 1 MB. The resulting error is that the MOF cannot be encrypted by Azure DSC Automation.

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

    Provide a VSCode extension similar to the ISE Addon

    43 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  19. Outgoing WebHooks

    It would be nice if it was possible to register callbacks for events like "Runbook Status Changed".
    This would allow people to execute runbooks using your existing WebHooks concept (HTTP POST), store the jobid and consume the result of the runbook through the callback once completed.

    43 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Webhooks  ·  Flag idea as inappropriate…  ·  Admin →
  20. Start-AzAutomationSourceControlSyncJob Add SyncType parameter to invoke 'Incremental' syncs

    The Start-AzAutomationSourceControlSyncJob function only triggers a FullSync from a connected Azure DevOps Repo, which can sometimes take a long time if you have lots of runbooks in a repo. Can we add a pramater to this to trigger an optional incremental sync?

    Use Case
    The Azure Automation account has this option as a feature toggle but not something that can be triggered ad-hoc after a full sync outside of Azure Automation. We don't want to use the AutoSync feature as we want to control the upload of runbooks via Azure DevOps pipelines with approvals etc. then trigger a sync job…

    40 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Source control integration  ·  Flag idea as inappropriate…  ·  Admin →

    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

  • Don't see your idea?

Feedback and Knowledge Base