Intune

Overview When the Intune Management Extension (IME) finishes running a Win32 app’s install command, it does two things with the result: it reads the process exit code to decide whether the install succeeded, failed, needs a retry, or asked for a reboot, and it applies the restart behavior you configured on the Program tab. Together … Read more

Overview When you assign a Win32 app in Intune, the single most important choice is the assignment intent: Required or Available. Required pushes the app to targeted users or devices automatically, with no user action. Available publishes the app to Company Portal so the user decides when (or whether) to install it. A third intent, … Read more

Overview Device sync is how a managed Windows device contacts Microsoft Intune to pull down current policy, app assignments, configuration profiles, and compliance state, and to report results back. Understanding the timing of that check-in is the difference between thinking a deployment is broken and knowing it simply has not been picked up yet. This … Read more

Overview Company Portal is the end-user side of Microsoft Intune app deployment. It is the app and website where users browse, install, and check the status of work apps that your organization has published to them. Understanding what users actually see in Company Portal helps you set expectations, validate pilots, and answer the most common … Read more

Overview A Win32 app that shows as Failed, Not installed, or Waiting in Intune is reporting a symptom, not a cause. The fastest way to fix it is to walk the same pipeline the device follows: targeting and assignment, requirement rules, content download, the install command and its return code, the detection rule, and finally … Read more

Overview The Intune Management Extension (IME) logs are the device-side record of everything that happens during Win32 app and PowerShell-script processing. They show whether a device received policy, evaluated requirements, checked detection, ran the install command, captured the exit code, and reported the result back to Intune. When the admin center says “Failed” or “Not … Read more

Overview Most Win32 app deployments that report a failure in Intune are not broken in the cloud at all. The package uploaded fine and the assignment is in place, but something on the device, in the install command, or in the detection logic prevents Intune from recording a clean success. Knowing the handful of causes … Read more

Overview A detection rule is how Intune answers a single question on every device that receives a Win32 app: is this app already installed? When the rule says yes, Intune leaves the device alone instead of running the installer again. When it says no, Intune runs the install command. That one signal also drives the … Read more

Overview Requirement rules are the gate that decides whether a Windows device is even eligible to receive a Win32 app. They are evaluated before detection rules run and before the install command is ever launched, so a device that fails its requirements is simply passed over: the app is filtered out and the install command … Read more

Overview A Win32 app is the application type Microsoft Intune uses to deploy classic Windows desktop software, the kind that ships as an EXE or MSI installer rather than from the Microsoft Store. It is the most capable app type in Intune because it gives you full control over how the software is packaged, installed, … Read more