Graph API Win32 App Upload Fails with commitFileFailed Error

Question

Graph API Win32 App Upload Fails with commitFileFailed Error

Brian Balser 40

Encountering issues with uploading a Win32 app using the Graph API. The following steps outline the process and the encountered problem:

Authenticated using client credentials with DeviceManagementApps.ReadWrite.All permission.
File uploads successfully to Azure Blob Storage via AzCopy.
The commit POST request returns a 200 status code (success).
Immediately after, the file state shows uploadState: "commitFileFailed" and isCommitted: false.
This issue persists with both 12GB and 1.5KB .intunewin files.
Encryption information is extracted correctly from detection.xml.
Manual portal upload works fine.
The PowerShell script adheres to the Microsoft Graph API documentation.

The commit payload structure used is as follows:

$encryptionInfoForCommit = [ordered]@{
       encryptionKey = $EncryptionInfo.encryptionKey
       macKey = $EncryptionInfo.macKey
       initializationVector = $EncryptionInfo.initializationVector
       mac = $EncryptionInfo.mac
       profileIdentifier = $EncryptionInfo.profileIdentifier
       fileDigest = $EncryptionInfo.fileDigest
       fileDigestAlgorithm = $EncryptionInfo.fileDigestAlgorithm
}

Any thoughts or directions on how to resolve this issue? Despite the successful upload and the app appearing in Intune, the commit process fails.

Answer accepted by question author

1 additional answer

Your answer

Answer 1

Arne 155

We are experiencing the same problem. Haven't found the root cause.
We recently updated out powershell version to 7.3, but have not found a direct link to the issue.

We are in to progress of testing with a older PS version. Maybe the way the newer PS version handle encoding could be the issue.

Have not found a mentioned change in the way we upload to the blob-storage.

Brian Balser 40 Reputation points

2025-10-02T15:06:12.4333333+00:00

so it turns out (at least in our case), the problem was using AZCopy instead of chunking the upload. After I changed my approach to use Invoke-Uploadwin32Lob I had success. Still faster than manually uploading through the portal, not as fast, unfortunately, as pushing in one big push using AZCopy. Hoping to resolve some of that with chunk size, et cetera.

Answer 2

Arne 155

Follow-up on our problem, it was indeed a change in behavior with a different PowerShell version.
(Maybe the same behaviour can be replicated with AZCopy when it uses Invoke-WebRequest and Invoke-RestMethod resting on PowerShell 7.4)

A detailed explanation can be found here and how we solved it: https://dutchscriptingguys.com/why-your-intune-file-commits-fail-in-powershell-7-4/

Brian Balser 40 Reputation points

2025-10-03T12:49:10.5266667+00:00

I'm going to mark this as the accepted answer even though my situation was slightly different - just because I feel this may help more people who come looking for a solution to this problem. Thank you!

Answer 3

Brian Balser 40

Dropping my comment response here just to make the answer (in our case) available to others if they are seeking it.

"..so it turns out (at least in our case), the problem was using AZCopy instead of chunking the upload. After I changed my approach to use Invoke-Uploadwin32Lob I had success. Still faster than manually uploading through the portal, not as fast, unfortunately, as pushing in one big push using AZCopy. Hoping to resolve some of that with chunk size, et cetera."

Share via

Graph API Win32 App Upload Fails with commitFileFailed Error

1 additional answer

Your answer