You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/active-directory/develop/tutorial-blazor-webassembly.md
+6-6Lines changed: 6 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@ ms.author: jricketts
6
6
ms.service: active-directory
7
7
ms.subservice: develop
8
8
ms.topic: tutorial
9
-
ms.date: 12/13/2022
9
+
ms.date: 12/14/2022
10
10
#Customer intent: As a developer, I want to add authentication and authorization to a Blazor WebAssembly app and call Microsoft Graph.
11
11
---
12
12
@@ -39,7 +39,7 @@ Every app that uses Azure AD for authentication must be registered with Azure AD
39
39
40
40
## Create the app using the .NET Core CLI
41
41
42
-
To create the app you need the latest Blazor templates. You can install them for the .NET Core CLI with the following command:
42
+
To create the app, you need the latest Blazor templates. You can install them for the .NET Core CLI with the following command:
43
43
44
44
```dotnetcli
45
45
dotnet new install Microsoft.Identity.Web.ProjectTemplates
@@ -67,17 +67,17 @@ dotnet run
67
67
68
68
In your browser, navigate to `https://localhost:<port number>`, and log in using an Azure AD user account to see the app running and logging users in with the Microsoft identity platform.
69
69
70
-
The components of this template that enable logins with Azure AD using the Microsoft identity platform are explained in the [ASP.NET doc on this topic](/aspnet/core/blazor/security/webassembly/standalone-with-azure-active-directory#authentication-package).
70
+
The components of this template that enable logins with Azure AD using the Microsoft identity platform are explained in the [ASP.NET doc on this article](/aspnet/core/blazor/security/webassembly/standalone-with-azure-active-directory#authentication-package).
71
71
72
72
## Retrieving data from a protected API (Microsoft Graph)
73
73
74
74
[Microsoft Graph](/graph/overview) contains APIs that provide access to Microsoft 365 data for your users, and it supports the tokens issued by the Microsoft identity platform, which makes it a good protected API to use as an example. In this section, you add code to call Microsoft Graph and display the user's emails on the application's "Fetch data" page.
75
75
76
76
This section is written using a common approach to calling a protected API using a named client. The same method can be used for other protected APIs you want to call. However, if you do plan to call Microsoft Graph from your application you can use the Graph SDK to reduce boilerplate. The .NET docs contain instructions on [how to use the Graph SDK](/aspnet/core/blazor/security/webassembly/graph-api?view=aspnetcore-5.0&preserve-view=true).
77
77
78
-
Before you start, log out of your app since you'll be making changes to the required permissions, and your current token won't work. If you haven't already, run your app again and select **Log out** before updating the code below.
78
+
Before you start, log out of your app since you'll be making changes to the required permissions, and your current token won't work. If you haven't already, run your app again and select **Log out** before updating the code in your app.
79
79
80
-
Now you will update your app's registration and code to pull a user's emails and display the messages within the app.
80
+
Now you'll update your app's registration and code to pull a user's emails and display the messages within the app.
81
81
82
82
First, add the `Mail.Read` API permission to the app's registration so that Azure AD is aware that the app will request to access its users' email.
83
83
@@ -239,5 +239,5 @@ After granting consent, navigate to the "Fetch data" page to read some email.
239
239
240
240
## Next steps
241
241
242
-
> [!div class="nextstepaction"]
242
+
> [!div class="nextstepaction"]
243
243
> [Microsoft identity platform best practices and recommendations](./identity-platform-integration-checklist.md)
0 commit comments