Update disaster-recovery.md

Author: laujan

articles/applied-ai-services/form-recognizer/disaster-recovery.md

@@ -15,6 +15,14 @@ ms.author: lajanuar
 
 # Back up and recover your Form Recognizer models
 
+::: moniker range="form-recog-3.0.0"
+[!INCLUDE [applies to v3.0](includes/applies-to-v3-0.md)]
+::: moniker-end
+
+::: moniker range="form-recog-2.1.0"
+[!INCLUDE [applies to v2.1](../includes/applies-to-v2-1.md)]
+::: moniker-end
+
 ::: moniker range=">= form-recog-2.1.0"
 
 When you create a Form Recognizer resource in the Azure portal, you specify a region. From then on, your resource and all of its operations stay associated with that particular Azure server region. It's rare, but not impossible, to encounter a network issue that hits an entire region. If your solution needs to always be available, then you should design it to either fail-over into another region or split the workload between two or more regions. Both approaches require at least two Form Recognizer resources in different regions and the ability to sync custom models across regions.