Skip to content

Commit 03297d6

Browse files
author
Markus Vilcinskas
committed
reclist01
1 parent b8ab7cc commit 03297d6

File tree

1 file changed

+16
-14
lines changed

1 file changed

+16
-14
lines changed

articles/active-directory/reports-monitoring/recommendation-integrate-third-party-apps.md

Lines changed: 16 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -22,39 +22,41 @@ ms.collection: M365-identity-device-management
2222

2323
# Azure AD recommendation: Integrate your third party apps
2424

25-
[Azure AD recommendations](overview-recommendations.md) is a feature that provides you with personalized insights with actionable guidance to align your tenant with recommended best practices.
25+
[Azure AD recommendations](overview-recommendations.md) is a feature that provides you with personalized insights and actionable guidance to align your tenant with recommended best practices.
2626

2727
This article covers the recommendation to integrate third party apps.
2828

2929

3030
## Description
3131

32-
As an Azure AD admin responsible for managing applications, you want to use the Azure AD security features.
32+
As an Azure AD admin responsible for managing applications, you want to use the Azure AD security features with your third party apps. Integrating these apps into Azure AD enables:
33+
34+
- You to use one unified method to manage access to your third party apps.
35+
- Your users to benefit from using single sign-on to access all your apps with a single password.
3336

34-
No users are currently authenticating to any pre-integrated, custom app (BYOA) or SaaS app.
3537

36-
3738

3839
## Logic
3940

40-
Any customer that is not currently authenticating to any pre-integrated, custom (BYOA), or SaaS app with AAD will receive this recommendation. This is validated by whether an application has an "application template id" or "parentappId" in the app metadata, These 2 values indicate that the customer has configured a pre-integrated app from our app gallery or configured a customer application via Bring Your Own App.
41+
If Azure AD determines that none of your users are using Azure AD to authenticate to your third party apps, this recommendation shows up.
4142

4243
## Value
4344

44-
Integrating 3rd party apps with Azure AD allows you to leverage Azure AD's security features, which enables seamless, more productive and more secure sign-ins. You can add an additional security layer to your 3rd party app sign-ins by using conditional access.Action Plan
45+
Integrating third party apps with Azure AD allows you to leverage Azure AD's security features.
46+
The integration:
47+
- Improves the productivity of your users.
4548

46-
Review your apps. Enterprise applications
49+
- Lowers your app management cost.
4750

48-
For each eligible apps, integrate your 3rd party app with Azure AD. Tutorials for integrating SaaS applications with Azure AD
51+
You can then add an additional security layer by using conditional access to control how your users can access your apps.
4952

50-
53+
## Action plan
5154

55+
1. Review the configuration of your apps.
56+
2. For each app that is not integrated into Azure AD yet, verify whether an integration is possible.
5257

5358

54-
55-
5659
## Next steps
5760

58-
* [Azure AD reports overview](overview-reports.md)
59-
* [Programmatic access to Azure AD reports](concept-reporting-api.md)
60-
* [Azure Active Directory risk detections](../identity-protection/overview-identity-protection.md)
61+
- [Tutorials for integrating SaaS applications with Azure Active Directory](../saas-apps/tutorial-list.md)
62+
- [Azure AD reports overview](overview-reports.md)

0 commit comments

Comments
 (0)