Related Articles
Newsletter
Join our blog
Join other Azure, Power Platform and SQL Server pros by subscribing to our blog.


-1.png)
Start with the FREE community plan and get your lifetime access to 20+ courses. Get Instant Access Now!
Need help? Talk to an expert: (904) 638-5743
Private Classes
Private deliveries of courses for groups
On-Demand Learning
Beginner to advanced classes taught by Microsoft MVPs and Authors.
Bootcamps
In-depth boot camps take you from a novice to mastery in less than a week.
Season Learning Pass
Get access to our very best training offerings for successful up-skilling.
Stream Pro Plus
Combine On-Demand Learning platform with face-to-face Virtual Mentoring.
Certification Training
Prepare and ace your next certification with CertXP.
Cheat Sheets
Quick references for when you need a little guidance.
Prag Guides
Explore our knowledge base for quick tips on syntax, functions, and more!
Downloads
Digital goodies - code samples, student files, and other must have files.
Blog
Stay up-to-date on all things Power BI, Power Apps, Microsoft 365 and Azure.
Community Discord Server
Start here for technology questions to get answers from the community.
Career Guides
Breaking into the field? Let these guides help get you started with a plan.
Nerd Guides
Summaries developed in conjunction with our Learn with the Nerds sessions.
Quickstarts
Hands-on training with expert-led collaborative development.
Private Training
Personalized approach for your specific training requirements
Hackathons
Use your own data to take your team's skills to the next level.
Virtual mentoring
Get there faster with your personal trainer.
Enablement
Comprehensive enterprise enablement training for your team.
Admin Hackathon
Tame your power platform environment.
In yesterday’s post I introduced you to Azure Data Factory Version 2 (ADF V2) and the visual tools that were added. Today, I’d like to talk about developing and deploying SSIS packages in Azure Data Factory V2. This blog will be quite brief as if you’re using Visual Studio and SQL Server data tools for building your packages, not much changes.
The experience from the development side doesn’t change and if you’re wondering about version control, this does not have to change; it’s the same development paradigm that you’re used to. The only real difference is where we deploy to – more on that in a bit.
Something else to understand about the development experience is that there is no separate version of SSIS required. If you’re building in more recent versions of SQL Server data tools within Visual Studio, you can choose to build your package in SSIS 2012, 2014 or 2017; you choose this setting at the project level.
With SSIS and Azure Data Factory, any of those versions will work. When deploying your project or packages out to the SSIS runtime in ADF, part of that deployment process is an upgrade or migration to the current version of SSIS (currently 2017). You don’t have to change your version in Visual Studio when developing, this happens automatically for you.
As I mentioned, the biggest difference is deployment. When you choose to deploy to an SSIS catalog hosted in Azure, you’ll be prompted for an authentication method. So, if you’re deploying on prem or using an older version of SQL Server data tools, we had no choice but to use Windows authentication.
But with the new tooling with Visual Studio, you now have a choice of what kind of authentication you want to use when you’re deploying your package out to the SSIS catalog in Azure.
There are many changes in the platform, but the good news is on the development and deployment side, the experience of SSIS in the cloud has not changed a whole lot. If you want more information about SSIS in the cloud or Azure Data Factory itself, we are your best resource. Click the link below or contact us—we’re here to help.
ABOUT THE AUTHOR
Free Trial
private training
Newsletter
Join other Azure, Power Platform and SQL Server pros by subscribing to our blog.
Leave a comment