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/healthcare-apis/register-application.md
+6-7Lines changed: 6 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
---
2
2
title: Register a client application in Microsoft Entra ID for the Azure Health Data Services
3
-
description: How to register a client application in the Microsoft Entra ID and how to add a secret and API permissions to the Azure Health Data Services
3
+
description: How to register a client application in the Microsoft Entra ID and add a secret and API permissions to the Azure Health Data Services
4
4
author: chachachachami
5
5
ms.service: azure-health-data-services
6
6
ms.subservice: fhir
@@ -63,19 +63,18 @@ To create a new client secret, use the following steps.
63
63
[](media/register-application-new-client-secret.png#lightbox)
64
64
65
65
1. Copy the secret value by selecting the copy button next to the **Value**.
66
-
[](media/register-application-copy-client-secret.png#lightbox)
66
+
[](media/register-application-copy-client-secret.png#lightbox)
67
67
68
68
69
69
>[!NOTE]
70
70
>It's important that you save the secret value, not the secret ID.
71
71
72
-
[](media/register-application-new-client-secret.png#lightbox)
73
72
74
-
Optionally, you can upload a certificate (public key) and use the Certificate ID, a GUID value associated with the certificate. For testing purposes, you can create a self-signed certificate by using tools such as the PowerShell command `New-SelfSignedCertificate`, and then export the certificate from the certificate store.
73
+
Optionally, you can upload a certificate (public key) and use the Certificate ID, a GUID value associated with the certificate. For testing purposes, you can create a self-signed certificate by using tools such as the PowerShell command `New-SelfSignedCertificate`, and then export the certificate from the certificate store. For more information, see [Create a self-signed public certificate to authenticate your application](/entra/identity-platform/howto-create-self-signed-certificate)
75
74
76
75
## API permissions
77
76
78
-
The following steps are required for the DICOM service, but optional for the FHIR service. In addition, you manage user access permissions or role assignments for Azure Health Data Services through RBAC. For more details, see [Configure Azure RBAC for Azure Health Data Services](configure-azure-rbac.md).
77
+
The following steps are required for the DICOM service, but optional for the FHIR service. In addition, you manage user access permissions or role assignments for Azure Health Data Services through RBAC. For more information, see [Configure Azure RBAC for Azure Health Data Services](configure-azure-rbac.md).
79
78
80
79
1. Select **API permissions**.
81
80
@@ -96,8 +95,8 @@ The following steps are required for the DICOM service, but optional for the FHI
96
95
[](dicom/media/dicom-select-scope.png#lightbox)
97
96
98
97
>[!NOTE]
99
-
>Use `grant_type` of `client_credentials` when getting an access token for the FHIR service using tools such as REST Client. For more details, see [Accessing Azure Health Data Services using the REST Client Extension in Visual Studio Code](./fhir/using-rest-client.md).
100
-
>>Use `grant_type` of `client_credentials` or `authentication_code` when getting an access token for the DICOM service. For more details, see [Using DICOM with cURL](dicom/dicomweb-standard-apis-curl.md).
98
+
>Use `grant_type` of `client_credentials` when getting an access token for the FHIR service using tools such as REST Client. For more information, see [Accessing Azure Health Data Services using the REST Client Extension in Visual Studio Code](./fhir/using-rest-client.md).
99
+
>>Use `grant_type` of `client_credentials` or `authentication_code` when getting an access token for the DICOM service. For more information, see [Using DICOM with cURL](dicom/dicomweb-standard-apis-curl.md).
0 commit comments