Benjamin Talmard

My feedback

  1. 55 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Web Apps  ·  Flag idea as inappropriate…  ·  Admin →
    Benjamin Talmard supported this idea  · 
  2. 1,426 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    20 comments  ·  Web Apps  ·  Flag idea as inappropriate…  ·  Admin →
    Benjamin Talmard supported this idea  · 
  3. 720 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    46 comments  ·  Web Apps  ·  Flag idea as inappropriate…  ·  Admin →

    .NET Framework 4.8 support is coming to App Service.

    Public Azure cloud deployment will begin in mid-late July 2020 completing by mid-September 2020. For our Sovereign clouds, deployment will begin by mid-late August 2020 and complete by early-October 2020.

    We will update this item periodically to inform you of the deployment progress.

    Benjamin Talmard supported this idea  · 
  4. 37 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    planned  ·  1 comment  ·  Azure Marketplace » Feature Request  ·  Flag idea as inappropriate…  ·  Admin →
    Benjamin Talmard supported this idea  · 
  5. 3,041 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    187 comments  ·  Signup and Billing  ·  Flag idea as inappropriate…  ·  Admin →

    Quick update,

    We have been considering all of the risks and investigating the steps required to ensure we implement this feature with high positive impact and low to no negative impact.

    After this investigation we have decided we will enable Pay-As-You-Go customers the option to configure a spending limit on a Pay-As-You-Go subscription, with appropriate safeguards and measures to prevent both service abuse and production service failure.

    We have not yet finished determining the details of what this feature will look like, nor do we have a timeline for release, but we have heard your voices and have added this feature to our backlog.

    Thanks for your continued feedback,

    -Adam (Azure Billing Team)

    Benjamin Talmard supported this idea  · 
  6. 261 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Stream Analytics  ·  Flag idea as inappropriate…  ·  Admin →
    Benjamin Talmard supported this idea  · 
  7. 249 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    started  ·  7 comments  ·  Networking » Azure Front Door Service  ·  Flag idea as inappropriate…  ·  Admin →
    Benjamin Talmard supported this idea  · 
  8. 294 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    planned  ·  7 comments  ·  Networking » Azure Front Door Service  ·  Flag idea as inappropriate…  ·  Admin →
    Benjamin Talmard supported this idea  · 
  9. 895 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    79 comments  ·  Azure Active Directory » Authentication  ·  Flag idea as inappropriate…  ·  Admin →
    Benjamin Talmard supported this idea  · 
  10. 50 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Azure Kubernetes Service (AKS) » Portal  ·  Flag idea as inappropriate…  ·  Admin →
    Benjamin Talmard supported this idea  · 
  11. 231 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    15 comments  ·  Storage » General  ·  Flag idea as inappropriate…  ·  Admin →
    Benjamin Talmard supported this idea  · 
  12. 133 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    planned  ·  4 comments  ·  Networking » Content Delivery Network  ·  Flag idea as inappropriate…  ·  Admin →
    Benjamin Talmard supported this idea  · 
  13. 109 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    9 comments  ·  Networking » Content Delivery Network  ·  Flag idea as inappropriate…  ·  Admin →
    planned  ·  Anton Kucer [MSFT] responded

    Azure CDN by default ignores Vary header except when it is used with Vary: accept-encoding. This is done as the Vary header can easily cause serious cache bloat issues. Long term we are targeting feature to allow users to easily adjust this default behavior.

    Benjamin Talmard supported this idea  · 
  14. 44 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Networking » Content Delivery Network  ·  Flag idea as inappropriate…  ·  Admin →
    Benjamin Talmard shared this idea  · 
  15. 64 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Stream Analytics  ·  Flag idea as inappropriate…  ·  Admin →
    Benjamin Talmard supported this idea  · 
  16. 362 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    planned  ·  18 comments  ·  Azure Backup » Retention and Storage  ·  Flag idea as inappropriate…  ·  Admin →
    Benjamin Talmard supported this idea  · 
  17. 1,084 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    26 comments  ·  Storage » General  ·  Flag idea as inappropriate…  ·  Admin →

    Thank you for your feedback. We view this ask as a set of related features.

    Soft delete for blobs enables you to save and recover your data where blobs or blob snapshots are deleted. It does not protect against container or account deletion. This feature is currently generally available. You can see the announcement here: https://azure.microsoft.com/en-us/blog/soft-delete-for-azure-storage-blobs-ga/ and the full documentation here: https://docs.microsoft.com/en-us/azure/storage/blobs/storage-blob-soft-delete

    Object versioning will also offer object-level protection, and will offer a few incremental improvements to soft delete. Specifically, it will make recovery of deleted data easier. This feature is planned for the coming year.

    Container soft delete will protect against container-level deletion and modification. This feature is planned for the coming year as well.

    Native support for blob backup will protect against account-level deletion and modification, and is currently on our backlog.

    We will provide updates when they become available. For any further questions, or to discuss your…

    Benjamin Talmard supported this idea  · 
  18. 1,528 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    41 comments  ·  Azure Search » Pricing and Quotas  ·  Flag idea as inappropriate…  ·  Admin →
    Benjamin Talmard supported this idea  · 
  19. 175 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    triaged  ·  4 comments  ·  Networking » Application Gateway  ·  Flag idea as inappropriate…  ·  Admin →
    Benjamin Talmard shared this idea  · 
  20. 165 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    41 comments  ·  Azure portal » Other  ·  Flag idea as inappropriate…  ·  Admin →

    Hey,

    This is something we’re still actively working on. It has a been a big area of investment and it still is moving forward. We keep investing in performance, both from a client and server side perspective.

    We have a few things coming in the near future which should help address some of the initial UI performance issues. We’re also heavily engaged with all of our partners driving a broad effort to improve performance across the portal for all experiences.

    If you have any specific areas which are causing pain please feel free to reach out to me or comment and state if we can contact you, it would be great to understand the common pain points.

    Cheers,
    Sean.

    Benjamin Talmard supported this idea  · 
← Previous 1 3

Feedback and Knowledge Base