Skip to content

Commit 62b16b3

Browse files
committed
review feedback
1 parent f0da12d commit 62b16b3

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/active-directory/develop/msal-net-adfs-support.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -32,12 +32,12 @@ Microsoft Authentication Library for .NET (MSAL.NET) supports two scenarios for
3232
## MSAL connects to Azure AD, which is federated with AD FS
3333
MSAL.NET supports connecting to Azure AD, which signs in managed-users (users managed in Azure AD) or federated users (users managed by another identity provider such as AD FS). MSAL.NET does not know about the fact that users are federated. As far as it’s concerned, it talks to Azure AD.
3434

35-
The [authority](msal-client-application-configuration.md#authority) you use in this case is the usual authority (common, or organizations, or tenant).
35+
The [authority](msal-client-application-configuration.md#authority) you use in this case is the usual authority (authority host name + tenant, common, or organizations).
3636

3737
### Acquiring a token interactively
3838
When you call the `AcquireTokenInteractive` method, the user experience is typically:
3939

40-
1. The user enters their UPN (or the account or login hint, which is provided as part of the call to the `AcquireTokenAsync` method).
40+
1. The user enters their account ID.
4141
2. Azure AD displays briefly the message "Taking you to your organization's page".
4242
3. The user is redirected to the sign-in page of the identity provider. The sign-in page is usually customized with the logo of the organization.
4343

0 commit comments

Comments
 (0)