Deploying Microsoft Office from the Mac App Store


When macOS Mojave’s Mac App Stores new look was unveiled during WWDC 2018 it was also announced that Microsoft would be bringing the Office suite to the Mac App Store.

Well, earlier this week the announcement was fulfilled.

See below for some information on how this might affect us admins as well as some things to consider.

Microsoft KB

Microsoft have supplied a KB for use admins centred around deployment, which is available here.

The following has mostly come from the above, just expanded upon a little further.

So, I can now just deploy Microsoft Office from the Mac App Store?

Well, no.. or maybe.. erm, it’s not quite that simple.

There are a few things to be mindful of beforehand.


Office 365 is the version of the Office suite which is available via the Mac App Store.

If you see the versioning section in my previous post on Microsoft Office, I mention the version 16.17+ being for both 2019 & O365. This is still correct but see below for a difference.


Whilst these Mac App Store apps are the same version as the “2019” suite, the Mac App Store Office Apps cannot be volume license as per:

No. Perpetual licenses, including Office 2019 and Office 2016, are not supported with Office apps available from the Mac App Store. The Volume License (VL) Serializer is not compatible with these apps. Attempts to use a perpetual license with Mac App Store apps will cause the apps to enter reduced functionality mode.

Operating System Support

Again, in my previous post I mention which versions of the Office Suite support which versions of macOS.

And above I mentioned that, we’re looking at the current O365 version of the Office Suite.

So, it should make sense that the O365 apps available on the App Store support 10.12+ & up.

If you support older OS’s, (why?), then these are not for you.


Ok, so you’ve reviewed the above & still wish to go through with your deployment. Below are some more things to bear in mind.


As we’re talking about apps available on the Mac App Store, you’ll need an MDM/EMM to deploy these apps via VPP.

Another item to mention here is that VPP cannot do “Suites”, so instead of deploying the Office 365 Suite you’ll need to deployment the component apps one-by-one.

Migrating to the Mac App Store Office Apps

If you are already deploying O365 & wish to move to deploying the Apps via VPP, I’m afraid it’s not as simple as deploying the VPP apps on top.

Microsoft do mention this in a section of their KB, which I’ve quoted below:

There is no automated process for performing a CDN to Mac App Store conversion. Depending on your EMM’s capabilities, you may be able to orchestrate the process through a script. The high-level steps for each Mac are as follows:
1. Close all Office apps
2. Remove the Office apps from the /Applications folder
3. Remove the Office entries from the keychain
4. Remove the Office package registrations (pkgutil --forget)
5. Trigger the MDM server to install the Office apps (such as jamf recon)

The majority of the above is simple enough, but step 3 refers to items on the User Keychain.

Paul Bowden has a script which can be used for this, but depending on if a deployment is multi-user etc this might become a little complex. Especially if you’re looking to logout then perform the steps 2-5 above.

At dataJAR, I’ve tasked Darren with looking into this & if an elegant workflow is found he’ll post it on his blog.


If you’re not sure how the Office Apps installed on your devices were installed, Microsoft do note the following:

• Open Finder, and navigate to the Applications folder
• Locate the Office app (such as Microsoft, control-click, and choose Show Package Contents
• Navigate into the Contents folder
• If a folder named _MASReceipt is present, the app was downloaded from the Mac App Store

Reduced Functionality Mode

A valid O365 subscription is needed to be able to edit documents in Word, Excel & PowerPoint, or to send emails within Outlook.

This is important as you might deploy the O365 apps to a Mac, but those apps might not be activated via a valid subscription.

This might be due to the O365 apps not being activated by that user.

Or the VPP apps have been deployed to a Mac with a Volume License or a Volume License has been deployed post VPP app install.

Microsoft has another article on this, & you have two options if the above is the issue. Which depends on the end goal license:

  1. O365: Completely remove the Office Apps & keychain etc, as per these steps, then reinstall from the Mac App Store & activate via a valid O365 license.
  2. 2019: Completely remove the Office Apps installed from the Mac App Store, & re-install the “CDN” versions, as per these steps.

So, what to do?

Well, at dataJAR, we are going to leverage VPP for all new O365 deployments.

For those we’ve historically deployed O365 apps from the “CDN” media, as the migration steps seem a bit of a faff & the end-user is getting the same versions, we’ll leave them as they are.

We’ll then review this if the migration steps become simpler.

2 thoughts on “Deploying Microsoft Office from the Mac App Store

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.