Guang Yang [MSFT]

My feedback

  1. 3 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  ·  Diagnostics and Monitoring  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Guang Yang [MSFT] commented  · 

    Move to virtual machine forum.

  2. 5 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

    2 comments  ·  Virtual Machines » Windows  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Guang Yang [MSFT] commented  · 

    Move to virtual machine forum

  3. 8 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

    1 comment  ·  Virtual Machines » Windows  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Guang Yang [MSFT] commented  · 

    Move to virtual machine forum since this is about having Windows Azure PowerShell available by default in VM.

  4. 19 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  ·  Scripting and Command Line Tools » Powershell  ·  Flag idea as inappropriate…  ·  Admin →

    We understand the needs. Will think about besides expose the cmdlet, what else do we need to make it good for scripting.

    An error occurred while saving the comment
    Guang Yang [MSFT] commented  · 

    Thanks for the feedback, Jeremy. I saw you've also asked this on stackoverflow and you've figured out a solution by yourself. http://stackoverflow.com/questions/11342390/azure-powershell-cmdlets-for-1-7-june-2012-whats-happened-to-get-operationsta. :)

    I think the feedback in general is about providing a better experience for both sync and async operations. Maybe we can think of providing a sync/async switch parameter on each cmdlet which supports these 2 modes. In this way if you want the sync or async behavior, you can just specify it in the cmdlet itself. And for each async cmdlet, we'd provide a way to check the operation status.

    Does this sound like something you'd like to see?

Feedback and Knowledge Base