Get started with Azure and .NET
This document provides an overview of key concepts and services .NET developers should be familar with to get started developing apps using Azure services.
Azure subscription: A subscription is the billing plan within which Azure resources are created. Subscriptions can be individual subscriptions or enterprise subscriptions managed by your company. Your Azure account can be associated with multiple subscriptions. In this case, make sure you're selecting the correct subscription when creating resources. For more information, see Understanding accounts, subscriptions and billing.
If you have a Visual Studio subscription, you have monthly Azure credits waiting to be activated.
Resource group: Resource groups are a way to organize your Azure resources into groups for management. Resources created in Azure will be stored in a resource group, similar to saving a file in a folder on a computer.
Hosting: To run code in Azure, it needs to be hosted in a service that supports executing user-provided code.
Managed services: Azure provides some services where you provide data or information to Azure, and Azure's implementation takes the appropriate action. One example is Azure Blob Storage, where you provide files and Azure handles reading, writing, and persisting them.
Choosing a hosting option
Hosting in Azure can be divided into three categories.
Infrastructure-as-a-Service (IaaS): With IaaS, you provision the virtual machines you need along with associated network and storage components. You then deploy whatever software and applications you want onto those VMs. This model is the closest to a traditional on-premises environment except that Microsoft manages the infrastructure. You still manage the individual VMs, including the operating system, custom software, and security updates.
Platform-as-a-Service (PaaS): PaaS provides a managed hosting environment where you deploy your application without needing to manage VMs or networking resources. For example, instead of creating individual VMs, you specify an instance count, and the service will provision, configure, and manage the necessary resources. Azure App Service is an example of a PaaS service.
Functions-as-a-Service (FaaS): Commonly referred to as serverless computing, FaaS goes even further than PaaS in abstracting the concerns of the hosting environment. Instead of creating compute instances and then deploying code to those instances, you deploy your code and the service automatically runs it. You don't need to administer the compute resources. The platform seamlessly scales your code up or down to whatever level necessary to handle the traffic, and you pay only when your code is running. Azure Functions is a FaaS service.
Generally, the more your application favors FaaS and PaaS models, the more benefits you'll see from running in the cloud. Below is a summary of three common hosting choices in Azure and when to choose them.
Azure App Service: If you're looking to host a web application or service, look at App Service first. To get started with App Service and ASP.NET, WCF, and ASP.NET Core apps, see Create an ASP.NET Core web app in Azure.
Azure Functions: Azure Functions is great for event-driven workflows. Examples include responding to webhooks, processing items in queues or blob storage, and timers. To get started with Azure Functions, see Create your first function using Visual Studio.
Azure Virtual Machines: If App Service doesn't meet your needs for hosting an existing application due to specific dependencies, Virtual Machines will be the easiest place to start. To get started with Virtual Machines and ASP.NET or WCF, see Deploy an ASP.NET app to an Azure virtual machine.
Choosing a data storage service
Azure offers several services for storing your data depending on your needs. The most common data services for .NET developers are:
Azure SQL Database: If you're looking to migrate an application that is already using SQL Server to the cloud, Azure SQL Database is a natural place to start. To get started, see Tutorial: Build an ASP.NET app in Azure with SQL Database.
Azure Cosmos DB: Azure Cosmos DB is a modern database designed for the cloud. When starting a new application that doesn't yet have a specific database dependency, you should look at Azure Cosmos DB. Cosmos DB is a good choice for new web, mobile, gaming, and IoT applications where automatic scale, predictable performance, fast response times, and the ability to query schema-free data are important. To get started, see Quickstart: Build a .NET web app with Azure Cosmos DB using the SQL API and the Azure portal.
Azure Blob Storage: Azure Blob Storage is optimized for storing and retrieving large binary objects, such as images, files, and streams. Object stores enable the management of extremely large amounts of unstructured data. To get started, see Quickstart: Use .NET to create a blob in object storage.
For more information, see Choose the right data store.
Diagnosing problems in the Cloud
Once you deploy your application to Azure, you may run into cases where it worked in development but doesn't in Azure. Below are two good places to start when diagnosing issues:
Remote debug from Visual Studio: Most Azure compute services (including the services discussed in this document) support remote debugging with Visual Studio and acquiring logs. To explore Visual Studio's capabilities with your application, open the Cloud Explorer tool window by typing 'Cloud Explorer' into Visual Studio's quick launch toolbar (in the upper-right corner), and then locate your application in the tree. For details, see Troubleshoot a web app in Azure App Service using Visual Studio.
Application Insights: Application Insights is a complete application performance monitoring (APM) solution that captures diagnostic data, telemetry, and performance data from applications automatically. To get started collecting diagnostic data for your app, see Start monitoring your ASP.NET Web Application.