Skip to content

Commit 7f91667

Browse files
Merge pull request #266479 from EXPEkesheth/patch-150
Update configure-identity-providers.md
2 parents e61efc7 + 9f55612 commit 7f91667

File tree

1 file changed

+4
-1
lines changed

1 file changed

+4
-1
lines changed

articles/healthcare-apis/fhir/configure-identity-providers.md

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,10 @@ ms.author: namalu
1313

1414
# Configure multiple service identity providers
1515

16-
In addition to [Microsoft Entra ID](/entra/fundamentals/whatis), you can configure up to two additional identity providers for a FHIR service, whether the service already exists or is newly created. Identity providers must support OpenID Connect (OIDC), and must be able to issue JSON Web Tokens (JWT) with a `fhirUser` claim, a `azp` or `appId` claim, and an `scp` claim with [SMART on FHIR v1 Scopes](https://www.hl7.org/fhir/smart-app-launch/1.0.0/scopes-and-launch-context/index.html#scopes-for-requesting-clinical-data).
16+
In addition to [Microsoft Entra ID](/entra/fundamentals/whatis), you can configure up to two additional identity providers for a FHIR service, whether the service already exists or is newly created.
17+
18+
## Identity providers prerequisite
19+
Identity providers must support OpenID Connect (OIDC), and must be able to issue JSON Web Tokens (JWT) with a `fhirUser` claim, a `azp` or `appId` claim, and an `scp` claim with [SMART on FHIR v1 Scopes](https://www.hl7.org/fhir/smart-app-launch/1.0.0/scopes-and-launch-context/index.html#scopes-for-requesting-clinical-data).
1720

1821
## Enable additional identity providers with Azure Resource Manager (ARM)
1922

0 commit comments

Comments
 (0)