Updated figured for portal release

Author: hansenms

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

@@ -16,19 +16,19 @@ In this article, you will learn how to use [Azure Role Based Access Control (RBA
 
 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:
 
-![Confirm Azure RBAC mode](media/rbac/confirm-azure-rbac-mode.png)
+:::image type="content" source="media/rbac/confirm-azure-rbac-mode.png" alt-text="Confirm Azure RBAC mode":::
 
 The **Authority** should be set to the Azure Active directory tenant associated with your subscription and there should be no GUIDs in the box labeled **Allowed object IDs**. You will also notice that the box is disabled and a label indicates that Azure RBAC should be used to assign data plane roles.
 
 ## Assign roles
 
 To grant users, service principals or groups access to the FHIR data plane, click **Access control (IAM)**, then click **Role assignments** and click **+ Add**:
 
-![Add Azure RBAC role assignment](media/rbac/add-azure-rbac-role-assignment.png)
+:::image type="content" source="media/rbac/add-azure-rbac-role-assignment.png" alt-text="Add Azure RBAC role assignment":::
 
 In the **Role** selection, search for one of the built-in roles for the FHIR data plane:
 
-![Built-in FHIR data roles](media/rbac/built-in-fhir-data-roles.png)
+:::image type="content" source="media/rbac/built-in-fhir-data-roles.png" alt-text="Built-in FHIR data roles":::
 
 You can choose between:
 

articles/healthcare-apis/fhir-paas-portal-quickstart.md

@@ -26,29 +26,29 @@ Open the [Azure portal](https://portal.azure.com) and click **Create a resource*
 
 You can find Azure API for FHIR by typing "FHIR" into the search box:
 
-![Search for Healthcare APIs](media/quickstart-paas-portal/portal-search-healthcare-apis.png)
+:::image type="content" source="media/quickstart-paas-portal/portal-search-healthcare-apis.png" alt-text="Search for Healthcare APIs":::
 
 ## Create Azure API for FHIR account
 
 Select **Create** to create a new Azure API for FHIR account:
 
-![Create Azure API for FHIR account](media/quickstart-paas-portal/portal-create-healthcare-apis.png)
+:::image type="content" source="media/quickstart-paas-portal/portal-create-healthcare-apis.png" alt-text="Create Azure API for FHIR account":::
 
 ## Enter account details
 
 Select an existing resource group or create a new one, choose a name for the account, and finally click **Review + create**:
 
-![New healthcare api details](media/quickstart-paas-portal/portal-new-healthcareapi-details.png)
+:::image type="content" source="media/quickstart-paas-portal/portal-new-healthcareapi-details.png" alt-text="New healthcare api details":::
 
 Confirm creation and await FHIR API deployment.
 
 ## Additional settings (optional)
 
 You can also click **Next: Additional settings** to view the authentication settings. The default configuration for the Azure API for FHIR is to [use Azure RBAC for assigning data plane roles](configure-azure-rbac.md). When configured in this mode, the "Authority" for the FHIR service will be set to the Azure Active Directory tenant of the subscription:
 
-![Default Authentication settings](media/rbac/confirm-azure-rbac-mode.png)
+:::image type="content" source="media/rbac/confirm-azure-rbac-mode-create.png" alt-text="Default Authentication settings":::
 
-Notice that the box for entering allowed object IDs is greyed, since we use Azure RBAC for configuring role assignments in this case.
+Notice that the box for entering allowed object IDs is grayed out, since we use Azure RBAC for configuring role assignments in this case.
 
 If you wish to configure the FHIR service to use an external or secondary Azure Active Directory tenant, you can change the Authority and enter object IDs for user and groups that should be allowed access to the server. For more information, see the [local RBAC configuration](configure-local-rbac.md) guide.