Anonymous

My feedback

  1. 4 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  · 
  2. 2 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  · 
  3. 2 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Azure Monitor  ·  Flag idea as inappropriate…  ·  Admin →

    Thanks for the valid suggestion. Your feedback is now open for the user community to upvote & comment on. This allows us to effectively prioritize your request against our existing feature backlog and also gives us insight into the potential impact of implementing the suggested feature.

    Anonymous supported this idea  · 
  4. 2 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 » Runtime  ·  Flag idea as inappropriate…  ·  Admin →
    Anonymous supported this idea  · 
  5. 5 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  · 
  6. 35 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    This is an awesome idea, and we’re exploring a few options to make it a reality.
    However, the 600 connection limit per instance should be enough for most applications if you’re reusing or closing connections. If you truly need 600 open connections you are likely to run into the 10 minute timeout per execution.
    Even after we add this you will still need to be mindful of your connection management.

    Keep the votes coming!
    —Alex

    Anonymous supported this idea  · 
  7. 5 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  SDK and Tools  ·  Flag idea as inappropriate…  ·  Admin →
    Anonymous supported this idea  · 
  8. 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 Functions  ·  Flag idea as inappropriate…  ·  Admin →

    You can do this today by setting the hubName to WEBSITE_SITE_NAME in host.json. It should work in both V1 and V2 of Durable Functions. (NOTE: it should be WEBSITE_SITE_NAME surrounded in percent signs, user voice may not be displaying the percent signs properly) – Anthony

    Anonymous shared 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

    1 comment  ·  Azure Security Center  ·  Flag idea as inappropriate…  ·  Admin →
    Anonymous supported this idea  · 

Feedback and Knowledge Base