Introduction
This document provides step-by-step instructions to deploy Windows Passwordless v2.0 on managed Windows devices using Microsoft Intune (MDM).Prerequisites
- You must have admin access to the Microsoft Intune Admin Center.
- You must have the installation PowerShell script (.ps1).
-
You must have the detection rule PowerShell script (rule.ps1).
Note: Contact Oloid Support to obtain the PowerShell script (.ps1) and detection rule script (rule.ps1).
-
You must have downloaded the Microsoft Win32 Content Prep Tool (IntuneWinAppUtil).
Note: To download the Microsoft Win32 Content Prep Tool, click here.
- You must download the AutoPairConfig.txt file from the Tenant Admin Portal. For more information, refer to Windows Login - How to generate Auto-Pair config file for Windows Login in Tenant Admin Portal.
- You must download the Windows Login v2.0 installer file. For more information, refer to Windows Login v2.0 - How to download Windows Login v2.0 installer file from Tenant Admin Portal
Steps to Deploy Windows Passwordless 2.0 using Microsoft Intune (MDM)
- Create App Package
- Create and Configure App The Windows Passwordless v2.0 is deployed successfully to the target devices.
Steps to Create App Package
-
Place the Windows Login v2.0 installer file, AutoPairConfig.txt file, and installation PowerShell (.ps1) script in the same folder.
Note: If the AutoPair configuration file is added, the app is installed and paired automatically. If not, manual pairing is required after installation.

- Download and open the Microsoft Win32 Content Prep Tool.
-
Enter the following details when prompted by the tool:
-
Source folder: Enter the folder path that contains the
install.ps1file, autopair config file and the installer file. - Setup file: Enter the installer file name with the file extension.
-
Output folder: Enter the folder path where the
.intunewinfile must be created.Note: Before you generate the.intunewinfile, update the following values in theinstall.ps1script:- Set
$InstallerNameto the name of the.exeinstaller file used to install the app. - In
$SilentArgs, set the required feature flags totrueorfalsebased on the features you want to install.
The app package is created successfully. Navigate to the output folder and verify that the .intunewin app package file has been created successfully.

- Set
-
Source folder: Enter the folder path that contains the
Create and Configure App
- Log in to Microsoft Intune Admin Account. The Microsoft Intune home screen is displayed.
- Navigate to Apps > Windows.
The Windows apps screen is displayed.
- Click + Create.
The Select app type screen is displayed.
- In the app type dropdown, select Windows app (Win32) and click Select.
The Add App screen is displayed.
- On App Information tab, do the following:
-
Click Select app package file.
The App package file screen is displayed.
-
Browse and select the .intunewin app package file.
Note: Select the same .intunewin package file that was created in the Steps to Create Package File section.
-
Click OK.
The App information tab is displayed.
- Enter Publisher.
-
Click Next.
The Program tab is displayed.
-
Click Select app package file.
- On the Program tab, do the following:
- Ensure command line is selected as installer type.
Note: Use the following command.
- Ensure command line is selected as uninstaller type.
Note: Use the following command.
-
Select No as Allow available uninstall (Optional).
Note: Select No to prevent the application from being uninstalled through the Company Portal or Windows Control Panel.
- Ensure System is selected as Install behaviour.
-
Click Next.
The Requirements tab is displayed.
-
On the requirements tab, do the following.
- Select No as Check operating system architecture.
- Select Windows 10 1607 as Minimum operating system.
- Click Next.
The Detection Rules tab is displayed.
-
On the Detection Rules tab, do the following.
- Select Use a custom detection script as Rules format.
-
Upload Script file.
Note: To get the Script file, contact Oloid Support.
- Ensure No isselected as Run script as 32-bit process on 64-bit clients.
- Ensure No isselected as Enforce script signature check and run script silently.
-
Click Next.
The Dependencies tab is displayed.
-
Click Next.
The Supersedence tab is displayed.
-
Click Next.
The Assignments tab is displayed.
-
On the Assignments tab, do the following.
- On Required section, click Add group to assign this profile to your target device groups.
The Select groups pop-up is displayed.
- Do the following.
-
Select the group(s) from the list.
Note: You can select multiple groups (If required).
-
Click Select.
The Group is added in the list.
-
Select the group(s) from the list.
- On Required section, click Add group to assign this profile to your target device groups.
-
Click Next.
The Assignment tab is configured successfully and Review + create tab is displayed.
Note: To assign groups under the Available for enrolled devices and Uninstall sections, repeat Steps 9a and 9b as required. -
Review all settings and click Create.
The app the created successfully and added in the apps screen.
