Skip to content

Commit 9eac2fd

Browse files
alt-text references improved
1 parent c64747b commit 9eac2fd

File tree

2 files changed

+6
-6
lines changed

2 files changed

+6
-6
lines changed

articles/healthcare-apis/dicom/dicom-register-application.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -63,21 +63,21 @@ The following steps are required for the DICOM service. In addition, user access
6363

6464
1. Select the **API permissions** blade.
6565

66-
[ ![Add API permissions](./media/dicom-add-apis-permissions.png) ](./media/dicom-add-apis-permissions.png#lightbox)
66+
[ ![Screenshot of API permission page with Add a permission button highlighted.](./media/dicom-add-apis-permissions.png) ](./media/dicom-add-apis-permissions.png#lightbox)
6767

6868
2. Select **Add a permission**.
6969

7070
Add a permission to the DICOM service by searching for **Azure API for DICOM** under **APIs my organization** uses.
7171

72-
[ ![Search API permissions](./media/dicom-search-apis-permissions.png) ](./media/dicom-search-apis-permissions.png#lightbox)
72+
[ ![Screenshot of Search API permissions page with the APIs my organization uses tab selected.](./media/dicom-search-apis-permissions.png) ](./media/dicom-search-apis-permissions.png#lightbox)
7373

7474
The search result for Azure API for DICOM will only return if you've already deployed the DICOM service in the workspace.
7575

7676
If you're referencing a different resource application, select your DICOM API Resource Application Registration that you created previously under **APIs my organization**.
7777

7878
3. Select scopes (permissions) that the confidential client application will ask for on behalf of a user. Select **Dicom.ReadWrite**, and then select **Add permissions**.
7979

80-
[ ![Select permissions scopes](./media/dicom-select-scopes-new.png) ](./media/dicom-select-scopes-new.png#lightbox)
80+
[ ![Screenshot of scopes (permissions) that the client application will ask for on behalf of a user.](./media/dicom-select-scopes-new.png) ](./media/dicom-select-scopes-new.png#lightbox)
8181

8282
Your application registration is now complete.
8383

articles/healthcare-apis/register-application.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -71,21 +71,21 @@ The following steps are required for the DICOM service, but optional for the FHI
7171

7272
1. Select the **API permissions** blade.
7373

74-
[ ![Add API permissions](dicom/media/dicom-add-apis-permissions.png) ](dicom/media/dicom-add-apis-permissions.png#lightbox)
74+
[ ![Screenshot of API permission page with Add a permission button highlighted.](dicom/media/dicom-add-apis-permissions.png) ](dicom/media/dicom-add-apis-permissions.png#lightbox)
7575

7676
2. Select **Add a permission**.
7777

7878
If you're using Azure Health Data Services, you'll add a permission to the DICOM service by searching for **Azure API for DICOM** under **APIs my organization** uses.
7979

80-
[ ![Search API permissions](dicom/media/dicom-search-apis-permissions.png) ](dicom/media/dicom-search-apis-permissions.png#lightbox)
80+
[ ![Screenshot of Search API permissions page with the APIs my organization uses tab selected.](dicom/media/dicom-search-apis-permissions.png) ](dicom/media/dicom-search-apis-permissions.png#lightbox)
8181

8282
The search result for Azure API for DICOM will only return if you've already deployed the DICOM service in the workspace.
8383

8484
If you're referencing a different resource application, select your DICOM API Resource Application Registration that you created previously under **APIs my organization**.
8585

8686
3. Select scopes (permissions) that the confidential client application will ask for on behalf of a user. Select **user_impersonation**, and then select **Add permissions**.
8787

88-
[ ![Select permissions scopes.](dicom/media/dicom-select-scopes.png) ](dicom/media/dicom-select-scopes.png#lightbox)
88+
[ ![Screenshot of scopes (permissions) that the client application will ask for on behalf of a user.](dicom/media/dicom-select-scopes.png) ](dicom/media/dicom-select-scopes.png#lightbox)
8989

9090
>[!NOTE]
9191
>Use grant_type of client_credentials when trying to obtain an access token for the FHIR service using tools such as Postman or REST Client. For more details, visit [Access using Postman](./fhir/use-postman.md) and [Accessing Azure Health Data Services using the REST Client Extension in Visual Studio Code](./fhir/using-rest-client.md).

0 commit comments

Comments
 (0)