# Upload package to the Microsoft Intune from the Apptimized portal

#### Package requirements

Apptimized portal supports the following package formats:

Table 3. Package formats

<table border="1" id="bkmrk-package-type-details" style="width: 800px;"><tbody><tr><td width="162">**Package type**

</td><td width="450">**Details**

</td></tr><tr><td width="162">MSI

</td><td width="450">Only packages with a single **MSI** file are supported.

All external files (i.e., **CAB** and **CMD** files) should be included in the MSI package.

The package size is capped at **8 GB** per package.

</td></tr><tr><td width="162">IntuneWin

</td><td width="450">The **INTUNEWIN** file is created through the use of the **Microsoft Win32 Content Prep Tool**. The packaging tool converts application installation files into the **.intunewin** format via zipping all files and subfolders

To use Win32 app management, a user must ensure the following criteria:

- Windows 10 version 1607 or later (Enterprise, Pro, and Education versions);
- Devices must be joined to Azure AD and auto-enrolled;
- Windows application size is capped at **8 GB** per app.

[Learn more](https://docs.microsoft.com/en-us/mem/intune/apps/apps-win32-app-management).

</td></tr></tbody></table>

Apptimized portal shows an error message when these requirements are not fulfilled:

[![intune_33.png](https://docs.apptimized.com/uploads/images/gallery/2020-05/scaled-1680-/V68jbpCqmLeITtyf-intune_33.png)](https://docs.apptimized.com/uploads/images/gallery/2020-05/V68jbpCqmLeITtyf-intune_33.png)

#### Upload the package to Microsoft Intune

Before uploading the package to the Microsoft Intune, a user must ensure the availability of a ready-made package. The package can be generated using the **Packaging – Self Service** or **Packaging – Factory Service** steps of the **Project** workflow. [Learn more](https://docs.apptimized.com/books/apptimized-platform-user-manual/page/packaging) about how to package the application.

<p class="callout info">**Note.** Packages are available for upload from the Apptimized portal to Intune only after finishing the **Packaging** step (Self Service or Factory Service). In other words, the ready-made package that was imported to the project on the **Import** step (i.e., the Package step is skipped) is not available for upload to Intune.</p>

Apptimized portal supports the One-To-One-Integration model (i.e., 1 Apptimized project can be integrated into 1 Client App on the Microsoft Intune).

The option to upload the package to Microsoft Intune is available under the **Project** menu &gt; **Dashboards** &gt; **Portfolio** &gt; Select an application &gt; **Actions** column &gt; **Push to Intune** option.

[![intune_30.png](https://docs.apptimized.com/uploads/images/gallery/2020-05/scaled-1680-/oqh2j8Kgi7cZoYWi-intune_30.png)](https://docs.apptimized.com/uploads/images/gallery/2020-05/oqh2j8Kgi7cZoYWi-intune_30.png)

[![intune_31.png](https://docs.apptimized.com/uploads/images/gallery/2020-05/scaled-1680-/5tOUbKuDalJrAK0I-intune_31.png)](https://docs.apptimized.com/uploads/images/gallery/2020-05/5tOUbKuDalJrAK0I-intune_31.png)

Apptimized portal shows the following screen when successful:

[![intune_32_2.png](https://docs.apptimized.com/uploads/images/gallery/2021-09/scaled-1680-/uRNEXyBlmScubEwy-intune_32_2.png)](https://docs.apptimized.com/uploads/images/gallery/2021-09/uRNEXyBlmScubEwy-intune_32_2.png)

The **Intune apps list** provides a user the information on the full list of applications from the **Microsoft Intune** portal available in the **Apptimized** portal.

The **Intune apps list** enables a user to manage applications from the **Microsoft Intune** portal without leaving the **Apptimized** portal.

The option to upload the package to the **Microsoft Intune** portal is available under the **Add IntuneWin** button. The application information screen appears when successful:

[![intune_34_2.png](https://docs.apptimized.com/uploads/images/gallery/2021-09/scaled-1680-/tzGQAIeHL50nEaHk-intune_34_2.png)](https://docs.apptimized.com/uploads/images/gallery/2021-09/tzGQAIeHL50nEaHk-intune_34_2.png)

Table 4. Application settings

<table border="1" id="bkmrk-setting-description-" style="width: 797px; height: 1689px;" width="800"><tbody><tr style="height: 32px;"><td style="width: 237px; height: 32px;">**Setting**

</td><td style="width: 560px; height: 32px;">**Description**

</td></tr><tr style="height: 32px;"><td colspan="2" style="width: 797px; height: 32px;">**Application metadata block**

</td></tr><tr style="height: 138px;"><td style="width: 237px; height: 138px;">Display name

</td><td data-celllook="0" style="width: 560px; height: 138px;"><span data-contrast="auto">This setting indicates the application name that will be displayed in the </span><span data-contrast="auto">Intune apps list</span><span data-contrast="auto"> (i.e., </span>**<span data-contrast="auto">Tim </span><span data-contrast="auto">Kosse</span><span data-contrast="auto"> FileZilla</span>**<span data-contrast="auto">).</span><span data-ccp-props="{"201341983":0,"335559740":259}"> </span>

<span data-contrast="auto">A user must make sure that the name of the application </span><span data-contrast="auto">is ente</span><span data-contrast="auto">red </span><span data-contrast="auto">as it appears in the </span><span data-contrast="auto">C</span><span data-contrast="auto">ompany </span><span data-contrast="auto">P</span><span data-contrast="auto">ortal. </span><span data-contrast="auto">A</span><span data-contrast="auto">ll </span><span data-contrast="auto">names </span><span data-contrast="auto">must be </span><span data-contrast="auto">unique.</span><span data-ccp-props="{"201341983":0,"335559740":259}"> </span>

<span data-contrast="auto">The field comes pre-filled </span><span data-contrast="auto">based on the application’s metadata.</span><span data-ccp-props="{"201341983":0,"335559740":259}"> </span>

<span data-contrast="auto">This </span><span data-contrast="auto">field</span><span data-contrast="auto"> is required.</span><span data-ccp-props="{"201341983":0,"335559740":259}"> </span>

</td></tr><tr style="height: 75px;"><td style="width: 237px; height: 75px;">Description

</td><td data-celllook="0" style="width: 560px; height: 75px;"><span data-contrast="auto">This setting helps the device users to understand what the application is and/or what they can do in the application. This description </span><span data-contrast="auto">appears in the company portal.</span><span data-ccp-props="{"201341983":0,"335559740":259}"> </span>

<span data-contrast="auto">This field is required.</span><span data-ccp-props="{"201341983":0,"335559740":259}"> </span>

</td></tr><tr style="height: 75px;"><td style="width: 237px; height: 75px;">Publisher

</td><td data-celllook="0" style="width: 560px; height: 75px;"><span data-contrast="auto">This setting indicates the name of the developer or the company’s name that distributes the application. This information </span><span data-contrast="auto">appears in the company portal.</span><span data-ccp-props="{"201341983":0,"335559740":259}"> </span>

<span data-contrast="auto">This field is required.</span><span data-ccp-props="{"201341983":0,"335559740":259}"> </span>

</td></tr><tr style="height: 53px;"><td style="width: 237px; height: 53px;">Privacy URL

</td><td data-celllook="0" style="width: 560px; height: 53px;"><span data-contrast="auto">This setting indicates the URL of a website that contains </span>privacy <span data-contrast="auto">information about the application.</span><span data-contrast="auto"> The URL appears in the company </span><span data-contrast="auto">portal.</span><span data-ccp-props="{"201341983":0,"335559740":259}"> </span>

</td></tr><tr style="height: 75px;"><td style="width: 237px; height: 75px;">Information URL

</td><td data-celllook="0" style="width: 560px; height: 75px;"><span data-contrast="auto">This setting indicates the URL of a website that contains information about the applica</span><span data-contrast="auto">tion (I.e., a</span><span data-contrast="auto"> l</span><span data-contrast="auto">ink to a website or documentation that </span><span data-contrast="auto">provides </span><span data-contrast="auto">more information about the app</span><span data-contrast="auto">lication)</span><span data-contrast="auto">. The URL </span><span data-contrast="auto">appears in the company portal.</span><span data-ccp-props="{"201341983":0,"335559740":259}"> </span>

</td></tr><tr style="height: 32px;"><td colspan="2" style="width: 797px; height: 32px;">**Application installation block**

</td></tr><tr style="height: 117px;"><td style="width: 237px; height: 117px;">Install command

</td><td style="width: 560px; height: 117px;">This setting configures the application installation command line to install the application (i.e., **msiexec /i "TimKosse\_FileZilla\_3.46.3.msi" /q**).

The field comes pre-filled based on the package’s metadata (in the case a package contains the MSI).

This field is required.

</td></tr><tr style="height: 138px;"><td style="width: 237px; height: 138px;">Uninstall command

</td><td style="width: 560px; height: 138px;">This setting configures the application uninstallation command line to uninstall the application based on its GUID (i.e., **msiexec /x "{C67DBEF5-4637-451C-991C-8794D3ECA1F6}" /q**).

The field comes pre-filled based on the package’s metadata (in the case a package contains the MSI).

This field is required.

</td></tr><tr style="height: 217px;"><td style="width: 237px; height: 217px;">Minimal system architecture

</td><td style="width: 560px; height: 217px;">This setting indicates the minimal system architecture requirements.

The following options are available:

- Windows 10 1607;
- Windows 10 1703;
- Windows 10 1709;
- Windows 10 1803;
- Windows 10 1809;
- Windows 10 1903.

The default value is **Windows 10 1607**.

This field is required.

</td></tr><tr style="height: 152px;"><td style="width: 237px; height: 152px;">Operating system architecture

</td><td style="width: 560px; height: 152px;">This setting indicates the operating system architecture type.

The following options are available:

- 32-bit;
- 64-bit.

Multiple choice is available.

This field is required.

</td></tr><tr><td style="width: 237px;">Install context

</td><td style="width: 560px;"><span data-contrast="auto">This field indicates the type of execution context the app runs in. The following options are available: </span><span data-ccp-props="{"201341983":0,"335559740":259}"> </span>

- <span data-contrast="auto">System</span><span data-ccp-props="{"134233279":true,"201341983":0,"335559739":160,"335559740":259}"> </span>
- <span data-contrast="auto">User</span><span data-ccp-props="{"134233279":true,"201341983":0,"335559739":160,"335559740":259}"> </span>

<span data-contrast="auto">The default value is </span>**<span data-contrast="auto">System</span>**<span data-contrast="auto">.</span><span data-ccp-props="{"201341983":0,"335559740":259}"> </span>

</td></tr><tr style="height: 32px;"><td colspan="2" style="width: 797px; height: 32px;">**MSI information block**

</td></tr><tr style="height: 96px;"><td style="width: 237px; height: 96px;">Product name

</td><td style="width: 560px; height: 96px;">This setting indicates the product name that will be displayed n the Microsoft Intune portal (i.e., **FileZilla**).

The field comes pre-filled based on the application’s metadata.

This field is required.

</td></tr><tr style="height: 96px;"><td style="width: 237px; height: 96px;">Product code

</td><td style="width: 560px; height: 96px;">This setting indicates the product code that is generated automatically using the GUID function (i.e., **{C67BDEF5-4637-451C-661C-8794D3ECA1F6}**).

The field comes pre-filled.

This field is required.

</td></tr><tr style="height: 96px;"><td style="width: 237px; height: 96px;">Publisher

</td><td style="width: 560px; height: 96px;">This setting indicates the publisher's name that will be displayed in the Microsoft Intune portal (i.e., **Tim Kosse**).

The field comes pre-filled based on the application’s metadata.

This field is required.

</td></tr><tr style="height: 75px;"><td style="width: 237px; height: 75px;">Product version

</td><td style="width: 560px; height: 75px;">This setting indicates the application version that will be displayed in the Microsoft Intune portal (i.e., **3.46.3**).

The field comes pre-filled based on the application’s metadata.

</td></tr><tr style="height: 32px;"><td colspan="2" style="width: 797px; height: 32px;">**Detection rules block**

</td></tr><tr style="height: 126px;"><td style="width: 237px; height: 126px;">Detection type

</td><td style="width: 560px; height: 126px;">This setting indicates the detection rule type.

The following options are available:

- Msi (Verify based on MSI version check);
- File (Verify based on file or folder detection, date, version, or size);
- Registry (Verify based on value, string, integer, or version).
- Script (Verify based on script).

</td></tr></tbody></table>

<p class="callout info">**Note.** The detection rules are used to detect the presence of the application (i.e., **Microsoft Intune** can determine that the **IntuneWin** package has been installed).</p>

Table 5. Detection rule types

<table border="1" id="bkmrk-detection-rule-type-" style="width: 800px;"><tbody><tr><td class="align-left" style="vertical-align: top;" width="186">**Detection rule type**

</td><td class="align-left" style="vertical-align: top;" width="438">**Description**

</td></tr><tr><td class="align-left" style="vertical-align: top;" width="186">Msi

</td><td class="align-left" style="vertical-align: top;" width="438">[![intune_35_2.png](https://docs.apptimized.com/uploads/images/gallery/2020-05/scaled-1680-/xOMosFi8LGmF9KdU-intune_35_2.png)](https://docs.apptimized.com/uploads/images/gallery/2020-05/xOMosFi8LGmF9KdU-intune_35_2.png)

The **Product Code** field requires a valid MSI product code for the application. The following options to provide the product code available:

- Msi information block &gt; Product code;
- To extract from the MSI package.

The option to verify the MSI product version in addition to the MSI product code is available under the **Check product version** checkbox.

[![intune_35_3.png](https://docs.apptimized.com/uploads/images/gallery/2020-05/scaled-1680-/k3bgtY3rzyWQLBE7-intune_35_3.png)](https://docs.apptimized.com/uploads/images/gallery/2020-05/k3bgtY3rzyWQLBE7-intune_35_3.png)

The option to set the operator condition rules is available under the **Operator** field.

The following options are available:

- Equals;
- Not equal to;
- Greater than or equal to;
- Greater than;
- Less than or equal to;
- Less than.

The default value is **Equals**.

The **product version** field sets the application version that will be used for applying the operator condition rules.

All required fields are marked with an asterisk <span style="color: #ff0000;">\*</span>.

</td></tr><tr><td class="align-left" style="vertical-align: top;" width="186">File

</td><td class="align-left" style="vertical-align: top;" width="438">[![intune_35_5.png](https://docs.apptimized.com/uploads/images/gallery/2020-05/scaled-1680-/4WA63h3jpWrJjUdS-intune_35_5.png)](https://docs.apptimized.com/uploads/images/gallery/2020-05/4WA63h3jpWrJjUdS-intune_35_5.png)

The **Path** field requires the full path of the folder containing the file or folder to detect.

The **File or folder** field requires the file or folder to detect.

The **Detection method** field requires the type of detection method used to validate the presence of the application.

The following options are available:

- Date created;
- Date modified;
- File or folder exists;
- Size in MB;
- String (version).

The default value is **File or folder exists**.

All required fields are marked with an asterisk \*.

</td></tr><tr><td class="align-left" style="vertical-align: top;" width="186">Registry

</td><td class="align-left" style="vertical-align: top;" width="438">[![intune_35_7.png](https://docs.apptimized.com/uploads/images/gallery/2020-05/scaled-1680-/xQ2Q3WinuPziw3Cd-intune_35_7.png)](https://docs.apptimized.com/uploads/images/gallery/2020-05/xQ2Q3WinuPziw3Cd-intune_35_7.png)

The **Key path** field requires the full path of the registry entry containing the value to detect.

The **Value name** field requires the name of the registry value to detect.

The **Detection method** field requires the type of detection method used to validate the presence of the application.

The following options are available:

- Key exists;
- Key does not exist;
- Integer comparison;
- String comparison;
- Version comparison.

The default value is **Key exists**.

All required fields are marked with an asterisk \*.

</td></tr><tr><td style="vertical-align: top;">Script

</td><td style="vertical-align: top;">[![intune_39.png](https://docs.apptimized.com/uploads/images/gallery/2021-07/scaled-1680-/n6qElzAQIUPY77ef-intune_39.png)](https://docs.apptimized.com/uploads/images/gallery/2021-07/n6qElzAQIUPY77ef-intune_39.png)

<span data-contrast="auto">The </span>**<span data-contrast="auto">Script content </span>**<span data-contrast="auto">field requires the full script code </span><span data-contrast="auto">containing the PowerShell script to detect app presence</span><span data-ccp-props="{"201341983":0,"335559740":259}"> </span>

<span data-ccp-props="{"201341983":0,"335559740":259}"> </span>

<span data-contrast="auto">The option to reprioritize signature check is available under </span>**<span data-contrast="auto">Enforce signature check </span>**<span data-contrast="auto">checkbox</span><span data-ccp-props="{"201341983":0,"335559740":259}"> </span>

<span data-ccp-props="{"201341983":0,"335559740":259}"> </span>

<span data-contrast="auto">The option to run script in 32 bit mode is available under </span>**<span data-contrast="auto">Run as 32 bit </span>**<span data-contrast="auto">checkbox.</span><span data-ccp-props="{"201341983":0,"335559740":259}"> </span>

</td></tr></tbody></table>

The ability to set multiple detection rules types is available under the **plus** symbol.

[![intune_36.png](https://docs.apptimized.com/uploads/images/gallery/2020-05/scaled-1680-/6E22WbFDBkckDXvC-intune_36.png)](https://docs.apptimized.com/uploads/images/gallery/2020-05/6E22WbFDBkckDXvC-intune_36.png)

The option to delete the detection rules type is available under the **bin** symbol.

[![intune_36_3.png](https://docs.apptimized.com/uploads/images/gallery/2020-05/scaled-1680-/o6uaNsz4EbS2FOHy-intune_36_3.png)](https://docs.apptimized.com/uploads/images/gallery/2020-05/o6uaNsz4EbS2FOHy-intune_36_3.png)

The application becomes available in the **Intune apps list** when clicking on the **Add** button and once the required settings are completed. The synchronization process may take a few moments.

[![intune_37.png](https://docs.apptimized.com/uploads/images/gallery/2020-05/scaled-1680-/uYtQPuhicrbzLXKJ-intune_37.png)](https://docs.apptimized.com/uploads/images/gallery/2020-05/uYtQPuhicrbzLXKJ-intune_37.png)

The application disappears from the **Intune apps list** in the **Apptimized** portal when deleted in the **Microsoft Intune** portal.

#### Edit application metadata

The option to change the metadata of the application is available under the **Edit** button.

[![intune_38.png](https://docs.apptimized.com/uploads/images/gallery/2020-05/scaled-1680-/Ay6tT6V58M6TEkmv-intune_38.png)](https://docs.apptimized.com/uploads/images/gallery/2020-05/Ay6tT6V58M6TEkmv-intune_38.png)

Apptimized shows the following modal window:

[![intune_39_2.png](https://docs.apptimized.com/uploads/images/gallery/2020-05/scaled-1680-/Bwl4AR1iEvRruQE6-intune_39_2.png)](https://docs.apptimized.com/uploads/images/gallery/2020-05/Bwl4AR1iEvRruQE6-intune_39_2.png)

The added or changed metadata information applies when clicking the **Save** button. After that, the application metadata is successfully saved for the application in the **Microsoft Intune** portal.