azureblog.co.uk
← cd ~/roles
// roles/azure · integration

FHIR Data ConverterAzure built-in role

Role allows user or principal to convert data from legacy format to FHIR

Role IDa1705bd2-3a8f-45a5-8683-466fcfd5cc24
CategoryIntegration
Actions0
Data actions2

Before you assign it

  • It reaches the data, not just the resource. It has 2 data actions, such as reading blobs, secrets or messages.

What it can do

No control-plane actions.

Data actions

PermissionWhat it allows
Microsoft.HealthcareApis/services/fhir/resources/convertData/actionData convert operation ($convert-data)
Microsoft.HealthcareApis/workspaces/fhirservices/resources/convertData/actionData convert operation ($convert-data)

Assign it

Scope it as tightly as you can: a resource or resource group rather than the whole subscription.

azure cli
az role assignment create \
  --assignee "jane.doe@contoso.com" \
  --role "FHIR Data Converter" \
  --scope "/subscriptions/<subscription id>/resourceGroups/<resource group>"
powershell3 lines
New-AzRoleAssignment -SignInName "jane.doe@contoso.com" `
  -RoleDefinitionName "FHIR Data Converter" `
  -Scope "/subscriptions/<subscription id>/resourceGroups/<resource group>"
bicep7 lines
resource assignment 'Microsoft.Authorization/roleAssignments@2022-04-01' = {
  name: guid(resourceGroup().id, principalId, 'a1705bd2-3a8f-45a5-8683-466fcfd5cc24')
  properties: {
    roleDefinitionId: subscriptionResourceId('Microsoft.Authorization/roleDefinitions', 'a1705bd2-3a8f-45a5-8683-466fcfd5cc24')
    principalId: principalId
  }
}

Who already has it?

kql · azure resource graph
authorizationresources
| where type == "microsoft.authorization/roleassignments"
| where tostring(properties.roleDefinitionId) endswith "a1705bd2-3a8f-45a5-8683-466fcfd5cc24"
| project principalId = tostring(properties.principalId), principalType = tostring(properties.principalType), scope = tostring(properties.scope)

Other integration roles

Find the smallest role for a task →

Sources