Storage Mover - AZSM1042 - CLAIM TARGET FAILURE]

Question

Storage Mover - AZSM1042 - CLAIM TARGET FAILURE]

Phil 271

Hello together,

i have an Issue with the Storage Mover.
i tried to synchronize an onPrem Fileshare with an Storage Accoun File Share.

The Storage Mover displays the error “AZSM1042 -CLAIM TARGET FAILURE]” when executing the job.

The FileShare is onboarded with an private Endpoint.
The necessary Right for the Identity are configured on the FIle Share Level.

Here is the complete error message:

Job failed state transition: (Started,Claimed -> Failed,Claimed). Message: Failed to claim target container Container in xxx: [CLAIM TARGET FAILURE] Unexpected error occurred while attempting claim on target container: Put "https://xxx.file.core.windows.net/xxx/__AZURE_STORAGE_MOVER_MARKER": EOF

What has already been tried:

The STorage Account was changed to Public Endpoint for an test.
An attempt was made to specify the fileshare directly as the destination and not a subfolder

The Microsoft Docs Troublehsooting Steps does not really help.

There it is described that it is a temporary error and otherwise you should open a Microsoft ticket.

Any Ideas?

Thanks.

Best Regards,
Phil

Vinod Kumar Reddy Chilupuri 3,035 Reputation points Microsoft External Staff

2025-02-27T11:13:16.8166667+00:00
Hi Phil

To fix the "AZSM1042 - CLAIM TARGET FAILURE" error in Azure Storage Mover, Follow the below steps that may resolves your issue.

Check Permissions:

Make sure the Managed Identity or Service Principal used by Storage Mover has the right permissions to access the storage account and file share. It usually needs the "Storage File Data SMB Share Contributor" role.

Check Network Settings:

Verify that your network settings allow access to the storage account. If you are using a private endpoint, check that the network rules and DNS settings are correct. https://learn.microsoft.com/en-us/azure/storage/common/storage-private-endpoints

Review Endpoint Settings: Double-check the settings for the Storage Mover. Make sure the target container and path are set up correctly. Overview of Azure Storage Mover

Try Again: Sometimes, the error might be temporary. Wait a few minutes and try the operation again.

Test with Public Endpoint:

As a test, you can switch the storage account to a public endpoint temporarily to see if that fixes the issue. This can help you find out if the problem is with the network settings. Network settings for Azure Storage accounts.
https://learn.microsoft.com/en-us/azure/storage/common/storage-network-security?tabs=azure-portal

Check Error Messages:

Look at the detailed error messages and logs from Storage Mover. They can give you more information about what went wrong.

Similar Thread: Please check this similar thread that may help you.

https://learn.microsoft.com/en-us/answers/questions/2045631/azure-storage-mover-error-azsm1024

https://learn.microsoft.com/en-us/azure/storage-mover/status-code

By following these steps and using the provided links, you will be able to troubleshoot and fix the "AZSM1042 - CLAIM TARGET FAILURE" error in Azure Storage Mover.

Hope the above suggestion helps! Please let us know do you have any further queries.

Please do consider “Accepting the answer” wherever the information provided helps you, this can be beneficial to other community members.
Phil 271 Reputation points

2025-02-27T13:35:22.9966667+00:00
Hello @Vinod Kumar Reddy Chilupuri ,

thanks for your Answer.
It helpes not really for the Problem.

Permissions are set on the Storage Account and on the Fileshare level direct

I said it before i tried the same with the public Endpoint -> Same Error

What do you mean with detailed Logs from Storage Mover?

To be honest, the logging and debugging for the jobs is not really well solved

The other Links doesnt work. But all i find about this Problem doesnt help.

Regards,
Phil
Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Vinod Kumar Reddy Chilupuri 3,035 Reputation points Microsoft External Staff

2025-02-28T09:18:02.3233333+00:00

Hi Phil
We are checking internally with our team on this issue. We will update you as soon as possible once we get an update from our team.
Phil 271 Reputation points

2025-02-28T09:23:44.76+00:00

Thank you for your help.

I will wait for the answer.

Accepted answer

