Jeff

My feedback

  1. 714 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.

    An error occurred while saving the comment
    Jeff commented  · 

    OK...

    so let me answer the question of why this is a big deal:

    https://docs.microsoft.com/en-us/dotnet/api/system.web.httpcookie.samesite?view=netframework-4.8&viewFallbackFrom=netframework-4.7

    Next month, Google is going to flip a switch and the default behavior for Chrome is going to change with respect to this cookie property.

    Initially, I just went ahead and upgraded all of our code to 4.8, and locally, the SameSite property on the cookie was working great. But then... I published to Azure... and the SameSite property disappeared (i.e. Azure is not supporting 4.8). I then think... ok... they're support 4.7, so let me switch to 4.7.2. which is where this new SameSite property was introduced, compile, publish to Azure... and... :( it's still not being emitted. Which tells me that Azure apparently doesn't even support 4.7.2.

    This is going to be REAL bad for us since we have a site that is completely dependent on cross-domain frames.
    (I went ahead and turned in a high-severity ticket with Microsoft, so we'll see if this continues to languish)

  2. 991 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    32 comments  ·  Storage » Blobs  ·  Flag idea as inappropriate…  ·  Admin →

    Our apologies for not updating this ask earlier. Renaming Blobs is on our backlog, but is unlikely to be released in the coming year. Today, you can use the “Copy Blob” API as a workaround.

    Using the Azure Files service you can address Azure Storage like a network share using the SMB2.1 protocol.  This enables usage of normal Windows API’s to rename files and directories.  You can get started with the Files service by visiting https://docs.microsoft.com/en-us/azure/storage/storage-dotnet-how-to-use-files.

    For any further questions, or to discuss your specific scenario, send us an email at azurestoragefeedback@microsoft.com.

    An error occurred while saving the comment
    Jeff commented  · 

    This is where we would be hoping for a .Rename method.

    An error occurred while saving the comment
    Jeff commented  · 

    You guys still need to write an in-place rename method (iislog.csv --> iislog.csv.processed). You already know this, but just figured I would remind you. It's clearly more complicated on the backend than we understand, which probably explains why you push the processing (copy/delete) down to us.

    And btw... Microsoft.Azure.Storage.File.CloudFile doesn't have a rename method either.

    But using files doesn't work for me because you don't have File event triggers in Data Factories. The only event I can develop against is Blob events (create and delete).

    Plus... most network administrators in most companies these days love to run around blocking SMB ports with their firewalls, so Microsoft.Azure.Storage. API (talking to the webservices on the back end) is the only option available to me.

    Jeff supported this idea  · 
  3. 1,638 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    170 comments  ·  Azure Resource Manager  ·  Flag idea as inappropriate…  ·  Admin →
    Jeff supported this idea  · 
    An error occurred while saving the comment
    Jeff commented  · 

    Renaming resources should *not* be handled like a resource move. Those are 2 different operations. The GUID for the resource group should rename the same, all we want to do is rename (assuming the name we want to change to is available and valid). After building out some sites and environments, names like "Default-Web-WestUS" no longer works for us, but we basically have to tear everything down and put it back together again. It should not be so.

Feedback and Knowledge Base