# Microsoft AutoUpdate on Mac: Settings and Shared Components

> Identify what AutoUpdate updates, separate automatic updates from background permission, and check its shared components before considering removal.

Published: 2026-07-08 | Updated: 2026-10-31

Microsoft AutoUpdate can remain on a Mac after you stop using an Office app. Before removing it, check whether another installed Microsoft app still uses it, and separate automatic updating from permission to run in the background. Changing one does not establish that the other is disabled.

## Identify What AutoUpdate Is Updating

[Microsoft Learn](https://learn.microsoft.com/en-us/microsoft-365-apps/mac/update-office-for-mac-using-msupdate) describes Microsoft AutoUpdate, or MAU, and lists supported applications beyond Word and Excel. Review AutoUpdate's actual app list before deciding it is an Office leftover.

Microsoft's [Office update instructions](https://support.microsoft.com/en-us/office/lifecycle/officeinstall/update-office-for-mac-automatically) distinguish apps installed from Microsoft's website from apps installed through the Mac App Store. The latter use App Store updates. That distinction applies to those apps, not automatically to every Microsoft product on the Mac.

| What you find | What it establishes | Next step |
| --- | --- | --- |
| An installed app appears in AutoUpdate | There is a reason to preserve its update route | Keep MAU and review its settings |
| Office came from the Mac App Store | Those Office apps use the App Store update route | Check other MAU consumers separately |
| No familiar Office app remains | Only that those apps were removed | Check the complete MAU app list and managed software |

Record the apps you intend to keep. Do not remove shared update components merely because you deleted Word or no longer have a Microsoft 365 subscription.

## Why It Appears in Background Items

Microsoft's [background-permission guidance](https://support.microsoft.com/en-us/office/office-for-mac/allow-microsoft-autoupdate-to-run-in-the-background-on-macos) explains that MAU detects, downloads and applies updates in the background. On macOS Ventura and later, macOS exposes background permissions in its settings.

The presence of a background entry alone does not identify a fault. Microsoft says blocking AutoUpdate can cause an Office app to display an update error, asking you to allow it again. A background-permission switch is therefore a poor substitute for choosing how updates should be handled.

If you disabled it and now see that error, use the linked Microsoft instructions to restore its background permission, then check for updates again. Leave managed-device policy to your administrator.

## Change Update Behavior in AutoUpdate

Open an Office app you still use, such as Word, and open its update check from the help menu. Microsoft's update instructions above document this route. Record the current automatic-update selection before changing it.

If your version shows an option for keeping Microsoft apps up to date automatically, change that option there rather than deleting launch files. Turning it off means taking responsibility for checking and applying app updates yourself; it is not a promise that MAU will never appear or update itself.

Microsoft's [current preference reference](https://learn.microsoft.com/en-us/microsoft-365-apps/mac/mau-preferences#howtocheck) distinguishes the following behavior:

| Preference value | Documented behavior |
| --- | --- |
| `AutomaticDownload` | Checks regularly and applies updates automatically |
| `AutomaticCheck` | Checks regularly and opens the interface when updates are found |
| `Manual` | Checks for MAU's own updates, without automatically offering other app updates |

These are preference identifiers, not a promise of three choices in your window. The reference says `Manual` has been removed from the GUI. If the controls differ or are managed, do not force an old screenshot's layout onto the current version.

## Locate the App and Its Launch Agent

Microsoft Learn's msupdate instructions locate the updater inside this system-wide directory:

```text
/Library/Application Support/Microsoft/MAU2.0/Microsoft AutoUpdate.app
```

A [Microsoft staff answer on Microsoft Q&A](https://learn.microsoft.com/en-my/answers/questions/5849528/disruptive-microsoft-auto-update) also identifies these associated items. This is a component inventory, not a deletion sequence:

| Location | Component |
| --- | --- |
| `/Library/LaunchAgents/com.microsoft.update.agent.plist` | Launch agent |
| `/Library/LaunchDaemons/com.microsoft.autoupdate.helper.plist` | Helper launch daemon |
| `/Library/PrivilegedHelperTools/com.microsoft.autoupdate.helper` | Helper executable |

Keep `/Library` distinct from `~/Library`. Do not erase a whole Microsoft support directory, remove a licensing helper, or change executable permissions just to stop an updater window.

## Remove It Only When No App Still Needs It

Treat removal as a separate decision after removing all apps that actually rely on MAU. The supported-app list is wider than Office, and a Mac App Store copy of Word does not prove another installed app is independent of MAU.

This is a conservative keep-or-remove rule, not a claim that Microsoft publishes a universal MAU removal checklist. The official pages above establish update responsibilities and component locations; they do not justify deleting every Microsoft-named file. On a managed Mac, ask the administrator to confirm the consumers and removal method.

For Office removal and Outlook data, follow [the Office removal article](https://mole.fit/blog/how-to-uninstall-microsoft-office-mac) and [the tested Office guide](https://mole.fit/tested-apps/microsoft-office). Keep that data decision separate from the updater decision.

## Verify the Change and Restore Updating

After a settings change, reopen AutoUpdate and confirm the selection, run an update check, then reopen an app you kept. Check the reported update result rather than treating a closed window as success. Restore the previous automatic-update choice if you no longer want to maintain updates manually.

If MAU is missing or damaged, Microsoft's [repair guidance](https://support.microsoft.com/en-gb/office/office-for-mac/troubleshoot-microsoft-autoupdate-in-microsoft-365-and-office-for-mac?nochrome=true) points to its latest installer. Reinstall through that official source and retry the update check. Do not delete more helpers in response to a missing-helper error.

For broader decisions, see [Mac app update sources](https://mole.fit/blog/how-to-update-mac-apps) and [startup items](https://mole.fit/blog/how-to-disable-startup-programs-on-mac).

## Where Mole Fits

Mole Mac filters shared Microsoft AutoUpdate paths out of Homebrew-derived uninstall leftovers and refuses its system-wide Microsoft support tree as an uninstall remnant. Its orphan-service scanner also excludes `com.microsoft.autoupdate.helper` unconditionally. Removing an Office app with Mole is not a request to remove this shared updater; use AutoUpdate itself to manage its update behavior.

## FAQ

### Can I Remove AutoUpdate After Deleting Word?

Deleting Word alone does not establish that MAU is unused. Check other registered apps and managed software first, and preserve the updater while an installed app relies on it.

### Does Turning Off Automatic Updates Stop Every MAU Process?

No. Update behavior and background permission are separate, and Microsoft's Manual preference still permits MAU to check for its own updates.

### What If Office Says AutoUpdate Cannot Run?

Check Microsoft's background-permission instructions first. If the updater is missing or damaged, use its official installer and verify that an update check works afterward.

---

Canonical HTML page: https://mole.fit/blog/microsoft-autoupdate-mac
Blog index for agents: https://mole.fit/blog/llms.txt
Site index for agents: https://mole.fit/llms.txt