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.

Moroney, Ian

My feedback

  1. 15 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Networking » Azure Front Door Service  ·  Flag idea as inappropriate…  ·  Admin →
    Moroney, Ian shared this idea  · 
  2. 24 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Web Apps  ·  Flag idea as inappropriate…  ·  Admin →
    Moroney, Ian supported this idea  · 
  3. 354 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    10 comments  ·  Networking » Azure Front Door Service  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Moroney, Ian commented  · 

    Indirect cname is the only way for us right now to use front door for one of our clients because azurefd.net does not support DNSSEC.
    We attempted to cname to our domain which does support it, to azure front door and the traffic wasn't routed due to this issue.

    If DNSSEC isn't going to be supported by azurefd.net, we at least need the ability to use indirect cnames.

    Moroney, Ian supported this idea  · 
  4. 6,072 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    271 comments  ·  Networking » DNS  ·  Flag idea as inappropriate…  ·  Admin →
    Moroney, Ian supported this idea  · 
  5. 7 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

    2 comments  ·  Azure Active Directory » Domain Services  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Moroney, Ian commented  · 

    Just encountered this issue when trying to configure LDAPS.
    Our security policy insists that we use AES256-SHA1 encryption and not 3DES, so I exported it in that format.
    Little did I know that LDAPS for AADDS does not support it.
    Had to re-export the PFX in 3DES in order for LDAPS setup to complete.

    Please support this feature!

    Moroney, Ian supported this idea  · 
  6. 3 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  ·  Cost Management » Reporting  ·  Flag idea as inappropriate…  ·  Admin →
    Moroney, Ian supported this idea  · 
  7. 3 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 Active Directory » Domain Services  ·  Flag idea as inappropriate…  ·  Admin →
    Moroney, Ian shared this idea  · 

Feedback and Knowledge Base