ANAVEM
Languagefr
How to Deploy Google Chrome on macOS Devices Using Microsoft Intune

How to Deploy Google Chrome on macOS Devices Using Microsoft Intune

Deploy Google Chrome browser across your macOS fleet using Microsoft Intune's Line-of-Business app deployment. Complete setup from PKG download to monitoring installation status.

March 29, 2026 15 min
mediumintune 8 steps 15 min

Why Deploy Chrome Through Microsoft Intune?

Managing browser deployments across a macOS fleet requires a centralized approach that ensures consistency, security, and compliance. Microsoft Intune provides enterprise-grade application deployment capabilities that integrate seamlessly with your existing device management infrastructure.

Deploying Google Chrome through Intune offers several advantages over manual installation methods. You gain centralized control over which devices receive Chrome, can enforce installation requirements, and monitor deployment success across your entire macOS fleet. This approach eliminates the need for individual device visits or complex scripting solutions.

What Makes macOS App Deployment Different in Intune?

macOS app deployment in Intune has evolved significantly, with Line-of-Business (LOB) apps using PKG installers becoming the preferred method over DMG files. The PKG format provides better silent installation capabilities and more reliable detection mechanisms, which are crucial for enterprise deployments.

Modern Intune deployments support macOS 12.0 (Monterey) and later, taking advantage of enhanced MDM capabilities and improved sync performance. The platform now offers better detection rules, more granular assignment options, and improved monitoring capabilities specifically designed for macOS environments.

How Does Chrome Enterprise Integration Work?

Google Chrome's enterprise features integrate well with Intune's management capabilities. Once deployed, you can use additional configuration profiles to manage Chrome policies, configure auto-updates, and enforce security settings across your organization.

This tutorial walks you through the complete process: from downloading the Chrome PKG installer to monitoring successful deployment across your macOS devices. You'll learn to configure detection rules, set up proper assignments, and verify that Chrome is working correctly on managed devices.

Implementation Guide

Full Procedure

01

Download Google Chrome Enterprise PKG Installer

First, you need to obtain the Chrome PKG installer file. While Google provides DMG files, PKG installers work more reliably with Intune's silent deployment mechanism.

Navigate to the Chrome enterprise download page or use the direct PKG link:

curl -L -o GoogleChrome.pkg "https://dl.google.com/chrome/mac/stable/googlechrome.pkg"

Alternatively, download from the web interface at https://www.google.com/chrome/ and select the Mac version. If you get a DMG file, mount it and extract the PKG:

hdiutil mount GoogleChrome.dmg
cp "/Volumes/Google Chrome/Google Chrome.pkg" ./GoogleChrome.pkg
hdiutil unmount "/Volumes/Google Chrome"
Pro tip: Always download the latest stable version. Chrome's current stable release is 123.0.6312.106 as of March 2026, but check for updates at download time.

Verification: Check the PKG file size (should be around 200MB) and verify it's not corrupted:

ls -lh GoogleChrome.pkg
file GoogleChrome.pkg
02

Access Microsoft Intune Admin Center

Sign into the Microsoft Intune admin center where you'll configure the app deployment. This is the central hub for all Intune management tasks.

Open your browser and navigate to:

https://endpoint.microsoft.com/

Sign in with your admin credentials. Once logged in, navigate to the Apps section:

1. Click Apps in the left navigation pane
2. Select All apps
3. Click the + Add button to start creating a new app deployment

You should see the app type selection screen. This is where you'll specify that you're deploying a macOS application.

Warning: Ensure you have the correct permissions. You need either Global Administrator or Intune Service Administrator role to deploy apps.

Verification: Confirm you can see the "Add app" interface and the app type dropdown menu is accessible.

03

Configure macOS Line-of-Business App

Now you'll create the app deployment configuration. Select the correct app type for macOS PKG files:

1. In the App type dropdown, select macOS app (DMG/PKG)
2. Choose Line-of-business app
3. Click Select

Upload your Chrome PKG file:

1. Click Select app package file
2. Browse and select your GoogleChrome.pkg file
3. Wait for the upload to complete (this may take 5-10 minutes depending on your connection)

Fill in the app information:

  • Name: Google Chrome
  • Description: Enterprise Chrome browser for macOS devices
  • Publisher: Google
  • Minimum operating system: macOS 12.0
  • Ignore app version: Yes (recommended for auto-updates)
Pro tip: Enable "Ignore app version" to allow Chrome's built-in auto-updater to work without Intune version conflicts.

Verification: Ensure the PKG file uploaded successfully and all required fields are populated before proceeding.

04

Set Up Detection Rules

Detection rules are crucial for Intune to determine if Chrome is successfully installed. Configure a file-based detection rule:

1. Click Next to reach the Detection rules section
2. Click + Add to create a new detection rule
3. Configure the rule with these exact settings:

  • Rule type: File
  • Path: /Applications/
  • File or folder: Google Chrome.app
  • Detection method: File or folder exists
  • Associated with a 32-bit app on 64-bit clients: No

For more robust detection, you can also add a version-based rule:

  • Rule type: File
  • Path: /Applications/Google Chrome.app/Contents/
  • File or folder: Info.plist
  • Detection method: File or folder exists
Warning: The path is case-sensitive. Use exactly /Applications/Google Chrome.app - any variation will cause detection failures.

Click Add to save the detection rule, then Next to continue.

Verification: Review that your detection rule shows the correct path and detection method before proceeding.

05

Configure Requirements and Dependencies

Set the system requirements for Chrome installation. This ensures the app only deploys to compatible devices:

In the Requirements section:

  • Operating system architecture: x64 (covers both Intel and Apple Silicon Macs)
  • Minimum operating system: macOS 12.0
  • Disk space required (MB): 500
  • Physical memory required (MB): 4096

