Skip to content

Commit f4687cb

Browse files
authored
Add note about security context to WAM page
1 parent 18a43df commit f4687cb

1 file changed

Lines changed: 3 additions & 0 deletions

File tree

  • msal-dotnet-articles/acquiring-tokens/desktop-mobile

msal-dotnet-articles/acquiring-tokens/desktop-mobile/wam.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -187,6 +187,9 @@ To use the broker, developers will need to call <xref:Microsoft.Identity.Client.
187187

188188
## Integration best practices
189189

190+
> [!IMPORTANT]
191+
> When using WAM, your application MUST be running in the context of an active, interactive Windows user session and be able to display UI. Attempting to acquire tokens using WAM while running as a Windows service, using task scheduler (unless *specifically* running as a logged in user) or while using `runas` to impersonate another account will result in errors by design.
192+
190193
To make sure that your customers have a great experience with WAM, we strongly advise you adhere to the following principles:
191194

192195
1. **Give the user context prior to authentication**. Draw a UI or window that will inform the user that they need to authenticate, along with reasons for authentication. Explain the benefits of your application if it is a background service.

0 commit comments

Comments
 (0)