Merge pull request #239471 from EXPEkesheth/patch-72

Update configure-import-data.md

Author: prmerger-automator[bot]

articles/healthcare-apis/fhir/configure-import-data.md

@@ -1,12 +1,12 @@
 ---
 title: Configure import settings in the FHIR service - Azure Health Data Services
 description: This article describes how to configure import settings in the FHIR service.
-author: RuiyiC
+author: Expekesheth
 ms.service: healthcare-apis
 ms.subservice: fhir
 ms.topic: how-to
 ms.date: 06/06/2022
-ms.author: chenrui 
+ms.author: kesheth
 ---
 
 # Configure bulk-import settings
@@ -148,9 +148,6 @@ Select **Enabled from selected virtual networks and IP addresses**. Under the Fi
 | West Europe          | 20.61.98.66       |
 | West US 2            | 40.64.135.77      |
 
-> [!NOTE]
-> The above steps are similar to the configuration steps described in the document **Converting your data to FHIR**. For more information, see [Configure the ACR firewall](./convert-data.md#step-6-optional-configure-the-azure-container-registry-firewall-for-secure-access).
-
 #### Option 2.2 : Access storage account provisioned in same Azure region as FHIR service
 
 The configuration process for IP addresses in the same region is just like above except a specific IP address range in Classless Inter-Domain Routing (CIDR) format is used instead (i.e., 100.64.0.0/10). The reason why the IP address range (100.64.0.0 – 100.127.255.255) must be specified is because an IP address for the FHIR service will be allocated each time an `$import` request is made.