Leave Dependencies empty unless you have specific requirements like VPN clients or security software that must be installed first.

For Return codes, keep the default settings:

  • Success: 0
  • Soft reboot: 1641
  • Hard reboot: 3010
  • Retry: 1618
Pro tip: The default return codes work for most macOS PKG installers. Chrome's installer follows standard macOS conventions.

Click Next to proceed to assignments.

Verification: Confirm the minimum OS version matches your environment's macOS deployment standards.

06

Assign Chrome to Device Groups

Configure which devices will receive Chrome. You can assign to all macOS devices or specific groups:

For organization-wide deployment:

1. Under Required, click + Add group
2. Search for and select All devices or your macOS device group
3. Set Assignment type to Required

For targeted deployment, create or select specific groups:

# Example: Target specific departments
# Marketing Macs
# Development Team Macs
# Executive Devices

Configure assignment settings:

  • Make this app required for all users: Yes
  • Install behavior: Install as system
  • Notification: Show all toast notifications

Set the deployment schedule:

  • Available: As soon as possible after assignment
  • Installation deadline: As soon as possible
Warning: Required assignments will force installation. Use Available assignments for optional software to give users choice.

Verification: Review your group assignments and ensure the correct devices are targeted before creating the deployment.

07

Deploy and Monitor Installation

Complete the app creation and monitor the deployment across your macOS fleet:

1. Review all settings on the final screen
2. Click Create to deploy Chrome
3. Wait for the app to sync (typically 5-10 minutes)

Monitor deployment status:

Navigate to Apps > All apps > Google Chrome > Device install status

You'll see installation progress across devices:

  • Installed: Chrome successfully deployed
  • Installing: Deployment in progress
  • Failed: Installation encountered errors
  • Not applicable: Device doesn't meet requirements

Force device sync for immediate deployment:

1. Go to Devices > All devices
2. Select a macOS device
3. Click Sync to trigger immediate policy refresh

Pro tip: macOS devices check in with Intune every 8 hours by default. Use the Sync button for immediate deployment during testing.

Verification: Check that Chrome appears in /Applications/ on target devices and launches successfully:

ls -la "/Applications/Google Chrome.app"
open "/Applications/Google Chrome.app"
08

Verify Installation and Configure Auto-Updates

Confirm Chrome is properly installed and configure ongoing management:

On managed macOS devices, verify the installation:

# Check Chrome version
"/Applications/Google Chrome.app/Contents/MacOS/Google Chrome" --version

# Verify app bundle integrity
spctl -a -v "/Applications/Google Chrome.app"

# Check if Chrome is running
ps aux | grep -i chrome

Configure Chrome auto-updates by deploying a configuration profile. Create a Custom Configuration Profile in Intune:

1. Go to Devices > Configuration profiles > + Create profile
2. Select macOS platform and Custom profile type
3. Add this configuration:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
    <key>PayloadContent</key>
    <array>
        <dict>
            <key>PayloadType</key>
            <string>com.google.Chrome</string>
            <key>PayloadVersion</key>
            <integer>1</integer>
            <key>PayloadIdentifier</key>
            <string>com.company.chrome.settings</string>
            <key>UpdatesSuppressed</key>
            <false/>
        </dict>
    </array>
</plist>

Monitor ongoing compliance through Intune reporting:

  • Device compliance: Check Chrome remains installed
  • App protection: Monitor for unauthorized removals
  • Update status: Track Chrome version across fleet

Verification: Confirm Chrome auto-updates are working by checking the version after a few days and ensuring it matches the latest stable release.

Frequently Asked Questions

Can I deploy Chrome to macOS devices without using the PKG installer format?+
While Intune supports DMG files, PKG installers are strongly recommended for Chrome deployment on macOS. DMG files often fail during silent installation because they require mounting and manual extraction. PKG files integrate natively with macOS installer mechanisms and provide more reliable deployment success rates. Google provides both formats, but enterprise deployments should always use the PKG version for better Intune compatibility.
What happens if Chrome auto-updates conflict with Intune version detection?+
Enable the 'Ignore app version' setting during app configuration to prevent conflicts between Chrome's built-in auto-updater and Intune's version tracking. This allows Chrome to update itself automatically while maintaining Intune's installation detection. You can also deploy a configuration profile to manage Chrome's update behavior, including setting update channels (stable, beta, dev) and controlling update timing across your organization.
How long does it take for Chrome to deploy to macOS devices through Intune?+
Chrome deployment timing depends on several factors: Intune policy sync intervals (every 8 hours by default), device online status, and network bandwidth. Initial deployment typically takes 15-30 minutes after assignment, but can extend to 8 hours if devices haven't checked in recently. You can force immediate deployment by using the 'Sync' button on individual devices in the Intune admin center, which triggers an immediate policy refresh and app installation.
Why do some macOS devices show 'Not Applicable' status for Chrome deployment?+
The 'Not Applicable' status typically indicates devices don't meet the deployment requirements you configured. Common causes include: macOS version below the minimum requirement (12.0), insufficient disk space (less than 500MB), inadequate RAM (less than 4GB), or devices not properly enrolled in Intune MDM. Check device compliance status and ensure all target devices meet the system requirements specified in your Chrome app deployment configuration.
Can I deploy Chrome with pre-configured enterprise policies through Intune?+
Yes, deploy Chrome first using the LOB app method, then create additional Custom Configuration Profiles targeting the com.google.Chrome domain to enforce enterprise policies. You can configure homepage settings, bookmark management, extension policies, security settings, and update behaviors. Create separate configuration profiles for different user groups or departments, allowing granular control over Chrome's behavior across your macOS fleet while maintaining centralized management through Intune.

Discussion

Share your thoughts and insights

Sign in to join the discussion