1. Azure's core components
In this video, we'll explore core components that form the foundation of Microsoft Azure.
2. Resources
As a user, when you purchase a service on Azure, whether it is web hosting, a virtual machine, or a database, you are purchasing what is referred to as a Resource. It is a generic object in a JSON template that represents a service you have purchased and remains available for the lifecycle of the service.
3. Resources
If you’re unfamiliar with JSON, it is a standard-text-based format for representing structured data in JavaScript. It’s commonly used for transmitting data.
A resource contains all the configuration properties needed to deploy your service. All resources contain four common properties: type, API version, name, and location. Depending on the service, additional configuration options will be available.
4. Resource groups
However, a resource cannot be created without a resource group. Resource Groups are logical groupings that hold related resources for an application. Think of Azure Resource Groups as a drawer in a filing cabinet where you organize related files. Similarly, Resource Groups are used to group related resources sharing the same life-cycle, permissions, and policies.
5. Resource groups
Consider a web app with an attached SQL database. To jointly manage, monitor, and maintain them, simply group them in the same Azure Resource Group.
You can use resource groups to control access and organize your resources after you have deployed to Azure.
You can group your resources in different ways, including by service type, application lifecycle, department, location, etc. No one policy fits all; many organizations adopt a combination of these to suit their specific needs.
6. Azure Resource Manager (ARM)
You can use many methods to purchase Azure services, most commonly through the portal. No matter which method you choose to purchase Azure, it all goes through the Azure Resource Manager. It’s a centralized management layer for all resources and resource groups in Azure using a unified language. The resource manager checks privileges against Azure ActiveDirectory anytime a user wants to create, manage, or delete a resource.
Azure AD is Microsoft's cloud-based identity and access management service that enables employees to securely sign in and access applications. Think of it as a digital club bouncer verifying your ID and only enabling those authorized individuals into the “digital club”. It easily integrates with the on-premises Active Directory to extend its capabilities.
7. Core offering
Now that we’ve identified how resources work let’s dive into some of Azure’s core offerings. Core services include Compute, Storage, Networking, and Databases.
8. Compute
Compute refers to a category of services that enable you to provision and manage cloud resources like the infrastructure needed to run your application without the need to manage the physical hardware.
Azure Compute has a variety of offerings, including Virtual Machines, Container Instances, Kubernetes Services, and more.
9. Storage
Storage is the managed service in Azure responsible for providing a range of readily available cloud storage solutions depending on the use case, from virtual machine images down to multimedia files.
Azure Storage has a variety of offerings, including Azure Data Lake Storage, Azure Files, Azure Blob Storage, and more.
10. Networking
Networking in Azure is all about connecting different resources, whether that be within the Azure Platform or on-premise networks. Azure networking is your digital highway, connecting different parts of your cloud environment just as roads connect places.
Azure Networking has a variety of offerings, including a Content Delivery Network, Virtual Network Manager, VPN Gateway, and more.
11. Databases
Lastly, we’ll cover Databases in Azure. These are powerful tools for storing structured and semi-structured data by providing a central repository to quickly retrieve and manage your data.
Azure Databases has a variety of offerings, including Cosmos DB, SQL Database, SQL Managed Instance, and more.
12. Let's practice!
Now, let's practice what you've learned.