Alexander Viken

My feedback

  1. 426 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    18 comments  ·  Azure Cosmos DB » MongoDB API  ·  Flag idea as inappropriate…  ·  Admin →
    Alexander Viken supported this idea  · 
  2. 60 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  API Management » API management experience  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Alexander Viken commented  · 

    This would be a really useful feature - We have at any given point a number of teams working on different applications - being able to assign a team key, or application key that works regardless of who is logged in as long as they are member of the dev team for the specific application

  3. 341 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    11 comments  ·  Azure Cosmos DB » Gremlin API  ·  Flag idea as inappropriate…  ·  Admin →
    Alexander Viken supported this idea  · 
  4. 152 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  4 comments  ·  API Management » Security  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Alexander Viken commented  · 

    This would really be useful and has been an obstacle we've been struggling with. Another option would be to be able to issue subscription keys to an application, regardless of who is working on it. The application owner could then add/remove team members as they need.

    Alexander Viken supported this idea  · 
  5. 314 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Alexander Viken supported this idea  · 
  6. 64 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    7 comments  ·  Azure Active Directory » B2C  ·  Flag idea as inappropriate…  ·  Admin →
    Alexander Viken supported this idea  · 
  7. 14 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Service Fabric  ·  Flag idea as inappropriate…  ·  Admin →
    Alexander Viken shared this idea  · 
  8. 84 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Service Fabric  ·  Flag idea as inappropriate…  ·  Admin →
    Alexander Viken supported this idea  · 
  9. 1,417 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    We definitely recognize the popularity of this feature, and we discuss it constantly during the planning phases. However there are certain technical limitations in the system that add a large amount of development cost. Because of the cost and the fact that there is a workaround available, other features get prioritized over this one.

    That being said, please keep voting for it. The popularity of the feature does help bring it up and makes us reconsider every time.

    Apologies for the delay.

    /Parakh


    Old message:
    We’re doing some research both on the specifics of this ask as well as what it would take to support this.
    Is the ask here to do the same thing that regular Azure AD does (see: https://blogs.technet.microsoft.com/enterprisemobility/2014/12/18/azure-active-directory-now-with-group-claims-and-application-roles/) or is are there different requirements around this for Azure AD B2C?

    An error occurred while saving the comment
    Alexander Viken commented  · 

    This would be very useful for instance when you create a B2C directory and could split users into ie. "subscribers" or "non-subscribers" groups. and create [Authorize(Roles = "subscribers")] attributes for your viewControllers without a lot of custom code.

    Alexander Viken supported this idea  · 
  10. 1,086 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    14 comments  ·  Storage » Tables  ·  Flag idea as inappropriate…  ·  Admin →
    Alexander Viken supported this idea  · 
  11. 124 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    10 comments  ·  Azure Marketplace » Billing Support  ·  Flag idea as inappropriate…  ·  Admin →
    started  ·  Will Merydith responded

    There are a couple factors that determine availability of Add-ons in a country.
    First, Azure continues to expand which countries are supported in the Store. Currently most of Europe is supported.
    Second, Store partners select which of the available countries from which they wish to allow purchases of their Add-on.

    Which Add-on were you interested in purchasing?

    An error occurred while saving the comment
    Alexander Viken commented  · 

    The use of public cloud and Azure is "booming" in Norway. It's about time customers here could take advantage of the same benefits offered to the rest of Europe (and the world)

    Alexander Viken supported this idea  · 

Feedback and Knowledge Base