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. ParentJobId not showing in Hybrid Worker scenario

    Recently the Azure Automation team released the functionality to be able to get the job Id of the current running Automation job. (https://feedback.azure.com/forums/246290-azure-automation/suggestions/10300698-power-shell-runbook-add-support-to-get-own-job-i)
    This works fine by using the command: $PsPrivateMetaData.JobId.Guid in a normal PowerShell runbook although if you use a hybrid worker scenario the earlier mentioned command gives no output.

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

    Update: our team is currently working on getting this fixed.

  2. Graphical Runbook: Input that had a default but afterwards is set to mandatory still have default value in tester

    Steps


    1. Create input at set a default value

    2. Set the input to be mandatory, which hides the default value textbox.

    3. test the runbook in the tester, and the default value will still be inserted in to the input textbox

    0 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    started  ·  2 comments  ·  Bug  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

Feedback and Knowledge Base