Trying to use Microsoft Azure Storage Explorer (version 1.4.2) to access storage accounts in Azure Government. I can connect to the subscription and enumerate the storage accounts but when I click on a storage account, it won't enumerate the containers in the storage account and many of the properties of the storage account show as "Error loading property". I have tried two different Azure Government subscriptions and accessing them from two different computers.
Not really a solution to your problem but you may want to create an issue here:
https://github.com/Microsoft/AzureStorageExplorer/issues.
Storage Explorer team is actively engaged on the issues there.
Related
My Azure resources only show Functions App and nothing else. I can't see Storage Accounts, Cosmos DB, or anything else but Functions. I have tried signing out, restarting, and signing back in but I'm not able to resolve it and get the rest of the resources to show. I have 2 Storage Accounts and 1 Cosmos DB account but I cannot get them to show. I have all of the Azure extensions installed in VS Code such as Azure Account, Azure Storage, Azure Databases and many more.
Here is what I can see:
My VS Code Resources
Here is what I should be able to see: Azure with all resources
or I think it should also look like this which I saw in a youtube video: Azure with all resources 2
Any help would be appreciated since I'm not sure what else to do.
Also, I'm not certain but I think this issue is causing me to have uploading issues anytime I try uploading my website files to Azure Storage because I get the following error:
“Could not find $web blob container for storage account "(name of my account)" ; When I checked in Azure my storage account, it had under "Container": $web.
Try to use the Visual Studio Code of version 1.67 and click on the resources in VS Code menu then sign in with your azure credentials.
Recheck the below mentioned point:
After sign in into VSCode, select the appropriate Subscription under resources in which you have all the resources like Storage Accounts, Cosmos DB and other resources...
I am wondering if the Azure Storage explorer can be used to access the files in Azure NetApp. If not, what is the storage explorer-like solution for Azure NetApp?
No storage explorer cannot be used to access NetApp files. I highly doubt if there is an explorer available as of now unless you use some commands and create your own onw
Where can I find the file share associated with the App Service?
I can view the files from Kudo console, but I don't see the share on my Storage Account using either the portal or Storage Explorer.
While the files are backed by a storage account, it is in a platform account and not one of your own accounts. That's why you cannot see the files in storage explorer. It's also why you can create a Web App without specifying a storage account.
One exception is for Azure Functions on Consumption plan, where the user storage account is used, and you'd see the Azure Files in storage explorer.
After generating SAS for an Azure Storage Container, when using it in Cloudberry or Azure Storage explorer tool, a base64 error is shown.
My question is can a Shared Access Signature for a container be used in client tools like Cloudberry or Azure Storage explorer?
No. AFAIK, all the client tools today support managing storage accounts using account name/key with the exception of ClumsyLeaf CloudXplorer. You can give that a try.
In 2020, SAS connection is also supported by Microsoft Azure Storage Explorer.
If anyone trying to solve 'ACL on azure storage' in your company without having full Azure AD - for now you're just going to have to get inventive with managing those connection keys, but this platform keeps evolving so keep an eye on the space.
I'm using Azure Storage Explorer to connect to storage accounts that I've created by hand on Azure. However when I go to browse the storage account that was created by Azure when I created a Media Services account, I'm unable to connect to it.
I'm using blob.core.windows.net as the storage endpoint domain, and setting the storage account name and storage account key to be the same as Azure has defined it in the dashboard, but attempts to connect (with or without HTTPS) result in a 502-Bad Gateway HTTP error.
I'd like an easy way to browse all media files I've created without having to write special code. Has anyone been able to get this to work?
All storage accounts regardless the way they are being created are browsable with Storage Explorer!
For such storage accounts, created when you Create Media Services, you have to use the Storage Account Name and Storage Account Key, but not the Media Service Account Name and Media Service Account Key! You will not be able to access Storage service with Media Key and vice-versa.
When you create a Media Services account, one/multiple storage accounts could be attached to a particular media services account. Let's say your account name is "MediaStorage123". I believe you need to pass the following data to storage explorer:
Account name/key: this can be found in the bottom of your storage account page in Azure portal: press Manage Key button you will see the data.
storage endpoint domain: Not sure why you need this, but if so, you can see the information in Dashboard of your media services account: https://xxx.blob.core.windows.net/.
Hope this helps.
Just for the record, In my case (with the use of proxy) I had do install a previous version of the Azure Storage Explorer