Add Office 365 Apps

Could you please add the products to remediate the below vulnerabilities in PatchMyPc?

1.Security Updates for Microsoft Excel Products C2R (May 2026) (314676)
2.Security Updates for Microsoft Office Products C2R (May 2026) (314675)

As this is in our top 10, just wanted to update everyone and reassure them that this is a topic that we come back to and revisit. By revisit, I of course mean we argue about internally.

We are pretty sure we understand the value: more reliable installs during Autopilot.

The amount of engineering to create and then maintain this one single app is admittedly daunting so it's been hard for us to commit to. We keep looking at it and deciding that we could add dozens of new apps to the catalog instead with the resources it will take to build this. However, as we keep knocking off stuff higher on the list, this one keeps climbing.

I realize that might not be super satisfying, just want you to know we've not forgotten.

Scappman was able to do it. Why are you not able to? In Scappman you could simply change the XML in the Pre-Installation process. It’s not nice as a former Scappman customer to migrate to a product which is a) more expensive and b) has less apps.

We are missing about 25 apps. Which is a huge drawback for us.

Due to the sheer volume of possible custom configurations for Office 365, it would be extremely difficult (if not impossible) for PMPC to handle detection of all such custom configurations. This particular app may be better suited for our Custom Apps feature.

wondering if this might still happen?

Very important. This would help alot

bump

inbuilt intune or configmgr for 365 deployment really isnt that great

https://brookspeppin.com/2020/03/20/how-to-deploy-office-365-with-ws1/

Would really be nice to have this. Using Pmpc to create the package and maintain the odt updated we really would just need to create the xml. Eventually storing and maintaining a share with the bits for a completely offline full installer and as a sources for updating clients

https://docs.vmware.com/en/VMware-Workspace-ONE-UEM/services/Software_Distribution/GUID-A00E59E6-29E3-4098-84AB-0753AC1DB960.html

interresting https://msendpointmgr.com/2022/10/23/installing-m365-apps-as-win32-app-in-intune/ but are still hoping pmpc will add this killer feature

+1

Would also be interesting in seeing this! Built-in 365 for Intune messes up ESP and using Win32 creates issues if office is already running.

To accommodate different instances could have multiple applications available?

• M365 Apps 1

• M365 Apps 2

• M365 Apps 3

• ...

Admins could then specify a different XML for each.

Custom detection methods would also be a nice-to-have for this app, due to all the varying configurations peoples might use. https://ideas.patchmypc.com/ideas/PATCHMYPC-I-2049

tesla incoming :P

i recommand

we are now also testing the intune integration… we need this now ^^

We would love to have a way to "get inbetween" O365 trying to go to the internet for these updates (which is traffic we don't want in our facilities internet pipes) and a way we can also better control approval. This would be AWESOME to do this in a more controlled manner via this channel

Yes please! Standard 365 Apps in Intune is flaky, to say the least.

maybe also add a sample base pmpc xml? i'm available for testing purposes ^^

<Configuration>

<Add SourcePath="\\patchmypc\Applications\Microsoft\Office 2019\x64" OfficeClientEdition="64" Channel="PerpetualVL2019" AllowCdnFallback="TRUE" ForceUpgrade="TRUE">

<Product ID="ProPlus2019Volume">

<Language ID="en-us" />

<Language ID="fr-fr" />

<Language ID="de-de" />

<Language ID="lb-lu" />

</Product>

<Product ID="VisioStd2019Volume">

<Language ID="en-us" />

<Language ID="fr-fr" />

<Language ID="de-de" />

<Language ID="lb-lu" />

</Product>

<Product ID="ProjectStd2019Volume">

<Language ID="en-us" />

<Language ID="fr-fr" />

<Language ID="de-de" />

<Language ID="lb-lu" />

</Product>

<Product ID="LanguagePack">

<Language ID="en-us" />

<Language ID="fr-fr" />

<Language ID="de-de" />

<Language ID="lb-lu" />

</Product>

<Product ID="ProofingTools">

<Language ID="en-us" />

<Language ID="fr-fr" />

<Language ID="de-de" />

<Language ID="lb-lu" />

</Product>

</Add>

<Property Name="PinIconsToTaskbar" Value="FALSE" />

<Updates Enabled="TRUE" />

<RemoveMSI />

<AppSettings>

<Setup Name="Company" Value="Patch My PC" />

</AppSettings>

<Display Level="None" AcceptEULA="TRUE" />

<Logging Level="Standard" Path="%temp%" />

<Property Name="FORCEAPPSHUTDOWN" Value="True" />

<Property Name="AUTOACTIVATE" Value="1" />

</Configuration>

Thats exactly how i supposed it to be implemented. Provide the odt binaries and we use our own custom xml configuration file with it. For starting i would already appreciate to have the possibility to only publish the base m365 apps configuration but yes the possibility to have multiple “configuration” available would be also neat but for now i think we can workaround it as you said with scripting. Yes i also dont see a need to check for specific versions for now.