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.
Related
In Azure I have 2 load balanced VMs with an IIS shared config. These are linked to a premium storage account. All up and running. I have persisted the premium fileshare to both VMs as a drive (S).
The wwwroot is on the storage account, along with the IIS config files.
The app pool is set up as the storage account password so I have access the the share.
All good up to this point.
My issue is that the app also needs to see data on another fileshare. (general fileshare, not premium). This will be used for storage and Archive.
The problem is that the IIS app pool is configured with the creds for the premium storage and fails when trying to also use the general storage.
Can this be done?
Is there a way to link to both fileshares in IIS or should I be looking somewhere else?
Thanks
Colin
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.
Is this even possible? I have a couple web apps and a couple of Azure Functions running under the same App Service Plan. I'd like to (ideally) have them use a specific Storage plan, so I can keep everything in one place. I envision them in different containers under the same plan.
If that's not possible...then where are the files? Are they on the storage that's built into the App Service Plan itself? If so, can I connect to this somehow, so I can manage the files through something like Storage Explorer?
Today when playing with the Azure Az Powershell tool I found I was able to provision a Function App without a Azure Storage back-end. This cannot be done via the UI. An easy way to provision a Function App with a storage account backend is by leveraging the Azure UI for provisioning.
When a Function App is provisioned via command line, the bits seem to be stored within the function app itself. There is an FTP URL given if you download the publish profile. The files can be read and written to using an FTP tool like WinSCP (as alternative to Kudu)
I'd like to (ideally) have them use a specific Storage plan, so I can keep everything in one place. I envision them in different containers under the same plan. If that's not possible...then where are the files?
Every Azure Web App has a home directory stored/backed by Azure Storage. More detail info please refer to Azure WebApp sandbox. It is owned by Azure WebApp Service, we are not able to choose Azure Storage to setup WebApp by ourselves currently. But we could config storage account for Azure WebApp Diagnostic logs.
Are they on the storage that's built into the App Service Plan itself? If so, can I connect to this somehow, so I can manage the files through something like Storage Explorer?
Different WebApp Service Plan has different volume of the storage. We could use Kudu tool (https://yoursite.scm.azurewebsites.net) to manage the files. More detail info about Kudu please refer to the document.
Update:
We could access the home directory with the Kudu tool. More details please refer to the snapshoot
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
My Web Role is on StorageAccount1 and my Azure Storage Table on StorageAccountB.
My Web Role performs operations (inserts, updates, queries) on the Storage Table.
Both of these Storage Accounts are in the SAME Affinity Group.
Will performance be better if my Web Role and Storage Table are in the same Storage Account?
You are probably confused by the "Publish" window in Visual Studio. The "Publish" window allows you to choose some info on how your application is deployed, like the Cloud Service but also the Storage Account. When you choose a storage account it doesn't mean your application will be stored in that storage account, it only means that the service package (the package which contains your application) will be uploaded there. Once the package is uploaded the Fabric Controller will take it and deploy it to your Cloud Service.
Besides that it's still a good idea to deploy your Cloud Service (Web Role) in the same affinity group as your Storage Account. By choosing the same affinity group Windows Azure will try to physically group your Cloud Services and Storage Accounts to minimize the network overhead.