Added Azure SQL DB as unsupported source server for package files.

Azure SQL DB cannot be utilized as source catalog for ispac files. It seems to only work with SQL Server on-premise
 - Error when using Azure SQL DB. "Failed to connect to server barcelona.database.windows.net."
 - There is no option to specify any credentials.

Author: GarrySinghMSFT

docs/integration-services/lift-shift/ssis-azure-deploy-run-monitor-tutorial.md

@@ -85,7 +85,7 @@ To learn more about deploying packages and about the Deployment Wizard, see [Dep
 
 2. On the **Select Source** page, select the existing SSIS project to deploy.
     -   To deploy a project deployment file that you created, select **Project deployment file** and enter the path to the .ispac file.
-    -   To deploy a project that resides in an SSIS catalog, select **Integration Services catalog**, and then enter the server name and the path to the project in the catalog.
+    -   To deploy a project that resides in an SSIS catalog, select **Integration Services catalog**, and then enter the server name and the path to the project in the catalog. (This step is not unsupported with Azure SQL DB)
     -   Select **Next** to see the **Select Destination** page.
 
 3.  On the **Select Destination** page, select the destination for the project.
@@ -213,4 +213,4 @@ Get-AzDataFactoryV2IntegrationRuntime -Status -DataFactoryName $DataFactoryName
 ```
 
 ## Next steps
-- Learn how to schedule package execution. For more info, see [Schedule SSIS package execution on Azure](ssis-azure-schedule-packages.md)
+- Learn how to schedule package execution. For more info, see [Schedule SSIS package execution on Azure](ssis-azure-schedule-packages.md)