Skip to content

Commit 30ad4e1

Browse files
evandigbyanydot
andauthored
Update dead link to proposed alternative (#72)
Update dead link related to "more info" for device code authorization to an active link with appropriate content. Fixes #71 Co-authored-by: anydot <[email protected]>
1 parent 8993881 commit 30ad4e1

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

DeviceProfileSample/README.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,12 +1,12 @@
11
# Device Profile Sample
22

3-
For a headless text output client application, it is not possible authenticate through an interactive prompt. Instead a text only approach is necessary. This flow leverages a user's external device (i.e. phone) to authenticate through an interactive login prompt and pass the auth token to the headless application. For more information [click here](https://azure.microsoft.com/resources/samples/active-directory-dotnet-deviceprofile/?v=17.23h).
3+
For a headless text output client application, it is not possible authenticate through an interactive prompt. Instead a text only approach is necessary. This flow leverages a user's external device (i.e. phone) to authenticate through an interactive login prompt and pass the auth token to the headless application. For more information [click here](https://docs.microsoft.com/en-us/azure/active-directory/develop/v2-oauth2-device-code).
44

55
If the tenant admin requires device authentication conditional access policies, using the Device profile flow won't be a good option.
66

77
## Sample Application
88

9-
This sample will walk you through the steps to create a client-side console application which uses **MSAL.NET** to authenticate a user via the [Device Profile flow](https://azure.microsoft.com/resources/samples/active-directory-dotnet-deviceprofile/?v=17.23h) and returns a JSON string containing all account team project data viewable by the authenticated user.
9+
This sample will walk you through the steps to create a client-side console application which uses **MSAL.NET** to authenticate a user via the [Device Profile flow](https://docs.microsoft.com/en-us/azure/active-directory/develop/v2-oauth2-device-code) and returns a JSON string containing all account team project data viewable by the authenticated user.
1010

1111
To run this sample you will need:
1212

0 commit comments

Comments
 (0)