Merge pull request #294314 from chugugrace/mybranch02082025

Fix in-consistency about SSIS IR starting time.

Author: prmerger-automator[bot]

articles/data-factory/azure-ssis-integration-runtime-virtual-network-configuration.md

@@ -18,6 +18,9 @@ When using SQL Server Integration Services (SSIS) in Azure Data Factory (ADF) or
 
 Here’s a table highlighting the differences between standard and express virtual network injection methods:
 
+> [!NOTE]
+> The Azure-SSIS IR starting duration usually applies to most situations. However, the actual startup time might be longer in some cases, such as if the SSIS-IR has a custom setup that requires extra processing time or uses specific node types.
+
 | Comparison | Standard virtual network injection | Express virtual network injection |
 |------------|------------------------------------|-----------------------------------|
 | **Azure-SSIS IR starting duration** | Around 30 minutes. | Around 5 minutes. | 

articles/data-factory/how-to-schedule-azure-ssis-integration-runtime.md

@@ -357,7 +357,7 @@ The following steps don't provide the complete details for creating a runbook. F
 
    :::image type="content" source="./media/how-to-schedule-azure-ssis-integration-runtime/start-runbook-window.png" alt-text="Screenshot of the pane for parameters in starting a runbook.":::
 
-6. On the **Job** pane, select the **Output** tile. On the **Output** pane, wait for the message **##### Completed #####** after you see **##### Starting #####**. Starting an Azure-SSIS IR takes about 20 minutes. Close the **Job** pane and get back to the **Runbook** page.
+6. On the **Job** pane, select the **Output** tile. On the **Output** pane, wait for the message **##### Completed #####** after you see **##### Starting #####**. Close the **Job** pane and get back to the **Runbook** page.
 
    :::image type="content" source="./media/how-to-schedule-azure-ssis-integration-runtime/start-completed.png" alt-text="Screenshot that shows the output pane.":::