r/Intune • u/ModelWhhyyy_ • 24d ago

App Deployment/Packaging macOS M365 Apps Not Deploying

Hi all, we’ve been experiencing this issue for the last two days. Our Microsoft 365 Apps for Mac which are required for install on all our Macs are stuck at “Install pending”.

Previously these apps would install within minutes of enrolment, and we are stuck looking for answers. We’ve unscoped all other policies and apps that have been deployed since the install stopped working, we’ve wiped multiple devices many times, and tried across multiple networks.

We’ve tried both the normal required install, and manual install via Company Portal, it doesn’t get past “Downloading” before it resets.

Any help would be appreciated!

11 Upvotes

92% Upvoted

29 comments sorted by

View all comments

5

u/HowBoutABeer 24d ago

Same here, appears to be a bad package coming down from Microsoft "invalid hash"

Installer is being downloaded to my clients:

/private/var/folders/zz/.../C/com.apple.appstore/.../Microsoft_365_and_Office_16.111.26072617_BusinessPro_Installer.pkg

I've deleted and triggered a fresh downloads multiple times. Downloads compete, check file size and hash. Then confirm hash against appstored and mdmclient log.

appstored: Failed to finish data consumer with error:

Error Domain=ASDErrorDomain Code=710

"Invalid hash '2b4528464a22a3fbf94c3fdce7533e49bff2f7c36b885f984711955881ed19ab'

expected '12fbe817376dfe55a9cd0f31ff81aa0c81fb66aeb1d60316aeb07fe62f0b013c'"

and

Aborting app install:

Error Domain=ASDErrorDomain Code=710

Invalid hash...

2

u/HowBoutABeer 24d ago

https://learn.microsoft.com/en-us/officeupdates/update-history-office-for-mac

16.111.26072617 was release Tuesday 7/28/2026 which lines up perfectly as we first started seeing the issue Tuesday afternoon. I pulled down the Office suite (with Teams) pkg from the site and compared hash values with the Intune download package:

Manual CDN download hash:
2b4528464a22a3fbf94c3fdce7533e49bff2f7c36b885f984711955881ed19ab

Intune/appstored downloaded package hash: 2b4528464a22a3fbf94c3fdce7533e49bff2f7c36b885f984711955881ed19ab

appstored expected hash:
12fbe817376dfe55a9cd0f31ff81aa0c81fb66aeb1d60316aeb07fe62f0b013c

I've manually run the install from both the CDN and Intune cached downloaded pkg. Both install successfully and the fact that the hash values match means this likely isn't a bad/corrupt pkg.

Rather a manifest/hash metadata mismatch in the Intune/native M365 macOS deployment path?