Skip to content

Commit 8e43681

Browse files
committed
Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into heidist-work
2 parents 12e8085 + 867938f commit 8e43681

File tree

196 files changed

+3202
-1011
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

196 files changed

+3202
-1011
lines changed

.openpublishing.redirection.defender-for-cloud.json

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -764,6 +764,11 @@
764764
"source_path_from_root": "/articles/defender-for-cloud/plan-multicloud-security-other-resources.md",
765765
"redirect_url": "/azure/defender-for-cloud/multicloud",
766766
"redirect_document_id": true
767+
},
768+
{
769+
"source_path_from_root": "/articles/defender-for-cloud/defender-for-servers-introduction.md",
770+
"redirect_url": "/azure/defender-for-cloud/plan-defender-for-servers",
771+
"redirect_document_id": true
767772
}
768773
]
769774
}

articles/active-directory/develop/msal-android-shared-devices.md

Lines changed: 9 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ ms.service: active-directory
99
ms.subservice: develop
1010
ms.topic: conceptual
1111
ms.workload: identity
12-
ms.date: 09/30/2021
12+
ms.date: 12/06/2022
1313
ms.author: henrymbugua
1414
ms.reviewer: brandwe
1515
ms.custom: aaddev, identitypla | Azuretformtop40
@@ -93,8 +93,14 @@ If your application is running in multiple-account mode, and an administrator pu
9393

9494
These Microsoft applications support Azure AD's shared device mode:
9595

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+
98104
## Shared device sign-out and the overall app lifecycle
99105

100106
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.

articles/active-directory/develop/msal-shared-devices.md

Lines changed: 13 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -17,24 +17,17 @@ ms.custom: aaddev
1717

1818
# Overview of shared device mode
1919

20-
Shared device mode is a feature of Azure Active Directory that 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.
2121

2222
>[!IMPORTANT]
2323
> Shared device mode for iOS [!INCLUDE [PREVIEW BOILERPLATE](../../../includes/active-directory-develop-preview.md)]
2424
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.
3225

3326
### Supporting multiple users on devices designed for one user
3427

3528
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.
3629

37-
### Global sign-in and sign-out (SSO)
30+
### Automatic single sign-in and single sign-out
3831

3932
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.
4033

@@ -45,7 +38,7 @@ Azure Active Directory enables these scenarios with a feature called **shared de
4538
As mentioned, shared device mode is a feature of Azure Active Directory that enables you to:
4639

4740
* 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.
4942

5043
### Build applications that support frontline workers
5144

@@ -60,7 +53,11 @@ Supported features are:
6053

6154
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.
6255

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.
6461

6562
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.
6663

@@ -70,6 +67,11 @@ Once your applications support shared device mode and include the required data
7067

7168
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.
7269

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+
7375
## Next steps
7476

7577
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.

articles/active-directory/governance/complete-access-review.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,7 @@ ms.reviewer: mwahl
1717
ms.collection: M365-identity-device-management
1818
---
1919

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
2121

2222
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.
2323

articles/active-directory/governance/conditional-access-exclusion.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,7 @@ ms.reviewer: mwahl
1717
ms.collection: M365-identity-device-management
1818
---
1919

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
2121

2222
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.
2323

@@ -142,7 +142,7 @@ that is excluded from the policy. Here is a recommended access review where memb
142142
![Create an access review pane for example 2](./media/conditional-access-exclusion/create-access-review-2.png)
143143

144144
>[!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).
146146
147147
## Access review results and audit logs
148148

@@ -160,7 +160,7 @@ Now that you have everything in place, group, Conditional Access policy, and acc
160160

161161
![Access reviews audit logs listing actions](./media/conditional-access-exclusion/access-reviews-audit-logs.png)
162162

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 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.
164164

165165
## Next steps
166166

articles/active-directory/governance/deploy-access-reviews.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -442,5 +442,5 @@ For more advanced queries and analysis of access reviews, and to track changes a
442442

443443
Learn about the following related technologies:
444444

445-
* [What is Microsoft Entra entitlement management?](entitlement-management-overview.md)
446-
* [What is Microsoft Entra Privileged Identity Management?](../privileged-identity-management/pim-configure.md)
445+
* [What is Microsoft entitlement management?](entitlement-management-overview.md)
446+
* [What is Microsoft Privileged Identity Management?](../privileged-identity-management/pim-configure.md)

articles/active-directory/governance/entitlement-management-access-package-approval-policy.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
2-
title: Change approval settings for an access package in Microsoft Entra entitlement management - Azure Active Directory
3-
description: Learn how to change approval and requestor information settings for an access package in Azure Active Directory entitlement management.
2+
title: Change approval settings for an access package in entitlement management - Microsoft Entra
3+
description: Learn how to change approval and requestor information settings for an access package in entitlement management.
44
services: active-directory
55
documentationCenter: ''
66
author: owinfreyATL
@@ -20,7 +20,7 @@ ms.collection: M365-identity-device-management
2020
#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.
2121

2222
---
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
2424

2525
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.
2626

articles/active-directory/governance/entitlement-management-access-package-assignments.md

Lines changed: 7 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
2-
title: View, add, and remove assignments for an access package in Microsoft Entra entitlement management - Azure Active Directory
3-
description: Learn how to view, add, and remove assignments for an access package in Azure Active Directory entitlement management.
2+
title: View, add, and remove assignments for an access package in entitlement management - Microsoft Entra
3+
description: Learn how to view, add, and remove assignments for an access package in entitlement management.
44
services: active-directory
55
documentationCenter: ''
66
author: owinfreyATL
@@ -20,13 +20,13 @@ ms.collection: M365-identity-device-management
2020
#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.
2121

2222
---
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
2424

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.
2626

2727
## Prerequisites
2828

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:
3030

3131

3232
- Azure AD Premium P2
@@ -111,7 +111,8 @@ In some cases, you might want to directly assign specific users to an access pac
111111
> 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).
112112
113113
## 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.
115116

116117
**Prerequisite role:** Global administrator, User administrator, Catalog owner, Access package manager or Access package assignment manager
117118

0 commit comments

Comments
 (0)