Skip to content

Commit 365bfac

Browse files
KendalBond007KendalBond007
committed
markdown and content edits
1 parent 7e75562 commit 365bfac

File tree

2 files changed

+17
-17
lines changed

2 files changed

+17
-17
lines changed

‎articles/healthcare-apis/azure-api-for-fhir/configure-azure-rbac.md

Lines changed: 13 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -11,34 +11,34 @@ ms.author: kesheth
1111

1212
# Configure Azure RBAC for FHIR
1313

14-
[!INCLUDE [retirement banner](../includes/healthcare-apis-azure-api-fhir-retirement.md)]
14+
[!INCLUDE[retirement banner](../includes/healthcare-apis-azure-api-fhir-retirement.md)]
1515

16-
In this article, you'll learn how to use [Azure role-based access control (Azure RBAC)](../../role-based-access-control/index.yml) to assign access to the Azure API for FHIR data plane. Azure RBAC is the preferred methods for assigning data plane access when data plane users are managed in the Microsoft Entra tenant associated with your Azure subscription. If you're using an external Microsoft Entra tenant, refer to the [local RBAC assignment reference](configure-local-rbac.md).
16+
In this article, you learn how to use [Azure role-based access control (Azure RBAC)](../../role-based-access-control/index.yml) to assign access to the Azure API for FHIR® data plane. Azure RBAC is the preferred methods for assigning data plane access when data plane users are managed in the Microsoft Entra tenant associated with your Azure subscription. If you're using an external Microsoft Entra tenant, refer to the [local RBAC assignment reference](configure-local-rbac.md).
1717

1818
## Confirm Azure RBAC mode
1919

20-
To use Azure RBAC, your Azure API for FHIR must be configured to use your Azure subscription tenant for data plane and there should be no assigned identity object IDs. You can verify your settings by inspecting the **Authentication** blade of your Azure API for FHIR:
20+
To use Azure RBAC, your Azure API for FHIR must be configured to use your Azure subscription tenant for data plane, and there should be no assigned identity object IDs. You can verify your settings by inspecting the **Authentication** of your Azure API for FHIR:
2121

2222
:::image type="content" source="media/rbac/confirm-azure-rbac-mode.png" alt-text="Confirm Azure RBAC mode":::
2323

24-
The **Authority** should be set to the Microsoft Entra tenant associated with your subscription and there should be no GUIDs in the box labeled **Allowed object IDs**. You'll also notice that the box is disabled and a label indicates that Azure RBAC should be used to assign data plane roles.
24+
The **Authority** should be set to the Microsoft Entra tenant associated with your subscription and there should be no GUIDs in the box labeled **Allowed object IDs**. Notice the box is disabled and a label indicates that Azure RBAC should be used to assign data plane roles.
2525

2626
## Assign roles
2727

28-
To grant users, service principals or groups access to the FHIR data plane, select **Access control (IAM)**, then select **Role assignments** and select **+ Add**:
28+
To grant users, service principals, or groups access to the FHIR data plane, select **Access control (IAM)**, then select **Role assignments** and select **+ Add**.
2929

3030
:::image type="content" source="media/rbac/add-azure-rbac-role-assignment.png" alt-text="Add Azure role assignment":::
3131

32-
In the **Role** selection, search for one of the built-in roles for the FHIR data plane:
32+
In the **Role** selection, search for one of the built-in roles for the FHIR data plane.
3333

3434
:::image type="content" source="media/rbac/built-in-fhir-data-roles.png" alt-text="Built-in FHIR data roles":::
3535

36-
You can choose between:
36+
You can choose from among the following.
3737

38-
* FHIR Data Reader: Can read (and search) FHIR data.
39-
* FHIR Data Writer: Can read, write, and soft delete FHIR data.
40-
* FHIR Data Exporter: Can read and export (`$export` operator) data.
41-
* FHIR Data Contributor: Can perform all data plane operations.
38+
* FHIR Data Reader: Can read (and search) FHIR data
39+
* FHIR Data Writer: Can read, write, and soft delete FHIR data
40+
* FHIR Data Exporter: Can read and export (`$export` operator) data
41+
* FHIR Data Contributor: Can perform all data plane operations
4242

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

@@ -48,7 +48,7 @@ In the **Select** box, search for a user, service principal, or group that you w
4848
4949
## Caching behavior
5050

51-
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.
51+
The Azure API for FHIR caches 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.
5252

5353
## Next steps
5454

@@ -72,4 +72,4 @@ In this article, you learned how to assign Azure roles for the FHIR data plane.
7272
>[!div class="nextstepaction"]
7373
>[Configure Private Link](configure-private-link.md)
7474
75-
FHIR® is a registered trademark of [HL7](https://hl7.org/fhir/) and is used with the permission of HL7.
75+
[!INCLUDE[FHIR trademark statement](../includes/healthcare-apis-fhir-trademark.md)]

‎articles/healthcare-apis/azure-api-for-fhir/configure-cross-origin-resource-sharing.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -10,15 +10,15 @@ ms.subservice: fhir
1010
---
1111
# Configure cross-origin resource sharing in Azure API for FHIR
1212

13-
[!INCLUDE [retirement banner](../includes/healthcare-apis-azure-api-fhir-retirement.md)]
13+
[!INCLUDE[retirement banner](../includes/healthcare-apis-azure-api-fhir-retirement.md)]
1414

15-
Azure API for FHIR supports [cross-origin resource sharing (CORS)](https://wikipedia.org/wiki/Cross-Origin_Resource_Sharing). CORS allows you to configure settings so that applications from one domain (origin) can access resources from a different domain, known as a cross-domain request.
15+
Azure API for FHIR® supports [cross-origin resource sharing (CORS)](https://wikipedia.org/wiki/Cross-Origin_Resource_Sharing). CORS allows you to configure settings so that applications from one domain (origin) can access resources from a different domain, known as a cross-domain request.
1616

1717
CORS is often used in a single-page app that must call a RESTful API to a different domain.
1818

1919
## Configure CORS settings
2020

21-
To configure a CORS setting in the Azure API for FHIR, specify the following settings:
21+
To configure a CORS setting in the Azure API for FHIR, specify the following settings.
2222

2323
- **Origins (Access-Control-Allow-Origin)**. A list of domains allowed to make cross-origin requests to the Azure API for FHIR. Each domain (origin) must be entered in a separate line. You can enter an asterisk (*) to allow calls from any domain, but we don't recommend it because it's a security risk.
2424

@@ -42,4 +42,4 @@ In this article, you learned how to configure cross-origin resource sharing in A
4242
>[!div class="nextstepaction"]
4343
>[Deploy Azure API for FHIR](fhir-paas-portal-quickstart.md)
4444
45-
FHIR® is a registered trademark of [HL7](https://hl7.org/fhir/) and is used with the permission of HL7.
45+
[!INCLUDE[FHIR trademark statement](../includes/healthcare-apis-fhir-trademark.md)]

0 commit comments

Comments
 (0)