spm

My feedback

  1. 42 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  4 comments  ·  API Management » Policies  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    spm commented  · 

    This seems to be under review since 2016, does APIM support multipart/form-data handling via. policy expression?

  2. 3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  API Management » Policies  ·  Flag idea as inappropriate…  ·  Admin →
    spm shared this idea  · 
  3. 168 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  4 comments  ·  API Management » Policies  ·  Flag idea as inappropriate…  ·  Admin →
    spm supported this idea  · 
    An error occurred while saving the comment
    spm commented  · 

    Code re-usability is going to be critical feature to have a maintainable 'Api Management' implementation, i see the existing version does not support such a feature, i have explored using C# anonymous functions (Action/Func), and this too is not supported. I understand it is feasible to leverage Azure functions to accomplish some of this, but this definitely will add latency. Hoping re-usability will be incorporated in the future.

  4. 241 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    planned  ·  28 comments  ·  Azure Governance » Azure Policy  ·  Flag idea as inappropriate…  ·  Admin →
    spm supported this idea  · 
    An error occurred while saving the comment
    spm commented  · 

    One of the standard practices to name a resource in Azure is to use the 'environment' aspect. For example: to name a resourceGroup in the dev environment the suggested pattern will be <service short name>-<environment>-rg i.e., 'contoso-dev-rg'. This pattern is also recommended by Microsoft, however, using the existing Azure like/match functions it is not possible to easily validate this format in policies. A regex support will be essential to have any meaningful policy implementation for naming resources in Azure. Could you please update, if this is under consideration to implement, if so, timelines? Thanks.

Feedback and Knowledge Base