Update: Microsoft will be moving away from UserVoice sites on a product-by-product basis throughout the 2021 calendar year. We will leverage 1st party solutions for customer feedback. Learn more here.

David

My feedback

  1. 2 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Support Feedback  ·  Flag idea as inappropriate…  ·  Admin →
    David shared this idea  · 
  2. 17 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    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 posting this suggestion!

    There are a couple of existing features that may get you most of what you are looking for.

    1. While we do not have a debug mode where you can step through your runbook and see output, we do have an Add-On for the ISE and you can debug your runbooks in the ISE. http://www.powershellgallery.com/packages/AzureAutomationAuthoringToolkit/0.2.3.1

    2. If you are using graphical runbooks, there are settings that you can turn on to show exactly what is happening and what command ran with it by turning on additional logging. Select your graphical runbook > Settings > Logging and Tracing > turn on Verbose and change Trace Level to detailed to get the level of detail you are looking for.

    3. For scripts, you can set your verbose preference to continue (instead of silentlycontinue) in your runbook to debug and write to the verbose stream. $VerbosePreference =…

    David shared this idea  · 

Feedback and Knowledge Base