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. Webhooks ARM Template

    Webhooks from ARM Template still don't work.
    I've seen the schema you're providing: https://docs.microsoft.com/en-us/azure/templates/microsoft.automation/automationaccounts/webhooks
    The PowerShell commandlets first request to generate a token before it is apply in the template.
    When I run the ARM Template with your schema I cannot provide the URI and i get the error: "Invalid uri"

    I know it's a duplicate of https://feedback.azure.com/forums/246290-automation/suggestions/13227531-webhooks-arm-template
    but you've closed the item and it is still not working.

    132 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    triaged  ·  9 comments  ·  Webhooks  ·  Flag idea as inappropriate…  ·  Admin →
  2. WebHook Job Monitoring

    Allow people to use the same WebHook Url used for triggering a runbook for querying job status.
    Instead of doing a HTTP POST (used for triggering) you could allow a HTTP GET with the JobId as parameter. This would be a lightweight alternative for consuming runbook results no matter client and platform.
    Note: Using the same url means same access token which leads to monitoring being possible for the lifetime of the access token.

    71 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Webhooks  ·  Flag idea as inappropriate…  ·  Admin →
  3. 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.

    46 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  Webhooks  ·  Flag idea as inappropriate…  ·  Admin →
  4. 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 →
  5. Azure automation webhook to subscribe to Microsoft Graph subscription

    Would like to be able to have an Azure automation webhook subscribe to a Microsoft Graph subscription. Not able to do subscription validation because the Azure automation webhook endpoints does not send a response to validate the subscription.

    "The notification endpoint must send a 200 response with the value of <token> as its body and a content type of text/plain, as shown below, within 10 seconds otherwise the creation request will be discarded."

    POST https://webhook.azurewebsites.net/api/send/myNotifyClient?validationToken=<token>

    Response should be:

    HTTP/1.1 200 OK
    Content-type: text/plain
    Content-length: 7
    <token>

    Getting this error in Graph:

    {

    &quot;error&quot;: {
    
    &quot;code&quot;: &quot;InvalidRequest&quot;,
    &quot;message&quot;: &quot;Subscription validation
    13 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Webhooks  ·  Flag idea as inappropriate…  ·  Admin →
  6. Add Authentication Key to Webhooks for secuirity.

    Automation webhooks can be called without any sort of authentication.

    If there was an option on each runbook for a key (Azure generated or user input), that would be great for security.

    We have to consider that anyone in the world can attempt to run our webhooks, and we add a significant amount of verification to ensure the webhook was executed it was from a legitimate source.

    9 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Webhooks  ·  Flag idea as inappropriate…  ·  Admin →
  7. Python runbooks parameter WEBHOOKDATA

    The python demo for runbook parameters it's [too simple.](https://github.com/Diastro/AzureAutomation-PythonExamples/blob/master/Parameters/parameters.py)

    Ideally, we would parse the WEBHOOKDATA parameter, but i don't know how to parse the WEBHOOKDATA back to a python dict.
    json.load(sys.argv[1]) won't work

    5 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 →
  8. Webhook lists limited to 100 entries

    Webhook lists display only the first 100 entries. Please change the webhook list control to unlimited length. We need more than 100 webhooks and can only manage those beyond 100 via PowerShell which is a little too complicated for some colleagues.

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Webhooks  ·  Flag idea as inappropriate…  ·  Admin →
  9. Support translating WebHookData to parameters without a wrapping runbook

    Currently I need to either create a wrapper runbook to translate the WebHookData parameter, or add the param and a bunch of translation code to each runbook I want to expose via webhook.

    Instead, it would be awesome to be able to define a webhook without having to modify the existing runbook or add a new wrapper.

    Even if this requires custom PS, that would be fine (if not ideal), as long as it can be added as part of the definition of the webhook itself.

    So, for instance, on the Configure Parameters blade, provide a multiline textbox to enter…

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Webhooks  ·  Flag idea as inappropriate…  ·  Admin →
  10. door de batterijen te vervangen

    je kan door een batterij 2 lijnen connecteren maar ik weet niet hoe
    ah wacht ik denk dat ik me wijsmaak dat ik wel weet hoe

    1 vote
    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 →
  11. Ability to manually enter the webhook expiry date

    Currently we can only specify the expiry date by picking a date from the calendar. It would be nice if we could manually enter the year/month/day of the expiry date without using the calendar.

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Webhooks  ·  Flag idea as inappropriate…  ·  Admin →
    under review  ·  Beth Cooper responded

    Thanks for this suggestion. Is there a reason that you don’t like the date picker?

  • Don't see your idea?

Feedback and Knowledge Base