Chad

My feedback

  1. 20 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    3 comments  ·  Azure Active Directory » B2C  ·  Flag idea as inappropriate…  ·  Admin →
    Chad supported this idea  · 
  2. 1 vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Azure Active Directory » B2C  ·  Flag idea as inappropriate…  ·  Admin →
    Chad shared this idea  · 
  3. 9 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Networking » Web Application Firewall  ·  Flag idea as inappropriate…  ·  Admin →
    Chad shared this idea  · 
  4. 14 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    4 comments  ·  Azure Key Vault » Other  ·  Flag idea as inappropriate…  ·  Admin →
    Chad supported this idea  · 
  5. 170 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    17 comments  ·  Azure Active Directory » B2C  ·  Flag idea as inappropriate…  ·  Admin →
    Chad commented  · 

    We have this automated using the AZ powershell but are plagued with the error: "Updates to converged applications are not allowed in this version."

    Inability to control the Access token version ("accessTokenAcceptedVersion": 2)

    Inability to programmatically grant consent - API doesn't exist (even with a GA service account)

    Chad supported this idea  · 
  6. 209 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    24 comments  ·  Azure Active Directory » B2C  ·  Flag idea as inappropriate…  ·  Admin →

    We are looking to add additional MFA options for Azure AD B2C in the next few months. As part of the investigation, we want to learn more about your requirements. Email your feedback to aadb2cpreview@microsoft.com.

    When you say “support for Microsoft Authenticator”, which feature are you referring to?
    1. The ability to see the codes in the authenticator app
    2. The ability to receive push notifications for MFA

    If both, which do you prefer more?

    Again, please email your feedback to aadb2cpreview@microsoft.com. Feel free to include more details about your scenarios/requirements!

    Chad supported this idea  · 
  7. 47 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Azure Active Directory » B2C  ·  Flag idea as inappropriate…  ·  Admin →
    Chad supported this idea  · 
  8. 76 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    triaged  ·  2 comments  ·  API Management » Security  ·  Flag idea as inappropriate…  ·  Admin →
    Chad commented  · 

    This is especially critical for a native azure solution since you cannot put an App Gateway in front of APIM and still support Mutual Authentication with certificate checks.

    Chad supported this idea  · 
  9. 3 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Azure Key Vault » Other  ·  Flag idea as inappropriate…  ·  Admin →
    Chad supported this idea  · 
  10. 3 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Azure Key Vault » Other  ·  Flag idea as inappropriate…  ·  Admin →
    Chad supported this idea  · 
  11. 32 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    6 comments  ·  Azure Key Vault » Other  ·  Flag idea as inappropriate…  ·  Admin →
    Chad supported this idea  · 
  12. 61 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    started  ·  7 comments  ·  Azure Key Vault  ·  Flag idea as inappropriate…  ·  Admin →
    Chad supported this idea  · 
  13. 79 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    3 comments  ·  Azure Key Vault » Other  ·  Flag idea as inappropriate…  ·  Admin →
    Chad supported this idea  · 
  14. 423 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    planned  ·  11 comments  ·  API Management » Integration  ·  Flag idea as inappropriate…  ·  Admin →
    Chad commented  · 

    An important item to track here would be to support the KeyVault Sign operation for HSM backed Certificates used for backend mutual authentication (AKA Private Key Non Exportable + RSA-HSM ). This would important so Backend gateway "client cert" credentials can be used for mutual authentication in FIPS compliant fashion with the native KeyVault integration.

    Chad supported this idea  · 
  15. 35 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  1 comment  ·  API Management » Defining APIs  ·  Flag idea as inappropriate…  ·  Admin →
    Chad commented  · 

    Also, rather than using the APIM key store, why not allow the use of KeyVault for public certs? This would be especially useful if expiration notices were sent. See: https://feedback.azure.com/forums/906355-azure-key-vault/suggestions/37844218-support-storing-certificates-without-private-keys

    Chad supported this idea  · 
  16. 8 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    planned  ·  0 comments  ·  API Management » Integration  ·  Flag idea as inappropriate…  ·  Admin →
    Chad supported this idea  · 
  17. 13 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  API Management » Lifecycle  ·  Flag idea as inappropriate…  ·  Admin →
    Chad supported this idea  · 
  18. 54 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  API Management » Security  ·  Flag idea as inappropriate…  ·  Admin →
    Chad supported this idea  · 
  19. 95 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Networking » Azure Front Door Service  ·  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

    Chad supported this idea  · 
  20. 997 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    52 comments  ·  Networking » Application Gateway  ·  Flag idea as inappropriate…  ·  Admin →
    Chad commented  · 

    Please consider adding a "x-forwarded-client-cert" style header so we can validate the client certificate in downstream proxies (ex: Azure Api Management)

    Chad supported this idea  · 
← Previous 1 3

Feedback and Knowledge Base