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: powerapps-docs/developer/common-data-service/walkthrough-blazor-webassembly-single-tenant.md
+7-7Lines changed: 7 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -22,7 +22,7 @@ Use the steps in this tutorial to create a Blazor WebAssembly app that connects
22
22
23
23
Blazor WebAssembly is one of two hosting models available for ASP.NET Core Blazor, the other is Blazor Server. For a complete description of the differences, see [ASP.NET Core Blazor hosting models](/aspnet/core/blazor/hosting-models).
24
24
25
-
This tutorial depends on the instructions in the [Secure an ASP.NET Core Blazor WebAssembly standalone app with Azure Active Directory](/aspnet/core/security/blazor/webassembly/standalone-with-azure-active-directory) topic. Because Common Data Service uses Azure Active Directory (AAD) for authentication, this tutorial will describe how to modify the basic app created using the app template provided so that it can connect to Common Data Service.
25
+
This tutorial depends on the instructions in the [Secure an ASP.NET Core Blazor WebAssembly standalone app with Azure Active Directory](/aspnet/core/security/blazor/webassembly/standalone-with-azure-active-directory) topic. Because Common Data Service uses Azure Active Directory (Azure AD) for authentication, this tutorial will describe how to modify the basic app created using the app template provided so that it can connect to Common Data Service.
26
26
27
27
## Goal
28
28
@@ -37,7 +37,7 @@ To complete this tutorial, you must have:
37
37
38
38
- Access to a [Common Data Service environment with a database](https://docs.microsoft.com/power-platform/admin/create-environment#create-an-environment-with-a-database)
39
39
- A Common Data Service user with a security role that provides read access to the Account and Contact entities
40
-
- Application Administrator, Application Developer, Cloud Application Administrator, or Hybrid Identity Administrator role access to the AAD tenant that the Common Data Service environment uses.
40
+
- Application Administrator, Application Developer, Cloud Application Administrator, or Hybrid Identity Administrator role access to the Azure AD tenant that the Common Data Service environment uses.
41
41
- Understanding of the C# programming language
42
42
- Understanding of ASP.NET Core Blazor is helpful but not required
43
43
- The latest version of Visual Studio 2019 with the **ASP.NET and web development** workload installed.
@@ -81,11 +81,11 @@ It will look something like this: `https://yourorgname.api.crm.dynamics.com/api/
81
81
82
82
This takes you to the starting point for Step 2.
83
83
84
-
## Step 2: Create a Blazor WebAssembly standalone app using AAD for authentication
84
+
## Step 2: Create a Blazor WebAssembly standalone app using Azure AD for authentication
85
85
86
86
The [Secure an ASP.NET Core Blazor WebAssembly standalone app with Azure Active Directory](/aspnet/core/security/blazor/webassembly/standalone-with-azure-active-directory) topic provides a complete set of instructions to create the app.
87
87
88
-
These steps will describe how to create an app registration in AAD and run a .NET Core CLI command to generate the scaffold for the basic app with support for AAD authentication.
88
+
These steps will describe how to create an app registration in Azure AD and run a .NET Core CLI command to generate the scaffold for the basic app with support for Azure AD authentication.
89
89
90
90
> [!NOTE]
91
91
> At this time, you must use the .NET Core CLI command to generate the app. There is no template for this specific type of app when creating a project using Visual Studio.
@@ -138,7 +138,7 @@ The port setting used by Visual Studio is randomly generated. The callback URI i
138
138
:::image type="content" source="media/blazor-webassembly-walkthrough-project-debug-settings.png" alt-text="The Visual Studio project Debug page.":::
139
139
140
140
1. Under **Web Server Settings** copy the **Enable SSL** value that includes the random port assigned for debugging
141
-
1. Return to your app registration in AAD, In the **Authentication** section, change the **Redirect URI** to include this root Uri, then save your changes
141
+
1. Return to your app registration in Azure AD, In the **Authentication** section, change the **Redirect URI** to include this root Uri, then save your changes
@@ -148,13 +148,13 @@ Now that the Redirect URI has been updated; you should be able to press F5 in Vi
148
148
149
149
:::image type="content" source="media/blazor-webassembly-walkthrough-application-before-code-changes.png" alt-text="The default behavior of the Blazor WebAssembly app before changes are made.":::
150
150
151
-
At this point, all the capabilities of the app work whether you log-in or not. Only members of the AAD tenant can log in.
151
+
At this point, all the capabilities of the app work whether you log-in or not. Only members of the Azure AD tenant can log in.
152
152
153
153
## Step 3: Grant API permissions
154
154
155
155
To connect to Common Data Service, you must configure permissions for the app to connect.
156
156
157
-
1. Return to your app registration in AAD, In the **API permissions** section, click **Add a permission**.
157
+
1. Return to your app registration in Azure AD, In the **API permissions** section, click **Add a permission**.
158
158
159
159
:::image type="content" source="media/blazor-webassembly-walkthrough-add-permissions.png" alt-text="The registered application API Permissions settings page.":::
0 commit comments