Skip to content

Commit d5bc3a7

Browse files
Merge pull request #251092 from omondiatieno/hybrid-integrations
Secure hybrid-integrations - UI updates
2 parents d3eb56b + 1400218 commit d5bc3a7

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

articles/active-directory/manage-apps/secure-hybrid-access-integrations.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -37,10 +37,10 @@ The solution that you build can include the following parts:
3737

3838
* **App discovery** - Often, customers aren't aware of every application in use
3939
* Application discovery finds applications, facilitating app integrating with Azure AD
40-
* **App migration** - Create a workflow to integrate apps with Azure AD without using the Azure portal
40+
* **App migration** - Create a workflow to integrate apps with Azure AD without using the Microsoft Entra admin center
4141
* Integrate apps that customers use today
4242
* **Legacy authentication support** - Connect apps with legacy authentication methods and single sign-on (SSO)
43-
* **Conditional Access** - Enable customers to apply Azure AD policies to apps in your solution without using the Azure portal
43+
* **Conditional Access** - Enable customers to apply Azure AD policies to apps in your solution without using the Microsoft Entra admin center
4444

4545
Learn more: [What is Conditional Access?](../conditional-access/overview.md)
4646

@@ -250,7 +250,7 @@ https://graph.microsoft.com/v1.0/applications/54c4806b-b260-4a12-873c-9671169837
250250

251251
After the SaaS applications are registered in Azure AD, the applications need to start using Azure AD as the identity provider (IdP):
252252

253-
- **Applications support one-click SSO** - Azure AD enables the applications. In the Azure portal, the customer performs one-click SSO with the administrative credentials for the supported SaaS applications.
253+
- **Applications support one-click SSO** - Azure AD enables the applications. In the Microsoft Entra admin center, the customer performs one-click SSO with the administrative credentials for the supported SaaS applications.
254254
- Learn more: [One-click app configuration of single sign-on](./one-click-sso-tutorial.md)
255255
- **Applications don't support one-click SSO** - The customer enables the applications to use Azure AD.
256256
- [Tutorials for integrating SaaS applications with Azure Active Directory](../saas-apps/tutorial-list.md)
@@ -357,7 +357,7 @@ https://graph.microsoft.com/v1.0/applications/{Application Object ID}
357357
358358
### Apply Conditional Access policies
359359

360-
Customers and partners can use the Microsoft Graph API to create or apply per application [Conditional Access policies](../conditional-access/overview.md). For partners, customers can apply these policies from your solution without using the Azure portal. There are two options to apply Azure AD Conditional Access policies:
360+
Customers and partners can use the Microsoft Graph API to create or apply per application [Conditional Access policies](../conditional-access/overview.md). For partners, customers can apply these policies from your solution without using the Microsoft Entra admin center. There are two options to apply Azure AD Conditional Access policies:
361361

362362
- [Assign the application to a Conditional Access policy](#use-a-conditional-access-policy)
363363
- [Create a new Conditional Access policy and assign the application to it](#create-a-new-conditional-access-policy)

0 commit comments

Comments
 (0)