minor corrections

Author: derisen

2-WebApp-graph-user/2-6-BFF-Proxy/CallGraphBFF/ClientApp/src/components/Home.js

@@ -44,7 +44,7 @@ export class Home extends Component {
             </ul>
             <p>To help you get started, we have also set up:</p>
             <ul>
-              <li><strong>Client-side navigation</strong>. For example, click <em>Counter</em> then <em>Back</em> to return here.</li>
+              <li><strong>Client-side navigation</strong>. For example, click <em>Profile</em>, then <em>Back</em> to return here.</li>
               <li><strong>Development server integration</strong>. In development mode, the development server from <code>create-react-app</code> runs in the background automatically, so your client-side resources are dynamically built on demand and the page refreshes when you modify any file.</li>
               <li><strong>Efficient production builds</strong>. In production mode, development-time features are disabled, and your <code>dotnet publish</code> configuration produces minified, efficiently bundled JavaScript files.</li>
             </ul>

2-WebApp-graph-user/2-6-BFF-Proxy/CallGraphBFF/Controllers/AuthController.cs

@@ -1,9 +1,9 @@
-using Microsoft.AspNetCore.Authentication;
+using System.Security.Claims;
+using Microsoft.AspNetCore.Authentication;
 using Microsoft.AspNetCore.Authentication.Cookies;
 using Microsoft.AspNetCore.Authentication.OpenIdConnect;
 using Microsoft.AspNetCore.Authorization;
 using Microsoft.AspNetCore.Mvc;
-using System.Security.Claims;
 
 namespace TodoListBFF.Controllers;
 

2-WebApp-graph-user/2-6-BFF-Proxy/CallGraphBFF/Controllers/ProfileController.cs

@@ -1,14 +1,13 @@
 using Microsoft.AspNetCore.Mvc;
 using Microsoft.AspNetCore.Authorization;
-using Microsoft.Graph;
 using Microsoft.AspNetCore.Authentication.Cookies;
 using Microsoft.Identity.Web;
 using Microsoft.Identity.Client;
+using Microsoft.Graph;
 
 namespace TodoListBFF.Controllers;
 
-[Authorize(AuthenticationSchemes = CookieAuthenticationDefaults.AuthenticationScheme)]
-[AuthorizeForScopes(Scopes = new string[] { "user.read" })]
+[Authorize]
 [Route("api/[controller]")]
 [ApiController]
 public class ProfileController : Controller
@@ -38,7 +37,7 @@ public async Task<ActionResult<User>> GetProfile()
         }
         catch (Exception ex)
         {
-            return BadRequest("An error occurred while calling the downstream API\n" + ex.Message);
+            return BadRequest(ex.Message);
         }
     }
 }

2-WebApp-graph-user/2-6-BFF-Proxy/CallGraphBFF/appsettings.json

@@ -11,6 +11,7 @@
     //    "CertificateDistinguishedName": "CN=CallGraphBFF"
     //  }
     //],
+    "ClientCapabilities": [ "CP1" ],
     "CallbackPath": "/api/auth/signin-oidc",
     "SignedOutCallbackPath": "/api/auth/signout-oidc"
   },

2-WebApp-graph-user/2-6-BFF-Proxy/README.md

@@ -35,7 +35,7 @@ extensions:
 
 ## Overview
 
-This sample demonstrates a ASP.NET Core web app calling Microsoft Graph.
+This sample demonstrates a React single-page application with an ASP.NET Core backend authenticating users and calling the Microsoft Graph API using the backend for frontend proxy pattern.
 
 > :information_source: To learn how applications integrate with [Microsoft Graph](https://aka.ms/graph), consider going through the recorded session: [An introduction to Microsoft Graph for developers](https://www.youtube.com/watch?v=EBbnpFdB92A)
 
@@ -171,20 +171,23 @@ Open the project in your IDE (like Visual Studio or Visual Studio Code) to confi
 From your shell or command line, execute the following commands:
 
 ```console
-    cd 2-WebApp-graph-user/2-6-BFF-Proxy
+    cd 2-WebApp-graph-user/2-6-BFF-Proxy/CallGraphBFF
     dotnet run
 ```
 
 ## Explore the sample
 
-> * Explain how to explore the sample.
-> * Insert a screenshot of the client application.
+1. Open your browser and navigate to `https://localhost:7000`.
+1. Select the **Login** button on the navigation bar to sign-in.
+1. Select the **Profile** button on the navigation bar to call Microsoft Graph.
+
+![Screenshot Image](./ReadmeFiles/screenshot.png)
 
 > :information_source: Did the sample not work for you as expected? Then please reach out to us using the [GitHub Issues](../../../../issues) page.
 
 ## We'd love your feedback!
 
-Were we successful in addressing your learning objective? Consider taking a moment to [share your experience with us](Enter_Survey_Form_Link).
+Were we successful in addressing your learning objective? Consider taking a moment to [share your experience with us](https://forms.office.com/Pages/ResponsePage.aspx?id=v4j5cvGGr0GRqy180BHbR73pcsbpbxNJuZCMKN0lURpUNEFCQ0FSMFlPQTJURkJZMTRZWVJRNkdRMCQlQCN0PWcu).
 
 ## Troubleshooting
 
@@ -225,8 +228,8 @@ Follow the link to [Publish with Visual Studio](https://docs.microsoft.com/visua
 #### Update the Azure AD app registration (CallGraphBFF)
 
 1. Navigate back to to the [Azure portal](https://portal.azure.com).
-In the left-hand navigation pane, select the **Azure Active Directory** service, and then select **App registrations (Preview)**.
-1. In the resulting screen, select the `callgraphbff` application.
+In the left-hand navigation pane, select the **Azure Active Directory** service, and then select **App registrations**.
+1. In the resulting screen, select the `CallGraphBFF` application.
 1. In the app's registration screen, select **Authentication** in the menu.
     1. In the **Redirect URIs** section, update the reply URLs to match the site URL of your Azure deployment. For example:
         1. `https://callgraphbff.azurewebsites.net/api/auth/signin-oidc`