Skip to content

Commit 8586583

Browse files
committed
graph-name
1 parent e2d2add commit 8586583

File tree

1 file changed

+6
-4
lines changed

1 file changed

+6
-4
lines changed

articles/active-directory/reports-monitoring/recommendation-migrate-from-adal-to-msal.md

Lines changed: 6 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ ms.service: active-directory
88
ms.topic: reference
99
ms.workload: identity
1010
ms.subservice: report-monitor
11-
ms.date: 03/15/2023
11+
ms.date: 04/18/2023
1212
ms.author: sarahlipsey
1313
ms.reviewer: jamesmantu
1414

@@ -19,7 +19,7 @@ ms.collection: M365-identity-device-management
1919

2020
[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.
2121

22-
This article covers the recommendation to migrate from the Azure Active Directory Library to the Microsoft Authentication Libraries. This recommendation is called `???` in the recommendations API in Microsoft Graph.
22+
This article covers the recommendation to migrate from the Azure Active Directory Library to the Microsoft Authentication Libraries. This recommendation is called `AdalToMsalMigration` in the recommendations API in Microsoft Graph.
2323

2424
## Description
2525

@@ -29,7 +29,7 @@ This recommendation shows up if your tenant has applications that still use ADAL
2929

3030
## Value
3131

32-
MSAL is designed to enable a secure solution without developers having to worry about the implementation details. MSAL simplifies and manages acquiring, managing, caching, and refreshing tokens, and uses best practices for resilience. For more information on migrating to MSAL, see [Migrate applications to MSAL](../develop/msal-migration.md).
32+
MSAL is designed to enable a secure solution without developers having to worry about the implementation details. MSAL simplifies how tokens are acquired, managed, cached, and refreshed. MSAL also uses best practices for resilience. For more information on migrating to MSAL, see [Migrate applications to MSAL](../develop/msal-migration.md).
3333

3434
Existing apps that use ADAL will continue to work after the end-of-support date.
3535

@@ -38,16 +38,18 @@ Existing apps that use ADAL will continue to work after the end-of-support date.
3838
The first step to migrating your apps from ADAL to MSAL is to identify all applications in your tenant that are currently using ADAL. You can run the following set of commands in Windows PowerShell or [view the Sign-ins Workbook in Azure AD](../develop/howto-get-list-of-all-active-directory-auth-library-apps.md).
3939

4040
1. Open Windows Powershell as an administrator.
41+
4142
1. Connect to Microsoft Graph:
4243
- `Connect-MgGraph-Tenant <YOUR_TENANT_ID>`
44+
4345
1. Select your profile:
4446
- `Select-MgProfile beta`
47+
4548
1. Get a list of your recommendations:
4649
- `Get-MgDirectoryRecommendation | Format-List`
4750

4851
The steps to migrate from ADAL to MSAL vary depending on the type of application. For example, the steps for .NET and Python applications have separate instructions. For a full list of instructions for each scenario, see [How to migrate to MSAL](../develop/msal-migration.md#how-to-migrate-to-msal)
4952

50-
5153
## Next steps
5254

5355
- [Review the Azure AD recommendations overview](overview-recommendations.md)

0 commit comments

Comments
 (0)