Tom Harren

My feedback

  1. 19 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  (General Feedback) » azure.microsoft.com  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Tom Harren commented  · 

    Agreed! The 'Diagnostic Settings' export tools and/or export Log Analytics would be most helpful for making scaling and AppService reshuffling decisions.

    Tom Harren supported this idea  · 
  2. 64 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    7 comments  ·  (General Feedback) » Availability  ·  Flag idea as inappropriate…  ·  Admin →

    Apologies for the delay in updating this item. We are aware of the challenges around this limit and are actively working to be able to raise it; however, we don’t have an ETA yet.

    We will update this item as we get more clarity on the timeline. Stay tuned and thank you for the understanding.

    -Arturo Lucatero
    @ArLucaID

    An error occurred while saving the comment
    Tom Harren commented  · 

    This limit seems artificial and low. If there are even 10 assignments per resource, that means we only get 200 resources per subscription!? I'm not what the reasoning is for this constraint, but will become a problem for us soon.

    Tom Harren supported this idea  · 
  3. 220 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    under review  ·  Azure AD Team responded

    Thank you for the feedback! This is in the backlog and we are looking into this. We don’t have an ETA yet, but we will share once we have one. Please keep voting if this feature matters to you.

    Tom Harren supported this idea  · 

Feedback and Knowledge Base