Skip to content

Commit 736c1e0

Browse files
committed
Merge branch 'main' into release-cm2208-tp
2 parents cb028a0 + e0f4c58 commit 736c1e0

2 files changed

Lines changed: 4 additions & 3 deletions

File tree

memdocs/intune/apps/apps-win32-supersedence.md

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ keywords:
66
author: Erikre
77
ms.author: erikre
88
manager: dougeby
9-
ms.date: 08/18/2022
9+
ms.date: 08/25/2022
1010
ms.topic: how-to
1111
ms.service: microsoft-intune
1212
ms.subservice: apps
@@ -62,7 +62,7 @@ The following steps help you create a supersedence relationship between apps:
6262
6. Once this step is finalized, click **Review + save** > **Save**.
6363

6464
> [!IMPORTANT]
65-
> Superseding apps do not get automatic targeting. Each app must have explicit targeting to take effect. Superseding apps that are not targeted will be ignored by the agent. If the superseding app is targeted to a device with a superseded app, then the supersedence will take place regardless of whether the superseded app has targeting or not. For more information on Supersedence behavior, please refer to the matrix below. This behavior is in direct contrast to dependencies, which does not require targeting.
65+
> Superseding apps do not get automatic targeting. Each app must have explicit targeting to take effect. Superseding apps that are not targeted will be ignored by the agent. If the superseding app is targeted to a device with a superseded app, then the supersedence will take place regardless of whether the superseded app has targeting or not. For more information on Supersedence behavior, please refer to the matrix below. This behavior is in direct contrast to dependencies, which does not require targeting. Additionally, only apps that are targeted will show install statuses in Microsoft Endpoint Manager admin center.
6666
6767
## Supersedence behavior
6868

@@ -153,6 +153,7 @@ In the following Supersedence diagram, there are five nodes in total. Hence, fiv
153153
Additional supersedence limitations:
154154
- Azure Virtual Desktop multi-session only supports supersedence relationships with system-context (device-based) apps.
155155
- The Enrollment Status Page (ESP) is not supported with the supersedence public preview. ESP displays provisioning progress after a new device is enrolled, as well as when new users sign into the device. For the supersedence public preview, if an app has a supersedence relationship, it will not be enforced during ESP even if it is included as a selected app in an ESP policy. Additionally, apps that are involved in supersedence relationships will not be sent to the client device during ESP. However, the apps will be sent to the device after ESP completes, and the supersedence relationship will be respected.
156+
- Only apps that are targeted will show install statuses in Microsoft Endpoint Manager admin center.
156157

157158
## Next steps
158159

windows-365/enterprise/requirements.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -71,7 +71,7 @@ You must use [Microsoft Endpoint Manager admin center](https://admin.microsoft.c
7171

7272
## Role and identity requirements
7373

74-
- Admin role: You must be an [Intune Administrator in Azure AD](/azure/active-directory/users-groups-roles/directory-assign-admin-roles#intune-administrator) to provision Cloud PCs.
74+
- Admin role: You must be an [Intune Administrator in Azure AD](/azure/active-directory/users-groups-roles/directory-assign-admin-roles#intune-administrator) or [Windows 365 Administrator](/azure/active-directory/roles/permissions-reference.md#windows-365-administrator) to provision Cloud PCs.
7575
- User identity: Cloud PC users must be configured with [hybrid identities](/azure/active-directory/hybrid/whatis-hybrid-identity) so that they can authenticate with resources both on-premises and in the cloud.
7676

7777
## Supported Azure regions for Cloud PC provisioning

0 commit comments

Comments
 (0)