Bob

My feedback

  1. 356 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    7 comments  ·  Azure Cosmos DB » Management  ·  Flag idea as inappropriate…  ·  Admin →
    Bob supported this idea  · 
  2. 280 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    18 comments  ·  Automation » Integration with other products  ·  Flag idea as inappropriate…  ·  Admin →
    Bob commented  · 

    Any update on this?

  3. 10 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  (General Feedback) » Other  ·  Flag idea as inappropriate…  ·  Admin →
    Bob supported this idea  · 
  4. 9 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    8 comments  ·  Update Management » Deployments  ·  Flag idea as inappropriate…  ·  Admin →
    Bob commented  · 

    I had this same issue and found the root cause for my situation was that I was reporting to two different workspaces one of which that no longer existed. And I seem to remember hearing that your nodes can only point to one workspace if you wish to use Azure Update Management to apply patches to the node.

  5. 83 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    9 comments  ·  Virtual Machines  ·  Flag idea as inappropriate…  ·  Admin →
    Bob supported this idea  · 
  6. 4 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Signup and Billing  ·  Flag idea as inappropriate…  ·  Admin →
    Bob supported this idea  · 
  7. 23 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  (General Feedback) » Availability  ·  Flag idea as inappropriate…  ·  Admin →
    Bob supported this idea  · 
  8. 4 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  (General Feedback) » Availability  ·  Flag idea as inappropriate…  ·  Admin →
    Bob supported this idea  · 
  9. 604 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  Service Bus  ·  Flag idea as inappropriate…  ·  Admin →
    Bob supported this idea  · 
  10. 19 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  SDK and Tools » .NET  ·  Flag idea as inappropriate…  ·  Admin →
    Bob supported this idea  · 
  11. 27 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  SDK and Tools  ·  Flag idea as inappropriate…  ·  Admin →
    under review  ·  Brady Gaster responded

    I know this has been improved since the post was originally sent in, but will check with the team to verify exactly what the limitations are in the latest release.

    Bob supported this idea  · 
  12. 57 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  SDK and Tools  ·  Flag idea as inappropriate…  ·  Admin →
    under review  ·  Brady Gaster responded

    We are currently investigating the opportunities around shipping more features as NuGet packages. We have opened up far more areas as NuGet packages than in previous releases. That said, the idea of creating a NuGet package that contains the emulator is a large effort. As we progress towards this goal or realize that it isn’t possible I’ll update the forum thread.

    For the time being, rest assured we’ve heard this comment, which has been echoed by the larger Windows Azure community. As an Azure developer myself I find merit in this request and feel there is a good chance it could eventually be realized.

    Bob supported this idea  · 
  13. 243 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  SDK and Tools » .NET  ·  Flag idea as inappropriate…  ·  Admin →
    Bob supported this idea  · 
  14. 2 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Automation » Linux support  ·  Flag idea as inappropriate…  ·  Admin →
    Bob supported this idea  · 
  15. 6 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Automation » Linux support  ·  Flag idea as inappropriate…  ·  Admin →
    Bob supported this idea  · 
  16. 441 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  15 comments  ·  Diagnostics and Monitoring  ·  Flag idea as inappropriate…  ·  Admin →
    Bob commented  · 

    How is that review going?

  17. 47 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Diagnostics and Monitoring  ·  Flag idea as inappropriate…  ·  Admin →

    Thank you for the suggestion. This seems like a reasonable way to make sure that you collect all of the diagnostic data from your virtual machines. I have passed this idea on to the WAD team.

  18. 62 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Diagnostics and Monitoring  ·  Flag idea as inappropriate…  ·  Admin →

    This is very good feedback. Today we have separate datasources for what your quotas are (e.g. network, memory), and the metrics that we emit. Ideally, we could bring those two points together to give you a percentage of those metrics.

    Also, once these are exposed, they will automatically be available for autoscale — already today you can use any exposed metric for scaling.

  19. 244 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    17 comments  ·  Diagnostics and Monitoring  ·  Flag idea as inappropriate…  ·  Admin →
  20. 147 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    35 comments  ·  Azure portal » Other  ·  Flag idea as inappropriate…  ·  Admin →

    Hey,

    This is something we’re still actively working on. It has a been a big area of investment and it still is moving forward. We keep investing in performance, both from a client and server side perspective.

    We have a few things coming in the near future which should help address some of the initial UI performance issues. We’re also heavily engaged with all of our partners driving a broad effort to improve performance across the portal for all experiences.

    If you have any specific areas which are causing pain please feel free to reach out to me or comment and state if we can contact you, it would be great to understand the common pain points.

    Cheers,
    Sean.

    Bob commented  · 

    Slow and painful

    Bob supported this idea  · 

Feedback and Knowledge Base