Azure file share issue

N Wakchaure, Jagdish 120

We have two main share folder DATA 1 and DATA 2 and under that also there are multiple share folder.

We implemented Azure file sync and both data 1 and data 2 is synced on Azure file share. these share users can access using private link, these share large in size.

now customer request is instead of data1 and data 2 accessing these share . they want to see all the share under data1 and data2.

like \servername\ all multiple share under data 1 and data2

incase if we add all the individual share in azure file sync and it will be difficult to manage all the share.

so is there any possibility that customer can see all the share under one umbrella.

Regards

Jagdish

Keshavulu Dasari 510 Reputation points Microsoft Vendor

2024-09-13T15:22:30.6466667+00:00

Hi N Wakchaure, Jagdish,
This is your kind information, There is a way to organize your sections under one umbrella to make it easier for users to access both sections under DATA 1 and DATA 2 .

You can create a common root folder with all the subfolders (shares) in DATA 1 and DATA 2. Then, you can synchronize this common root folder with the Azure file share. This way, users can access all parts of a path, such as \servername\commonroot, which will include all subfolders from DATA 1 and DATA 21 .

Please check below.

Create Common Root Folder : Create a new folder (e.g. CommonRoot) on your Windows Server.

Move subfolders: Move all subfolders from DATA 1 and DATA 2 to this CommonRoot folder.

Synchronize common root folders: Configure Azure File Sync to synchronize the CommonRoot folder with the Azure file share.

Access via Private Link: Ensure that the Azure file share is accessible via private link as before.

This system will allow users to see all the components under one umbrella, making access and management easier And also, please go through the given below link https://learn.microsoft.com/en-us/windows-server/manage/windows-admin-center/azure/azure-file-sync
please let us know if you have any further queries. I’m happy to assist you further.
N Wakchaure, Jagdish 120 Reputation points

2024-09-13T16:32:03.37+00:00
Thank you, Dasari for the Answers. so this looks like there lot of manual effort at on prem windows side.

so just to sunmaries we need to follow below steps

Create common root folder on windows ( no share)

Add this common root folder on Azure file sync

move all share folder from data 1 and data 2 to commonroot one by one using robocopy so the permission will intact, correct?

add all the share folder in azure file sync under common

this should solve the problem ?
N Wakchaure, Jagdish 120 Reputation points

2024-09-16T17:23:11.2666667+00:00

problem is when client use the \servername he see all the share folders or if the click on network and on the server name all the shares' folders are visible. he wants exact the same when he accesses the azure file sync private link. is it possible to get the same result like you access \server name and all shares you see , same for azure file sync link as well?
Keshavulu Dasari 510 Reputation points Microsoft Vendor

2024-09-17T09:44:32.4566667+00:00
Hi N Wakchaure, Jagdish,
Apologies for the delay response,
Problem is when client use the \servername he see all the share folders , Create a single Azure file share and organize all your subfolders (shares) within this file share. Users can then access the Azure file share via the private link and navigate through the nested folders to find the specific shares they need.

This approach simplifies management but requires users to navigate through the folder structure. Use Azure Storage Explorer, a free tool from Microsoft, which allows users to connect to Azure storage accounts and view all file shares. Azure File Sync does not natively support displaying all shares under a single umbrella in the same way as \servername does on a local network.
N Wakchaure, Jagdish 120 Reputation points

2024-09-17T10:23:39.01+00:00

also what i have observe is in the lab. we can only one server endpoint . just to test i created one test folder on the drive, added few share folder inside. then created sync gorup , cloudenpoint and server point. and mapped the root share folder it works. but let say we have another share folder in another drive we cannot do that. as there is limitation. we can have only one server endpoint. we can't add multiple.

Also

Data1\shares

data2\shares

there are multiple shares under above path , some folder dont have shared. but there are share folder inside it.

so when client access the \servername he see all the shares. but see different folder when he accesses private link for above path.

is there any solution for above this. as we cannot move these folders under common folder as sharing will be removed during the movement even permission also. so any alternate solution to see all shares under one link.

I know Azure is SMb share & we cannot create any share folder. but how we can have better view while accessing the azure file url so client just can see share folders which is on the server.

Regards

Jagdish
Keshavulu Dasari 510 Reputation points Microsoft Vendor

2024-09-17T14:34:04.7833333+00:00

Hi Jagdish,
With the limitation of having only one server endpoint per synchronization group in Azure File Sync.
Use DFS Names with Azure File Sync
As mentioned earlier, DFS Namespaces can help you create a unified namespace for your components. This way, users can access all the components in one go, as if they go to \servername.

Create more networking groups
If you have drives with different shares, you can create multiple synchronization groups, each with its own server endpoint. Here’s how you can deal with it.
Create separate communication groups:
Create a sync group for each drive or shares.
Each connection group will have its own server endpoint and cloud endpoint.

Use DFS Names:
Associate folders from different synchronization groups with the same DFS namespace. This gives users a consensus to navigate certain segments.
If migrating folders is not an option due to licensing issues, consider using Azure File Share snapshots to create time point snapshots of your components. This can help manage parts and get them without moving.
Keshavulu Dasari 510 Reputation points Microsoft Vendor

2024-09-18T17:15:19.71+00:00

Hi Jagdish,
If you have any questions, let me know in the "comments" and I would be happy to help you.
N Wakchaure, Jagdish 120 Reputation points

2024-09-18T17:47:32.2966667+00:00

Hello Dasari, Thanks for your help. however what we have thought now that . we will create multiple shares and also multiple cloud endpoint with below server endpoints. so users can access the individual.

One question is can we just access the url as below and we can see all the folders ? is there any possibility we can create custom dns for url and this will work? as i observed we need to give full url plus data folder name also. if we just use the url we can achieve this.

abc01.file.core.windows.net

\abc01.file.core.windows.net\Account

\abc01.file.core.windows.net\Finance

\abc01.file.core.windows.net\Marketing

\abc01.file.core.windows.net\HR
Keshavulu Dasari 510 Reputation points Microsoft Vendor

2024-09-20T13:09:33.2+00:00

Hi N Wakchaure, Jagdish ,
If you have any questions, let me know in the "comments" and I would be happy to help you.
Keshavulu Dasari 510 Reputation points Microsoft Vendor

2024-09-23T12:10:27.8+00:00

Hi N Wakchaure, Jagdish ,
If you have any questions, let me know in the "comments" and I would be happy to help you.

1 answer

Keshavulu Dasari 510 Reputation points Microsoft Vendor

2024-09-19T11:37:17.1733333+00:00
Hi N Wakchaure, Jagdish ,
Welcome to Microsoft Q&A Forum, Thank you for posting your query here!
Based on your scenario there are few possible causes: Firstly, you can create a custom DNS for your Azure file shares to simplify access for your users, purchase a custom domain if you don’t already have one. In your DNS provider’s management portal, create a CNAME record that maps your custom domain to the Azure file share URL If you are using Azure DNS, you can create a DNS zone and add the CNAME record there. This will ensure that files.yourdomain.com resolves to abc01.file.core.windows.net.

Once the custom DNS is configured, users can access the file shares using the custom domain. For example: \files.yourdomain.com\Account, \files.yourdomain.com\Finance

Ensure that your Azure file shares are accessible via a private endpoint. This will allow users to securely access the shares over a private network connection

For more information: https://learn.microsoft.com/en-us/azure/storage/file-sync/file-sync-networking-endpoints

Please let us know if you have any further queries. I’m happy to assist you further
Please sign in to rate this answer.

0 comments No comments
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

Azure file share issue

1 answer

Your answer