0 additional answers

Your answer

Phil 271 Reputation points

2025-02-27T13:35:22.9966667+00:00

Hello @Vinod Kumar Reddy Chilupuri ,

thanks for your Answer.
It helpes not really for the Problem.

Permissions are set on the Storage Account and on the Fileshare level direct

I said it before i tried the same with the public Endpoint -> Same Error

What do you mean with detailed Logs from Storage Mover?

To be honest, the logging and debugging for the jobs is not really well solved

The other Links doesnt work. But all i find about this Problem doesnt help.

Regards,
Phil
Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Vinod Kumar Reddy Chilupuri 3,035 Reputation points Microsoft External Staff

2025-02-28T09:18:02.3233333+00:00

Hi Phil
We are checking internally with our team on this issue. We will update you as soon as possible once we get an update from our team.
Phil 271 Reputation points

2025-02-28T09:23:44.76+00:00

Thank you for your help.

I will wait for the answer.

Answer 1

Venkatesan S 585 Microsoft External Staff

Hi Phil

Welcome to Microsoft Q&A

Since you’ve already verified permissions, tested with a public endpoint, and still face the same issue, let’s go deeper.

Test manual uploading via Azcopy :

Command:

azcopy copy "C:\testfile.txt" "https://<storage-account>.file.core.windows.net/<share-name>/testfile.txt?<SAS token>" --from-to=LocalFile --recursive

If this fails, it’s a connectivity issue rather than a Storage Mover issue.

Check which Storage Mover identity can claim the Azure File Share first. Then, connect using the Storage Mover identity that can claim the target file share.

Command:

 Connect-AzAccount -Identity$storage
 Context = New-AzStorageContext -StorageAccountName "<your-storage-account>" -UseConnectedAccount
 New-AzStorageFile -ShareName "<your-file-share>" -Path "testfile.txt" -Context $storageContext

If this fails, it’s a storage-level issue, not a Storage Mover issue.

Check Storage Mover Logs.

Command:

StorageMoverJobRunLogs
| where TimeGenerated > ago(3d) 
| where StatusCode != "AZSM0000"   // Filter out success logs
| project TimeGenerated, JobRunName, StatusCode, Message
| order by TimeGenerated desc

The above query will list all job failures in the last 3 days, including the error code.

If you have a specific Job Run ID, replace [job run ID] and check errors:

Command:

StorageMoverCopyLogsFailed 
| where TimeGenerated > ago(30d) 
| where JobRunName == "[job run ID]"
| project TimeGenerated, JobRunName, StatusCode, Message
| order by TimeGenerated desc

Run this PowerShell command to check the file share quota and used capacity:

Command:

$accountName = "xxxx"
$accountKey = "xxxx"
$shareName = "xxx"
$ctx = New-AzStorageContext -StorageAccountName $accountName -StorageAccountKey $accountKey
$share = Get-AzStorageShare -Name $shareName -Context $ctx
$client = $share.ShareClient
$stats = $client.GetStatistics()
$usedBytes = $stats.Value.ShareUsageInBytes
$usedGB = [math]::Round([float]($usedBytes / 1GB), 2)
$quotaGB = [float]$share.Quota
Write-Host "Quota: $quotaGB GB"
Write-Host "Used Space: $usedGB GB"

Reference:

Hope this answer helps! please let us know if you have any further queries. I’m happy to assist you further.

Please do not forget to "Accept the answer” and “up-vote” wherever the information provided helps you, this can be beneficial to other community members.

Venkatesan S 585 Reputation points Microsoft External Staff

2025-03-04T05:14:44.97+00:00

Following up to see if the above answer was helpful. If this answers your query, do click Accept Answer and Yes for was this answer helpful. And, if you have any further query do let us know.
Phil 271 Reputation points

2025-03-04T06:17:09.0033333+00:00
Hello,

I will test the first two points in the next few days.

Check which Storage Mover identity can claim the Azure File Share first. Then, connect using the Storage Mover identity that can claim the target file share. Command: PowerShellCopy

