Martin Francis

My feedback

  1. 761 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    43 comments  ·  Networking » Application Gateway  ·  Flag idea as inappropriate…  ·  Admin →
    Martin Francis commented  · 

    would this cover mutual TLS . Use case would be to only allow traffic from specific clients to be allowed . Not requiring to allow clients based on IP

  2. 10 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Networking » Application Gateway  ·  Flag idea as inappropriate…  ·  Admin →
    Martin Francis shared this idea  · 
  3. 712 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    29 comments  ·  Networking » Application Gateway  ·  Flag idea as inappropriate…  ·  Admin →
    Martin Francis commented  · 

    I completely agree. The lack of wild card support in "hostname" field is a major hindrance.
    Here is what I want to use AG for.
    I want to front end AG for several AKS (Kubernetes clusters). I want to be able to route http(s) traffic to individual AKS clusters depending on wild card in the hostname.
    For instance: I want to
    route *.ecom.constoso.com --> AKS Cluster1
    *.b2b.constoso.com ---> AKS Cluster 2
    currently AG can not do that. So I am having to specify each and every hostname in the Application gateway.
    for instance
    shippingsvc.ecom.contoso.com --> AKS Cluster1
    receivingsvc.ecom.contoso.com --> AKS Cluster1
    orderingsvc.ecom.contoso.com --> AKS Cluster1

    This is painful and not productive.

    Martin Francis supported this idea  · 

Feedback and Knowledge Base