This document discusses different options for hosting web applications in Microsoft Azure, including Azure Websites, Virtual Machines, and Cloud Services. It provides details on Azure Websites, such as automatic scaling, free hosting options with shared resources, and paid hosting plans with dedicated resources and more capabilities. It also covers authentication methods, managing Azure subscriptions, and deploying web applications to Azure.

1. Nitesh Luharuka
Entrepreneur | Programmer | C# Corner MVP |
C# Corner Kolkata Chapter Lead
@niteshluharuka
http://www.niteshluharuka.com

2.  Hosting your application in Azure – Different Offerings
 Azure Websites
 Understanding Authentication
 Web Hosting Plans
 Deploy to Websites
 Configure your Website

3.  Azure Websites
 Virtual Machines
 Cloud Services

4.  Supports most popular web development frameworks (even
non-Microsoft ones!)
 Deploy using the tools you want to use
 Set it up in seconds … for free
 Scale up and out as needed, pay only for the amount you use

5.  Monitoring, logging, etc.
 Impervious to hardware failures

6.  Scott Guthrie: Choose Azure Websites 99% of the time
 Very little responsibility, and (relatively) less control
 You will not use Azure websites only if you have any special
requirement for your project where you need any specific
software installed on the server.

7.  You have total control, but you have all the responsibility

8.  The original cloud-based website hosting option from
Microsoft (aka “Web Role” and “Worker Role”)
 Remote desktop, MSI installers

9.  Benefits over VMs:
◦ Multiple deployment environments
◦ Automatic operating system update management
◦ Seamless platform switching between 32bit and 64bit
◦ You lose: deployment options
◦ Cannot use FTP
◦ Cannot deploy from Git/Web deploy etc.

11.  Create a website and publish to Azure

12.  Certificate based
 Credential based

13.  Manage Azure subscription
 Automate management of azure subscription using azure
service management API
 Use any tools that use Azure Services like Visual Studio &
Powershell
 Deploy a web application to azure

14.  Use Username & Password to Authenticate your Azure
Subscription

15.  Management Certificates
 Gives you access to revoke permissions in case of adhoc situations
like employee leaves an org or your private key is in bad hands
 Make sure who is owning the file is having the access to your azure
subscription
 Limit of maximum 100 certificates per subscription
 http://manage.windowsazure.com/publishsettings/index

17.  Similar to a traditional web hosting plan
 One Subscription can have one or more Website Plans
◦ Actually, a Subscription has one or more Resource Groups and each
Resource Group can have one or more Website Plans
◦ A resource group is intended to group all websites/storage
accounts/VMs that are part of same logical application

18.  Azure Websites deployed into the same Subscription,
Resource Group and Geographic Location can share a single
Web Hosting Plan.
 Each Azure Website sharing a Web Hosting Plan can leverage
all the capabilities in that plan

19.  Azure Websites deployed into the same Subscription,
Resource Group and Geographic Location can share a single
Web Hosting Plan.
 Each Azure Website sharing a Web Hosting Plan can leverage
all the capabilities in that plan
 In fact, they sit in the same “compute instance” meaning they
share the same set of resources
 Compute instance means a server for layman people

20.  Shared Instances
◦ Free Plan

21. Storage
Controller
IIS
Application
Request
Router
AzureLoadBalancer
Hosting
Sites DB
Site’s
Content DB
?

22. Storage
Controller
IIS
Application
Request
Router
AzureLoadBalancer
Hosting
Sites DB
Site’s
Content DB
?

23. Storage
Controller
IIS
Application
Request
Router
AzureLoadBalancer
Hosting
Sites DB
Site’s
Content DB

24. Storage
Controller
IIS
Application
Request
Router
AzureLoadBalancer
Hosting
Sites DB
Site’s
Content DB
Web Worker

25. Storage
Controller
IIS
Application
Request
Router
AzureLoadBalancer
Hosting
Sites DB
Site’s
Content DB
Web Worker

26. Storage
Controller
IIS
Application
Request
Router
AzureLoadBalancer
Hosting
Sites DB
Site’s
Content DB
Web Worker

27.  In free plan, your website is removed from the web worker
role if it not being used for sometime to free up resources
that can be used by other users.
 In Azure, if a machine fails the request router will go through
the provisioning process again and provision your website to
a new web worker role and your site is up again

28. Storage
Controller
IIS
Application
Request
Router
AzureLoadBalancer
Hosting
Sites DB
Site’s
Content DB

29. Storage
Controller
IIS
Application
Request
Router
AzureLoadBalancer
Hosting
Sites DB
Site’s
Content DB
Web Worker

30.  Shared Instances
◦ Free Plan
◦ Shared Plan – you are paying so you’re in a high density multi tenant
environment but fewer websites and more power/scaling/load
balancing etc…

31. Instances 1

32. Instances 2

34.  Shared Instances
◦ Free Plan
◦ Shared Plan
 Reserved Instances (reserved Dedicated compute instance,
doesn’t unload them from memory)
◦ Basic Plan
◦ Standard Plan

35.  Scale out to multiple DEDICATED compute instances
 SSL Certificates
 Web Sockets
 SLA 99.9%

36.  Scale out to up to 10 DEDICATED compute instances
 Backups
 Auto scale
 Azure Scheduler
 Staged Publishing

39.  Run code at scheduled time at a specific frequency
 Clean up log files or do some data processing
 3 ways –
◦ On a schedule (once a day/hour/minute/between period of date)
◦ Manually
◦ Run continuously
 Scaling up a website mean scaling up the Web Job as well

40.  Link VS with Azure account via VS accounts section on portal
 Publish using DEBUG configuration and not RELEASE
 Server Explorer > Websites > Select Website > Attach to
Process
 Bingo!!!!