Merge pull request #110761 from MladjoA/patch-23

Portal not supported for new IR with existing SSISDB

Author: PRMerger18

articles/data-factory/configure-bcdr-azure-ssis-integration-runtime.md

@@ -11,7 +11,7 @@ manager: mflasko
 ms.reviewer: douglasl
 ms.topic: conceptual
 ms.custom: seo-lt-2019
-ms.date: 08/14/2018
+ms.date: 04/09/2020
 ---
 
 # Configure the Azure-SSIS Integration Runtime with Azure SQL Database geo-replication and failover
@@ -107,9 +107,11 @@ When an ADF or Azure-SSIS IR disaster occurs in current region, you can make you
 
 ### Steps
 
-Follow these steps to stop your Azure-SSIS IR, switch the IR to a new region, and start it again.
+Follow these steps to move your Azure-SSIS IR to a new region.
+> [!NOTE]
+> Step 3 (creation of IR) needs to be done via PowerShell. Azure portal will report an error stating that SSISDB already exists.
 
-1. Execute stored procedure to make SSISDB attached to **\<new_data_factory_name\>** or **\<new_integration_runtime_name\>**.
+1. Execute stored procedure to update metadata in SSISDB to accept connections from **\<new_data_factory_name\>** and **\<new_integration_runtime_name\>**.
    
   ```SQL
     EXEC [catalog].[failover_integration_runtime] @data_factory_name='<new_data_factory_name>', @integration_runtime_name='<new_integration_runtime_name>'