(Weird though that Microsoft sends an ‘exe’ file instead of an ‘msi’.)įinally, we imported the Firewall O365 settings (they were available for import) and activated them, and the installations became available for the endusers.If your goal is to restrict the usage of Office applications on non-managed devices and only allow Web access in limited mode (as explained in my article: Limit Access to Outlook Web Access, SharePoint Online and OneDrive using Conditional Access App Enforced Restrictions) you might ask yourself if you want the Office applications to be downloadable from the different portals. This was an error we couldn’t find any information over in the Microsoft Docs, neither did Google offer any help.Īfter some troubleshooting, I noticed that the firewall tried to download an ‘exe’ file and it was blocked. We then deployed it to our pilot group, but all of the O365 App package deployments went into failure with the following error code: Now the next step was creating an O365 Suite App package in Intune: You can just follow the guide, and click the Apps you want in your package, choose the Language, Installation settings, …Īt the end of the customization tool, you can download your custom XML and ours looks like this: It’s easy to work with and you can copy the XML in your Intune O365 package. Deploying the whole O365 suite (Teams included) to all Hybrid Joined Intune MDM managed devicesĬ: you can make a custom config installation XML through that site.O365 Suite was already installed on certain computers, but not the whole suite.
Migrated to Hybrid Joined Intune MDM managed devices.
0 kommentar(er)