` Connect-AzAccount -Identity$storage Context = New-AzStorageContext -StorageAccountName "<your-storage-account>" -UseConnectedAccount New-AzStorageFile -ShareName "<your-file-share>" -Path "testfile.txt" -Context $storageContext`

You mean the Azure Arc Identity?
Can you explain this step with the Identity Part a little bit more?

What I can already say however is that the lower part from the Log Analytics Workspace and its queries make little sense, as the job does not start.

Command: SQLCopy

`StorageMoverJobRunLogs | where TimeGenerated > ago(3d) | where StatusCode != "AZSM0000" // Filter out success logs | project TimeGenerated, JobRunName, StatusCode, Message | order by TimeGenerated desc`

Command: SQLCopy

`StorageMoverCopyLogsFailed | where TimeGenerated > ago(30d) | where JobRunName == "[job run ID]" | project TimeGenerated, JobRunName, StatusCode, Message | order by TimeGenerated desc`

So i can only find the postet Error Entry and not more helpful Logs in the Log Analytic Workspace.

Run this PowerShell command to check the file share quota and used capacity:

Its a completly new Fileshare.

Regards,
Phil
Venkatesan S 585 Reputation points Microsoft External Staff

2025-03-04T07:02:20+00:00
Phil

You mean the Azure Arc Identity? Can you explain this step with the Identity Part a little bit more?

According to this MS-Document,

The Storage Mover service needs an identity that has the necessary permissions to access and write to the Azure File Share. This identity is typically:

A Managed Identity (System-assigned or User-assigned)

Azure Arc Identity (if applicable for hybrid scenarios)

Permissions for the Storage Mover Identity has been granted to Azure Key vault (Key Vault Secrets User) and Storage Account + File Share (Storage Data Privileged Contributor)

How to manage Azure Storage Mover endpoints | Microsoft Learn

Since you tested with both Private Endpoint and Public Endpoint, this is less likely, but you may want to check NSG/Firewall settings on the storage account.

Hope this answer helps! please let us know if you have any further queries. I’m happy to assist you further.
Phil 271 Reputation points

2025-03-04T10:30:19.7333333+00:00

For my understanding.

Do I need one of the two or do I need an Azure Arc Identity and a System or User Assigend Managed Identity?

At the moment the agent is registered as an azure arc object and have permissions on the Target Storage account.
Venkatesan S 585 Reputation points Microsoft External Staff

2025-03-04T10:35:16.21+00:00
You do not necessarily need both an Azure Arc Identity and a Managed Identity—your Azure Arc-registered agent should be sufficient if it has the correct permissions.

When the Storage Mover agent is registered in Azure Arc, it acts as an Azure Arc-enabled Server and uses the Azure Arc identity (a system-assigned managed identity associated with the Azure Arc resource).

This Azure Arc identity must have the required permissions on the target Azure File Share.

You can get the role assignments using powershell:

Get-AzRoleAssignment -ObjectId "<Azure_Arc_Identity_ObjectId>"

Reference:

Get-AzRoleAssignment (Az.Resources) | Microsoft Learn
Venkatesan S 585 Reputation points Microsoft External Staff

2025-03-05T04:13:46.0966667+00:00

Just checking in to see if the provided answer helped. If this answers your query, do click "Accept the answer” for the same, which might be beneficial to other community members reading this thread. And, if you have any further queries do let us know.
Phil 271 Reputation points

2025-03-12T12:21:09.4733333+00:00

Hey,

sorry for the late response.
I haven't gotten to all the tests yet.

As soon as I have been able to carry out the tests, I will report back here.

But I can already say one thing.

When I try to execute “Get-AzRoleAssignment - Object ID”, I get an empty output.

However, the Azure ARC resource is authorized to the current resources under IAM
Phil 271 Reputation points

2025-03-13T14:31:01.1066667+00:00

Thanks for your help.

It was a very simple and stupid mistake.

The Problem was the Connection to the Private Endpoint over The Firewall.
There was only one network rule and no application rule.

After creating the application rule, it worked immediately.

Share via

Storage Mover - AZSM1042 - CLAIM TARGET FAILURE]

0 additional answers

Your answer