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/configure-azure-rbac.md
+4Lines changed: 4 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -41,6 +41,10 @@ If these roles are not sufficient for your need, you can also [create custom rol
41
41
42
42
In the **Select** box, search for a user, service principal, or group that you wish to assign the role to.
43
43
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
+
44
48
## Next steps
45
49
46
50
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:
Copy file name to clipboardExpand all lines: articles/healthcare-apis/configure-local-rbac.md
+26Lines changed: 26 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,6 +15,28 @@ This article explains how to configure the Azure API for FHIR to use an external
15
15
> [!NOTE]
16
16
> 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).
17
17
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:
az ad sp create --id 3274406e-4e0a-4852-ba4f-d7226630abb7
38
+
```
39
+
18
40
## Configure local RBAC
19
41
20
42
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
31
53
32
54
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.
33
55
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
+
34
60
## Next steps
35
61
36
62
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