Skip to content

Commit 230881d

Browse files
committed
Needed to also update FAQ article.
1 parent cbb690d commit 230881d

File tree

1 file changed

+1
-12
lines changed

1 file changed

+1
-12
lines changed

articles/healthcare-apis/azure-api-for-fhir/fhir-faq.yml

Lines changed: 1 addition & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -217,15 +217,4 @@ sections:
217217
Is there a way to encrypt my data using my personal key and not a default key?
218218
answer: |
219219
Yes, Azure API for FHIR allows configuring customer-managed keys, leveraging support from Cosmos DB. For more information about encrypting your data with a personal key, see [Configure customer-managed keys at REST](customer-managed-key.md).
220-
221-
- name: "Azure API for FHIR: Preview Features"
222-
questions:
223-
- question: |
224-
Can I configure scaling capacity for Azure IoT Connector for FHIR (preview)?
225-
answer: |
226-
Since Azure IoT Connector for FHIR is free of charge during public preview, its scaling capacity is fixed and limited. Azure IoT Connector for FHIR configuration available in public preview is expected to provide a throughput of about 200 messages per second. Some form of resource capacity configuration will be made available in General Availability (GA).
227-
228-
- question: |
229-
Why can't I install Azure IoT Connector for FHIR (preview) when Private Link is enabled on Azure API for FHIR?
230-
answer: |
231-
Azure IoT Connector for FHIR doesn't support Private Link capability at this time. Hence, if you have Private Link enabled on Azure API for FHIR, you can't install Azure IoT Connector for FHIR and vice-versa. This limitation is expected to go away when Azure IoT Connector for FHIR is available for General Availability (GA).
220+

0 commit comments

Comments
 (0)