Office for Mac Issues

Fix Office Apps Not Opening on Mac Managed by Kandji (ADAL4.framework)

Khadija KhanKhadija Khan Oct 26, 2026 868 views

Question details

Users are unable to open Microsoft 365 applications on Kandji-managed Macs due to a missing framework dependency error after deployment.

Fix Microsoft Office Apps Not Opening on Macs Managed by Kandji
Product
Microsoft 365
Device & OS
macOS
Scenario
Deploying the combined Microsoft Office installation package to Mac endpoints using Kandji MDM.
Observed behavior
The installation reports as successful, but launching any Office application triggers a crash or an error message stating that ADAL4.framework cannot be loaded.
Before you start

Ensure you have administrator privileges in your Kandji MDM portal and access to a test Mac device. Download the latest official Microsoft 365 installer package directly from the Microsoft enterprise portal for testing.

Solution 1Recommended

Deploy Individual Office Application Packages

Bypass the shared framework deployment bug in the combined suite installer by deploying Word, Excel, and PowerPoint as individual packages.

When Mobile Device Management (MDM) platforms like Kandji deploy the combined Microsoft 365 suite package, permission or unpacking issues can occasionally cause shared dependencies like ADAL4.framework to fail installation. Installing the applications separately often bypasses this specific error.

1
Download Individual Installers

Log into the Microsoft enterprise deployment portal and download the standalone installer packages for Microsoft Word, Excel, and PowerPoint instead of the combined suite.

2
Create New Custom Apps in Kandji

Navigate to your Kandji dashboard, go to Library, and click 'Add New'. Select 'Custom App' and upload the individual Microsoft application packages.

3
Assign and Deploy

Assign these new individual custom apps to your target Mac blueprints. Ensure the old combined package is removed from the blueprint to prevent conflicts.

4
Verify Installation

On a target Mac, allow Kandji to sync and install the individual apps. Launch Word or Excel to verify that the ADAL4.framework error no longer appears.

Deploy Individual Office Application Packages
Recommended Workaround: Individual deployment is currently the most reliable workaround for MDM-related framework loading failures on macOS.
Free Microsoft Office alternative

Deploy WPS Office on Mac as a Seamless Alternative

If MDM deployment of Microsoft 365 continues to cause framework errors and disrupt productivity, consider switching to WPS Office. It provides a lightweight, unified office suite that is incredibly easy to deploy across macOS environments without complex dependency or framework issues.

  1. 1. Download the Installer: Visit the official WPS Office website and download the latest macOS installer package.
  2. 2. Deploy via MDM or Install Manually: Upload the lightweight WPS Office package to Kandji or install it manually on your Mac. The unified architecture prevents missing framework errors.
  3. 3. Open and Edit Seamlessly: Launch WPS Office and immediately begin opening, editing, and saving your existing Microsoft Office documents with complete format compatibility.
Unified, lightweight installer package that prevents framework dependency issues during MDM deploymentHigh compatibility with Microsoft Word, Excel, and PowerPoint file formats (.docx, .xlsx, .pptx)Familiar, intuitive user interface that requires zero training for your teamResource-efficient application footprint ideal for enterprise macOS environments
microsoft office alternative - wps office

Frequently Asked Questions

What is the ADAL4.framework in Microsoft Office?

ADAL4.framework stands for Active Directory Authentication Library. It is a critical component used by Microsoft Office applications on Mac to securely handle user sign-in and enterprise authentication with Microsoft 365 services.

Why does the combined Office package fail in Kandji while separate apps work?

Combined suite installers are extremely large and contain shared dependencies. During MDM deployment, background unpacking or permission restrictions can sometimes cause shared components like ADAL4.framework to be skipped or improperly linked. Individual app packages handle their own dependencies separately, often bypassing this deployment bug.

Can I manually copy the missing ADAL4.framework file from another Mac?

No, manually copying framework files is strongly discouraged. macOS utilizes strict Gatekeeper and code-signing security protocols. Manually pasting a framework into the application bundle will invalidate the app's signature, causing macOS to block the app entirely.