Heymega

My feedback

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

    We’ll send you updates on this idea

    1 comment  ·  Azure Container Instances  ·  Flag idea as inappropriate…  ·  Admin →
    Heymega shared this idea  · 
  2. 9 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Azure Container Registry  ·  Flag idea as inappropriate…  ·  Admin →
    Heymega shared this idea  · 
  3. 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 Active Directory » B2C  ·  Flag idea as inappropriate…  ·  Admin →
    Heymega shared this idea  · 
  4. 153 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    10 comments  ·  Azure Functions  ·  Flag idea as inappropriate…  ·  Admin →

    I’ve gotten a few questions about this item recently, so I just wanted to give a more detailed status. We still have this on the backlog; it hasn’t been forgotten. But we don’t have a clear timeline for when we would get to it right now. The “unplanned” status just means that it can’t be tied to a timeline, but we do think this is a valid request that we would like to have in the product.
    - Matthew

    Heymega commented  · 

    Whilst you cannot do this with Azure Functions, you can do it with Azure API Management. If you were to put this API gateway in front of your serverless functions then you could use this to delegate the security.

    I believe you can add custom OAuth2.0 and OpenID Connect providers through Azure API Management.

    A slightly more costly solution but an API gateway is generally a must have anyways.

Feedback and Knowledge Base