Skip to content

Commit 65d5a98

Browse files
committed
Adding more details to RBAC information
1 parent 9215dc7 commit 65d5a98

File tree

2 files changed

+30
-0
lines changed

2 files changed

+30
-0
lines changed

articles/healthcare-apis/configure-azure-rbac.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -41,6 +41,10 @@ If these roles are not sufficient for your need, you can also [create custom rol
4141

4242
In the **Select** box, search for a user, service principal, or group that you wish to assign the role to.
4343

44+
## Caching behavior
45+
46+
The Azure API for FHIR will cache decisions for up to 5 minutes. If you grant a user access to the FHIR server by adding them to the list of allowed object ids, or you remove them from the list, you should expect it to take up to five minutes for changes in permissions to propagate.
47+
4448
## Next steps
4549

4650
In this article, you learned how to assign Azure RBAC roles for the FHIR data plane. Next learn about additional settings for the Azure API for FHIR:

articles/healthcare-apis/configure-local-rbac.md

Lines changed: 26 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -15,6 +15,28 @@ This article explains how to configure the Azure API for FHIR to use an external
1515
> [!NOTE]
1616
> If your FHIR service data plane is configured to use your primary Azure Active Directory tenant associated with your subscription, [use Azure RBAC to assign data plane roles](configure-azure-rbac.md).
1717
18+
## Add service principal
19+
20+
Local RBAC allows you to use an external Azure Active Directory tenant with your FHIR server. In order to allow the RBAC system to check group memberships in this tenant, the Azure API for FHIR must have a service principal in the tenant. This service principal will get created automatically in tenants tied to subscriptions that have deployed the Azure API for FHIR, but in case your tenant has no subscription tied to it, a tenant administrator will need to create this service principal with one of the following commands:
21+
22+
Using the `Az` PowerShell module:
23+
24+
```azurepowershell-interactive
25+
New-AzADServicePrincipal -ApplicationId 3274406e-4e0a-4852-ba4f-d7226630abb7
26+
```
27+
28+
or you can use the `AzureAd` PowerShell module:
29+
30+
```azurepowershell-interactive
31+
New-AzureADServicePrincipal -AppId 3274406e-4e0a-4852-ba4f-d7226630abb7
32+
```
33+
34+
or you can use Azure CLI:
35+
36+
```azurecli-interactive
37+
az ad sp create --id 3274406e-4e0a-4852-ba4f-d7226630abb7
38+
```
39+
1840
## Configure local RBAC
1941

2042
You can configure the Azure API for FHIR to use an external or secondary Azure Active Directory tenant in the **Authentication** blade:
@@ -31,6 +53,10 @@ You can read the article on how to [find identity object IDs](find-identity-obje
3153

3254
After entering the required object IDs, click **Save** and wait for changes to be saved before trying to access the data plane using the assigned users, service principals, or groups.
3355

56+
## Caching behavior
57+
58+
The Azure API for FHIR will cache decisions for up to 5 minutes. If you grant a user access to the FHIR server by adding them to the list of allowed object ids, or you remove them from the list, you should expect it to take up to five minutes for changes in permissions to propagate.
59+
3460
## Next steps
3561

3662
In this article, you learned how to assign FHIR data plane access using an external (secondary) Azure Active Directory tenant. Next learn about additional settings for the Azure API for FHIR:

0 commit comments

Comments
 (0)