Azure Policy built-in definitions for Azure API for FHIR
The name of each built-in policy definition links to the policy definition in the Azure portal. Use the link in the Version column to view the source on the Azure Policy GitHub repo.
Azure API for FHIR
|Azure API for FHIR should use a customer-managed key to encrypt data at rest||Use a customer-managed key to control the encryption at rest of the data stored in Azure API for FHIR when this is a regulatory or compliance requirement. Customer-managed keys also deliver double encryption by adding a second layer of encryption on top of the default one done with service-managed keys.||audit, disabled||1.0.1|
|Azure API for FHIR should use private link||Azure API for FHIR should have at least one approved private endpoint connection. Clients in a virtual network can securely access resources that have private endpoint connections through private links. For more information, visit: https://aka.ms/fhir-privatelink.||Audit, Disabled||1.0.0|
|CORS should not allow every domain to access your API for FHIR||Cross-Origin Resource Sharing (CORS) should not allow all domains to access your API for FHIR. To protect your API for FHIR, remove access for all domains and explicitly define the domains allowed to connect.||audit, disabled||1.0.0|
|CORS should not allow every domain to access your FHIR Service||Cross-Origin Resource Sharing (CORS) should not allow all domains to access your FHIR Service. To protect your FHIR Service, remove access for all domains and explicitly define the domains allowed to connect.||audit, disabled||1.0.0|