Anyone deploying applications with Intune faces a choice between Line-of-Business (LOB) and Win32 apps. This decision impacts not only the technical implementation, but also the maintainability, flexibility, and stability of the deployment.
Differences such as detection rules, supersedence, or dependencies are crucial in many scenarios – especially for automated deployments across multiple locations, device groups, or user segments, for example, in conjunction with Autopilot.
This article highlights the differences between LOB and Win32 apps for software distribution with Microsoft Intune and when each format makes sense.
Key Takeaways
- LOB apps are suitable for simple software deployments, but offer limited features and configuration options.
- Win32 apps support detection rules, dependencies, and supersedence and are therefore significantly more flexible and powerful.
- Mixing LOB and Win32 apps can lead to conflicts in certain Autopilot scenarios, but is supported with Windows Autopilot Device Preparation.
- In enterprise environments, many administrators opt for Win32 apps, as they better support complex deployments and long-term maintainability.
1 The Choice Between Line-of-Business (LOB) App and Win32 App in Microsoft Intune
When administrators in Microsoft Intune when adding a new application, several app types are available. These include, for example, Microsoft Store Apps, Web links, Built-in Apps, or Enterprise App Catalog entries. These options cover various scenarios – such as store applications, simple links to web applications, or Microsoft-provided software.
However, the situation is different for traditional enterprise software. Many applications come from third-party vendors, are deployed outside the Microsoft Store, and require individual integration into the corporate environment. For these specific cases, Intune offers two key options: Line-of-Business (LOB) Apps and Win32 Apps.
Administrators are therefore faced with a fundamental decision when integrating such applications: Which of these two app types is the better choice for deployment?
Since both options are relevant for distributing traditional desktop software, this article focuses on the differences between LOB and Win32 apps and their practical use.
2 What is a Line-of-Business (LOB) App?
Line-of-Business (LOB) Apps are applications used internally within an organization or specifically developed for it. In Microsoft Intune, these apps can typically be deployed directly via MSI or APPX files – without additional wrappers, scripts, or complex configurations.
The main advantage is their quick and straightforward deployment, especially for simple software packages. However, LOB apps in Intune quickly encounter functional limitations. They lack advanced features such as Detection Rules, Supersedence, or dependency control.
- Detection Rules: Define how Intune detects whether an application has already been installed. This enables more reliable control of installations and prevents unnecessary re-installations.
- Supersedence: Enables the automatic replacement or update of existing software versions. This allows older versions to be uninstalled in a controlled manner and replaced with new ones.
- Dependency Management (Dependencies): Ensures that required components or applications are automatically installed before the actual installation. This significantly simplifies the management of complex software packages and application environments.
LOB apps are therefore particularly suitable for standardized, low-complexity setups – where simplicity and speed are more important than flexibility or scalability.
3 What is a Win32 App?
Win32 apps are the classic and most powerful deployment format in Microsoft Intune – especially for complex or scalable deployment scenarios. They are based on an installation set that, with the tool IntuneWinAppUtil is packaged into the .intunewin format. This allows almost all common installer types (MSI, EXE, scripts) to be processed.
The format offers extensive control options: individual installation and uninstallation commands, custom detection rules, defined return codes, dependency management, and supersedence for automatically replacing older versions. Additionally, Win32 apps can be time-controlled, specifically distributed (e.g., via Delivery Optimization), and adapted to different device configurations.
4 Technical Differences at a Glance
LOB apps are among the older deployment formats in Intune. Before Win32 apps were supported via the Intune Management Extension, primarily MSI and APPX installations could be uploaded directly as Line-of-Business apps. Win32 is therefore the newer and significantly more flexible option.
The choice between LOB and Win32 apps in Intune isn't just a matter of format – it determines the available features in the deployment process. LOB apps use native Intune functions for deployment but offer limited control. There's no way to define individual installation parameters, automatically replace versions, or implement complex detection logic.
Win32 apps, on the other hand, allow complete control over the installation process. Custom parameters enable the handling of almost all installer types – whether EXE, MSI, or scripts. Features like Detection Rules, Supersedence, Dependencies, Return Codes, and Time Control provide precise management.
However, Delivery Optimization is not an exclusive Win32 feature; it's a Windows mechanism for optimized content distribution. With Win32 apps, download priority can also be controlled specifically for each app.
The decision for or against a format thus influences not only "how" the installation is done but also its maintainability, automation, and scalability.
Comparison: LOB vs. Win32 Deployment
5 Why you shouldn't carelessly mix LOB and Win32 apps
Although it's technically possible to use LOB and Win32 apps in parallel in Intune, administrators should be fully aware of the implications. Conflicts can arise during installation, especially with MSI-based LOB apps.
In the classic Windows Autopilot scenario, deploying Win32 and LOB apps simultaneously can lead to issues. One reason is that both installation mechanisms can access the Windows Installer or the Trusted Installer. This results in failed or stuck installations during the enrollment process. Microsoft therefore continues to point out that mixing both app types in classic Autopilot can be problematic.
The situation is different with Windows Autopilot Device Preparation (Autopilot V2). Here, Microsoft explicitly supports the joint deployment of Win32 and LOB apps. The modified processing logic significantly reduces the known conflicts. In another blog post, we will delve deeper into the Differences between Autopilot V1 and V2 one.
Regardless, many Intune administrators today consistently rely on Win32 apps as much as possible. The reason is less about Autopilot limitations and more about the additional features and the resulting greater flexibility in packaging. Therefore, anyone using both formats should do so consciously and with clear use cases.
6 Conclusion: Decision-making aid for the right app deployment
The choice between LOB and Win32 apps should always be made based on technical requirements – not out of habit or convenience. LOB apps score with easy handling but are functionally very limited. Win32 apps offer significantly more control, scalability, and stability- This applies especially in professional and automated environments.
For long-term maintainable deployments with Microsoft Intune, the Win32 format is in most cases the future-proof choice. Those who follow clear rules, avoid mixed formats, and use packaging tools strategically ensure smooth processes – from testing to productive rollout.
Also as part of our Intune Consulting we rely almost exclusively on the Win32 format in customer projects within the upper mid-market and enterprise sectors – due to its flexibility, configurability, and future-proofing in complex IT landscapes.
Since 2011, Thore has focused exclusively on endpoint management and endpoint security topics. Initially focused on software packaging and software distribution with Microsoft MECM/SCCM and Ivanti DSM, he is now a sought-after interlocutor when it comes to unified endpoint management, system hardening, patch management and endpoint protection. The focus is in particular on the Microsoft technologies Intune, Configuration Manager, Entra and Defender. Thore is co-founder of the “Endpoint Management” expert group at IAMCP e.V.
Years of Experience
Managed Endpoints
