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.

Sean Feldman

My feedback

  1. 54 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  2 comments  ·  Storage » Queues  ·  Flag idea as inappropriate…  ·  Admin →
    Sean Feldman supported this idea  · 
  2. 527 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  18 comments  ·  Diagnostics and Monitoring  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Sean Feldman commented  · 

    OpsTera used to offer this as a service.
    While it's not a technical parameter to monitor, it is a crucial business criteria to monitor and alert based on. I'd say even with 0 votes it should be implemented.

    Sean Feldman supported this idea  · 
  3. 1,845 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    185 comments  ·  Azure Resource Manager  ·  Flag idea as inappropriate…  ·  Admin →
    Sean Feldman supported this idea  · 
  4. 135 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    planned  ·  5 comments  ·  API Management » API management experience  ·  Flag idea as inappropriate…  ·  Admin →
    Sean Feldman shared this idea  · 
  5. 30 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    5 comments  ·  Automation » User Experience  ·  Flag idea as inappropriate…  ·  Admin →
    under review  ·  Beth Cooper responded

    You can currently edit the description on runbooks and assets. To do this for runbooks, go to the Configuration page.

    On the names, would the ability to add a friendly name (that you can edit at any time) be sufficient or are you hoping to change the workflow name as well?

    An error occurred while saving the comment
    Sean Feldman commented  · 

    Finally figured out what I'm really after -- logical grouping of Runbooks. When Automation container contains multiple workbooks, they are all presented in a giant list w/o any relation to each other so you have to resort to prefexing runbook (workflow) names which violates the whole the advised practice of runbook naming conventions (verb-noun). If we could get a logical grouping, that would resolve the need in editing details. example:

    [Distaster Recovery]
    provision-web-front-end
    provision-back-end
    update-iis
    restore-backups
    [Test DR]
    provision-web-front-end
    provision-back-end
    update-iis
    restore-backups
    [Scheduled Tasks]
    start-deploymentVM
    stop-deploymentVM
    [etc]
    connect-azure
    delete-storageaccount
    etc...

    This will also allow us to use same names for runbooks under different groups as they are representing similar logical construct, just within different context (example above: production environment DR runbooks vs testing environment DR runbooks).

    Thank you.

    An error occurred while saving the comment
    Sean Feldman commented  · 

    Now that I'm thinking about it -- you're right. Label only/description is enough. But a lot of times you'd like to take what you have and use it as a base (including description/label). Perhaps a better option is to "clone" an existing runbook and use pre-populated values from original runbook?

    Sean Feldman shared this idea  · 

Feedback and Knowledge Base