Joe Levy (Azure Automation Team)

My feedback

  1. 11 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Automation » Integration with other products  ·  Flag idea as inappropriate…  ·  Admin →
    Joe Levy (Azure Automation Team) commented  · 
  2. 68 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    8 comments  ·  Automation » Desired State Configuration  ·  Flag idea as inappropriate…  ·  Admin →
    Joe Levy (Azure Automation Team) commented  · 

    Automation DSC is part of the OMS suite (https://www.microsoft.com/en-us/server-cloud/operations-management-suite/pricing.aspx) and provides this functionality (https://azure.microsoft.com/en-us/documentation/articles/automation-dsc-overview/).

    Can folks please comment as to the gaps in Automation DSC preventing this from being marked 'completed,' in their view?

  3. 3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Automation » Other  ·  Flag idea as inappropriate…  ·  Admin →
    Joe Levy (Azure Automation Team) shared this idea  · 
  4. 19 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Automation » User Experience  ·  Flag idea as inappropriate…  ·  Admin →
    under review  ·  Beth Cooper responded

    Thanks for this suggestion. Yes, as you mentioned & Joe explained this is a known issue in SMA and Azure Automation, but there are workarounds now.
    We can use this request to track making connection types mutable.

    Joe Levy (Azure Automation Team) commented  · 

    Thanks for the feedback. Connection types are immutable. Right now you need to either change the name of the connection type when you import a module, or you must delete the old version of the connection type before importing the module. For the latter, see https://t.co/FjMKwJ1cXb

  5. 6 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    planned  ·  4 comments  ·  Automation » Debugging and troubleshooting  ·  Flag idea as inappropriate…  ·  Admin →
    Joe Levy (Azure Automation Team) commented  · 
    Joe Levy (Azure Automation Team) commented  · 

    You can enable verbose streams in textual test jobs today. See https://azure.microsoft.com/blog/2014/09/17/azure-automation-controlling-runbook-streams-for-testing-and-troubleshooting/ for more details.

  6. 24 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  1 comment  ·  Automation » User Experience  ·  Flag idea as inappropriate…  ·  Admin →
    Joe Levy (Azure Automation Team) commented  · 

    Related to this, if an error (not an exception) is hit in the runbook, the runbook will still complete successfully, and show "Completed" status, but may not have done what it is supposed to do. The dashboard and job status page will not show this as a suspended or failed runbook, since no exception was hit. There should maybe be another category on the dashboard page for runbooks that "completed with errors" so the user is aware that these jobs may need to be looked at.

    Joe Levy (Azure Automation Team) shared this idea  · 

Feedback and Knowledge Base