Anonymous

My feedback

  1. 1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Service Bus  ·  Flag idea as inappropriate…  ·  Admin →
    Anonymous shared this idea  · 
  2. 21 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    5 comments  ·  Service Bus  ·  Flag idea as inappropriate…  ·  Admin →
    Anonymous supported this idea  · 
  3. 67 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 →
    Anonymous supported this idea  · 
  4. 745 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    Due to various technical limitations, the first iteration of the customer-owned domains functionality will not be available for a few more months. We will provide an update as soon as we can get a more specific ETA.

    If you are looking to use custom domains to use javascript, we are now looking to enable that experience by providing a new (non-customizable) domain. Please look for updates here: https://feedback.azure.com/forums/169401-azure-active-directory/suggestions/15493536-add-support-for-javascript-inside-the-custom-ui-br

    /Parakh

    Anonymous supported this idea  · 
  5. 1,664 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    371 comments  ·  Azure Active Directory » SaaS Applications  ·  Flag idea as inappropriate…  ·  Admin →

    We’re currently evaluating an option that will provide the functionality offered by nested groups, but removes the complexity nested groups adds. We appreciate your patience on this ask and want to ensure we deliver a solution that benefits all of our customers. Below are use cases that we’d like for you to stack rank, with #1 being priority for you. We thank you for the continued comments and feedback.

    Use case A: nested group in a cloud security group inherits apps assignment
    Use case B: nested group in a cloud security group inherits license assignment
    Use case C: nesting groups under Office 365 groups

    Anonymous supported this idea  · 
  6. 1,266 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    76 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?

    Anonymous supported this idea  · 
  7. 1,125 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    unplanned  ·  88 comments  ·  SQL Server » Suggestions  ·  Flag idea as inappropriate…  ·  Admin →
    Anonymous supported this idea  · 
  8. 70 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 →
    Anonymous supported this idea  · 
  9. 90 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 →
    Anonymous supported this idea  · 
  10. 326 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    7 comments  ·  Storage » General  ·  Flag idea as inappropriate…  ·  Admin →
    Anonymous supported this idea  · 
  11. 17 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Cloud Services (Web and Worker Role)  ·  Flag idea as inappropriate…  ·  Admin →
    Anonymous supported this idea  · 
  12. 1,684 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    49 comments  ·  Storage » Tables  ·  Flag idea as inappropriate…  ·  Admin →
    Anonymous supported this idea  · 
  13. 728 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    15 comments  ·  Storage » Tables  ·  Flag idea as inappropriate…  ·  Admin →
    Anonymous supported this idea  · 
  14. 6 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Azure Functions » Feature  ·  Flag idea as inappropriate…  ·  Admin →

    Changing this and clarifying. You can do this today with the Event Grid trigger (e.g. create an event grid trigger and then add subscriptions for each container in a storage account – or many storage accounts – and point to same function). That’s the way that works today and is planned to be the solution for this short term. However leaving this open as I think it was more general to have the Blob and not the Event Grid trigger do this. Keep the votes coming and comment on if Event Grid may not be enough.

    -
    Jeff

    Anonymous supported this idea  · 
  15. 10 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Azure Functions  ·  Flag idea as inappropriate…  ·  Admin →
    Anonymous supported this idea  · 
  16. 43 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Azure Functions » Feature  ·  Flag idea as inappropriate…  ·  Admin →
    Anonymous supported this idea  · 
  17. 20 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Azure Functions  ·  Flag idea as inappropriate…  ·  Admin →
    Anonymous supported this idea  · 
  18. 51 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    4 comments  ·  Azure Functions  ·  Flag idea as inappropriate…  ·  Admin →
    Anonymous supported this idea  · 
  19. 24 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Azure Functions » Feature  ·  Flag idea as inappropriate…  ·  Admin →

    I believe in our latest SDK versions you should be able to use connection strings specific to a single queue / listen-only. These connection strings are stored in app settings and can be updated / rolled without having to modify or redeploy the code. Believe this would be sufficient today? Not sure if anything blocking anymore

    https://docs.microsoft.com/en-us/azure/azure-functions/functions-bindings-service-bus-trigger?tabs=csharp#configuration

    Anonymous supported this idea  · 
  20. 83 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 →

    Moving this work item to unplanned, as it is clear that this request is no for a global throughput limit.

    We do now offer the ability to limit your maximum instances in the Premium plan, which will allow you to avoid swamping downstream resources. https://docs.microsoft.com/en-us/azure/azure-functions/functions-premium-plan#plan-and-sku-settings

    We prioritized that above a max call per X limit, because our only control to limit throughput is to outright deny some number of requests above a threshold.

    Keep the feedback coming!
    Alex
    Azure Functions Team

    Anonymous supported this idea  · 
← Previous 1

Feedback and Knowledge Base