Skip to content

Commit 53dfcb6

Browse files
[Azure AD] Conditional Access - Retire Approved Client App
1 parent 951616e commit 53dfcb6

File tree

1 file changed

+104
-0
lines changed

1 file changed

+104
-0
lines changed
Lines changed: 104 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,104 @@
1+
---
2+
title: Migrate approved client app to application protection policy in Conditional Access
3+
description: The approved client app control is going away. Migrate to App protection policies.
4+
5+
services: active-directory
6+
ms.service: active-directory
7+
ms.subservice: conditional-access
8+
ms.topic:
9+
ms.date: 01/09/2023
10+
11+
ms.author: joflore
12+
author: MicrosoftGuyJFlo
13+
manager: amycolannino
14+
ms.reviewer: jogro
15+
16+
ms.collection: M365-identity-device-management
17+
---
18+
# Migrate approved client app to application protection policy in Conditional Access
19+
20+
In this article, you’ll learn how to migrate from the approved client app Conditional Access grant to the application protection policy grant. App protection policies provide the same data loss and protection as approved client app policies, but with other benefits. For more information about the benefits of using app protection policies, see the article [App protection policies overview](https://learn.microsoft.com/en-us/mem/intune/apps/app-protection-policy).
21+
22+
The approved client app grant will be retired in March 2026. Please transition all current Conditional Access policies that use only the Require Approved Client App grant to Require Approved Client App or Application Protection Policy by March 2026. Additionally, for any new Conditional Access policy, only apply the Require application protection policy grant.
23+
24+
After March 2026, Microsoft will stop enforcing require approved client app control and it will be as if this grant is not selected. Therefore, please follow the below steps before March 2026 to protect your organization’s data.
25+
26+
## Edit an existing Conditional Access policy
27+
28+
Require approved client apps or app protection policy with mobile devices
29+
30+
The following steps will make an existing Conditional Access policy require an approved client app or an app protection policy when using an iOS/iPadOS or Android device. This policy works in tandem with an app protection policy created in Microsoft Intune.
31+
32+
Organizations can choose to deploy this policy using the steps outlined below or using the Conditional Access templates (Preview).Organizations can choose to deploy this policy using the steps outlined below or using the Conditional Access templates (Preview).
33+
34+
Sign in to the Azure portal as a Conditional Access Administrator, Security Administrator, or Global Administrator.
35+
36+
Browse to Azure Active Directory > Security > Conditional Access.
37+
38+
Select a policy that uses the approved client app grant.
39+
40+
Under Access controls > Grant, select Grant access.
41+
42+
Select Require approved client app and Require app protection policy
43+
44+
For multiple controls select Require one of the selected controls
45+
46+
Confirm your settings and set Enable policy to Report-only.
47+
48+
Select Create to create to enable your policy.
49+
50+
After confirming your settings using report-only mode, an administrator can move the Enable policy toggle from Report-only to On.
51+
52+
Repeat the above steps with all of your policies that leverage the approved client app grant.
53+
54+
> [!WARNING]
55+
> Not all applications that are supported as approved applications or support application protection policies. For a list of some common client apps, see [App protection policy requirement](https://learn.microsoft.com/en-us/azure/active-directory/conditional-access/concept-conditional-access-grant#require-app-protection-policy). If your application is not listed there, contact the application developer.
56+
57+
## Create a Conditional Access policy
58+
59+
Require app protection policy with mobile devices
60+
61+
The following steps will help create a Conditional Access policy requiring an approved client app or an app protection policy when using an iOS/iPadOS or Android device. This policy works in tandem with an [app protection policy created in Microsoft Intune](https://learn.microsoft.com/en-us/mem/intune/apps/app-protection-policies).
62+
63+
Organizations can choose to deploy this policy using the steps outlined below or using the Conditional Access templates (Preview).Organizations can choose to deploy this policy using the steps outlined below or using the Conditional Access templates (Preview).
64+
65+
Sign in to the Azure portal as a Conditional Access Administrator, Security Administrator, or Global Administrator.
66+
67+
Browse to Azure Active Directory > Security > Conditional Access.
68+
69+
Select New policy.
70+
71+
Give your policy a name. We recommend that organizations create a meaningful standard for the names of their policies.
72+
73+
Under Assignments, select Users or workload identities.
74+
75+
Under Include, select All users.
76+
77+
Under Exclude, select Users and groups and exclude at least one account to prevent yourself from being locked out. If you don't exclude any accounts, you can't create the policy.
78+
79+
Under Cloud apps or actions, select All cloud apps.
80+
81+
Under Conditions > Device platforms, set Configure to Yes.
82+
83+
Under Include, Select device platforms.
84+
85+
Choose Android and iOS
86+
87+
Select Done.
88+
89+
Under Access controls > Grant, select Grant access.
90+
91+
Select Require app protection policy
92+
93+
Confirm your settings and set Enable policy to Report-only.
94+
95+
Select Create to create to enable your policy.
96+
97+
After confirming your settings using report-only mode, an administrator can move the Enable policy toggle from Report-only to On.
98+
99+
## Next steps
100+
101+
For more information on application protection policies, see:
102+
103+
[App protection policies overview](https://learn.microsoft.com/en-us/mem/intune/apps/app-protection-policy)
104+

0 commit comments

Comments
 (0)