Skip to content

Commit aa78794

Browse files
authored
Merge pull request #106691 from MicrosoftGuyJFlo/SessionFix
[Azure AD] Conditional Access - Session control article fix
2 parents cfcd0a1 + ecac757 commit aa78794

File tree

1 file changed

+7
-19
lines changed
  • articles/active-directory/conditional-access

1 file changed

+7
-19
lines changed

articles/active-directory/conditional-access/controls.md

Lines changed: 7 additions & 19 deletions
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,7 @@ ms.collection: M365-identity-device-management
1717
---
1818
# Custom controls (preview)
1919

20-
Custom controls are a capability of the Azure Active Directory Premium P1 edition. When using custom controls, your users are redirected to a compatible service to satisfy further requirements outside of Azure Active Directory. To satisfy this control, a users browser is redirected to the external service, performs any required authentication or validation activities, and is then redirected back to Azure Active Directory. Azure Active Directory verifies the response and, if the user was successfully authenticated or validated, the user continues in the Conditional Access flow.
20+
Custom controls are a capability of the Azure Active Directory Premium P1 edition. When using custom controls, your users are redirected to a compatible service to satisfy further requirements outside of Azure Active Directory. To satisfy this control, a user's browser is redirected to the external service, performs any required authentication or validation activities, and is then redirected back to Azure Active Directory. Azure Active Directory verifies the response and, if the user was successfully authenticated or validated, the user continues in the Conditional Access flow.
2121

2222
These controls allow the use of certain external or custom services as Conditional Access controls, and generally extend the capabilities of Conditional Access.
2323

@@ -42,7 +42,7 @@ To create a custom control, you should first contact the provider that you wish
4242

4343
Custom controls cannot be used with Identity Protection's automation requiring multi-factor authentication or to elevate roles in Privileged Identity Manager (PIM).
4444

45-
Copy the JSON data and then paste it into the related textbox. Do not make any changes to the JSON unless you explicitly understand the change youre making. Making any change could break the connection between the provider and Microsoft and potentially lock you and your users out of your accounts.
45+
Copy the JSON data and then paste it into the related textbox. Do not make any changes to the JSON unless you explicitly understand the change you're making. Making any change could break the connection between the provider and Microsoft and potentially lock you and your users out of your accounts.
4646

4747
The option to create a custom control is in the **Manage** section of the **Conditional Access** page.
4848

@@ -54,7 +54,7 @@ Clicking **New custom control**, opens a blade with a textbox for the JSON data
5454

5555
## Deleting custom controls
5656

57-
To delete a custom control, you must first ensure that it isnt being used in any Conditional Access policy. Once complete:
57+
To delete a custom control, you must first ensure that it isn't being used in any Conditional Access policy. Once complete:
5858

5959
1. Go to the Custom controls list
6060
1. Click …
@@ -64,22 +64,10 @@ To delete a custom control, you must first ensure that it isn’t being used in
6464

6565
To edit a custom control, you must delete the current control and create a new control with the updated information.
6666

67-
## Session controls
68-
69-
Session controls enable limited experience within a cloud app. The session controls are enforced by cloud apps and rely on additional information provided by Azure AD to the app about the session.
70-
71-
![Control](./media/controls/31.png)
72-
73-
### Use app enforced restrictions
74-
75-
You can use this control to require Azure AD to pass device information to the selected cloud apps. The device information enables the cloud apps to know whether a connection is initiated from a compliant or domain-joined device. This control only supports SharePoint Online and Exchange Online as selected cloud apps. When selected, the cloud app uses the device information to provide users, depending on the device state, with a limited or full experience.
76-
77-
To learn more, see:
67+
## Next steps
7868

79-
- [Enabling limited access with SharePoint Online](https://aka.ms/spolimitedaccessdocs)
80-
- [Enabling limited access with Exchange Online](https://aka.ms/owalimitedaccess)
69+
- [Conditional Access common policies](concept-conditional-access-policy-common.md)
8170

82-
## Next steps
71+
- [Report-only mode](concept-conditional-access-report-only.md)
8372

84-
- If you want to know how to configure a Conditional Access policy, see [Require MFA for specific apps with Azure Active Directory Conditional Access](app-based-mfa.md).
85-
- If you are ready to configure Conditional Access policies for your environment, see the [best practices for Conditional Access in Azure Active Directory](best-practices.md).
73+
- [Simulate sign in behavior using the Conditional Access What If tool](troubleshoot-conditional-access-what-if.md)

0 commit comments

Comments
 (0)