Networking

The Networking forum covers all aspects of Networking in Azure, including endpoints, load-balancing, network security, DNS, Traffic Manager, virtual networks, and external connectivity.

Virtual Network:

  • Service overview

  • Technical documentation

  • Pricing details

  • Traffic Manager:

  • Service overview

  • Technical documentation

  • Pricing details

  • Network Watcher:

  • Service overview

  • Technical documentation

  • Pricing details

  • If you have any feedback on any aspect of Azure relating to Networking, we’d love to hear it.

    • Hot ideas
    • Top ideas
    • New ideas
    • My feedback
    1. Allow Traffic Manager Endpoint monitor setting to support complex scenario like authentication

      Traffic Manager can be used to redirect traffic to REST APIs that are protected by some kind of authentication (e.g. Basic or OAuth).

      Please allow more complex "Endpoint monitor setting" to be able to ping those endpoints (e.g. Allow to make POST request, add http headers or VS web test)

      2 votes
      Vote
      Sign in
      (thinking…)
      Sign in with: Microsoft
      Signed in as (Sign out)
      You have left! (?) (thinking…)
      0 comments  ·  DNS  ·  Flag idea as inappropriate…  ·  Admin →
    2. Export private DNS zones

      Please extend the import/export of DNS zones also to private DNS zones. At the moment only import/export is possible with regular DNS as stated here:
      https://docs.microsoft.com/bs-latn-ba/azure/dns/dns-import-export

      Import/export of private zones via CLI/powershell/Python SDK would be also helpful.

      1 vote
      Vote
      Sign in
      (thinking…)
      Sign in with: Microsoft
      Signed in as (Sign out)
      You have left! (?) (thinking…)
      0 comments  ·  DNS  ·  Flag idea as inappropriate…  ·  Admin →
    3. Need DNS logs

      I cannot believe this has not been requested before. We need access to logs in order to understand why there are sudden spikes in traffic. When hacker perform reconnaissance, they cruise through the DNS space looking for targets like admin.domain .com.

      Microsoft will not release logs that we pay for. Incredible.

      1 vote
      Vote
      Sign in
      (thinking…)
      Sign in with: Microsoft
      Signed in as (Sign out)
      You have left! (?) (thinking…)
      0 comments  ·  DNS  ·  Flag idea as inappropriate…  ·  Admin →
    4. Traffic analytics error reporting IP vs NIC

      We have several app-ways in the same subnet.
      Traffic analytics is display a DestIPs which does not correspond with the displayed NICs (it belongs to a different app-way).

      1 vote
      Vote
      Sign in
      (thinking…)
      Sign in with: Microsoft
      Signed in as (Sign out)
      You have left! (?) (thinking…)
      planned  ·  1 comment  ·  DNS  ·  Flag idea as inappropriate…  ·  Admin →
    5. DNS BUG! servers should be located in more than one AS

      Go to https://zonemaster.net/domain_check

      Azure.com as example: https://zonemaster.net/result/6d710df34ffad843

      Getting warnings

      18 CONNECTIVITY WARNING All nameservers in the delegation have IPv4 addresses in the same AS (8068).
      19 CONNECTIVITY WARNING All nameservers in the delegation have IPv6 addresses in the same AS (8075).

      In most cases this is not an issue, however this should be fixed, and while at it, integrate the zonemaster checks into the Azure UI.

      1 vote
      Vote
      Sign in
      (thinking…)
      Sign in with: Microsoft
      Signed in as (Sign out)
      You have left! (?) (thinking…)
      0 comments  ·  DNS  ·  Flag idea as inappropriate…  ·  Admin →
    6. Add support for additional expected status codes in Azure Traffic Manager

      Please consider adding support for additional expected status codes in Azure Traffic Manager. As it stands today, only status codes of 200-299 or 301 are supported. However, my monitored workload is expected to return a 401. As such, I'm forced to use the less accurate TCP method for monitoring my endpoints.

      1 vote
      Vote
      Sign in
      (thinking…)
      Sign in with: Microsoft
      Signed in as (Sign out)
      You have left! (?) (thinking…)
      0 comments  ·  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

    7. Is adding external endpoints via IP address available instead of FQDN? i don't think it is? can some one clarify it please..

      On Azure Traffic Manager, is external endpoints addition via IP address available instead of FQDN? i don't think it is yet? can some one clarify it please..

      1 vote
      Vote
      Sign in
      (thinking…)
      Sign in with: Microsoft
      Signed in as (Sign out)
      You have left! (?) (thinking…)
      planned  ·  0 comments  ·  DNS  ·  Flag idea as inappropriate…  ·  Admin →
    8. Azure Services consistent domain ownership verification

      It would be nice to have a single method for verifying domain ownership prior to DNS change.

      E.g. App Services uses "awverify TXT <appname>.azurewebsites.net" and Front Door uses "afdverify.www.contoso.com CNAME afdverify.contoso.azurefd.net"

      Similar to O365, we should be able to specify a single TXT record (maybe a hashed tenant ID) that indicates domain ownership.

      Thanks.

      1 vote
      Vote
      Sign in
      (thinking…)
      Sign in with: Microsoft
      Signed in as (Sign out)
      You have left! (?) (thinking…)
      triaged  ·  0 comments  ·  DNS  ·  Flag idea as inappropriate…  ·  Admin →
    9. DNS Services

      Hello Support,
      we request you if there DNS Services we can use for our internal AD instead of using DNS of ISP or any other third party like Google or OpenDNS to lookup, is there anything similar to this not Azure AD services.

      1 vote
      Vote
      Sign in
      (thinking…)
      Sign in with: Microsoft
      Signed in as (Sign out)
      You have left! (?) (thinking…)
      triaged  ·  0 comments  ·  DNS  ·  Flag idea as inappropriate…  ·  Admin →
    10. Allow single top level domain for private zone name

      Allow to create private DNS zone like .lan. Currently zone names require 2 or more labels (foo.lan).

      1 vote
      Vote
      Sign in
      (thinking…)
      Sign in with: Microsoft
      Signed in as (Sign out)
      You have left! (?) (thinking…)
      0 comments  ·  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

    1 2 3 4 6 Next →
    • Don't see your idea?

    Feedback and Knowledge Base