Intune User Guide
Introduction
Intune is a cloud-based service that focuses on mobile device management (MDM) and mobile application management (MAM) which enables the following:
- To be 100% cloud with Intune, or to be co-managed with Configuration Manager and Intune;
- To set rules and configure settings on personal and organization-owned devices to access data and networks;
- To deploy and authenticate apps on devices (both on-premises and mobile);
- To control the way users access and share information;
- To stay compliant with company security requirements.
Integration Intune with Apptimized saves time and enables a user to upload, update, and manage the ready-made packages without the need to leave Apptimized.
Initial integration to Apptimized requires a one-time configuration of settings in the Microsoft Azure portal and the Apptimized portal, namely:
- Application registrations in the Microsoft Azure portal;
- Assigning permissions to a user to work with Microsoft Intune from the Microsoft Azure portal;
- Integration of the application from the Microsoft Azure portal into the Apptimized portal.
Integration
Application registrations
The application registration is carried out in the Microsoft Azure portal via administrative credentials. A user can choose one of the following types of accounts:
A tenant admin account;
- A tenant user account (with the enabled “Users can register applications” setting).
The option to open an application registration page is available under:
- Microsoft Azure portal > Azure services > App registrations;
- Microsoft Azure portal > Search > Enter a search request (i.e., “App registrations”) > Select the service in the list > App registrations;
- Microsoft Azure portal > Menu > All services > Enter a search request (i.e., “App registrations”) > Select the service in the list > App registrations.
Microsoft Azure portal shows the screen when successful:
The option to create a new application registration is available under the New registration option.
Microsoft Azure portal shows the Create window when successful:
To create a new application registration, a user fills in the fields in the form (see Table 1 and the Microsoft Azure manual).
Table 1. A new application registration
Field name | Details |
Name | This field sets a meaningful application name to display to users (i.e., Apptimized Intune Test) |
Supported accounts |
This option identifies types of accounts that can use the application.
|
Redirect URI |
This setting is optional, and the values can be provided later.
|
When clicking on the Register button, Microsoft Azure portal shows the following screen:
When the application is successfully registered, a user needs to make a series of settings steps, namely:
- To add a redirect URIs;
- To add new client secret string;
- To grant permissions to the application to call API.
Next, each setting block is shown in more detail.
The option to add redirect URIs to the application is available under the All services > App registrations > Select the application in the list > Manage menu > Authentication > Platform configurations > Add a platform> Web > Redirect URLs > Fill in new URI > Configure button.
The following URL is required to be added: https://app.apptimized.com/Account/AuthCode
The option to add new client secret string is available under the All services > App registrations > Select the application in the list > Manage menu > Certificates & secrets > Client secrets > New client secret button > Fill in the description > Set the expiry mode > Add button.
Note. When clicking on the Add button, the client secret value appears (i.e., ~_fd-Y49~haNZ~g8RbDz9yQCF4KQ__1j49). A user must copy the value to the clipboard to use it in the client’s application code. It becomes inaccessible once a user leaves this page. The Client secret value correlates with the Client secret field when integrating Intune into the Apptimized portal.
The option to configure permissions to the application to call API is available under All services > App registrations > Select the application in the list > Manage menu > API permissions > Add a permission > Microsoft Graph.
Microsoft Azure portal shows the following screen when successful:
The option to set the types of permissions to the application is available under the Delegated permissions button > Select the permissions from the list > Add permissions button. The screenshot below shows the list of enabled permissions:
Some delegated permissions can be consented by non-administrative users, but some higher-privileged permissions require administrator consent. The option to grant permissions is available under the Grant admin consent for [company name] button.
Note. If the application runs as a background service or daemon without a signed-in user, the required option is Application permissions. The Applications permissions are the permissions that are used by applications that run without a signed-in user present. Using Application permissions enables Apptimized users to push packages to Intune without requiring an own Intune access or even an AAD account in the target Azure directory. By configuring the use of application permissions, the API will be authorized to push packages to Intune without requiring an authenticated AAD Intune user with adequate permissions to provide this authorization.
The DeviceManagementApps permissions in Applications permissions are identical to Delegated permissions group.
Integration of the application from the Microsoft Azure portal into the Apptimized portal
The one-time configuration is available for project administrators under the Project menu > Administration > Settings > Integration section > Intune.
Intune becomes active when switched on and once the required settings are completed. All required fields are marked with an asterisk *.
Table 2. Basic settings
Settings |
Details |
Tenant Identifier |
The Tenant Identifier corresponds to the term Directory (tenant) ID in the Microsoft Azure portal. The Directory (tenant) ID is a unique identifier generated automatically by the Microsoft Azure portal for every application during its creation. |
Client Identifier |
The Client Identifier corresponds to the term Application (client) ID in the Microsoft Azure portal. The Application (client) ID is a unique identifier generated automatically by the Microsoft Azure portal for every application during its creation. |
Client Secret |
The Client Secret corresponds to the term Value of secret in the Microsoft Azure portal. The Client Secret is a unique identifier generated automatically by the Microsoft Azure portal for every application during its creation. |
Use applications permissions |
The Use application permissions correspond to the term Applications permissions in the Microsoft Azure portal. The Applications permissions are the permissions that are used by applications that run without a signed-in user present. Using Application permissions enables Apptimized users to push packages to Intune without requiring an own Intune access or even an AAD account in the target Azure directory. By configuring the use of application permissions, the API will be authorized to push packages to Intune without requiring an authenticated AAD Intune user with adequate permissions to provide this authorization.
|
Apptimized shows the following notification when successful:
Manage project roles
Intune requires the assignment of the project user to the role with the required permission. Assigning needed permissions is available under the Project menu > Administration > Roles.
It is possible to add permission to the existing group or to create a new one by clicking the Add new role button, as shown on the screenshots below.
The new role requires its meaningful name and Intune project permission.
Apptimized shows the following screen and notification when successful:
For a user to be able to perform any activities related to the Intune, he must be assigned a role with the Intune project permission. The option to assign the role to a user (or a group) is available under the Update users or Update groups buttons respectively.
Instructions on how to edit or manage roles within the project are available in the Apptimized Portal user manual > Project role section.
Intune apps list
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 access Intune applications list is available under Project menu > Intune apps.
Assigning permissions to a user to work with Microsoft Intune from Microsoft Azure
The option to open an application registration page is available under:
- Microsoft Azure portal > Search > Enter a search request (i.e., “Intune”) > Select the service in the list > Intune;
- Microsoft Azure portal > Menu > All services > Enter a search request (i.e., “Intune”) > Select the service in the list > Intune.
Microsoft Azure portal shows the following screen when successful:
The option to add new Intune role is available under the All services > Tenant administration > Roles > All roles > Create button.
Microsoft Azure portal shows the screen when successful:
The screenshot below shows the procedure for creating a new custom role (Create button > Enter role name > Enter role description > Select scope tags > Create button):
Microsoft Azure portal shows the following screen when successful:
When the new custom role appears in the list, the assignments must be provided. Microsoft Azure portal shows the following screen when clicking the new custom role name:
The option to provide assignments is available under the Roles > Select and click on role > Assignments > Assign button.
The screenshot below shows the procedure for role assignments (Assign button > Enter role assignment name > Enter role assignment description > Select admin groups > Select scope groups > Select scope tags > Create button):
Microsoft Azure portal shows the following screen when successful:
Upload package to the Microsoft Intune from the Apptimized portal
Package requirements
Apptimized portal supports the following package formats:
Table 3. Package formats
Package type |
Details |
MSI |
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. |
IntuneWin |
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:
|
Apptimized portal shows an error message when these requirements are not fulfilled:
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 about how to package the application.
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.
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 > Dashboards > Portfolio > Select an application > Actions column > Push to Intune option.
Apptimized portal shows the following screen when successful:
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:
Table 4. Application settings
Setting |
Description |
Application metadata block |
|
Display name |
This setting indicates the application name that will be displayed in the Intune apps list (i.e., Tim Kosse FileZilla). A user must make sure that the name of the application is entered as it appears in the Company Portal. All names must be unique. The field comes pre-filled based on the application’s metadata. This field is required. |
Description |
This setting helps the device users to understand what the application is and/or what they can do in the application. This description appears in the company portal. This field is required. |
Publisher |
This setting indicates the name of the developer or the company’s name that distributes the application. This information appears in the company portal. This field is required. |
Privacy URL |
This setting indicates the URL of a website that contains privacy information about the application. The URL appears in the company portal. |
Information URL |
This setting indicates the URL of a website that contains information about the application (I.e., a link to a website or documentation that provides more information about the application). The URL appears in the company portal. |
Application installation block |
|
Install command |
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. |
Uninstall command |
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. |
Minimal system architecture |
This setting indicates the minimal system architecture requirements. The following options are available:
The default value is Windows 10 1607. This field is required. |
Operating system architecture |
This setting indicates the operating system architecture type. The following options are available:
Multiple choice is available. This field is required. |
Install context |
This field indicates the type of execution context the app runs in. The following options are available:
The default value is System. |
MSI information block |
|
Product name |
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. |
Product code |
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. |
Publisher |
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. |
Product version |
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. |
Detection rules block |
|
Detection type |
This setting indicates the detection rule type. The following options are available:
|
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).
Table 5. Detection rule types
Detection rule type |
Description |
Msi |
The Product Code field requires a valid MSI product code for the application. The following options to provide the product code available:
The option to verify the MSI product version in addition to the MSI product code is available under the Check product version checkbox. The option to set the operator condition rules is available under the Operator field. The following options are available:
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 *. |
File |
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:
The default value is File or folder exists. All required fields are marked with an asterisk *. |
Registry |
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:
The default value is Key exists. All required fields are marked with an asterisk *. |
Script |
The Script content field requires the full script code containing the PowerShell script to detect app presence
The option to reprioritize signature check is available under Enforce signature check checkbox
The option to run script in 32 bit mode is available under Run as 32 bit checkbox. |
The ability to set multiple detection rules types is available under the plus symbol.
The option to delete the detection rules type is available under the bin symbol.
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.
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.
Apptimized shows the following modal window:
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.