{"id":12446,"date":"2017-06-14T09:30:29","date_gmt":"2017-06-14T16:30:29","guid":{"rendered":"https:\/\/blogs.msdn.microsoft.com\/visualstudio\/?p=12446"},"modified":"2019-03-01T22:47:02","modified_gmt":"2019-03-02T06:47:02","slug":"take-your-web-app-to-azure","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/visualstudio\/take-your-web-app-to-azure\/","title":{"rendered":"Take your web app to Azure"},"content":{"rendered":"

You\u2019ve built your web app. It\u2019s running, and getting good traffic. Now you need to move on to solving the \u2018good problems\u2019 to have. You want to scale your app to support more users, but only at peak times. Or you need better hardware and simply don\u2019t want to manage that hardware\u2026 or software, or even the network. What if you just want to improve your app\u2019s reliability? Any of these may be reasons to look at hosting your app in Azure. Azure gives you a variety of hosting options so you can balance cost, performance, and ease of management; and Visual Studio makes it simple to deploy and manage your apps in Azure.<\/p>\n

Visual Studio 2017 gives you options to publish your app directly from your desktop, or to use Visual Studio Team Services to setup a CI\/CD pipeline<\/a>. Need to add monitoring and diagnostics to your app? Right click to connect to the Application Insights<\/a> service. Want to secure your app with Azure Active Directory<\/a>? Right click and add. Need to add a SQL Database<\/a> to your Azure app? You can easily make it part of your publishing process.<\/p>\n

Publishing to Azure<\/h2>\n

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

Publishing your Visual Studio 2017 app to Azure is as simple as right-clicking your app\u2019s project node and choosing to publish. From there you can choose to create new resources in Azure or select from existing resources to update your existing application. To make this work, you only need an Azure subscription, which you can set up for free with Visual Studio Dev Essentials<\/a> (which will also get you access to training materials and other tools) or the free Azure trial<\/a>.<\/p>\n

Now that you are set to publish we can publish to existing resources, or we can create new resources. Choosing new resources is simple and straightforward, just find them in your subscription and you are all set. Follow the publishing steps, and in a few minutes your app will be deployed.<\/p>\n

But what if you need to create new resources, how do you decide what resources to create? It all depends on you and your app, there is no right or wrong answer. Since the publishing steps are pretty much the same, let\u2019s look at some of the capabilities of each hosting option:<\/p>\n\n\n\n\n\n
\"Virtual<\/a><\/td>\n\"\"<\/a><\/td>\n\"Service<\/a><\/td>\n\"Docker<\/a><\/td>\n<\/tr>\n
Virtual Machines<\/a><\/span><\/td>\nApp Service<\/a><\/span><\/td>\nService Fabric<\/a><\/span><\/td>\nDocker & Containers<\/a><\/span><\/td>\n<\/tr>\n
\n
    \n
  • Infrastructure as a Service (IaaS)<\/span><\/li>\n
  • Supporting Linux and Windows VM\u2019s<\/span><\/li>\n
  • Quickly move existing applications to the cloud, because you have full control over the configuration of the Virtual Machine<\/span><\/li>\n
  • See how to deploy your app to a Virtual Machine at: aka.ms\/deployvm<\/a><\/span><\/li>\n<\/ul>\n<\/td>\n
\n
    \n
  • Platform as a Service (PaaS)<\/span><\/li>\n
  • Supporting Linux and Windows OS\u2019s<\/span><\/li>\n
  • Unified development and management experiences eliminate the confusion of disparate services and providers, resulting in less navigation and lower overhead<\/span><\/li>\n
  • See how to deploy your app to App Services at: aka.ms\/deployappservice<\/a><\/span><\/li>\n<\/ul>\n<\/td>\n
\n\n