{"id":36942,"date":"2018-10-04T15:57:53","date_gmt":"2018-10-04T22:57:53","guid":{"rendered":"https:\/\/blogs.msdn.microsoft.com\/webdev\/?p=15455"},"modified":"2018-10-04T15:57:53","modified_gmt":"2018-10-04T22:57:53","slug":"use-hybrid-connections-to-incrementally-migrate-applications-to-the-cloud","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/dotnet\/use-hybrid-connections-to-incrementally-migrate-applications-to-the-cloud\/","title":{"rendered":"Use Hybrid Connections to Incrementally Migrate Applications to the Cloud"},"content":{"rendered":"

As the software industry shifts to running software in the cloud, organizations are looking to migrate existing applications from on-premises to the cloud. Last week at Microsoft\u2019s Ignite conference, Paul Yuknewicz<\/a> and I delivered a talk focused on how to get started migrating applications to Azure (watch the talk free<\/a>) where we walked through the business case for migrating to the cloud, and choosing the right hosting and data services. If your application is a candidate for running in App Service<\/a>, one of the most useful pieces of technology that we showed was Hybrid Connections<\/a>. Hybrid Connections let you host a part of your application in Azure App Service, while calling back into resources and services not running in Azure (e.g. still on-premises). This enables you to try running a small part of your application in the cloud without the need to move your entire application and all of its dependencies at once; which is usually time consuming, and extremely difficult to debug when things don\u2019t work. So, in this post I\u2019ll show you how to host an ASP.NET front application in the cloud, and configure a hybrid connection to connect back to a service on your local machine.<\/p>\n

Publishing Our Sample App to the Cloud<\/h2>\n

For the purposes of this post, I\u2019m going to use the Smart Hotel 360 App sample<\/a> that uses an ASP.NET front end that calls a WCF service which then accesses a SQL Express LocalDB instance on my machine. ** The first thing I need to do is publish the ASP.NET application to App Service. To do this, right click on the \u201cSmartHotel.Registration.Web\u201d project and choose \u201cPublish\u201d \"clip_image001\"<\/a><\/p>\n

The publish target dialog is already on App Service, and I want to create a new one, so I will just click the \u201cPublish\u201d button. This will bring up the \u201cCreate App Service\u201d dialog.\u00a0 Next, I will click \u201cCreate\u201d and wait for a minute while the resources in the cloud are created and the application is published. \"clip_image003\"<\/a> When it\u2019s finished publishing, my web browser will open to my published site. At this point, there will be an error loading the page since it cannot connect to the WCF service. To fix this we’ll add a hybrid connection. \"image\"<\/a><\/p>\n

Create the Hybrid Connection<\/h2>\n

To create the Hybrid Connection, I navigate to the App Service I just created in the Azure Portal. One quick way to do this is to click the \u201cManaged in Cloud Explorer\u201d link on the publish summary page \"clip_image005\"<\/a><\/p>\n

Right click the site, and choose \u201cOpen in Portal\u201d (You can manually navigate to the page by logging into the Azure portal<\/a>, click App Services, and choose your site). \"clip_image006\"<\/a><\/p>\n

To create the hybrid connection: Click the \u201cNetworking\u201d tab in the Settings section on the left side of the App Service page Click \u201cConfigure your hybrid connection endpoints\u201d in the \u201cHybrid connections\u201d section \"image\"<\/a> Next, click \u201cAdd a hybrid connection\u201d Then click \u201cCreate a new hybrid connection\u201d \"clip_image010\"<\/a><\/p>\n

Fill out the \u201cCreate new hybrid connection\u201d form as follows: * Hybrid connection Name: **any unique name that you want**** * **Endpoint Host:<\/strong> This is the machine URL your application is currently using to connect to the on-premises resource. In this case, this is \u201clocalhost\u201d (*Note: per the documentation, use the hostname rather than a specific IP address if possible as it\u2019s more robust)***** * Endpoint Port: **The port the on-premises resource is listening on. In this case, the WCF service on my local machine is listening on 2901**** * **Servicebus namespace:<\/strong> If you\u2019ve previously configured hybrid connections you can re-use an existing one, in this case we\u2019ll create a new one, and give it a name****<\/p>\n

\"clip_image011\"<\/a><\/p>\n

**** Click \u201cOK\u201d. It will take about 30 seconds to create the hybrid connection, when it\u2019s done you\u2019ll see it appear on the Hybrid connections page.<\/p>\n

Configure the Hybrid Connection Locally<\/h3>\n

Now we need to install the Hybrid Connection Manager on the local machine. To do this, click the \u201cDownload connection manager\u201d on the Hybrid connections page and install the MSI. **\"clip_image013\"<\/a><\/p>\n

** After the connection manager finishes installing, launch the \u201cHybrid Connections Manager UI\u201d, it should appear in your Windows Start menu if you type \u201cHybrid Connections\u201d. (If for some reason it doesn\u2019t appear on the Start Menu, launch it manually from \u201cC:\\Program Files\\Microsoft\\HybridConnectionManager <version#>\u201d) Click the \u201cAdd a new Hybrid Connection\u201d button in the Hybrid Connections Manager UI and login with the same credentials you used to publish your application. \"clip_image015\"<\/a> Choose the subscription you used published your application from the \u201cSubscription\u201d dropdown, choose the hybrid connection you just created in the portal, and click \u201cSave\u201d. \"clip_image017\"<\/a> In the overview, you should see the status say \u201cConnected\u201d. *Note: If the state won\u2019t change from \u201cNot Connected\u201d, I\u2019ve found that rebooting my machine fixes this (it can take a few minutes to connect after the reboot). *\"clip_image019\"<\/a> ** Make sure everything is running correctly on your local machine, and then when we open the site running in App Service we can see that it loads with no error. In fact, we can even put a breakpoint in the GetTodayRegistrations() method of Service.svc.cs, hit F5 in Visual Studio, and when the page loads in App Service the breakpoint on the local machine is hit! \"clip_image021\"<\/a><\/p>\n

Conclusion<\/h2>\n

If you are looking to move applications to the cloud, I hope that this quick introduction to Hybrid Connections will enable you to try moving things incrementally. If you are looking to migrate an application to the cloud, please tell us about it by taking this short survey<\/a>. Additionally, you may find these resources helpful: * Video: Azure App Service with Hybrid Connections to On-premises Resources<\/a> * Watch our talk on migrating applications to Azure<\/a> * Migrate your .NET app to Azure<\/a> * .NET application architecture guides<\/a> As always, if you have any questions, or problems let me know via Twitter<\/a>, or in the comments section below.<\/p>\n","protected":false},"excerpt":{"rendered":"

As the software industry shifts to running software in the cloud, organizations are looking to migrate existing applications from on-premises to the cloud. Last week at Microsoft\u2019s Ignite conference, Paul Yuknewicz and I delivered a talk focused on how to get started migrating applications to Azure (watch the talk free) where we walked through the […]<\/p>\n","protected":false},"author":404,"featured_media":21383,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[197,327,7252,7257],"tags":[31,37,7539,91,7576,7339],"class_list":["post-36942","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-aspnet","category-azure","category-cloud","category-wcf","tag-asp-net","tag-azure","tag-cloud","tag-lift-and-shift","tag-migrate-to-the-cloud","tag-wcf"],"acf":[],"blog_post_summary":"

As the software industry shifts to running software in the cloud, organizations are looking to migrate existing applications from on-premises to the cloud. Last week at Microsoft\u2019s Ignite conference, Paul Yuknewicz and I delivered a talk focused on how to get started migrating applications to Azure (watch the talk free) where we walked through the […]<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/posts\/36942","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/users\/404"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/comments?post=36942"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/posts\/36942\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/media\/21383"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/media?parent=36942"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/categories?post=36942"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/tags?post=36942"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}