Removing IoMT FHIR Connector reference

Author: msjasteppe

articles/healthcare-apis/azure-api-for-fhir/disaster-recovery.md

@@ -15,7 +15,7 @@ Azure API for FHIR is a fully managed service, based on Fast Healthcare Interope
 
 The DR feature provides a Recovery Point Objective (RPO) of 15 minutes and a Recovery Time Objective (RTO) of 60 minutes.
 
- ## How to enable DR 
+## How to enable DR 
 
 To enable the DR feature, create a one-time support ticket. You can choose an Azure paired region or another region where the Azure API for FHIR is supported. The Microsoft support team will enable the DR feature based on the support priority.
 
@@ -33,30 +33,29 @@ By default, Azure API for FHIR offers data protection through backup and restore
 
 It's worth noting that the throughput RU/s must have the same values in the primary and secondary regions.
 
-[ ![Azure Traffic Manager.](media/disaster-recovery/azure-traffic-manager.png) ](media/disaster-recovery/azure-traffic-manager.png#lightbox)
+[![Azure Traffic Manager](media/disaster-recovery/azure-traffic-manager.png)](media/disaster-recovery/azure-traffic-manager.png#lightbox)
 
 ### Automatic failover
 
 During a primary region outage, the Azure API for FHIR automatically fails over to the secondary region and the same service endpoint is used. The service is expected to resume in one hour or less, and potential data loss is up to 15 minutes' worth of data. Other configuration changes may be required. For more information, see [Configuration changes in DR](#configuration-changes-in-dr).
 
-[ ![Failover in disaster recovery.](media/disaster-recovery/failover-in-disaster-recovery.png) ](media/disaster-recovery/failover-in-disaster-recovery.png#lightbox)
+[![Failover in disaster recovery](media/disaster-recovery/failover-in-disaster-recovery.png)](media/disaster-recovery/failover-in-disaster-recovery.png#lightbox)
 
 ### Affected region recovery
 
 After the affected region recovers, it's automatically available as a secondary region and data replication restarts. You can start the data recovery process or wait until the failback step is completed.
 
-[ ![Replication in disaster recovery.](media/disaster-recovery/replication-in-disaster-recovery.png) ](media/disaster-recovery/replication-in-disaster-recovery.png#lightbox)
+[![Replication in disaster recovery](media/disaster-recovery/replication-in-disaster-recovery.png)](media/disaster-recovery/replication-in-disaster-recovery.png#lightbox)
 
 When the compute has failed back to the recovered region and the data hasn't, there may be potential network latencies. The main reason is that the compute and the data are in two different regions. The network latencies should disappear automatically as soon as the data fails back to the recovered region through a manual trigger.
 
-[ ![Network latency.](media/disaster-recovery/network-latency.png) ](media/disaster-recovery/network-latency.png#lightbox)
-
+[![Network latency](media/disaster-recovery/network-latency.png)](media/disaster-recovery/network-latency.png#lightbox)
 
 ### Manual failback
 
 The compute fails back automatically to the recovered region. The data is switched back to the recovered region manually by the Microsoft support team using the script. 
 
-[ ![Failback in disaster recovery.](media/disaster-recovery/failback-in-disaster-recovery.png) ](media/disaster-recovery/failback-in-disaster-recovery.png#lightbox)
+[![Failback in disaster recovery](media/disaster-recovery/failback-in-disaster-recovery.png)](media/disaster-recovery/failback-in-disaster-recovery.png#lightbox)
 
 ## Configuration changes in DR
 
@@ -93,13 +92,6 @@ The export job will be picked up from another region after 10 minutes without an
 
 Ensure that you grant the same permissions to the system identity of the Azure API for FHIR. Also, if the storage account is configured with selected networks, see [How to export FHIR data](../fhir/export-data.md).
 
-### IoMT FHIR Connector
-
-Any existing connection won't function until the failed region is restored. You can create a new connection once the failover has completed and your FHIR server is accessible. This new connection will continue to function when failback occurs.
-
-> [!NOTE]
-> IoMT Connector is a preview feature and does not provide support for disaster recovery. 
-
 ## How to test DR
 
 While not required, you can test the DR feature on a non-production environment. For DR test, only the data will be included and the compute won't be included. 
@@ -120,7 +112,6 @@ Consider the following steps for DR test.
 
 * (Optional) Share any feedback with the Microsoft support team.
 
-
 > [!NOTE]
 > The DR test will double the cost of your test environment during the test. No extra cost will incur after the DR test is completed and the DR feature is disabled.
 
@@ -131,12 +122,11 @@ The disaster recovery feature incurs extra costs because data of the compute and
 > [!NOTE]
 > The DR offering is subject to the [SLA for Azure API for FHIR](https://azure.microsoft.com/pricing/details/health-data-services), 1.0.
 
-
 ## Next steps
 
 In this article, you've learned how DR for Azure API for FHIR works and how to enable it. To learn about Azure API for FHIR's other supported features, see
 
->[!div class="nextstepaction"]
->[FHIR supported features](fhir-features-supported.md)
+> [!div class="nextstepaction"]
+> [FHIR supported features](fhir-features-supported.md)
 
 FHIR® is a registered trademark of [HL7](https://hl7.org/fhir/) and is used with the permission of HL7.