Skip to content

Commit ff1e505

Browse files
Apply suggestions from code review
1 parent 2d7bad6 commit ff1e505

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

articles/active-directory/develop/scenario-desktop-acquire-token-wam.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -27,17 +27,17 @@ Using an authentication broker such as WAM has numerous benefits.
2727
- Better support for Windows Hello, Conditional Access and FIDO keys
2828
- Integration with Windows' "Email and Accounts" view
2929
- Better Single Sign-On
30-
- Ability to sign-in silently with the current Windows account
30+
- Ability to sign in silently with the current Windows account
3131
- Most bug fixes and enhancements will be shipped with Windows
3232

3333
## WAM limitations
3434

35-
- Available on Win10+ and Win Server 2019+. On Mac, Linux, and earlier versions of Windows, MSAL will automatically fall back to a browser.
35+
- Available on Windows 10 and later and on Windows Server 2019 and later. On Mac, Linux, and earlier versions of Windows, MSAL will automatically fall back to a browser.
3636
- B2C and ADFS authorities aren't supported. MSAL will fall back to a browser.
3737

3838
## WAM integration package
3939

40-
Most apps will need to reference `Microsoft.Identity.Client.Broker` package to use this integration. MAUI apps are not required to do this, the functionality is inside MSAL when targetting `net6-windows` and above.
40+
Most apps will need to reference `Microsoft.Identity.Client.Broker` package to use this integration. MAUI apps are not required to do this; the functionality is inside MSAL when the target is `net6-windows` and later.
4141

4242
## WAM calling pattern
4343

0 commit comments

Comments
 (0)