Support Tip: Deploying Visio and Project as part of your Office Pro Plus Deployment

[Intune_Support_Team]

As we continue driving improvements to the Office Pro Plus deployment experience in Intune, we were recently alerted to a conflicting policy scenario. We’re working to adjust the experience, but know that it may take a few sprints to reach resolution.

If a user is targeted with more than one Office Pro Plus policy, only one of those will get delivered to an end users' device. Here is one such scenario you may have seen. A group of users are targeted Office Pro Plus as a required install on the device. Now, you want to make Visio and/or Project available to a subset of those users as an optional install. Install can only happen to one of those suites; in this case the required install only. IT Admins and end users may see error code 0x87D1041E in their respective portals.

Short term, you can bundle Office Pro Plus and Visio/Project as required in one policy, which will then ensure that Visio and Project are available for your end users. Alternatively you can create a policy to make Office Pro Plus with Visio/Project as available. However, keep in mind that all Office apps will need to be closed for your end user to go download Visio or Project from the Company Portal.

We’ll update this post and What’s New when there’s an updated experience released.

[ParameswaraRao Chaganti]

What took you guys so long? This is such an inconvenience for large organisations where Office is distributed to large set of users as a Core application Vs Project & Visio to small set of users. If Office Pro Plus is already installed on the device, are you guys advising to uninstall Office ProPlus and reinstall Office ProPlus + Visio?    

[Josh Hammond]

We were told by Microsoft legal/compliance that we could not deploy O365 w/ Visio and Project to all of our users. Even though it would be in limited functionality mode, they said it would be against EULA to have them installed on a non licensed users PC. Has this POV changed?

[David Wanderer]

I’ve found when we deploy Office Pro Plus to our M365B users, the licensing eventually syncs up and they would have Office 365 Business.  However, when we add MS Project to the install package, the Office 365 Business licensing changes back to ProPlus thus causing an invalid licensing situation since the users have M365 Business which doesn’t come with ProPlus.

Thw workaround has been to uninstall all instances manually including running some cscript to remove invalid keys.  Reboot.  Install o365 from the portal(manually) and then do the same manual step for MS Project..  

‘We’ve since disabled the intune deployment for Office which is a shame because it used to work great!

[ParameswaraRao Chaganti]

… and now we have a new issue...TEAMS...missing from the Office Pro Plus deployment. For Office Pro Plus, the update channel was set to "semi-annual" and looks like this is causing TEAMS failure to install along with Office. 

Give me few more days...and I'm pretty sure I will come back with few more issues. Thank you Microsoft Team/s.   

[kimmedi]

2 months past - any news on this issue? @Intune_Support_Team 

[Steve Parankewich]

What you do is create an Office + Visio group that includes Office and Vision and then create an Exclude with that group on your Normal just Office package. This has always been working as designed and is very annoying. It should be additive.

[SvenKoeppel]

Still the same issue here. When do you fix this? @Intune_Support_Team 

[Marcus Giles]

This *still* isnt fixed?!

[Paul Forbing]

I just ran into this today trying to setup a separate Visio install policy.  I ran across this recent article and my initial testing has been successful. 

Deploy Visio or Project with Intune to users with Microsoft 365 apps already installed. – Mobile-Fir...

[Aditya_sharma]

Musa vrail hona ha please 

[Matthias Vandenberghe]

+2y later and it seems this still isn't fixed....

When office 365 apps are already installed on the device, and the user wants to install Visio or Project which is available via the company portal, it still fails because the other apps aren't closed...

The only solution now is to not use the Intune policies for Microsoft 365 apps, but to use a win32app package using the AppDeploy toolkit so the closure of the opened M365 is handled correctly... the standard policies in intune are useless...

When will this be fixed?

I tried both with configuration designer, and the XML config, all with the same result. This is really disappointing.