diff --git a/memdocs/intune/enrollment/quickstart-setup-auto-enrollment.md b/memdocs/intune/enrollment/quickstart-setup-auto-enrollment.md index 47701b8017e..b9f4442956c 100644 --- a/memdocs/intune/enrollment/quickstart-setup-auto-enrollment.md +++ b/memdocs/intune/enrollment/quickstart-setup-auto-enrollment.md @@ -11,7 +11,7 @@ ms.service: microsoft-intune ms.subservice: enrollment ms.localizationpriority: high ms.topic: quickstart -ms.date: 5/10/2024 +ms.date: 10/03/2024 # optional metadata @@ -50,13 +50,13 @@ If you don't have an Intune subscription, [sign up for a free trial account](../ - [Create a group](../fundamentals/quickstart-create-group.md). - [Have Microsoft Entra ID P1 or P2](/azure/active-directory/active-directory-get-started-premium) or the [Premium trial subscription](https://go.microsoft.com/fwlink/?LinkID=816845). You can activate a free Premium trial subscription during setup. -To configure automatic MDM enrollment, you must be an [Intune Administrator](/entra/identity/role-based-access-control/permissions-reference#intune-administrator). If you signed up for an Intune Trial subscription at the beginning of this quickstart, your account has [Global Administrator](/entra/identity/role-based-access-control/permissions-reference#global-administrator) permissions and can complete all procedures in this article. +To configure automatic MDM enrollment, you must be a [Microsoft Entra Global Administrator](/entra/identity/role-based-access-control/permissions-reference#global-administrator). If you signed up for a Microsoft Intune Trial subscription at the beginning of this quickstart, your account has Global Administrator permissions and can complete all procedures in this article. ## Set up automatic enrollment For this example, you'll configure Microsoft Intune mobile device management (MDM) enrollment settings so that corporate-owned and personal devices automatically enroll in Microsoft Intune. *MDM user scope* enables automatic enrollment for Microsoft Intune device management. -1. In the [Microsoft Intune admin center](https://go.microsoft.com/fwlink/?linkid=2109431) go to **Devices** > **Enrollment**. +1. In the [Microsoft Intune admin center](https://go.microsoft.com/fwlink/?linkid=2109431), go to **Devices** > **Enrollment**. 2. Go to the **Windows** tab. Then select **Automatic Enrollment**. > [!IMPORTANT] diff --git a/memdocs/intune/enrollment/windows-enroll.md b/memdocs/intune/enrollment/windows-enroll.md index e840100b3a4..0c810d8fcb2 100644 --- a/memdocs/intune/enrollment/windows-enroll.md +++ b/memdocs/intune/enrollment/windows-enroll.md @@ -59,13 +59,13 @@ This article describes how to enable automatic mobile device management (MDM) en You must have: - A [Microsoft Entra ID P1 or P2 subscription](/azure/active-directory/active-directory-get-started-premium) or [Premium trial subscription](https://go.microsoft.com/fwlink/?LinkID=816845) for automatic MDM enrollment and custom company branding. - A Microsoft Intune subscription. -- A Microsoft Entra Global Administator or Intune Administrator role. For more information about role-based-access-control (RBAC), see [RBAC with Microsoft Intune](../fundamentals/role-based-access-control.md). +- A Microsoft Entra Global Administrator role. For more information about role-based-access-control (RBAC), see [RBAC with Microsoft Intune](../fundamentals/role-based-access-control.md). [!INCLUDE [AAD-enrollment](../includes/win10-automatic-enrollment-aad.md)] ## Support for device users -The Microsoft Intune user-help docs provide conceptual information, tutorials, and how-to guides for employees and students setting up their devices for work. You can point people directly to the Intune docs, or use these articles as guidance when developing and updating your own device management docs. +The Microsoft Intune user help docs provide conceptual information, tutorials, and how-to guides for employees and students setting up their devices for work. You can point people directly to the Intune docs, or use these articles as guidance when developing and updating your own device management docs. Users on personal devices running Windows 11 or Windows 10 can automatically enroll by adding their work or school account on their device, or by using the Intune Company Portal app. Devices running earlier versions of Windows must enroll using the Intune Company Portal app. For more information, see [Enroll Windows 10/11 devices](../user-help/enroll-windows-10-device.md). diff --git a/memdocs/intune/fundamentals/remote-help.md b/memdocs/intune/fundamentals/remote-help.md index d1ebb1bf7bb..988ed027dc7 100644 --- a/memdocs/intune/fundamentals/remote-help.md +++ b/memdocs/intune/fundamentals/remote-help.md @@ -93,7 +93,7 @@ Limitations: - Windows 10/11 on ARM64 devices - Windows 365 - Samsung and Zebra devices enrolled as Android Enterprise dedicated devices - - macOS 12, 13, 14 + - macOS 12, 13, 14, and 15 Remote Help isn't supported on GCC High or DoD (U.S. Department of Defense) tenants. For more information, go to [Microsoft Intune for US Government GCC High and DoD service description](intune-govt-service-description.md). @@ -109,7 +109,7 @@ This feature applies to: - Windows 10 on ARM64 devices - Windows 365 - Android Enterprise Dedicated (Samsung and Zebra devices) -- macOS 12, 13 and 14 +- macOS 12, 13, 14, and 15 ## Data and privacy diff --git a/windows-365/business/TOC.yml b/windows-365/business/TOC.yml index 8579a5e14e5..93968802c2d 100644 --- a/windows-365/business/TOC.yml +++ b/windows-365/business/TOC.yml @@ -31,6 +31,8 @@ items: href: change-organization-default-settings.md - name: Remotely manage Cloud PCs href: remotely-manage-business-cloud-pcs.md + - name: Resize a Cloud PC + href: resize-cloud-pc.md - name: Reset a user's password href: reset-user-password.md - name: Restore a Cloud PC to an earlier state diff --git a/windows-365/enterprise/resize-cloud-pc.md b/windows-365/enterprise/resize-cloud-pc.md index fb85c13b025..abe679ca475 100644 --- a/windows-365/enterprise/resize-cloud-pc.md +++ b/windows-365/enterprise/resize-cloud-pc.md @@ -7,7 +7,7 @@ keywords: author: ErikjeMS ms.author: erikje manager: dougeby -ms.date: 07/09/2024 +ms.date: 10/03/2024 ms.topic: overview ms.service: windows-365 ms.subservice: windows-365-enterprise @@ -31,30 +31,7 @@ ms.collection: # Resize a Cloud PC -The **Resize** remote action, which preserves user and disk data, lets you: - -- Upgrade the RAM, CPU, and storage size of a Cloud PC. -- Downgrade the RAM and CPU of Cloud PC. Resizing doesn't let you downsize disk space. - -These operations don't require reprovisioning of the Cloud PC. - -You might consider resizing a Cloud PC when a user needs: - -- Higher RAM and VCPU cores to run CPU intensive applications. -- More disk space for file storing. -- Less RAM and vCPU cores to run their current workload applications. - -Resizing supports: - -- Direct and group-based licenses. -- Paid, preview, and trial licenses. -- Bulk and single device operations. - -Resizing doesn't support: - -- GPU Cloud PCs. GPU Cloud PCs might show up in the resize flow, but trying to resize a GPU Cloud PC will result in an error. - -Resizing automatically disconnects the user from their session and any unsaved work might be lost. Therefore, it's best to coordinate any resizing with the user before you begin. Contact your end users and have them save their work and sign out before you begin resizing. +[!INCLUDE [Resize a Cloud PC intro](../includes/resize-introduction.md)] Downsizing may impact support for nested virtualization. For more information, see [Set up virtualization-based workloads support](nested-virtualization.md). @@ -75,24 +52,9 @@ To resize a Cloud PC, the admin must have certain built-in Microsoft Entra roles Alternatively, you can assign a custom role that includes the permissions of these built-in roles. -## IP address requirements - -When resizing a Microsoft Entra hybrid join bring-your-own-network Cloud PC, a second IP address must be available in the subnet for the Cloud PC to be resized. +[!INCLUDE [Resize a Cloud PC IP requirements](../includes/resize-ip-address-requirements.md)] -During the resizing operation, a second IP address is used when moving to the new size. This precaution makes sure that the Cloud PC can be rolled back to the original should an issue occur. - -To account for this precaution, you can: - -- Make sure that adequate IP addresses are available in the vNET for all Cloud PCs to be resized, or -- Stagger your resize operations to make sure that the address scope is maintained. - -If inadequate addresses are available, resize failures can occur. - -### Other requirements - -In order to use **Resize** there must be available licenses in inventory for the resized Cloud PC configuration. - -To **Resize** a Cloud PC, it must have a status of **Provisioned** in the Windows 365 provisioning node. +[!INCLUDE [Resize a Cloud PC other requirements](../includes/resize-other-requirements.md)] ## Resize a single Cloud PC provisioned with a direct assigned license @@ -174,13 +136,7 @@ If the source license isn't removed, and the target license isn't assigned withi If you have a combination of paid and trial licenses, the resize feature uses your paid licenses first. After these licenses run out, the resize operation uses your trial licenses. -When resizing starts, the user is automatically disconnected from their Cloud PC and any unsaved work might be lost. - -Resizing can take from 15 to 20 minutes before the user can access their Cloud PC again. You can monitor the status in the Windows 365 provisioning blade. Users can see their Cloud PC status at https://windows365.microsoft.com. - -If there are no licenses in your inventory, the resizing fails. To request more licenses, contact your procurement admin. After you purchase the license and added to the inventory in the Microsoft 365 admin center, you can retry the resize operation. Licenses can be purchased from various channels: EA, CSP, MCA, and Web Direct. - -Devices with a state of **Resize not supported** aren't resized. The status message and details can help you identify the issue. You can still proceed with a bulk resize even if you have devices in the list that are marked as **Resize not supported**. +[!INCLUDE [Resize a Cloud PC details](../includes/resize-details.md)] ## Resize with Step-up Licenses