> For the complete documentation index, see [llms.txt](https://docs.intunepckgr.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.intunepckgr.com/getting-started/creating-deployments/repositories/macos.md).

# MacOS

<figure><img src="/files/A0rZTENfWOtPjZ8Xp1OH" alt="" width="375"><figcaption></figcaption></figure>

## macOS

Pckgr supports deploying macOS applications through Microsoft Intune using two repository types.

When adding a macOS application, select the repository that best matches your deployment requirements.

The Private Mac Repository is currently in **Beta**.

We are actively expanding the application catalogue and adding new applications on an ongoing basis. Feedback is welcome and helps us prioritise improvements and new application requests.

| Repository               | Deployment Method                                                                   |
| ------------------------ | ----------------------------------------------------------------------------------- |
| Installomator Repository | Deploys applications using Installomator through Microsoft Intune shell scripts.    |
| Private Mac Repository   | Deploys applications as native Microsoft Intune macOS applications hosted by Pckgr. |

The primary differences between the two repository types are:

<table data-search="false"><thead><tr><th>Feature</th><th>Installomator Mac Repository</th><th>Private Mac Repository</th></tr></thead><tbody><tr><td><strong>Deployment type</strong></td><td>Bundled Installomator script deployed as an Intune shell script</td><td>Prepackaged application deployed as a native Intune macOS application</td></tr><tr><td><strong>Application source</strong></td><td>Downloaded from the software vendor during installation</td><td>Included in the deployment package</td></tr><tr><td><strong>Device dependencies</strong></td><td>GitHub (Installomator and swiftDialog) and the vendor's download servers</td><td>Microsoft Intune only</td></tr><tr><td><strong>Appears in Intune as</strong></td><td>macOS Shell Script</td><td>Native macOS Application</td></tr><tr><td><strong>User notifications</strong></td><td>Supported via swiftDialog</td><td>Not currently supported</td></tr><tr><td><strong>Update Only deployments</strong></td><td>Supported</td><td>Not available (Microsoft Intune limitation)</td></tr><tr><td><strong>Application updates</strong></td><td>Downloads the latest version each time the script runs</td><td>Pckgr rebuilds and republishes new application versions</td></tr><tr><td><strong>Availability</strong></td><td>Professional Plan and above</td><td>Business and Custom Plans</td></tr></tbody></table>

***

**Company Portal**

Both repository types support deployment through the Microsoft Intune Company Portal.

Applications can be configured as available deployments, allowing users to install approved software on demand.

For configuration instructions, see the [**macOS Company Portal**](/integrations/company-portal/macos-applications.md) documentation.

***

### Installomator Repository

**Overview**

The Installomator Repository deploys applications using Microsoft Intune shell scripts generated by Pckgr.

During deployment, the shell script executes the appropriate Installomator label, which downloads and installs the application directly from the software vendor.

Pckgr continuously monitors supported applications for new releases. When a new version becomes available, the deployment is automatically updated.

<details>

<summary>Implementation Steps</summary>

**Requirements**

Before deploying applications using the Installomator Repository:

* Your tenant must be connected through Policy Manager.
* Devices must be enrolled in Microsoft Intune.
* Devices must report as macOS within Intune.

Policy Manager provides the Microsoft Graph permissions required for Pckgr to create and manage the Intune shell scripts used for deployment.

**Deploying an application**

1. Open the **Application Library**.
2. Select **Add Application**.
3. Select **macOS**.
4. Select **Installomator** on the repository toggle.
5. Click the plus button next to an application to add to your library.
6. Click the three-dot menu and select deploy.
7. Configure your [deployment settings](/getting-started/creating-deployments/deployment-settings.md#macos-deployment-settings) and deploy the application.

Applications are created in Microsoft Intune under:

**Devices > macOS > Shell scripts**

**Application updates**

When a supported application releases a new version:

1. Pckgr detects the new release.
2. The updated deployment is validated.
3. The updated shell script is published to your Intune tenant.
4. Devices install the updated version during their next Intune check-in.

**Update Only deployments**

Installomator supports Update Only deployments.

This option updates devices where the application is already installed without deploying the application to devices that do not already have it installed.

</details>

***

### Private Mac Repository

**Overview**

The Private Mac Repository deploys applications as native Microsoft Intune macOS applications.

Applications are hosted by Pckgr and published directly to your Intune tenant. This deployment method does not use Installomator or require devices to access GitHub.

Pckgr continuously monitors supported applications for new releases. When a new version becomes available, a new application package is built, validated, and published automatically.

<details>

<summary>Implementation Steps</summary>

**Requirements**

Before deploying applications using the Private Mac Repository:

* Devices must be enrolled in Microsoft Intune.
* Devices must report as macOS within Intune.

**Deploying an application**

1. Open the **Application Library**.
2. Select **Add Application**.
3. Select **macOS**.
4. Enable the **Private Repository** toggle.
5. Click the plus button next to an application to add to your library.
6. Click the three-dot menu and select deploy.
7. Configure the [deployment settings](/getting-started/creating-deployments/deployment-settings.md#macos-deployment-settings).
8. Deploy to Intune.

Applications are created as native macOS applications within Microsoft Intune.

**Application updates**

When a supported application releases a new version:

1. Pckgr builds a new application package.
2. The package is validated.
3. The updated application is published to your Intune tenant.
4. Devices receive the update through Microsoft Intune.

**Update Only deployments**

Native macOS applications in Microsoft Intune do not support Update Only deployments.

This limitation is imposed by Microsoft Intune and applies to all vendors deploying native macOS applications through Intune.

If your deployment requires Update Only behaviour, use the Installomator Repository instead.

</details>

***

**Device Count and Billing**

macOS devices are not included in your licensed device count by default.

Devices are included once at least one macOS application has been deployed from the Pckgr Application Library.

***

#### **Migrating from Installomator to the Private Mac Repository**

If you have previously deployed an application using the **Installomator Repository** and want to move to the **Private Mac Repository**, simply:

1. Deploy the application again using the **Private Mac Repository**.
2. Remove the existing Installomator deployment from Intune.

The native Intune application deployed through the Private Mac Repository will then manage future installations and updates. There is no need to keep the previous Installomator deployment once the migration has been completed.

***

**Next Steps**

For deployment configuration options, see the [**Deployment Settings**](/getting-started/creating-deployments/deployment-settings.md) documentation.

For Company Portal configuration, see the [**macOS Company Portal**](/integrations/company-portal/macos-applications.md) documentation.

#### Additional Resources

* [Microsoft Intune Documentation](https://learn.microsoft.com/en-us/mem/intune/apps/macos-shell-scripts) (Shell Scripts (Installomator approach))
* [Microsoft Intune Documentation](https://learn.microsoft.com/en-us/intune/app-management/deployment/add-unmanaged-pkg-macos) (Native Deployment Detection Rules (Private Macapps))
* [Installomator GitHub Repository](https://github.com/Installomator/Installomator)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.intunepckgr.com/getting-started/creating-deployments/repositories/macos.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.