Skip to content

Commit e122588

Browse files
authored
Merge pull request #8371 from MicrosoftDocs/main
Publish main to live on 9/2 @ 10:30 am
2 parents 1b2f5ad + 808567e commit e122588

2 files changed

Lines changed: 8 additions & 10 deletions

File tree

memdocs/intune/enrollment/windows-bulk-enroll.md

Lines changed: 6 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ keywords:
66
author: Lenewsad
77
ms.author: lanewsad
88
manager: dougeby
9-
ms.date: 10/04/2021
9+
ms.date: 09/02/2022
1010
ms.topic: how-to
1111
ms.service: microsoft-intune
1212
ms.subservice: enrollment
@@ -37,7 +37,11 @@ ms.collection:
3737
As an administrator, you can join large numbers of new Windows devices to Azure Active Directory and Intune. To bulk enroll devices for your Azure AD tenant, you create a provisioning package with the Windows Configuration Designer (WCD) app. Applying the provisioning package to corporate-owned devices joins the devices to your Azure AD tenant and enrolls them for Intune management. Once the package is applied, it's ready for your Azure AD users to sign in.
3838

3939
> [!NOTE]
40-
> Creating a provisioning package does not require any administrator roles in your Azure AD tenant, but the user account that's used to retrieve the token must [be allowed to join devices to Azure AD](/azure/active-directory/devices/device-management-azure-portal#configure-device-settings).
40+
> In the past, any standard user in the tenant could retrieve a bulk enrollment token and create a provisioning package. To increase security, users must now have a specific Azure AD role assignment to create a bulk enrollment token. You can assign roles in Intune for Education > **Tenant settings** or in the Microsoft Endpoint Manager admin center > **Tenant administration**. The roles are:
41+
> - Global Administrator
42+
> - Cloud Device Administrator
43+
> - Intune Administrator
44+
> - Password Administrator
4145
4246
Azure AD users are standard users on these devices and receive assigned Intune policies and required apps. Windows devices that are enrolled into Intune using Windows bulk enrollment can use the Company Portal app to install available apps.
4347

memdocs/intune/remote-actions/remote-help.md

Lines changed: 2 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ keywords:
77
author: Smritib17
88
ms.author: smbhardwaj
99
manager: dougeby
10-
ms.date: 07/26/2022
10+
ms.date: 09/01/2022
1111
ms.topic: how-to
1212
ms.service: microsoft-intune
1313
ms.subservice: remote-actions
@@ -243,9 +243,6 @@ The use of remote help depends on whether you're requesting help or providing he
243243

244244
To request help, you must reach out to your support staff to request assistance. You can reach out through a call, chat, email, and so on, and you'll be the sharer during the session. Be prepared to enter a security code that you'll get from the individual who is assisting you. You'll enter the code in your remote help instance to establish a connection to the helper's instance of remote help.
245245

246-
> [!TIP]
247-
> To avoid an unexpected loss of work, plan to save your active work before a remote help session ends. This is because when a remote help session ends where a helper that has the *Elevation* permission set to **Yes** also uses *Full control*, you are signed out of your device.
248-
249246
As a sharer, when you’ve requested help and both you and the helper are ready to start:
250247

251248
1. Start the remote help app on the device and sign in to authenticate to your organization. The device might not need to be enrolled to Intune if your administrator allows you to get help on unenrolled devices.
@@ -262,10 +259,7 @@ As a sharer, when you’ve requested help and both you and the helper are ready
262259

263260
5. After the issues are resolved, or at any time during the session, both the sharer and helper can end the session. To end the session, select **Leave** in the upper right corner of the remote help app. Upon the end of a session, the sharer is automatically signed out of their device as a security precaution to ensure all connections between the devices close.
264261

265-
### Provide help
266-
267-
> [!TIP]
268-
> Plan to have the sharer save any active work before a remote help session ends to avoid an unexpected loss of work. This is because when a remote help session ends where a helper that has the *Elevation* permission set to Yes also uses *Full control*, the sharer is signed out of their device to ensure any elevated permissions are cleared from the device.
262+
### Provide help
269263

270264
As a helper, after receiving a request from a user who wants assistance by using the remote help app:
271265

0 commit comments

Comments
 (0)