Skip to content

Commit f61dbc0

Browse files
committed
Merging changes synced from https://github.com/MicrosoftDocs/memdocs (branch main)
2 parents 62eb137 + 3b432d5 commit f61dbc0

2 files changed

Lines changed: 1 addition & 10 deletions

File tree

memdocs/intune/enrollment/device-enrollment-program-enroll-ios.md

Lines changed: 0 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -234,16 +234,7 @@ Now that you've installed your token, you can create an enrollment profile for A
234234
- Won’t be evaluated for device compliance.
235235
- Will be redirected to the Company Portal from other apps if the user tries to open any managed applications that are protected by conditional access.
236236

237-
7. If you selected **Company Portal** for your authentication method, you can use a VPP token to automatically install Company Portal on the device. In this case, the user doesn't have to provide an Apple ID. To install Company Portal by using a VPP token, select a token in **Install Company Portal with VPP**. You need to have already added Company Portal to the VPP token. To ensure that Company Portal continues to be updated after enrollment, make sure that you've configured an app deployment in Intune (In Endpoint Manager select **Apps** > **All apps** > **Add**).
238237

239-
To ensure that user interaction isn't required, you'll probably want to make Company Portal an iOS/iPadOS VPP app, make it a required app, and use device licensing for the assignment. Make sure that the token doesn't expire and that you have enough device licenses for Company Portal. If the token expires or runs out of licenses, Intune installs the App Store Company Portal instead and prompts for an Apple ID.
240-
241-
> [!NOTE]
242-
> If you set the authentication method to **Company Portal**, make sure that the device enrollment process is completed within the first 24 hours of the Company Portal download to the ADE device. Otherwise enrollment might fail, and a factory reset will be needed to enroll the device.
243-
244-
:::image type="content" source="./media/device-enrollment-program-enroll-ios/install-cp-with-vpp.png" alt-text="Screenshot that shows the options for installing the Company Portal app with VPP.":::
245-
246-
For more information about connecting Intune to Apple Volume Purchase Program (VPP), see [Manage Apple volume-purchased apps](../apps/vpp-apps-ios.md). After you've connected to VPP, you can add the Company Portal app to your Apple Business Manager/Apple School Manager inventory so it can be assigned through Intune.
247238
8. If you selected **Setup Assistant (legacy)** for the authentication method but you also want to use Conditional Access or deploy company apps on the devices, you need to install Company Portal on the devices and sign in to complete the Azure AD registration. To do so, select **Yes** for **Install Company Portal**. If you want users to receive Company Portal without having to authenticate in to the App Store, in **Install Company Portal with VPP**, select a VPP token. Make sure the token doesn't expire and that you have enough device licenses for the Company Portal app to deploy correctly.
248239

249240
9. If you select a token for **Install Company Portal with VPP**, you can lock the device in Single App Mode (specifically, the Company Portal app) right after the Setup Assistant completes. Select **Yes** for **Run Company Portal in Single App Mode until authentication** to set this option. To use the device, the user must first authenticate by signing in with Company Portal.

memdocs/intune/enrollment/multi-factor-authentication.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -73,7 +73,7 @@ To require MFA when a device is enrolled, follow these steps:
7373
8. Choose **Done**.
7474
9. In the **Assignments** section, for **Conditions** you don't need to configure any settings for MFA.
7575
10. In the **Access controls** section, choose **Grant**.
76-
11. In **Grant**, choose **Grant access**, and then select **Require multi-factor authentication**. Don't select **Require device to be marked as compliant** because a device can't be evaluated for compliance until it's enrolled. Then choose **Select**.
76+
11. In **Grant**, choose **Grant access**, and then select **Require multi-factor authentication** and **Require device to be marked as compliant**. Then choose **Select**.
7777
12. In **New policy**, choose **Enable policy** > **On**, and then choose **Create**.
7878

7979
> [!NOTE]

0 commit comments

Comments
 (0)