Not able to upload files to file share

Mohan 0 Reputation points
2026-09-03T12:08:24.7066667+00:00

I have created a storage account and created a file share under storage account and assigned below roles: -

Storage File Data SMB Share Contributor

Storage File Data SMB Share Elevated Contributor

but i am not able to upload the files to file share with same permission i was able to upload the files.

Azure Files
Azure Files

An Azure service that offers file shares in the cloud.

0 comments

3 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. kagiyama yutaka 5,410 Reputation points
    2026-09-03T13:19:30.5266667+00:00

    I think Azure Files writes depend on either SMB NTFS ACL or REST’s Storage File Data Privileged Contributor, and those SMB roles sit at the share-level. A tiny upload in the portal shows whether you’re hitting SMB or REST and which permission is missing, so u fix only the one that matches how you’re uploading.

    Was this answer helpful?

    0 comments
  2. Marcin Policht 107.9K Reputation points MVP Volunteer Moderator
    2026-09-03T12:15:46.95+00:00

    Verify that identity-based authentication or networking restrictions are fully configured. Azure RBAC grants share-level permissions, but the storage account must also be configured to authenticate your identity and allow access to the storage data plane.

    The first thing to check is the identity source configuration. In the Storage Account, go to File shares and check Identity-based access. If it is not configured, you need to configure an appropriate directory service, such as Microsoft Entra ID, Microsoft Entra Domain Services, or on-premises Active Directory Domain Services, depending on your environment. As an alternative for testing, you can configure the default share-level permissions to provide authenticated users with the appropriate Contributor access.

    If you are accessing the file share through SMB, also check whether TCP port 445 is blocked. Some ISPs, firewalls, or network devices block outbound SMB traffic. If port 445 is unavailable, you will not be able to mount the Azure file share using standard SMB from that network. In that situation, you can use a VPN or Azure ExpressRoute to provide connectivity, or use Azure Storage Explorer, which can access the storage account without requiring a direct SMB connection.

    You should also check the Storage Account networking configuration. Go to Storage Account > Networking and verify whether access is restricted to selected virtual networks and IP addresses. If so, make sure the public IP address of the client you are using is permitted, or temporarily allow access from all networks for testing. If the upload works after changing the networking setting, the firewall or network configuration is the cause.

    Finally, if you assigned the RBAC roles recently, allow some time for the permissions to propagate. You can also completely sign out of the Azure portal and sign back in to obtain a refreshed authentication token. If the roles have been assigned correctly and the issue persists after propagation, focus on the identity-based access configuration and the Storage Account networking settings, as those are separate from the RBAC role assignment.

    If the above response helps answer your question, remember to "Accept Answer" so that others in the community facing similar issues can easily find the solution. Your contribution is highly appreciated.

    hth

    Marcin

    Was this answer helpful?

    0 comments

  3. AI answer

    2026-09-03T12:08:43.28+00:00

    For Azure Files, share-level Azure RBAC alone is often not enough to upload files.

    If access is through SMB with Microsoft Entra or AD credentials, both of these must be in place:

    1. Share-level permission
      • Storage File Data SMB Share Contributor allows read, write, and delete.
      • Storage File Data SMB Share Elevated Contributor also allows modify-ACLs.
    2. File and directory permissions (NTFS ACLs)
      • Without NTFS permissions on the share/root folder, uploads can fail even when the RBAC role is assigned.

    Also note:

    • Share-level permission changes usually take effect within 30 minutes, and sometimes longer.
    • If default share-level permissions are also configured for all authenticated identities, the effective permission is the higher of the default permission and the explicit RBAC assignment.

    If the upload is being done with OAuth/REST tools such as Storage Explorer and the error is 403 AuthorizationPermissionMismatch, assign Storage File Data Privileged Contributor at the storage account or file share scope. That role bypasses existing file/directory ACLs and grants read, write, delete, and modify-ACLs access to Azure Files data.

    To verify and fix:

    1. In Azure portal, go to the file share.
    2. Open Access Control (IAM).
    3. Confirm the role is assigned at the correct scope.
    4. If using Entra ID/OAuth upload, assign Storage File Data Privileged Contributor.
    5. If using SMB identity-based access, configure the required NTFS ACLs on the root folder and target folders.
    6. Wait for RBAC propagation, then try the upload again.

    If the issue is specifically SMB authentication/authorization, Debug-AzStorageAccountAuth can be used to check RBAC assignment and file access.

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.