Skip to content

Commit 8db267e

Browse files
committed
Fix read permission steps
1 parent b6d9c2c commit 8db267e

File tree

4 files changed

+10
-3
lines changed

4 files changed

+10
-3
lines changed

articles/blockchain/workbench/deploy.md

Lines changed: 10 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -170,7 +170,7 @@ If you choose to manually configure or verify Azure AD settings prior to deploym
170170

171171
### Blockchain Workbench API app registration
172172

173-
Blockchain Workbench deployment requires registration of an Azure AD application. You need an Azure Active Directory (Azure AD) tenant to register the app. You can use an existing tenant or create a new tenant. If you are using an existing Azure AD tenant, you need sufficient permissions to register applications, grant Graph API permissions, and allow guest access within an Azure AD tenant. If you do not have sufficient permissions in an existing Azure AD tenant create a new tenant.
173+
Blockchain Workbench deployment requires registration of an Azure AD application. You need an Azure Active Directory (Azure AD) tenant to register the app. You can use an existing tenant or create a new tenant. If you are using an existing Azure AD tenant, you need sufficient permissions to register applications, grant Graph API permissions, and allow guest access within an Azure AD tenant. If you do not have sufficient permissions in an existing Azure AD tenant, create a new tenant.
174174

175175

176176
1. Sign in to the [Azure portal](https://portal.azure.com).
@@ -190,7 +190,7 @@ Blockchain Workbench deployment requires registration of an Azure AD application
190190
Next, you need to modify the manifest to use application roles within Azure AD to specify Blockchain Workbench administrators. For more information about application manifests, see [Azure Active Directory application manifest](../../active-directory/develop/reference-app-manifest.md).
191191

192192

193-
1. You need to generate a GUID for the manifest. You can generate a GUID using the PowerShell command `[guid]::NewGuid()` or `New-GUID` cmdlet. Another option is to use a GUID generator website.
193+
1. A GUID is required for the manifest. You can generate a GUID using the PowerShell command `[guid]::NewGuid()` or `New-GUID` cmdlet. Another option is to use a GUID generator website.
194194
1. For the application you registered, select **Manifest** in the **Manage** section.
195195
1. Next, update the **appRoles** section of the manifest. Replace `"appRoles": []` with the provided JSON. Be sure to replace the value for the **id** field with the GUID you generated.
196196

@@ -228,8 +228,15 @@ Next, you need to modify the manifest to use application roles within Azure AD t
228228
The API application needs to request permission from the user to access the directory. Set the following required permission for the API application:
229229

230230
1. In the *Blockchain API* app registration, select **API permissions**. By default, the Graph API **User.Read** permission is added.
231+
1. The Workbench application requires read access to users' basic profile information. In *Configured permissions*, select **Add a permission**. In *Microsoft APIs**, select **Microsoft Graph**.
232+
1. Since the Workbench application uses the authenticated user credentials, select **Delegated permissions**.
233+
1. In the *User* category, choose **User.ReadBasic.All** permission.
231234

232-
1. In **Grant consent**, select **Grant admin consent** for the domain then select **Yes** for the verification prompt.
235+
![Azure AD app registration configuration showing adding the Microsoft Graph User.ReadBasic.All delegated permission](media/deploy/add-graph-user-permission.png)
236+
237+
Select **Add permissions**.
238+
239+
1. In *Configured permissions*, select **Grant admin consent** for the domain then select **Yes** for the verification prompt.
233240

234241
![Grant permissions](media/deploy/client-app-grant-permissions.png)
235242

97.2 KB
Loading
-8.34 KB
Loading
-585 Bytes
Loading

0 commit comments

Comments
 (0)