What's Next for BizTalk Server
Prepare your integration solutions for the future
Start foreseen at 14:00 CET
Nice to connect with you
Architect & Practice Lead Integration @ Codit since 2012
Hi, I’m Michel!
2
Agenda
| Support Lifecycles
| Paths for the future
| Other considerations
May 2021 What's Next for Microsoft's BizTalk Server 3
4
Support
Lifecycles
May 2021 What's Next for Microsoft's BizTalk Server 5
Lifecycle Phases
Type of Support Mainstream Extended End Of Life
Change Requests /
Features
Security Updates
Other Updates
Paid Support
6
BizTalk Support Lifecycle
May 2021 What's Next for Microsoft's BizTalk Server 7
BizTalk 2010
EOL
• January 12th
2021
Now
• May 20th 2021
BizTalk 2016
End
Mainstream
Support
• January 11th
2022
BizTalk 2013
(R2) EOL
• July 11th 2023
BizTalk 2020
End
Mainstream
Support
• January 9th
2024
BizTalk 2016
EOL
• January 11th
2027
BizTalk 2020
EOL
• January 9th
2029
8
Platform Lifecycle
May 2021 What's Next for Microsoft's BizTalk Server 9
Server 2012 (R2)
End Mainstream
Support
• October 9th, 2018
Server 2008 R2 SP1
EOL
• January 14th, 2020
Now
• May 20th, 2021
Server 2016 End
Mainstream
Support
• January 11th, 2022
Server 2012 (R2)
EOL
• October 10th, 2023
Server 2019 End
Mainstream
Support
• January 9th, 2024
Server 2016 EOL
• January 12th, 2027
Server 2019 EOL
• January 9th, 2029
SQL 2008 R2
EOL
• July 9th, 2019
Now
• May 20th, 2021
SQL 2016 End
Mainstream
Support
• July 13th, 2021
SQL 2012 EOL
• July 12th, 2022
SQL 2017 End
Mainstream
Support
• October 11th, 2022
SQL 2014 EOL
• July 9th, 2024
SQL 2019 End
Mainstream
Support
• January 7th, 2025
SQL 2016 EOL
• July 14th, 2026
SQL 2017 EOL
• October 12th, 2027
SQL 2019 EOL
• January 8th, 2030
10
Your Paths for
the Future
11
The BizTalk Upgrade Path
Upgrade to a newer, supported version of BizTalk
May 2021 What's Next for Microsoft's BizTalk Server 12
Pro Con
Minimal to no changes in application New environment needed
Supported by Microsoft Support eventually ends
Retain current knowledge Everything needs to be retested
13
The Extended Support Path
If your environment is currently running fine and supported
May 2021 What's Next for Microsoft's BizTalk Server 14
Pro Con
Absolutely no changes in application Only security updates and paid support
Supported by Microsoft Not applicable to BizTalk 2010
Retain current knowledge No new features will be released
Support will end sooner
15
The Migration Path
Preparing yourself for the future by migrating to Azure Integration Services
May 2021 What's Next for Microsoft's BizTalk Server 16
Pro Con
Best prepared for the future Learning curve for your BizTalk experts
Opportunity to optimize & refactor
integrations
Rewrite process might take time
Lower infrastructure and licensing costs Temporarily support two tech stacks
Applicable to all scenarios
17
The Hybrid Path
Take small steps towards the future by writing new applications in AIS
May 2021 What's Next for Microsoft's BizTalk Server 18
Pro Con
Not a big bang migration Need to keep in mind the support of
the current environment
Gain knowledge with new integrations Need to support two technology stacks
Opportunity to optimize & refactor
integrations
Extends your current environment
towards the cloud
19
Pauwels’ Personal Preferred Path Picker (P5)
When going for the upgrade path, all new functionality should be done in a hybrid manner.
20
BizTalk Version Preferred Path
2010 Upgrade -> Hybrid -> Migrate
2013 Upgrade -> Hybrid -> Migrate
(Migrate)
2013 R2 Migrate
(Upgrade -> Hybrid -> Migrate)
2016 Support -> Hybrid -> Migrate
(Migrate)
2020 Hybrid -> Migrate
21
Pauwels’ Personal Preferred Path Picker (P5)
Your scenario
Now
Azure
Integration
Services
Future
22
Other
Considerations
23
Other Considerations
| Keep your other applications into account
| What is their future
| Are you upgrading them to newer versions or maybe moving to SaaS variants?
| Connectivity towards these is important
| Depending on the path, connectivity towards the other applications might be impacted and need
changes
| Custom in-house APIs
| Investigate possibilities for migration
| App Services / Function Apps
| Lower infrastructure / licensing costs
| No need to maintain a webservice infrastructure even after migrating away from BizTalk
May 2021 What's Next for Microsoft's BizTalk Server
May 2021 What's Next for Microsoft's BizTalk Server 24
Other Considerations
| On-premises scenarios supported by Azure Integration Services
| Upcoming GA of Logic Apps V2
| Processing where you need it (On-Prem / Cloud)
| The final replacement of BizTalk
| Training
| Training in new Azure technologies
| Training in Kubernetes
| Company culture
| Vision
| Upcoming changes
25
Getting Started
26
| Extensive study that focuses on all
aspects of a migration project from
on-premises integration to a hybrid
or cloud solution
| Clear picture of the critical points,
where the need for change is
greatest and measures to take
| Roadmap to improvement
| Duration: 5 days
Migration
Assessment
27
Time for Q&A and Feedback
28
Thanks for Joining!

