Merge pull request #5367 from douglaslMS/ssis-everest-version

Clarified version requirements and cleaned up structure.

Author: Ja-Dunn

docs/integration-services/lift-shift/ssis-azure-lift-shift-ssis-packages-overview.md

@@ -17,7 +17,7 @@ ms.workload: "Inactive"
 ---
 # Lift and shift SQL Server Integration Services workloads to the cloud
 You can now move your SQL Server Integration Services (SSIS) packages and workloads to the Azure cloud.
--   Store and manage SSIS projects and packages in the SSIS Catalog database (SSISDB) on Azure SQL Database.
+-   Store and manage SSIS projects and packages in the SSIS Catalog database (SSISDB) on Azure SQL Database or SQL Database Managed Instance (Preview).
 -   Run packages in an instance of the Azure SSIS Integration Runtime, introduced as part of Azure Data Factory version 2.
 -   Use familiar tools such as SQL Server Management Studio (SSMS) for these common tasks.
 
@@ -33,7 +33,7 @@ The following table highlights the differences between SSIS on premises and SSIS
 | Storage | Runtime | Scalability |
 |---|---|---|
 | On premises (SQL Server) | SSIS runtime hosted by SQL Server | SSIS Scale Out (in SQL Server 2017 and later)<br/><br/>Custom solutions (in prior versions of SQL Server) |
-| On Azure (SQL Database) | Azure SSIS Integration Runtime, a component of Azure Data Factory version 2 | Scaling options for the SSIS IR |
+| On Azure (SQL Database or SQL Database Managed Instance (Preview)) | Azure SSIS Integration Runtime, a component of Azure Data Factory version 2 | Scaling options for the SSIS IR |
 | | | |
 
 Azure Data Factory hosts the runtime engine for SSIS packages on Azure. The runtime engine is called the Azure SSIS Integration Runtime (SSIS IR).
@@ -50,37 +50,42 @@ You only have to provision the SSIS IR one time. After that, you can use familia
 
 Data Factory also supports other types of Integration Runtimes. To learn more about the SSIS IR and the other types of Integration Runtimes, see [Integration runtime in Azure Data Factory](https://docs.microsoft.com/azure/data-factory/concepts-integration-runtime).
 
+## Version info
+
+You can deploy a package created with any version of SSIS to Azure. When you deploy a package to Azure, if there are no validation errors, the package is automatically upgraded to the latest package format. In other words, it is always upgraded to the latest version of SSIS.
+
+The deployment process validates packages to ensure that they can run on the Azure-SSIS Integration Runtime. For more info, see [Validate SSIS packages deployed to Azure](ssis-azure-validate-packages.md).
+
 ## Prerequisites
-The capabilities described in this article do not require SQL Server 2017 or SQL Server 2016.
 
-These capabilities require the following versions of SQL Server Data Tools (SSDT):
+The capabilities described in this article require the following versions of SQL Server Data Tools (SSDT):
 -   For Visual Studio 2017, version 15.3 (preview) or later.
 -   For Visual Studio 2015,  version 17.2 or later.
 
-> [!NOTE]
-> When you deploy packages to Azure, the Package Deployment Wizard always upgrades the packages to the latest package format.
-
 For more info about prerequisites in Azure, see [Deploy SSIS packages to Azure](https://docs.microsoft.com/azure/data-factory/tutorial-create-azure-ssis-runtime-portal).
 
-## SSIS features on Azure
-
-When you provision an instance of SQL Database to host SSISDB, the Azure Feature Pack for SSIS and the Access Redistributable are also installed. These components provide connectivity to **Excel and Access** files and to various **Azure** data sources, in addition to the data sources supported by the built-in components. You can't install **third-party components** for SSIS at this time (including third-party components from Microsoft, such as the Oracle and Teradata components by Attunity and the SAP BI components).
+## Provision SSIS on Azure
+Before you can deploy and run SSIS packages in Azure, you have to provision the SSIS Catalog database (SSISDB) and the Azure-SSIS Integration Runtime. Follow the provisioning steps in this article: [Deploy SSIS packages to Azure](https://docs.microsoft.com/azure/data-factory/tutorial-create-azure-ssis-runtime-portal).
 
 The **name of the SQL Database** that hosts SSISDB becomes the first part of the four-part name to use when you deploy and manage packages from SSDT and SSMS - `<sql_database_name>.database.windows.net`.
 
-You have to use the **project deployment model**, not the package deployment model, for projects you deploy to SSISDB on Azure SQL Database.
+For info about how to connect to the SSIS Catalog database, see [Connect to the SSISDB Catalog database on Azure](ssis-azure-connect-to-catalog-database.md).
 
+## Design packages
 You continue to **design and build packages** on-premises in SSDT, or in Visual Studio with SSDT installed.
 
-For info about how to connect to **on-premises data sources** from the cloud with Windows authentication, see [Connect to on-premises data sources with Windows Authentication](ssis-azure-connect-with-windows-auth.md).
+For info about how to connect to on-premises data sources from the cloud with **Windows authentication**, see [Connect to on-premises data sources and Azure file shares with Windows Authentication](ssis-azure-connect-with-windows-auth.md).
+
+For info about how to connect to files and file shares, see [Store and retrieve files on file shares on premises and in Azure with SSIS](ssis-azure-files-file-shares.md).
+
+When you provision an instance of SQL Database to host SSISDB, the Azure Feature Pack for SSIS and the Access Redistributable are also installed. These components provide connectivity to various **Azure** data sources and to **Excel and Access** files, in addition to the data sources supported by the built-in components.
 
-## Common tasks
+You can't install or use **third-party components** for SSIS at this time (including third-party components from Microsoft, such as the Oracle and Teradata components by Attunity and the SAP BI components).
 
-### Provision
-Before you can deploy and run SSIS packages in Azure, you have to provision the SSISDB Catalog database and the Azure SSIS Integration Runtime. Follow the provisioning steps in this article: [Deploy SSIS packages to Azure](https://docs.microsoft.com/azure/data-factory/tutorial-create-azure-ssis-runtime-portal).
+## Deploy and run packages
+You have to use the **project deployment model**, not the package deployment model, when you deploy projects to SSISDB on Azure.
 
-### Deploy and run packages
-To deploy projects and run packages on SQL Database, you can use one of several familiar tools and scripting options:
+To deploy projects and run packages on Azure, you can use one of several familiar tools and scripting options:
 -   SQL Server Management Studio (SSMS)
 -   Transact-SQL (from SSMS, Visual Studio Code, or another tool)
 -   A command-line tool
@@ -89,12 +94,12 @@ To deploy projects and run packages on SQL Database, you can use one of several
 
 To get started, see [Deploy, run, and monitor an SSIS package on Azure](ssis-azure-deploy-run-monitor-tutorial.md).
 
-### Monitor packages
+## Monitor packages
 To monitor running packages in SSMS, you can use one of the following reporting tools in SSMS.
 -   Right-click **SSISDB**, and then select **Active Operations** to open the **Active Operations** dialog box.
 -   Select a package in Object Explorer, right-click and select **Reports**, then **Standard Reports**, then **All Executions**.
 
-### Schedule packages
+## Schedule packages
 To schedule the execution of packages stored in SQL Database, you can use the following tools:
 -   SQL Server Agent on-premises
 -   The Data Factory SQL Server Stored Procedure activity