Microsoft Intune Graph API - commitFileFailed Error After Successful API Calls

Question

Issue Summary

Problem: commitFileFailed errors during .intunewin uploads via Graph API

All Graph API calls succeed (HTTP 200/201) including:

1. App creation, content version, file entry
2. Azure Storage upload with proper validation
3. Commit API call (Request ID: 3362aae2-747c-4dd2-84a0-2bbb587965a3)

Key Details

• File: putty-0.83-installer.intunewin (3,064,190 bytes)
• Tool: Microsoft Win32 Content Prep Tool v1.8.7
• File ID: 1baeaea5-642f-4ade-aa70-beffb0589368

Issue: Microsoft's backend processing fails with uploadState: "commitFileFailed"

Timeline

October 24, 2025

• 17:30:27 UTC - Content version created
• 17:30:28 UTC - File entry created
• 17:31:25 UTC - Commit API returns HTTP 200
• 17:31:43 UTC - Backend shows commitFileFailed

FileEncryptionInfo Payload

{
  "fileEncryptionInfo": {
    "encryptionKey": "pjej4QHNtXNufstQFRThg19DouxhTqY76MS9+BLMkb8=",
    "macKey": "PVNymN9sYP+BDY8rzAaYhHnR603togMd3lFVNCTZDcc=",
    "initializationVector": "HjknNQrYSzbCDTpLJHybtA==",
    "mac": "yGCYpy+gVmtphOguhQ4DpW6KaJdpeecbz1y85L+cP/I=",
    "profileIdentifier": "ProfileVersion1",
    "fileDigest": "/WtiXvFuBAyPnQNzIsRcu+1lyx1xLncDh0xy87ifWl0=",
    "fileDigestAlgorithm": "SHA256",
    "@odata.type": "microsoft.graph.fileEncryptionInfo"
  },
  "size": 3064190,
  "name": "putty-0.83-installer.intunewin"
}

Questions

1. Can you provide internal error logs for Request ID 3362aae2-747c-4dd2-84a0-2bbb587965a3?
2. What backend validations cause commitFileFailed after HTTP 200 commit response?
3. Are there undocumented fileEncryptionInfo requirements?

Requesting an assistance in Microsoft backend processing failure

Answer 1

Hello @Anusha Prasanth ,

Sorry you ran into this issue. I wanted to check whether you are still experiencing this issue.

If the problem persists, I would recommend reaching out to Microsoft Support (if you haven’t already), as they’ll be best placed to review the specific errors and help identify the underlying cause.

Based on similar cases we’ve seen in the past, this behavior can sometimes be related to encoding or encryption-handling differences in the scripts used during the upload process. The support team can help validate this and guide you toward a fix.

You can contact support directly from the Intune admin center using the following link: Get support in the Microsoft Intune admin center - Microsoft Intune | Microsoft Learn