Skip to content

Commit 4790ef4

Browse files
authored
Merge pull request #253168 from MicrosoftGuyJFlo/WindowsMAMUpdates
[Microsoft Entra] Windows MAM updates
2 parents 9e98f43 + e74d9ac commit 4790ef4

File tree

2 files changed

+36
-8
lines changed

2 files changed

+36
-8
lines changed

articles/active-directory/conditional-access/how-to-app-protection-policy-windows.md

Lines changed: 33 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ services: active-directory
66
ms.service: active-directory
77
ms.subservice: conditional-access
88
ms.topic: how-to
9-
ms.date: 09/05/2023
9+
ms.date: 10/04/2023
1010

1111
ms.author: joflore
1212
author: MicrosoftGuyJFlo
@@ -17,13 +17,15 @@ ms.collection: M365-identity-device-management
1717
---
1818
# Require an app protection policy on Windows devices (preview)
1919

20-
App protection policies apply mobile application management (MAM) to specific applications on a device. These policies allow for securing data within an application in support of scenarios like bring your own device (BYOD). In the preview, we support applying policy to the Microsoft Edge browser on Windows 11 devices.
20+
App protection policies apply [mobile application management (MAM)](/mem/intune/apps/app-management#mobile-application-management-mam-basics) to specific applications on a device. These policies allow for securing data within an application in support of scenarios like bring your own device (BYOD). In the preview, we support applying policy to the Microsoft Edge browser on Windows 11 devices.
2121

2222
![Screenshot of a browser requiring the user to sign in to their Microsoft Edge profile to access an application.](./media/how-to-app-protection-policy-windows/browser-sign-in-with-edge-profile.png)
2323

2424
## Prerequisites
2525

26-
Customers interested in the public preview need to opt in using the [MAM for Windows Public Preview Sign Up Form](https://aka.ms/MAMforWindowsPublic).
26+
- [Windows 11 Version 22H2 (OS build 22621)](/windows/release-health/windows11-release-information#windows-11-current-versions) or newer.
27+
- [Configured app protection policy targeting Windows devices](/mem/intune/apps/app-protection-policy-settings-windows).
28+
- Currently unsupported in sovereign clouds.
2729

2830
## User exclusions
2931
[!INCLUDE [active-directory-policy-exclusions](../../../includes/active-directory-policy-exclude-user.md)]
@@ -34,7 +36,13 @@ The following policy is put in to [Report-only mode](howto-conditional-access-in
3436

3537
### Require app protection policy for Windows devices
3638

37-
The following steps help create a Conditional Access policy requiring an app protection policy when using a Windows device. The app protection policy must also be configured and assigned to your users in Microsoft Intune. For more information about how to create the app protection policy, see the article [Preview: App protection policy settings for Windows](/mem/intune/apps/app-protection-policy-settings-windows). The following policy includes multiple controls allowing devices to either use app protection policies for mobile application management (MAM) or be managed and compliant with mobile device management (MDM) policies.
39+
The following steps help create a Conditional Access policy requiring an app protection policy when using a Windows device. The app protection policy must also be configured and assigned to your users in Microsoft Intune. For more information about how to create the app protection policy, see the article [App protection policy settings for Windows](/mem/intune/apps/app-protection-policy-settings-windows). The following policy includes multiple controls allowing devices to either use app protection policies for mobile application management (MAM) or be managed and compliant with mobile device management (MDM) policies.
40+
41+
> [!TIP]
42+
> App protection policies (MAM) support unmanaged devices:
43+
>
44+
> - If a device is already managed through mobile device management (MDM), then Intune MAM enrollment is blocked, and app protection policy settings aren't applied.
45+
> - If a device becomes managed after MAM enrollment, app protection policy settings are no longer applied.
3846
3947
1. Sign in to the [Microsoft Entra admin center](https://entra.microsoft.com) as at least a [Conditional Access Administrator](../roles/permissions-reference.md#conditional-access-administrator).
4048
1. Browse to **Protection** > **Conditional Access**.
@@ -44,12 +52,14 @@ The following steps help create a Conditional Access policy requiring an app pro
4452
1. Under **Include**, select **All users**.
4553
1. Under **Exclude**, select **Users and groups** and choose at least your organization's emergency access or break-glass accounts.
4654
1. Under **Target resources** > **Cloud apps** > **Include**, select **Office 365**.
55+
> [!WARNING]
56+
> Selecting **All apps** prevents users from signing in.
4757
1. Under **Conditions**:
48-
1. **Device platforms**, set **Configure** to **Yes**.
58+
1. **Device platforms** set **Configure** to **Yes**.
4959
1. Under **Include**, **Select device platforms**.
5060
1. Choose **Windows** only.
5161
1. Select **Done**.
52-
1. **Client apps**, set **Configure** to **Yes**.
62+
1. **Client apps** set **Configure** to **Yes**.
5363
1. Select **Browser** only.
5464
1. Under **Access controls** > **Grant**, select **Grant access**.
5565
1. Select **Require app protection policy** and **Require device to be marked as compliant**.
@@ -62,6 +72,17 @@ After administrators confirm the settings using [report-only mode](howto-conditi
6272
> [!TIP]
6373
> Organizations should also deploy a policy that [blocks access from unsupported or unknown device platforms](howto-policy-unknown-unsupported-device.md) along with this policy.
6474
75+
In organizations with existing Conditional Access policies that target:
76+
77+
- The **All cloud apps** resource.
78+
- The **Mobile apps and desktop clients** condition.
79+
- Use **Require app protection policy** or a **Block access** grant control.
80+
81+
End users are unable to enroll their Windows device in MAM without the following policy changes.
82+
83+
1. Register the **Microsoft Edge Auth** service principal in your tenant using the command `New-MgServicePrincipal -AppId f2d19332-a09d-48c8-a53b-c49ae5502dfc`.
84+
1. Add an exclusion for **Microsoft Edge Auth** to your existing policy targeting **All cloud apps**.
85+
6586
## Sign in to Windows devices
6687

6788
When users attempt to sign in to a site that is protected by an app protection policy for the first time, they're prompted: To access your service, app or website, you may need to sign in to Microsoft Edge using `[email protected]` or register your device with `organization` if you're already signed in.
@@ -79,7 +100,7 @@ This process opens a window offering to allow Windows to remember your account a
79100
80101
![Screenshot showing the stay signed in to all your apps window. Uncheck the allow my organization to manage my device checkbox.](./media/how-to-app-protection-policy-windows/stay-signed-in-to-all-your-apps.png)
81102

82-
After selecting **OK**, you may see a progress window while policy is applied. After a few moments, you should see a window saying "you're all set", app protection policies are applied.
103+
After selecting **OK**, you may see a progress window while policy is applied. After a few moments, you should see a window saying **You're all set**, app protection policies are applied.
83104

84105
## Troubleshooting
85106

@@ -96,9 +117,13 @@ To resolve these possible scenarios:
96117
- Wait a few minutes and try again in a new tab.
97118
- Contact your administrator to check that Microsoft Intune MAM policies are applying to your account correctly.
98119

120+
#### All apps selected
121+
122+
If your policy for Windows devices targets **All apps** your users aren't able to sign in. Your policy should only target **Office 365**.
123+
99124
### Existing account
100125

101-
If there's a pre-existing, unregistered account, like `[email protected]` in Microsoft Edge, or if a user signs in without registering using the Heads Up Page, then the account isn't properly enrolled in MAM. This configuration blocks the user from being properly enrolled in MAM. This is a known issue.
126+
There's a known issue where there's a pre-existing, unregistered account, like `[email protected]` in Microsoft Edge, or if a user signs in without registering using the Heads Up Page, then the account isn't properly enrolled in MAM. This configuration blocks the user from being properly enrolled in MAM.
102127

103128
## Next steps
104129

articles/active-directory/conditional-access/howto-policy-approved-app-or-app-protection.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -63,6 +63,9 @@ Organizations can choose to deploy this policy using the steps outlined below or
6363

6464
After administrators confirm the settings using [report-only mode](howto-conditional-access-insights-reporting.md), they can move the **Enable policy** toggle from **Report-only** to **On**.
6565

66+
> [!TIP]
67+
> Organizations should also deploy a policy that [blocks access from unsupported or unknown device platforms](howto-policy-unknown-unsupported-device.md) along with this policy.
68+
6669
### Block Exchange ActiveSync on all devices
6770

6871
This policy will block all Exchange ActiveSync clients using basic authentication from connecting to Exchange Online.

0 commit comments

Comments
 (0)