I was wondering if it is possible to mount a drive in Windows that is from an Azure file share, and the user only has access to that specific share. I would think creating a SAS signature for the share could work, but I have only seen examples of mounting a share using the Storage account key (and that provides access to all shares)
Note: To mount an Azure file share, you will need the primary (or secondary) storage key. SAS keys are not currently supported for mounting.
To use an Azure file share with Windows, you must either mount it, which means assigning it a drive letter or mount point path, or access it via its UNC path.
For more details, refer "Using an Azure file share with Windows".
Related
I am designing a web application and it needs to be in the Azure web app. The app is focused on managing files, so it needs to upload files and store them.
As is a cloud app, I suppose that I am not able to create a directory in the web app service. My question is if I have to use the benefits of Azure and create a Storage Account and if this is the solution, What will be the best storage solution, Blob or File?
Thank you in advance.
Best wishes
Container is a Blob Storage, which is a great option for programmable storage, where our program can read and write to the storage account.
If we don't want to allow websites and the public to access the files, we can choose the below options.
Blob Storage Containers can contain any binary files/ binary large objects, there is no ordering and hierarchy, we can have a virtual folder structure.
Containers are usually programmed to share files to access using Shared Access Signature and Access Policy
I suppose that I am not able to create a directory in the web app service
Azure Files is more useful for mounting a file share to a server and multiple servers can mount the same file share. It can have a quota.
File share has a Directory Structure, we can create Directories and Subdirectories in a Hierarchical manner compared to Containers.
The Connect option in the File Share gives you details on how to mount drive onto a Windows/Linux machine.
Use file storage if you need the shared drive protocol, if not we can design the applications and use blob storage.
As per your requirement, if you want to create Directories you can choose AzureFile Share.
Reference link Azure Blob and Fileshare storage mentioned by #deherman-MSFT
I have an AKS cluster on which i am running a pod.
I am using dynamic pvc with the cluster and mounting it on my application's config path.
The problem is when I use hostPath based volume for my application, it works fine as application is able to store files with the appropriate permissions and ownership in the hostPath based volume .
But with using azure file share, as far I have understood there seems to be a concept of single user and same file permission on the azure file share (which is configured using storage class)
What I want is for the azure fileshare to not interfere with the application's ability to modify the file permissions or if there is a way to bypass this.
I feel like I am missing something.
Any help will be appreciated. Thanks in advance.
Azure File Share does not support manipulation of permissions within the mounted volume. Operations such as chown and chmod will not work with CIFS implementation of the SMB protocol.
You will either need to create separate volumes for each permissions variation required, or select a different storage class/volume type for your volume.
I know this is possible to link Azure blob to our local computer but can't remember how
My goal is to make possible to access blob like it is local disk, for example here i can access to a blob from local desktop
edit: I don't want to use azure storage explorer
Firstly there is a charge way to mount blob to local, you could refer to this blog: Use CloudBerry Drive to create a local mapped network drive to Azure Blob Storage.
Except this, you could choose to use Rclone to implement this. Rclone is a command line program to sync files and directories. However fro now this service could not Run mount as a daemon, means could not mount automatically with system startup.
I mount one container to my local.
In fact, it's possible using Azure Files. You can mount it using Powershell or map a network drive:
https://learn.microsoft.com/en-us/azure/storage/files/storage-how-to-use-files-windows
EDIT: Full answer:
Use the storage account name prepended with AZURE\ as the username and a storage account key as the password:
I've got a storage account in Azure that I made a network drive on my PC. It seems as if the drive I configure does not maintain connectivity for very long.
It feels as if every time I reboot, I have to remove the drive and reconnect to Azure.
Is there some configuration I'm missing for this?
If you use the Azure file share in windows, you can persist the mount with the document Persisting Azure file share credentials in Windows here. If in Linux, follow the document Create a persistent mount point for the Azure file share with /etc/fstab here.
Working in IaaS environment in AZURE and need to create a shared file for applications that will be sharing the same files uploaded by end users. The file share needs to be scene on various servers and appear as a fixed drive letter or mount point. Already created a Storage account and a file share in azure but can not overcome the issue that the mapped drive is associated with a users profile.
Was wondering if any has come up with a solution. ... I'm the system administrator assigned to this task and can do things in powershell or pass code information to developers for their review.
Did not resolve issue, developers are going to use Blog storage.
The trick with this was getting the application to see the drive letter. For us having a local user run as a service with the associated Azure file share mapping might have worked
NOTE to map the azure drive a use would need the Azure Storage account and Key generated for that account to access it.