David Schlum

My feedback

  1. 226 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    10 comments  ·  Storage » Managed Disk Storage  ·  Flag idea as inappropriate…  ·  Admin →
    David Schlum supported this idea  · 
  2. 667 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    12 comments  ·  Networking » DNS  ·  Flag idea as inappropriate…  ·  Admin →
    David Schlum supported this idea  · 
  3. 369 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    22 comments  ·  Networking » Application Gateway  ·  Flag idea as inappropriate…  ·  Admin →

    We have raised the limit to 100 recently. We are regularly reviewing the limits and will continue to look for opportunities to raise the limits even further. If you have scenarios requiring limits higher than what is supported, please add your scenario details here (if you are comfortable with that) or raise an issue with Azure support and we will get back to you.

    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  · 
  4. 309 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    9 comments  ·  Networking » Virtual Network  ·  Flag idea as inappropriate…  ·  Admin →
    David Schlum supported this idea  · 
  5. 304 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    10 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  · 
  6. 789 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    30 comments  ·  Networking » Application Gateway  ·  Flag idea as inappropriate…  ·  Admin →
    David Schlum supported this idea  · 
    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??

  7. 3,049 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    125 comments  ·  Storage » Files  ·  Flag idea as inappropriate…  ·  Admin →

    Hi everyone,

    We recently announce the General Availability of Azure Active Directory Domain Services (Azure AD DS) authentication for Azure Files! By enabling integration with Azure AD DS, you can mount your Azure file share over SMB using Azure AD credentials from Azure AD DS domain joined Windows VMs with NTFS ACLs enforced. For more details, please refer to our blog post:http://aka.ms/azure-file-aadds-authentication-ga-blog.

    A part of the GA announcement, we shared the upcoming plan to extend the authentication support to Active Directory (AD) either hosted on-premises or in cloud. If you need an Azure Files solution with AD authentication today, you can consider installing Azure File Sync (AFS) on your Windows File Servers where AD integration is fully supported.

    If you are interested to hear future updates on Azure Files Active Directory Authentication, please complete this sign-up survey:https://aka.ms/AzureFilesADAuthPreviewSurvey.

    Thanks,
    Azure Files Team

    David Schlum supported this idea  · 

Feedback and Knowledge Base