Hello James-99978,
Greetings! Welcome to Microsoft Q&A Platform.
I understand that you are encountering an error - AZSM1024 with Azure Storage Mover while performing the migration from on prem to Azure file share.
Please check the below considerations to resolve the issue,
Try creating a new local user, which has the same name, as is the value of the Key-Vault-User-Secret (had to shorten the secret to match the maximum allowed characters for user names) and configure the password to be the same as the Key-Vault-Password-Secret and assign the SMB permissions to this newly created local user account then try to migrate the files.
Ensure you have met the Prerequisites for the SMB Share:
- Ensure you have an active Azure subscription and a resource group.
- You need at least one SMB Azure file share in your storage account.
- Your local network must allow the Storage Mover agent to communicate with Azure. Ensure that port 443 (TLS) is open outbound, and your firewall rules do not limit traffic to Azure.
The permissions on the files and folders will remain when you migrate the data, the share permissions have to be configured using the RBAC roles. there are three Azure built-in roles for granting share-level permissions to users:
Storage File Data SMB Share Reader allows read access in Azure Storage file shares over SMB.
Storage File Data SMB Share Contributor allows read, write, and delete access in Azure Storage file shares over SMB.
Storage File Data SMB Share Elevated Contributor allows read, write, delete and modify NTFS permissions in Azure Storage file shares over SMB.
Check if you have assigned the appropriate permission to your resources on target location.
A 403-status code typically signifies that the request was understood by the server, but the server is refusing to authorize, and it suggests that the authorization configuration might be inconsistent or that there are intermittent issues with the Azure service or on your network.
If your application is using tokens for authorization, the tokens may be expiring or not being refreshed properly, leading to occasional failures.
If the issue is related to a storage account which I presume, try regenerating the storage account access keys and updating your application with the new keys.
Also, verify that no network or firewall rules are blocking the connection. You might need to allow access from all networks temporarily to test if this resolves the issue.
If the issue continues to occur and you are unable to resolve it with the above steps, it might require deep investigation and i would request you to raise a support ticket to investigate further.
Hope this answer helps! please let us know if you have any further queries. I’m happy to assist you further.
Please "Accept the answer” and “up-vote” wherever the information provided helps you, this can be beneficial to other community members