Update dead link to proposed alternative (microsoft#72)

Update dead link related to "more info" for device code authorization to an active link with appropriate content. Fixes microsoft#71 Co-authored-by: anydot <[email protected]>
HexagonsProductionSoftware · Apr 23, 2021 · 30ad4e1 · 30ad4e1
1 parent 8993881
commit 30ad4e1
Showing 1 changed file with 2 additions and 2 deletions.
diff --git a/DeviceProfileSample/README.md b/DeviceProfileSample/README.md
@@ -1,12 +1,12 @@
 # Device Profile Sample
 
-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).
+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).
 
 If the tenant admin requires device authentication conditional access policies, using the Device profile flow won't be a good option.
 
 ## Sample Application
 
-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.
+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.
 
 To run this sample you will need: