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.

aidman_nz

My feedback

  1. 220 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

    50 comments  ·  Azure Cloud Shell » General  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    aidman_nz commented  · 

    I find cloudshell shuts down frequently due to 'inactivity' while I have a powershell script or terraform deployment running even when it has been running for <10mins and not for 20 mins like the timeout threshold is supposed to be. Please fix this asap as it needs to be robust for long running tasks and not just for running quick one off commands.

    aidman_nz supported this idea  · 
  2. 7 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  ·  Azure Cloud Shell » General  ·  Flag idea as inappropriate…  ·  Admin →
    aidman_nz supported this idea  · 
    An error occurred while saving the comment
    aidman_nz commented  · 

    We need this too, we deploy resources via Terraform using the Cloud Shell and as soon as you enable the firewall for selected networks you can no longer manage the resource anymore from Cloud Shell. It is impossible to create an exception manually for this as Cloud Shell uses a private IP address and private IPs can't be added as exceptions. There needs to be an exception for Cloud Shell to be designated as a trusted Azure Service.

  3. 87 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    triaged  ·  4 comments  ·  Networking » Load Balancer  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    aidman_nz commented  · 

    This behavior is completely unexpected and stumped us for days! Please resolve asap, it is obvious in enterprises that you would use Standard Internal Load balancers as you want it to be highly available across AZs to load balance for VMs that are across AZs. But you still want your VMs that don't have public ips to be able to talk to azure services and the public internet the same as they can if they aren't attached to the load balancer.

    aidman_nz supported this idea  · 
  4. 1 vote

    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

    0 comments  ·  Azure Security Center  ·  Flag idea as inappropriate…  ·  Admin →
    aidman_nz shared this idea  · 

Feedback and Knowledge Base