yaegashi

My feedback

  1. 3 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Lab Services  ·  Flag idea as inappropriate…  ·  Admin →
    yaegashi supported this idea  · 
  2. 13 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    3 comments  ·  Lab Services  ·  Flag idea as inappropriate…  ·  Admin →
    yaegashi supported this idea  · 
  3. 1 vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Lab Services » DevTest Labs - Security  ·  Flag idea as inappropriate…  ·  Admin →
    yaegashi shared this idea  · 
  4. 1 vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Lab Services » DevTest Labs - Security  ·  Flag idea as inappropriate…  ·  Admin →
    yaegashi shared this idea  · 
  5. 1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Networking » DNS  ·  Flag idea as inappropriate…  ·  Admin →

    Thanks for the valid suggestion. Your feedback is now open for the user community to upvote which allows us to effectively prioritize your request against our existing feature list and also gives us insight into the potential impact of implementing the suggested feature

    yaegashi shared this idea  · 
  6. 13 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Networking » Virtual Network  ·  Flag idea as inappropriate…  ·  Admin →
    yaegashi commented  · 

    This feature gets more meaningful and important when it comes to VNet peering.

    Currently hosts in VNet still receive DNS suffix via DHCP like rxswwfbgpbpuhmmafhobadrtsc.lx.internal.cloudapp.net which is specific to each VNet they connect to. So there's no easy way for hosts to resolve names of peer hosts in other VNets.

    Using DNS private zones linked to all of VNets and this custom DNS suffix feature will make it much simper.

    yaegashi supported this idea  · 
  7. 291 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    8 comments  ·  Networking » Virtual Network  ·  Flag idea as inappropriate…  ·  Admin →
    yaegashi supported this idea  · 
  8. 6 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Networking » Virtual Network  ·  Flag idea as inappropriate…  ·  Admin →
    yaegashi supported this idea  · 
  9. 5 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  1 comment  ·  Networking » Application Gateway  ·  Flag idea as inappropriate…  ·  Admin →
    yaegashi supported this idea  · 
  10. 6 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Networking » Virtual Network  ·  Flag idea as inappropriate…  ·  Admin →
    yaegashi shared this idea  · 
  11. 3 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Lab Services » DevTest Labs - Virtual Machines  ·  Flag idea as inappropriate…  ·  Admin →
    yaegashi supported this idea  · 
    yaegashi shared this idea  · 
  12. 46 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Networking » DNS  ·  Flag idea as inappropriate…  ·  Admin →
    yaegashi supported this idea  · 
  13. 1 vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Lab Services  ·  Flag idea as inappropriate…  ·  Admin →
    yaegashi shared this idea  · 
  14. 37 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    4 comments  ·  Lab Services  ·  Flag idea as inappropriate…  ·  Admin →
    yaegashi supported this idea  · 
  15. 40 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    13 comments  ·  Lab Services  ·  Flag idea as inappropriate…  ·  Admin →

    Thanks for your feedback! As more further investigate, the DevTest Labs supports VSTS Git and GitHub today. I’ve added this into the backlog. Given different Git repo offers different client for Labs to use and connect to, it’d be helpful if you could share with us which one you want to support first, so that the Labs can support them one by one. Thanks!

    yaegashi commented  · 

    It only supports GitHub or VSTS, and what is more surprising, only private repos! Quite useless and inconvenient. Please implement a generic Git client with generic authentication/transport support using SSH/HTTPS.

    yaegashi supported this idea  · 
  16. 8 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    3 comments  ·  Lab Services  ·  Flag idea as inappropriate…  ·  Admin →
    yaegashi supported this idea  · 
  17. 56 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  2 comments  ·  Networking » Virtual Network  ·  Flag idea as inappropriate…  ·  Admin →
    yaegashi shared this idea  · 

Feedback and Knowledge Base