ANAVEM
Languagefr
How to Deploy Windows Apps to Devices Using Microsoft Intune 2026

How to Deploy Windows Apps to Devices Using Microsoft Intune 2026

Deploy Windows applications to enterprise devices using Microsoft Intune admin center. Configure Store apps, assign to user groups, and automate installation across your organization.

March 29, 2026 15 min
mediumintune 9 steps 15 min

Why Deploy Apps Through Microsoft Intune?

Microsoft Intune provides enterprise-grade application deployment capabilities that streamline software distribution across your Windows device fleet. Instead of manually installing applications on each device or relying on users to download software themselves, Intune automates the entire process while maintaining security and compliance standards.

The platform supports multiple app types including Microsoft Store applications, line-of-business (LOB) apps, and Win32 applications. For 2026, Microsoft has enhanced the "Microsoft Store app (new)" deployment method, which offers improved reliability and automatic update management compared to traditional deployment methods.

What Makes Intune App Deployment Different in 2026?

Recent updates to Microsoft Intune have introduced significant improvements to app deployment workflows. The new Store app integration provides better detection rules, enhanced reporting, and support for both user and device context installations. Device context installations are particularly valuable for organizations that need applications available immediately after device enrollment, without waiting for user sign-in.

The deployment process now supports priority rules where device context overrides user context, and install intents override uninstall intents. This gives administrators more granular control over application lifecycle management across diverse device scenarios.

What Will You Accomplish?

By following this tutorial, you'll master the complete workflow for deploying Windows applications through Microsoft Intune. You'll learn to configure app assignments, target specific user or device groups, monitor deployment success rates, and troubleshoot common installation issues. The skills you develop here apply to deploying any Microsoft Store application across your enterprise environment, from productivity tools like Microsoft Teams to specialized business applications.

Implementation Guide

Full Procedure

01

Access Microsoft Intune Admin Center

Start by signing into the Microsoft Intune admin center where you'll manage all app deployments.

Open your browser and navigate to endpoint.microsoft.com. Sign in with your admin credentials that have Intune administrator permissions.

Once logged in, navigate to Apps in the left sidebar, then click All apps. This shows your current app inventory.

Pro tip: Bookmark the direct URL https://endpoint.microsoft.com/#view/Microsoft_Intune_DeviceSettings/AppsMenu/~/overview for quick access to the apps section.

Verification: You should see the Apps dashboard with options to add new applications and view existing deployments.

02

Add a New Microsoft Store App

Now you'll add a Windows app from the Microsoft Store to your Intune app catalog.

Click the Add button at the top of the All apps page. In the app type dropdown, select Microsoft Store app (new).

You have two options to find your app:

  • Search method: Click Search the Microsoft Store app (new) and enter your app name
  • Store URL method: If you have the Microsoft Store URL, paste it directly

For this example, let's deploy Microsoft Teams. Search for "Microsoft Teams" and select the official Microsoft Teams app from the results.

App Name: Microsoft Teams
Publisher: Microsoft Corporation
Category: Business

Verification: The app details should populate automatically, showing the app icon, description, and publisher information.

03

Configure App Information and Settings

Configure the app details and installation behavior before deployment.

On the App information tab, review and modify these fields:

  • Name: Keep the default or customize (e.g., "Microsoft Teams - Corporate")
  • Description: Add deployment notes for your organization
  • Publisher: Usually auto-populated
  • Category: Select appropriate category (Business, Productivity, etc.)

Click Next to proceed to the Assignments tab. The system will automatically handle installation and detection rules for Microsoft Store apps.

Warning: Don't modify the app package name or identifier unless absolutely necessary, as this can break automatic updates from the Microsoft Store.

Verification: Ensure all required fields are populated and the app category matches your organization's app catalog structure.

04

Create and Configure Target Groups

Before assigning the app, ensure you have the appropriate Azure AD groups configured for your deployment.

Open a new browser tab and navigate to portal.azure.com. Go to Azure Active Directory > Groups.

Create a new group for your app deployment:

Group Type: Security
Group Name: Teams-Deployment-Pilot
Membership Type: Assigned
Members: Add your pilot users or devices

For device-based deployments, create a device group:

Group Type: Security
Group Name: Corporate-Windows-Devices
Membership Type: Dynamic Device
Dynamic Query: (device.deviceOSType -eq "Windows")
Pro tip: Use dynamic groups with device queries to automatically include new devices that meet your criteria, reducing manual management overhead.

Verification: Return to the Azure AD Groups page and confirm your new groups appear with the correct member count.

05

Assign App to Target Groups

Now assign the Microsoft Teams app to your configured groups with the appropriate installation intent.

Back in the Intune admin center, on the Assignments tab, click Add group.

Configure the assignment:

  • Assignment type: Choose between:
    • Required: App installs automatically
    • Available for enrolled devices: Users can install from Company Portal
  • Included groups: Select your target group (e.g., "Teams-Deployment-Pilot")

For automatic deployment, select Required and choose your user or device group:

Assignment Type: Required
Included Groups: Teams-Deployment-Pilot
Install Context: User context (default for Store apps)
Notifications: Show all toast notifications

Click Next to review your configuration.

Warning: Required assignments will force-install the app on all targeted devices. Test with a small pilot group first to avoid widespread issues.

Verification: The assignment should show your selected group with the correct assignment type in the summary.

06

Review and Create the App Deployment

Review all configuration details before finalizing the deployment.

