Skip to content

Commit f0004e2

Browse files
authored
Update admin-manage-apps.md
Adding content for the ability to apply Conditional Access policies to granular apps.
1 parent faa52cf commit f0004e2

File tree

1 file changed

+48
-0
lines changed

1 file changed

+48
-0
lines changed

power-platform/admin/admin-manage-apps.md

Lines changed: 48 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -132,6 +132,54 @@ Set-AppAsUnquarantined -EnvironmentName <EnvironmentName> -AppName <AppName>
132132
Get-AppQuarantineState -EnvironmentName <EnvironmentName> -AppName <AppName>
133133
```
134134

135+
## Conditional Access on granular apps (preview)
136+
In addition to respecting Conditional Access policies applied to the Power Apps service, it is possible to apply Azure AD Conditional Access policies to granular Power Apps apps. E.g. An admin can apply a Conditional Access policy requiring Multi-factor authentication only on apps containing sensitive data. Power Apps leverages [Azure AD Conditional Access authentication context](https://docs.microsoft.com/azure/active-directory/conditional-access/concept-conditional-access-cloud-apps#authentication-context-preview) as the mechanism to target Conditional Access policies on granular apps. Admins are the persona allowed to add and remove authentication contexts on an app. Makers cannot edit authentication contexts on an app.
137+
138+
> [!NOTE]
139+
> 1. Authentication contexts set on an app are not moved with apps in solutions and moved across environments. This allows different authentication contexts to be applied to apps in different environments. Also, as an app moves across environments via solutions the authentication context set in an environment is preserved, e.g. if an authentication context is set on an app in a UAT environment, that authentication context is preserved.
140+
> 2. Multiple authentication contexts may be set on an app. An end-user must pass the union of Conditional Access policies applied by multiple authentication contexts.
141+
142+
The following table outlines how Conditional Access enforcement on a specific app impacts the experiences for Admins, Makers and End-users.
143+
144+
| Persona | Experience |
145+
|----------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
146+
| Admin | Regardless of Conditional Access policies associated with an app, an app is visible to admins in Power Platform Admin Center and PowerShell cmdlets. |
147+
| Maker | Regardless of Conditional Access policies associated with an app, an app is visible in https://make.powerapps.com and can be opened for editing in Power Apps Studio. |
148+
| End User | Conditional Access policies applied to an app are enforced when end-users launch the app. A user that does not pass the Conditional Access checks is presented a dialog in the authentication experience indicating they’re not allowed to access the resource. |
149+
150+
After admins associate authentication contexts to Conditional Access policies in https://portal.azure.com they may set the authentication context id on an app. The following image illustrates where to get the authentication context id.
151+
152+
> [!div class="mx-imgBorder"]
153+
> ![Azure Portal Authentication Context id.](media/admin-manage-apps/power_apps_authentication_context_id.png "Azure Portal Authentication Context id.")
154+
155+
End-users that do not meet Conditional Access policy requirements will observe the following dialog after signing in to access an app.
156+
157+
> [!div class="mx-imgBorder"]
158+
> ![Conditional Access enforcement experience.](media/admin-manage-apps/power_apps_conditional_access_AAD_dialog.png "Conditional Access enforcement experience" )
159+
160+
The following table reflects conditional access on granular apps support:
161+
162+
| Power Apps type | Conditional Access on granular apps support |
163+
|------------------|---------------------------------------------|
164+
| Canvas app | Preview availability |
165+
| Model driven app | Not supported |
166+
167+
### Add Conditional Access authentication context ids to an app
168+
```PowerShell
169+
Set-AdminPowerAppConditionalAccessAuthenticationContextIds –EnvironmentName <EnvironmentName> -AppName <AppName> -AuthenticationContextIds <id1, id2, etc...>
170+
```
171+
172+
### Get Conditional Access authentication context ids set on an app
173+
```PowerShell
174+
$app = Get-AdminPowerApp -EnvironmentName <EnvironmentName> -AppName <AppName>
175+
$app.Internal.properties.executionRestrictions.conditionalAccessAuthenticationContextIds
176+
```
177+
178+
### Remove Conditional Access authentication context ids on an app
179+
```PowerShell
180+
Remove-AdminPowerAppConditionalAccessAuthenticationContextIds –EnvironmentName <EnvironmentName> -AppName <AppName>
181+
```
182+
135183
### See also
136184
[Power Apps admin PowerShell support](powerapps-powershell.md#power-apps-commands)
137185

0 commit comments

Comments
 (0)