Craig Alvord

@epopisces Have you had a chance to answer the above questions?

@sixeyes Odd... Out of curiosity, is this the result of default sorting (when the table is first opened)? Does manually sorting the column resolve the issue?

@sixeyes As a workaround, you can simply turn off the Natural Sort Order setting. Natural sort order is implemented like this: ```js "43ea54abb79849539b3e6880982b1dce".localeCompare("251540a0dd7541ccadac81d50807a7b0", undefined, { numeric: true }) // Returns...

Can you also share your Storage Explorer app logs? How long does it take for the hang to occur? Can't seem to find them right now, but we have a...

Yeah, that sounds about right. Tokens are normally good for about an hour before they need to be refreshed. So, it definitely sounds like AzCopy is not getting the refreshed...

Yep, error message says the token is expired. So I highly suspect that's why the job is hanging. I'm pretty sure something in AzCopy isn't checking for a refreshed token....

We have no significant updates. The AzCopy team is aware of the issue and are currently looking into it.

@jarkko-siitonen Keep in mind there are two different kinds of SAS: key-based SAS and user-delegated SAS. Storage Explorer supports both. So you do not need to give out List Keys...

@jarkko-siitonen They are actively working on a fix for the issue. They've given us an estimated release date in January. @JasonYeMSFT > For user with contributor role Storage explorer uses...

@SammMoney Correct. As mentioned above, a fix for this depends on an update to AzCopy that we are still waiting for. The earliest we can expect that update is the...