What's Next for Microsoft's BizTalk Server

  • 1.
    What's Next forBizTalk Server Prepare your integration solutions for the future Start foreseen at 14:00 CET
  • 2.
    Nice to connectwith you Architect & Practice Lead Integration @ Codit since 2012 Hi, I’m Michel! 2
  • 3.
    Agenda | Support Lifecycles |Paths for the future | Other considerations May 2021 What's Next for Microsoft's BizTalk Server 3
  • 4.
  • 5.
    May 2021 What'sNext for Microsoft's BizTalk Server 5 Lifecycle Phases Type of Support Mainstream Extended End Of Life Change Requests / Features Security Updates Other Updates Paid Support
  • 6.
  • 7.
    BizTalk Support Lifecycle May2021 What's Next for Microsoft's BizTalk Server 7 BizTalk 2010 EOL • January 12th 2021 Now • May 20th 2021 BizTalk 2016 End Mainstream Support • January 11th 2022 BizTalk 2013 (R2) EOL • July 11th 2023 BizTalk 2020 End Mainstream Support • January 9th 2024 BizTalk 2016 EOL • January 11th 2027 BizTalk 2020 EOL • January 9th 2029
  • 8.
  • 9.
    Platform Lifecycle May 2021What's Next for Microsoft's BizTalk Server 9 Server 2012 (R2) End Mainstream Support • October 9th, 2018 Server 2008 R2 SP1 EOL • January 14th, 2020 Now • May 20th, 2021 Server 2016 End Mainstream Support • January 11th, 2022 Server 2012 (R2) EOL • October 10th, 2023 Server 2019 End Mainstream Support • January 9th, 2024 Server 2016 EOL • January 12th, 2027 Server 2019 EOL • January 9th, 2029 SQL 2008 R2 EOL • July 9th, 2019 Now • May 20th, 2021 SQL 2016 End Mainstream Support • July 13th, 2021 SQL 2012 EOL • July 12th, 2022 SQL 2017 End Mainstream Support • October 11th, 2022 SQL 2014 EOL • July 9th, 2024 SQL 2019 End Mainstream Support • January 7th, 2025 SQL 2016 EOL • July 14th, 2026 SQL 2017 EOL • October 12th, 2027 SQL 2019 EOL • January 8th, 2030
  • 10.
  • 11.
  • 12.
    The BizTalk UpgradePath Upgrade to a newer, supported version of BizTalk May 2021 What's Next for Microsoft's BizTalk Server 12 Pro Con Minimal to no changes in application New environment needed Supported by Microsoft Support eventually ends Retain current knowledge Everything needs to be retested
  • 13.
  • 14.
    The Extended SupportPath If your environment is currently running fine and supported May 2021 What's Next for Microsoft's BizTalk Server 14 Pro Con Absolutely no changes in application Only security updates and paid support Supported by Microsoft Not applicable to BizTalk 2010 Retain current knowledge No new features will be released Support will end sooner
  • 15.
  • 16.
    The Migration Path Preparingyourself for the future by migrating to Azure Integration Services May 2021 What's Next for Microsoft's BizTalk Server 16 Pro Con Best prepared for the future Learning curve for your BizTalk experts Opportunity to optimize & refactor integrations Rewrite process might take time Lower infrastructure and licensing costs Temporarily support two tech stacks Applicable to all scenarios
  • 17.
  • 18.
    The Hybrid Path Takesmall steps towards the future by writing new applications in AIS May 2021 What's Next for Microsoft's BizTalk Server 18 Pro Con Not a big bang migration Need to keep in mind the support of the current environment Gain knowledge with new integrations Need to support two technology stacks Opportunity to optimize & refactor integrations Extends your current environment towards the cloud
  • 19.
  • 20.
    Pauwels’ Personal PreferredPath Picker (P5) When going for the upgrade path, all new functionality should be done in a hybrid manner. 20 BizTalk Version Preferred Path 2010 Upgrade -> Hybrid -> Migrate 2013 Upgrade -> Hybrid -> Migrate (Migrate) 2013 R2 Migrate (Upgrade -> Hybrid -> Migrate) 2016 Support -> Hybrid -> Migrate (Migrate) 2020 Hybrid -> Migrate
  • 21.
    21 Pauwels’ Personal PreferredPath Picker (P5) Your scenario Now Azure Integration Services Future
  • 22.
  • 23.
    23 Other Considerations | Keepyour other applications into account | What is their future | Are you upgrading them to newer versions or maybe moving to SaaS variants? | Connectivity towards these is important | Depending on the path, connectivity towards the other applications might be impacted and need changes | Custom in-house APIs | Investigate possibilities for migration | App Services / Function Apps | Lower infrastructure / licensing costs | No need to maintain a webservice infrastructure even after migrating away from BizTalk May 2021 What's Next for Microsoft's BizTalk Server
  • 24.
    May 2021 What'sNext for Microsoft's BizTalk Server 24 Other Considerations | On-premises scenarios supported by Azure Integration Services | Upcoming GA of Logic Apps V2 | Processing where you need it (On-Prem / Cloud) | The final replacement of BizTalk | Training | Training in new Azure technologies | Training in Kubernetes | Company culture | Vision | Upcoming changes
  • 25.
  • 26.
    26 | Extensive studythat focuses on all aspects of a migration project from on-premises integration to a hybrid or cloud solution | Clear picture of the critical points, where the need for change is greatest and measures to take | Roadmap to improvement | Duration: 5 days Migration Assessment
  • 27.
    27 Time for Q&Aand Feedback
  • 28.