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.

David Schlum

My feedback

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

    0 comments  ·  Azure Monitor » Other  ·  Flag idea as inappropriate…  ·  Admin →
    David Schlum supported this idea  · 
  2. 416 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    David Schlum supported this idea  · 
    An error occurred while saving the comment
    David Schlum commented  · 

    In a world of hosting applications behind Azure Application Gateway by default for WAF rules, at least X-Forward-For should be a default parser value.

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

    under review  ·  4 comments  ·  Azure Active Directory » Domain Services  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    David Schlum commented  · 

    We too find ourselves in a position of wanting Windows Hello for Business on Azure AD DS domain-joined Windows 10 Enterprise machines. We are a consulting company and do a TON of remote desktop connectivity. We were unable to use RDP to Windows 10 machines that were only Azure AD-joined without disabling NLA on the RDP settings. The solution was to domain-join the machines instead but when that happened, even though they are still connected to Azure AD, they will no longer allow me to enable Windows Hello For Business on the device.

    It does seem that the Hybrid AD DS deployment is normally the answer for this outside of Azure AD DS.

    When you say that you can already do Windows Hello For Business directly, can you provide some documentation of how that is supposed to work? I've been searching for hours upon hours and it appears that as soon as you domain join, you lose that ability from Azure AD.

    David Schlum supported this idea  · 
  4. 132 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Azure Search » Crawlers  ·  Flag idea as inappropriate…  ·  Admin →
    David Schlum supported this idea  · 
  5. 437 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    21 comments  ·  Storage » Managed Disk Storage  ·  Flag idea as inappropriate…  ·  Admin →
    David Schlum supported this idea  · 
  6. 1,371 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    31 comments  ·  Networking » DNS  ·  Flag idea as inappropriate…  ·  Admin →
    David Schlum supported this idea  · 
  7. 501 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    25 comments  ·  Networking » Application Gateway  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    David Schlum commented  · 

    Definitely need this. It just so happens that the project I'm working on with a client has exactly 10 unique domains so with http to https redirects and the https listener, I'm able to make it work. However, if the client wants to add even one more site on their multisite CMS, we'll have to spin up a whole new Application Gateway to the tune of $200/month. This seems like an artificial limitation as I've never seen another firewall strictly limit what amounts to reverse proxies behind it. I come from a Microsoft TMG world and it would be unthinkable to only be able to add 20 sites behind one.

    In another month when the client is planning to move another site over to Azure and into their multisite CMS, this becomes a problem. Can support at least punch a number in on the backend to lift this limitation?

    David Schlum supported this idea  · 
  8. 447 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    15 comments  ·  Networking » Virtual Network  ·  Flag idea as inappropriate…  ·  Admin →
    David Schlum supported this idea  · 
  9. 464 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    27 comments  ·  Networking » Application Gateway  ·  Flag idea as inappropriate…  ·  Admin →

    Support for both public and private IP at the same time is available on both V1 and V2 SKU. Customers can host multiple sites behind the same IP and port using multi-site listener today.

    Support for allowing same port on both public and private IP is in the roadmap.

    David Schlum supported this idea  · 
  10. 1,127 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    57 comments  ·  Networking » Application Gateway  ·  Flag idea as inappropriate…  ·  Admin →
    David Schlum supported this idea  · 
    An error occurred while saving the comment
    David Schlum commented  · 

    Just ran into this today. I have a multi-site CMS that supports subdomains for different sites. It would be ideal to be able to configure *.domain.com so that I don't have to set up separate listeners for every site. I also like the idea of at least giving me the option of specifying multiple hosts per listener. AND, why in the world am I only limited to 20 listeners??

Feedback and Knowledge Base