Enrolling corporate iOS devices authenticating with Setup Assistant

Through Intune, you can improve workflow to enroll corporate iOS devices with user affinity into Intune, specifically when these devices use Setup Assistant for authentication.

 This aims to improve the enrollment experience and give end users a shortened workflow. The following is detailed information on this enrolment improvement.

Experience for enrolling new devices

if you enroll new devices authenticating with Setup Assistant, you can choose whether or not to deploy the Intune Company Portal app automatically in Intune not Azure (not available in hybrid MDM).  Also doing away with “Identify your device” screen and the “Confirm your device” screen, where end users enter the last 4 digits of the device’s serial number in the Company Portal app. 

Experience for existing enrolled devices

if you want to enable Conditional Access for devices already enrolled via Setup Assistant, you’ll have to push the Company Portal down to those devices. Here’s how you would do that:

1. In the Intune on Azure portal, Add the Intune Company Portal if necessary, by going to Intune > Client Apps > Apps > Add Go to Client apps > App configuration policies, to create an app configuration policy for the Company Portal app.

If you use hybrid Mobile Device Management (Hybrid MDM),

• Create a new app policy in the Configuration Manager console for the Company Portal app.
• Go to Software Library > Application Management > App Configuration Policies.

1. Create an app configuration policy with the xml below.

<dict>

    <key>IntuneCompanyPortalEnrollmentAfterUDA</key>

    <dict>

        <key>IntuneDeviceId</key>

        <string>{{deviceid}}</string>

        <key>UserId</key>

        <string>{{userid}}</string>

    </dict>

</dict>

1. Deploy Company Portal to devices with the app configuration policy targeted to desired groups.
2. Tell end users to sign into the Company Portal app when it is automatically installed.

What does this XML do? The provided XML snippet represents a dictionary (or associative array) structure with specific keys and values. Let's break down what this structure is likely used for based on the keys provided:

XML Key Components:

- <dict>: Indicates a dictionary or key-value pair structure within an XML or property list format.

- <key>: Represents a key identifier within the dictionary.

- <string>: Indicates a string value associated with a key.

Analysis:

1. Top-Level Dictionary (`<dict>`):

   - This is the root dictionary containing one key-value pair.

2. Key: IntuneCompanyPortalEnrollmentAfterUDA

   - This key likely represents an action or event related to Intune Company Portal enrollment after User Device Affinity (UDA).

3. Value: Nested Dictionary (`<dict>`):

   - The value associated with the key IntuneCompanyPortalEnrollmentAfterUDA is another nested dictionary containing additional key-value pairs.

4. Keys within Nested Dictionary:

   - IntuneDeviceId: This key likely represents the Intune Device ID associated with the enrolled device.

   - ‘UserId`: This key likely represents the user ID associated with the enrolled device.

Purpose:

This XML is used for passing data related to Intune Company Portal enrollment after establishing User Device Affinity (UDA). The values for IntuneDeviceId and UserId are placeholders (`{{deviceid}}` and {{userid}}) that would typically be replaced with actual device and user identifiers during runtime or processing.

Usage Scenario:

 This structure could be part of a configuration or data payload used in an automated process or integration where:

- After User Device Affinity is established (e.g., associating a user with a specific device in Intune),

- This action triggers enrollment or further processing in the Intune Company Portal based on the device ID (`IntuneDeviceId`) and associated user ID (`UserId`).

In summary

This XML snippet defines a data structure used for passing device and user information within an Intune integration flow, specifically related to device enrollment after User Device Affinity is established. The actual values (`{{deviceid}}` and {{userid}}) would be populated dynamically with specific device and user identifiers during execution.

Shady Khorshed is a Microsoft enthusiast. He loves writing on iOS/Android, MacOS, Windows 11, Windows 365 and related Microsoft Intune. He is here to share quick tips and tricks for all young professionals.

#MicrosoftIntune #MacOSDeviceManagement #TechSolutions #MobileSecurity #MicrosoftIntune #MobileDeviceManagement #DeviceEnrollment #TechInnovation #Apple #ios #android #decisiontree #microsoft #intune #COPE #COSU #COBO #BYOD #Appprotectionpolicy #Workprofile #devices #design #environment #Learning #MacOS