You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/active-directory/develop/msal-android-shared-devices.md
+9-3Lines changed: 9 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,7 +9,7 @@ ms.service: active-directory
9
9
ms.subservice: develop
10
10
ms.topic: conceptual
11
11
ms.workload: identity
12
-
ms.date: 09/30/2021
12
+
ms.date: 12/06/2022
13
13
ms.author: henrymbugua
14
14
ms.reviewer: brandwe
15
15
ms.custom: aaddev, identitypla | Azuretformtop40
@@ -93,8 +93,14 @@ If your application is running in multiple-account mode, and an administrator pu
93
93
94
94
These Microsoft applications support Azure AD's shared device mode:
95
95
96
-
*[Microsoft Teams](/microsoftteams/platform/)
97
-
*[Microsoft Managed Home Screen](/mem/intune/apps/app-configuration-managed-home-screen-app) app for Android Enterprise
96
+
-[Microsoft Teams](/microsoftteams/platform/)
97
+
-[Microsoft Managed Home Screen](/mem/intune/apps/app-configuration-managed-home-screen-app) app for Android Enterprise
98
+
-[Microsoft Edge](/microsoft-edge) (in Public Preview)
99
+
-[Yammer](/yammer) (in Public Preview)
100
+
101
+
> [!IMPORTANT]
102
+
> Public preview is provided without a service-level agreement and isn't recommended for production workloads. Some features might be unsupported or have constrained capabilities. For more information, see [Supplemental terms of use for Microsoft Azure previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/).
103
+
98
104
## Shared device sign-out and the overall app lifecycle
99
105
100
106
When a user signs out, you'll need to take action to protect the privacy and data of the user. For example, if you're building a medical records app you'll want to make sure that when the user signs out previously displayed patient records are cleared. Your application must be prepared for data privacy and check every time it enters the foreground.
Copy file name to clipboardExpand all lines: articles/active-directory/develop/msal-shared-devices.md
+13-11Lines changed: 13 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -17,24 +17,17 @@ ms.custom: aaddev
17
17
18
18
# Overview of shared device mode
19
19
20
-
Shared device mode is a feature of Azure Active Directorythat allows you to build applications that support frontline workers and enable shared device mode on the devices deployed to them.
20
+
Shared device mode is a feature of Azure Active Directory(Azure AD) that allows you to build and deploy applications that support frontline workers and educational scenarios that require shared Android and iOS devices.
21
21
22
22
>[!IMPORTANT]
23
23
> Shared device mode for iOS [!INCLUDE [PREVIEW BOILERPLATE](../../../includes/active-directory-develop-preview.md)]
24
24
25
-
## What are frontline workers?
26
-
27
-
Frontline workers are retail employees, maintenance and field agents, medical personnel, and other users that don't sit in front of a computer or use corporate email for collaboration. The following sections introduce the aspects and challenges of supporting frontline workers, followed by an introduction to the features provided by Microsoft that enable your application for use by an organization's frontline workers.
28
-
29
-
### Challenges of supporting frontline workers
30
-
31
-
Enabling frontline worker workflows includes challenges not usually presented by typical information workers. Such challenges can include high turnover rate and less familiarity with an organization's core productivity tools. To empower their frontline workers, organizations are adopting different strategies. Some are adopting a bring-your-own-device (BYOD) strategy in which their employees use business apps on their personal phone, while others provide their employees with shared devices like iPads or Android tablets.
32
25
33
26
### Supporting multiple users on devices designed for one user
34
27
35
28
Because mobile devices running iOS or Android were designed for single users, most applications optimize their experience for use by a single user. Part of this optimized experience means enabling single sign-on across applications and keeping users signed in on their device. When a user removes their account from an application, the app typically doesn't consider it a security-related event. Many apps even keep a user's credentials around for quick sign-in. You may even have experienced this yourself when you've deleted an application from your mobile device and then reinstalled it, only to discover you're still signed in.
36
29
37
-
### Global sign-in and sign-out (SSO)
30
+
### Automatic single sign-in and single sign-out
38
31
39
32
To allow an organization's employees to use its apps across a pool of devices shared by those employees, developers need to enable the opposite experience. Employees should be able to pick a device from the pool and perform a single gesture to "make it theirs" for the duration of their shift. At the end of their shift, they should be able to perform another gesture to sign out globally on the device, with all their personal and company information removed so they can return it to the device pool. Furthermore, if an employee forgets to sign out, the device should be automatically signed out at the end of their shift and/or after a period of inactivity.
40
33
@@ -45,7 +38,7 @@ Azure Active Directory enables these scenarios with a feature called **shared de
45
38
As mentioned, shared device mode is a feature of Azure Active Directory that enables you to:
46
39
47
40
* Build applications that support frontline workers
48
-
* Deploy devices to frontline workers and turn on shared device mode
41
+
* Deploy devices to frontline workers with apps that support shared device mode.
49
42
50
43
### Build applications that support frontline workers
51
44
@@ -60,7 +53,11 @@ Supported features are:
60
53
61
54
Supporting shared device mode should be considered a feature upgrade for your application, and can help increase its adoption in environments where the same device is used among multiple users.
62
55
63
-
Your users depend on you to ensure their data isn't leaked to another user. Share Device Mode provides helpful signals to indicate to your application that a change you should manage has occurred. Your application is responsible for checking the state of the user on the device every time the app is used, clearing the previous user's data. This includes if it is reloaded from the background in multi-tasking. On a user change, you should ensure both the previous user's data is cleared and that any cached data being displayed in your application is removed. We recommend you always perform a thorough security review process after adding shared device mode capability to your app.
56
+
Your users depend on you to ensure their data isn't leaked to another user. Share Device Mode provides helpful signals to indicate to your application that a change you should manage has occurred. Your application is responsible for checking the state of the user on the device every time the app is used, clearing the previous user's data. This includes if it is reloaded from the background in multi-tasking. On a user change, you should ensure both the previous user's data is cleared and that any cached data being displayed in your application is removed.
57
+
58
+
To support all data loss prevention scenarios, we also recommend you integrate with the [Intune App SDK](/mem/intune/developer/app-sdk). By using the Intune App SDK, you can allow your application to support Intune [App Protection Policies](/mem/intune/apps/app-protection-policy). In particular, we recommend that you integrate with Intune's [selective wipe](/mem/intune/developer/app-sdk-android-phase5#selective-wipe) capabilities and [deregister the user on iOS](/mem/intune/developer/app-sdk-ios#deregister-user-accounts) during a sign-out.
59
+
60
+
Lastly, we recommend you always perform a thorough security review process after adding shared device mode capability to your app.
64
61
65
62
For details on how to modify your applications to support shared device mode, see the [Next steps](#next-steps) section at the end of this article.
66
63
@@ -70,6 +67,11 @@ Once your applications support shared device mode and include the required data
70
67
71
68
An organization's device administrators are able to deploy their devices and your applications to their stores and workplaces through a mobile device management (MDM) solution like Microsoft Intune. Part of the provisioning process is marking the device as a *Shared Device*. Administrators configure shared device mode by deploying the [Microsoft Authenticator app](https://support.microsoft.com/account-billing/how-to-use-the-microsoft-authenticator-app-9783c865-0308-42fb-a519-8cf666fe0acc) and setting shared device mode through configuration parameters. After performing these steps, all applications that support shared device mode will use the Microsoft Authenticator application to manage its user state and provide security features for the device and organization.
72
69
70
+
### Use App Protection Policies to provide data loss prevention between users.
71
+
For data protection capabilities along with shared device mode, Microsoft’s supported data protection solution for Microsoft 365 applications on Android and iOS is Microsoft Intune Application Protection Policies. For more information about the policies, see [App protection policies overview - Microsoft Intune | Microsoft Learn](/mem/intune/apps/app-protection-policy).
72
+
73
+
When setting up App protection policies for shared devices, we recommend using [level 2 enterprise enhanced data protection](/mem/intune/apps/app-protection-framework#level-2-enterprise-enhanced-data-protection). With level 2 data protection, you can restrict data transfer scenarios that may cause data to move to parts of the device that are not cleared with shared device mode.
74
+
73
75
## Next steps
74
76
75
77
We support iOS and Android platforms for shared device mode. Review the documentation below for your platform to begin supporting frontline workers in your applications.
Copy file name to clipboardExpand all lines: articles/active-directory/governance/complete-access-review.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -17,7 +17,7 @@ ms.reviewer: mwahl
17
17
ms.collection: M365-identity-device-management
18
18
---
19
19
20
-
# Complete an access review of groups and applications in Microsoft Entra access reviews
20
+
# Complete an access review of groups and applications in access reviews
21
21
22
22
As an administrator, you [create an access review of groups or applications](create-access-review.md) and reviewers [perform the access review](perform-access-review.md). This article describes how to see the results of the access review and apply them.
Copy file name to clipboardExpand all lines: articles/active-directory/governance/conditional-access-exclusion.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -17,7 +17,7 @@ ms.reviewer: mwahl
17
17
ms.collection: M365-identity-device-management
18
18
---
19
19
20
-
# Use Microsoft Entra access reviews to manage users excluded from Conditional Access policies
20
+
# Use access reviews to manage users excluded from Conditional Access policies
21
21
22
22
In an ideal world, all users follow the access policies to secure access to your organization's resources. However, sometimes there are business cases that require you to make exceptions. This article goes over some examples of situations where exclusions may be necessary. You, as the IT administrator, can manage this task, avoid oversight of policy exceptions, and provide auditors with proof that these exceptions are reviewed regularly using Azure Active Directory (Azure AD) access reviews.
23
23
@@ -142,7 +142,7 @@ that is excluded from the policy. Here is a recommended access review where memb
142
142

143
143
144
144
>[!IMPORTANT]
145
-
>If you have many exclusion groups and therefore need to create multiple access reviews, we now have an API in the Microsoft Graph beta endpoint that allows you to create and manage them programmatically. To get started, see the [Microsoft Entra access reviews API reference](/graph/api/resources/accessreviewsv2-overview) and [Example of retrieving Microsoft Entra access reviews via Microsoft Graph](https://techcommunity.microsoft.com/t5/Azure-Active-Directory/Example-of-retrieving-Azure-AD-access-reviews-via-Microsoft/td-p/236096).
145
+
>If you have many exclusion groups and therefore need to create multiple access reviews, we now have an API in the Microsoft Graph beta endpoint that allows you to create and manage them programmatically. To get started, see the [access reviews API reference](/graph/api/resources/accessreviewsv2-overview) and [Example of retrieving access reviews via Microsoft Graph](https://techcommunity.microsoft.com/t5/Azure-Active-Directory/Example-of-retrieving-Azure-AD-access-reviews-via-Microsoft/td-p/236096).
146
146
147
147
## Access review results and audit logs
148
148
@@ -160,7 +160,7 @@ Now that you have everything in place, group, Conditional Access policy, and acc
As an IT administrator, you know that managing exclusion groups to your policies is sometimes inevitable. However, maintaining these groups, reviewing them on a regular basis by the business owner or the users themselves, and auditing these changes can be made easier with Microsoft Entra access reviews.
163
+
As an IT administrator, you know that managing exclusion groups to your policies is sometimes inevitable. However, maintaining these groups, reviewing them on a regular basis by the business owner or the users themselves, and auditing these changes can be made easier with access reviews.
#Customer intent: As an administrator, I want detailed information about how I can edit an access package so that requestors have the resources they need to perform their job.
21
21
22
22
---
23
-
# Change approval and requestor information settings for an access package in Microsoft Entra entitlement management
23
+
# Change approval and requestor information settings for an access package in entitlement management
24
24
25
25
As an access package manager, you can change the approval and requestor information settings for an access package at any time by editing an existing policy or adding a new policy for requesting access.
#Customer intent: As an administrator, I want detailed information about how I can edit an access package so that requestors have the resources they need to perform their job.
21
21
22
22
---
23
-
# View, add, and remove assignments for an access package in Microsoft Entra entitlement management
23
+
# View, add, and remove assignments for an access package in entitlement management
24
24
25
-
In Microsoft Entra entitlement management, you can see who has been assigned to access packages, their policy, and status. If an access package has an appropriate policy, you can also directly assign user to an access package. This article describes how to view, add, and remove assignments for access packages.
25
+
In entitlement management, you can see who has been assigned to access packages, their policy, and status. If an access package has an appropriate policy, you can also directly assign user to an access package. This article describes how to view, add, and remove assignments for access packages.
26
26
27
27
## Prerequisites
28
28
29
-
To use Microsoft Entra entitlement management and assign users to access packages, you must have one of the following licenses:
29
+
To use entitlement management and assign users to access packages, you must have one of the following licenses:
30
30
31
31
32
32
- Azure AD Premium P2
@@ -111,7 +111,8 @@ In some cases, you might want to directly assign specific users to an access pac
111
111
> When assigning users to an access package, administrators will need to verify that the users are eligible for that access package based on the existing policy requirements. Otherwise, the users won't successfully be assigned to the access package. If the access package contains a policy that requires user requests to be approved, users can't be directly assigned to the package without necessary approval(s) from the designated approver(s).
112
112
113
113
## Directly assign any user (Preview)
114
-
Microsoft Entra Entitlement Management also allows you to directly assign external users to an access package to make collaborating with partners easier. To do this, the access package must have a policy that allows users not yet in your directory to request access.
114
+
115
+
Entitlement management also allows you to directly assign external users to an access package to make collaborating with partners easier. To do this, the access package must have a policy that allows users not yet in your directory to request access.
115
116
116
117
**Prerequisite role:** Global administrator, User administrator, Catalog owner, Access package manager or Access package assignment manager
0 commit comments