On the Review + create tab, verify these key settings:

  • App name and publisher information
  • Assignment groups and types
  • Installation context (user vs device)
  • Notification settings

If everything looks correct, click Create to deploy the app.

The system will process your deployment and return you to the All apps page where you'll see your new app listed.

Status: Creating...
Assignments: 1 group (Required)
Install Status: Processing

Verification: Your app should appear in the All apps list with a "Creating" or "Active" status. The deployment typically takes 2-5 minutes to process.

07

Monitor Deployment Status and Results

Track the deployment progress and troubleshoot any installation issues.

Click on your deployed app from the All apps list to open its details page. Navigate to Monitor > Device install status.

Here you'll see deployment metrics:

  • Installed: Successful installations
  • Failed: Installation failures with error codes
  • Pending: Devices that haven't processed the policy yet
  • Not applicable: Devices outside the assignment scope

For detailed troubleshooting, click on individual devices to see specific error messages:

Common Status Codes:
0x80073D02: App already installed
0x80073CF3: Package installation failed
0x80073D01: App not found in store

You can also check User install status to see per-user deployment results.

Pro tip: Set up automated email reports by going to Reports > App install status and configuring scheduled reports for your management team.

Verification: Run this PowerShell command on a target device to confirm the app installed: Get-AppxPackage | Where-Object {$_.Name -like "*Teams*"}

08

Configure Advanced Deployment Options

Optimize your deployment with advanced settings for better control and user experience.

Return to your app's configuration by clicking Properties from the app details page. Here you can modify:

Installation Context Options:

  • User context: Installs when user signs in (default for Store apps)
  • Device context: Installs immediately on device (requires device groups)

For immediate deployment without waiting for user sign-in, change to device context:

Installation Context: Device
Target: Device Groups Only
Behavior: Install immediately after policy sync

Notification Settings:

  • Show all toast notifications: Users see installation progress
  • Show toast notifications for computer restarts only: Minimal notifications
  • Hide all toast notifications: Silent installation
Warning: Device context installations require targeting device groups only. Assigning to user groups will result in the error "A user can't be targeted with a device context install."

Verification: Save changes and monitor the deployment status to ensure the new settings take effect within the next sync cycle (typically 8 hours or on-demand).

09

Test and Validate App Functionality

Verify the deployed app works correctly on target devices and troubleshoot common issues.

On a test device from your target group, check the installation:

# Check if app is installed
Get-AppxPackage -Name "*Teams*" | Select-Object Name, Version, InstallLocation

# Verify app can launch
Start-Process "ms-teams://"

# Check Windows Event Logs for installation issues
Get-WinEvent -LogName "Microsoft-Windows-AppXDeployment/Operational" | Where-Object {$_.TimeCreated -gt (Get-Date).AddHours(-2)}

Test key functionality:

  • App launches without errors
  • User can sign in with corporate credentials
  • App receives automatic updates from Microsoft Store
  • Uninstall works correctly (if needed)

For troubleshooting failed installations, check the Company Portal app on the device or use Intune's remote diagnostics:

Common Issues:
- Device not synced: Force sync in Settings > Accounts > Access work or school
- Store connectivity: Check Microsoft Store app functionality
- Group membership: Verify user/device is in assigned groups
Pro tip: Create a test checklist document that includes app functionality verification steps specific to your organization's use cases.

Verification: Document successful installation on at least 3 test devices before expanding to larger groups. Check that automatic updates work by monitoring the app version over time.

Frequently Asked Questions

What's the difference between user context and device context app installation in Intune?+
User context installations occur when a user signs into the device and are tied to the user's profile. Device context installations happen immediately after the device syncs with Intune policies, regardless of user sign-in status. Device context requires targeting device groups only and is ideal for applications that need to be available immediately after device enrollment or for shared devices.
Can I deploy custom LOB applications alongside Microsoft Store apps in Intune?+
Yes, Intune supports multiple app types simultaneously. You can deploy Microsoft Store apps (new), line-of-business APPX/MSIX packages, and Win32 applications (.msi or .intunewin files) to the same device groups. Each app type has different requirements - LOB apps support both user and device context, while Win32 apps typically require device context and silent installation parameters.
How long does it take for apps to install on devices after Intune deployment?+
App installation timing depends on several factors. Device policy sync occurs every 8 hours by default, but can be forced manually. User context apps install during the next user sign-in after policy sync. Device context apps install immediately after policy sync. Microsoft Store apps typically download and install within 5-15 minutes once the installation process begins, depending on app size and network connectivity.
What should I do if app deployment fails with error code 0x80073CF3?+
Error 0x80073CF3 indicates a package installation failure, commonly caused by insufficient device storage, corrupted app package, or conflicting existing installations. First, verify the device has adequate storage space and the Microsoft Store app is functioning. Try uninstalling any existing versions of the app, restart the device, and force a policy sync. If the issue persists, check the Windows Event Logs under Microsoft-Windows-AppXDeployment/Operational for detailed error information.
How can I prevent users from uninstalling required apps deployed through Intune?+
Configure app protection policies in Intune to prevent uninstallation of required applications. Go to Apps > App protection policies and create a policy targeting your user groups. Enable the 'Prevent app uninstall' setting for required apps. Additionally, you can use device compliance policies to detect and automatically reinstall removed applications during the next policy sync cycle. For critical business applications, consider using device context deployment which provides stronger installation persistence.

Discussion

Share your thoughts and insights

Sign in to join the discussion