DEV Community: Emmanuel Akpadia

Deploying a Web App to Azure from VS Code Using Azure CLI, ARM Templates, and GitHub

Emmanuel Akpadia — Thu, 12 Jun 2025 01:59:48 +0000

🧭 Step 1: Introduction

Modern application development doesn’t end at writing code—it includes how you deploy, manage, and automate your infrastructure. In this article, you’ll learn how to deploy a web application to Azure App Service using a full local-to-cloud pipeline, powered by:

Azure CLI (from within VS Code) to manage resources

ARM templates to provision infrastructure as code

GitHub Actions for CI/CD automation

By the end of this guide, you’ll be able to:

✅ Provision an App Service and supporting resources using an ARM template;
✅ Deploy your app to Azure;
✅ Automate future deployments with GitHub Actions;
using the command line in VS Code

Use Case: This guide is ideal for solo developers, small teams, or DevOps engineers who want fast, consistent deployments using tools they already use—like Visual Studio Code and GitHub.

Benefits: complete local-to-cloud workflow, repeatable deployments, automation using Infrastructure as Code (IaC) and GitHub Actions.

🧰 Step 2: Prerequisites

Before diving into deploying your web app, make sure you have the following tools and accounts set up:
✅ Tools Installed

VS Code Download VS Code
Azure CLI Install Azure CLI
Azure Account Extension for VS Code
Git Install Git
GitHub account
Azure subscription

🛠 Step 3: Project Setup in VS Code

In this step, we set up our local directory and connect it to our remote repository (Github)

🛠3.1:

Unzip the Free website template from Themewagon to your DevOps folder.
Open VS Code and navigate to the edit panel, open your folder

Doing this sets the folder as our working directory in VS Code Terminal.

🛠3.2: Push Project to GitHub

Next we create a new GitHub repository for our webapp. Go to GitHub, login then click on the Green button on the top left hand corner that says New

After creating the repo, we go back to VS Code Terminal to connect our local repo to GitHub.
We would need to initilize the folder (i.e tell Git to track changes in the folder) then add the files to our commit.

Run

git init
git add .
git commit -m "first website commit"

Then

git remote add origin https://github.com/Emmanuelakpadia/emzeeviolino-website.git
git push -u origin master

| ⛔️ Note: The link is gotten from your github repo.

Step 4: ARM Templates

In our current working directory we can create a folder for our ARM templates.

In terminal, Run

mkdir az-templates && cd az-templates
touch template.json && touch parameters.json

This creates a folder within our working directory and creates the .json files we need to deploy our WebApp.

Open the templates.json file and paste

{
    "$schema": "https://schema.management.azure.com/schemas/2019-04-01/deploymentTemplate.json#",
    "contentVersion": "1.0.0.0",
    "resources": [
      {
        "type": "Microsoft.Web/serverfarms",
        "apiVersion": "2021-01-15",
        "name": "[parameters('appServicePlanName')]",
        "location": "[resourceGroup().location]",
        "sku": {
          "name": "F1",
          "tier": "Free",
          "size": "F1",
          "family": "F",
          "capacity": 1
        }
      },
      {
        "type": "Microsoft.Web/sites",
        "apiVersion": "2021-01-15",
        "name": "[parameters('webAppName')]",
        "location": "[resourceGroup().location]",
      "dependsOn": [
          "[resourceId('Microsoft.Web/serverfarms', parameters('appServicePlanName'))]"
        ],
        "properties": {
          "serverFarmId": "[resourceId('Microsoft.Web/serverfarms', parameters('appServicePlanName'))]",
          "siteConfig": {
            "appSettings": [
              {
                "name": "SCM_DO_BUILD_DURING_DEPLOYMENT",
                "value": "true"
              }
            ]
          }
        }
      }
    ],
    "parameters": {
      "appServicePlanName": {
        "type": "string"
      },
      "webAppName": {
        "type": "string"
      }
    }
  }

Also open the parameters.json and paste

{
  "$schema": "https://schema.management.azure.com/schemas/2019-04-01/deploymentParameters.json#",
  "contentVersion": "1.0.0.0",
  "parameters": {
    "appServicePlanName": {
      "value": "myAppServicePlan"
    },
    "webAppName": {
      "value": "<insert your webapp name>"
    }
  }
}

| ⛔️ Note: make sure you edit the WebApp name and press Ctrl + S to save the code to the files.

🚀 Step 5: Use Azure CLI to Deploy the ARM Template

Now that we’ve set up our app and infrastructure template in VS Code, it’s time to deploy our resources to Azure using Azure CLI—all from the terminal inside the editor.

🚀5.1: Log In to Azure

In your VS Code terminal, run:

az login

This will open a browser window for you to sign in to your Azure account. Once authenticated, the terminal will return information about your subscriptions.

If you have more than one subscription, set the desired one as default:

az account set --subscription "<YOUR_SUBSCRIPTION_NAME_OR_ID>"

🚀5.2: Create a Resource Group

A resource group is a container for all related Azure resources.

Run this to create one:

az group create -n mywebrg -l westus

|💡 You can choose a different region by replacing westus with your preferred Azure region.

5.3: Deploy the ARM Template

Next, deploy the template.json template to the resource group.

az deployment group create --resource-group mywebrg --template-file template.json --parameters parameters.json

| ⏳ This may take a minute or two. Once done, you’ll see a JSON response confirming the resources were created.

🚀5.3: Deploy the WebApp

Run

az webapp deployment source config \
  --name emzeeviolino-website \
  --resource-group mywebrg \
  --repo-url https://github.com/Emmanuelakpadia/emzeeviolino-website \
  --branch master \
  --manual-integration

🌍 Step 6: Visit Your Web App

To get the URL of our deployed WebApp, we run

az webapp show \
--name emzeeviolino-web \
--resource group mywebrg \
--query defaultHostName \
--output tsv

🎉 That’s it! You now have:

✅ A web app deployed on Azure
✅ Infrastructure managed via ARM templates
✅ A full local-to-cloud pipeline built in VS Code

🔧 Errors encountered

No file or directory found when deploying ARM templates.

Fix: Check to see if the directory is correct.

Error when deploying ARM Templates

Fix: Honestly, the error goes away when you run the command a second time

A Simple Guide to Creating Azure Virtual Networks and Subnets.

Emmanuel Akpadia — Fri, 30 May 2025 18:34:16 +0000

A Simple Guide to Creating Azure Virtual Networks and Subnets.

Your company, Oasis IT group is migrating their on-premises infrastructure to the cloud. To begin the whole process, you are tasked with creating a Virtual Network and Subnets for each of the four departments. The given IP address is 192.152.50.0/24 and the subnet size is /28.

First, go to portal.azure.com, search for Virtual Networks and create one.

Create a new Resource group — RG1
Name the Virtual Network — OasisVN
Select the region

Next configure the IP addresses.

For this exercise, we would create 3 subnets while deploying the virtual network and the last one after.

Type in the chosen IP Address, It automatically indicates how many address the network can contain.
Select the prefix.
Edit the default subnet for the first department.

The first subnet is for the Operations Department.
The starting address is by default the network ID for the subnet.
The /28 size determines how many addresses are can be contained in the subnet.

save and repeat the process for the next 2 subnets.

Note: The subnet ranges are unique in every address space (i.e no two subnets can overlap)

Next, click on Review+create, and deploy the Virtual Network.

After the resource has been deployed successfully, click on go to resource.

On the overview page, Go to Settings>Subnets

Then click on +Subnet.

Configure the subnet settings and save.

And that’s how to create and configure a simple Virtual Network and subnets.

A Simple Guide to Creating Azure Virtual Networks and Subnets.

Emmanuel Akpadia — Fri, 30 May 2025 18:34:16 +0000

A Simple Guide to Creating Azure Virtual Networks and Subnets.

First, go to portal.azure.com, search for Virtual Networks and create one.

Create a new Resource group — RG1
Name the Virtual Network — OasisVN
Select the region

Next configure the IP addresses.

For this exercise, we would create 3 subnets while deploying the virtual network and the last one after.

Type in the chosen IP Address, It automatically indicates how many address the network can contain.
Select the prefix.
Edit the default subnet for the first department.

The first subnet is for the Operations Department.
The starting address is by default the network ID for the subnet.
The /28 size determines how many addresses are can be contained in the subnet.

save and repeat the process for the next 2 subnets.

Note: The subnet ranges are unique in every address space (i.e no two subnets can overlap)

Next, click on Review+create, and deploy the Virtual Network.

After the resource has been deployed successfully, click on go to resource.

On the overview page, Go to Settings>Subnets

Then click on +Subnet.

Configure the subnet settings and save.

And that’s how to create and configure a simple Virtual Network and subnets.

Azure App Services: Deploy a WebApp with CI/CD Pipelines

Emmanuel Akpadia — Wed, 14 May 2025 00:28:43 +0000

Azure App Service is a fully managed platform as a service (PaaS) that lets you run web applications, mobile back ends, and RESTful APIs.
App Service can run on Linux and Windows and supports a number of web stacks, including Node.js, PHP, Java, and .NET. Or, if your app is containerized, you can just deploy it as a custom container.

We will be deploying a sample website using Azure App Services, GitHub and Git via Visual Studio Code. The sample website can be gotten from Themewagon.
Unzip the downloaded file from Themewagon to a location on your PC.

Step 1: GitHub

Create a new repository in GitHub

Step 2: Git

In the Visual Studio Code app, open the folder where you unzipped the sample folder to.
Next, open the terminal; the folder opens as the default directory in the VS Code terminal

First, we initialize Git. (Ask Git to track changes in this folder.)

$ git init

Next, we add all the files in the folder to the staging area

$ git add .

Then create a commit using $ git commit -m "my first website commit"

We check the status of the commit using

$ git status

Next, we go to our GitHub page to copy the next command to link our Git to our remote repository on GitHub.

Lastly, we push our code to GitHub.

$ git push -u origin master

Step 3: Azure App Services

To host our WebApp on Azure App Service, we need to create an App Service Plan first.

First, create a new resource group (1) and a name for the App Service plan (2).
Then select a region (3) and pricing plan (4), then review and create the resource.

Now we can create the App Service.

Search for App Services on the Azure portal and open it, then click on Create > WebApp.

First, we select the resource group (1) and create a name for our WebApp (2).
The runtime stack we are selecting is PHP 8.4 (3), and we select the same region (4) as our App Service plan. The pricing plan automatically changes to our app service plan.
Next, review and create.

Once the resource is deployed, go to the overview page.

A default domain is created for our web app. If you copy and paste the address to a new tab and load it, a default PHP page will show, awaiting your deployment.

Step 4: Connect Azure WebApp to Remote Repo (Github)

On the overview page, select Deployment Centre (1).
Then select the remote repository source (2). Sign in and authorize your GitHub account (3), then select the organisation (4), repository (5) and branch hosting the sample website code (6).
Next, select Add a workflow (7), which uses the Azure default deployment workflow.
Then save.

A build/deploy log starts running.

On the GitHub platform, the workflow starts running.

The deployment gets completed after a few minutes.

If we reload the PHP default page, our content will be running.

Git & Github: Quick Setup Guide

Emmanuel Akpadia — Mon, 12 May 2025 03:20:00 +0000

What is Git

Git is a version control system that allows multiple developers in a team collaborate on a project in real time, by tracking changes to source codes.

Key Git Concepts

Repository - A folder where Git stores your project's code and its history of changes. It can be stored Locally or Remotely.
Clones - A copy of a remote repository on your computer.
Pull - Getting the lates changes from a remote repository.
Push - Saving your changes to a remote repository.
Commit - A snapshot of changes made to the repository.
Branch - A parallel version of the repository.
Merge - Combining changes from different branches.

What is Github

GitHub is a cloud-based platform based on Git, which hosts code repositories and helps developers collaborate.

Setting up Git

Git can be downloaded from git-scm.com

For windows: Simply download and run the installer to install Git and Gitbash
For MacOS: Open terminal and run $ brew install wget to install brew, then run $ brew install git.

Configuring Git

Git requires your Username and email address to label your commits.
To add Username, run

$ git config --global user.name "Username"

To add Email Address

$ git config --global user.email "email@example.com"

Creating a Repository

using terminal on MacOS, or Git bash on Windows, create a directory for your project.

$ mkdir git-lab

Change the working directory to the one we just created.

$ cd git-lab

Initialize Git

To create our Repository in this directory, run

$ git init

A simple Html file can be created via the notepad or using the terminal.

$ touch index.html

To quickly add text to the html file

$ echo "this is an index file for my first repo" > index.html

Then we check the status of our file

$ git status

At this point, it is untracked. This means it is present in our folder, but it's absent from the staging area.

So we need to tell Git to track our file.

$ git add index.html

or git add -all , git add -A or git add . to add all the files in the directory.

To unstage a file

git restore --staged index.html

Then check the status.

Commit

To save the staged file(s)

$ git commit -m "My first commit"

To see previous commit history,

$ git log

Branches

If we wanted to add changes to our project without affecting the main project, we create a branch.

$ git branch "parallel-repo"

To see all branches

$ git branch

To switch between branches

$ git checkout parallel-repo

To delete a branch

$ git branch -d parallel-repo

Merging

To combine changes from one branch into another, first switch to the branch you want to merge into(main or master)

$ git checkout main

Now we merge

$ git merge parallel-repo

Creating a Remote Repo

Go to github.com and create a new repository.

Copy git remote add origin https://github.com/username/repository.git, then paste in terminal and run.

Finally run,

$ git push -u origin main

Git would ask to authorize Github, then the local commit gets pushed to the Github repository.

A Simple Guide to Creating Azure Virtual Networks and Subnets.

Emmanuel Akpadia — Mon, 12 May 2025 00:29:11 +0000

First, go to portal.azure.com, search for Virtual Networks and create one.

Create a new Resource group — RG1
Name the Virtual Network — OasisVN
Select the region

Next configure the IP addresses.

For this exercise, we would create 3 subnets while deploying the virtual network and the last one after.

Type in the chosen IP Address, It automatically indicates how many address the network can contain.
Select the prefix.
Edit the default subnet for the first department.

The first subnet is for the Operations Department.
The starting address is by default the network ID for the subnet.
The /28 size determines how many addresses are can be contained in the subnet.

save and repeat the process for the next 2 subnets.

Note: The subnet ranges are unique in every address space (i.e no two subnets can overlap)

Next, click on Review+create, and deploy the Virtual Network.

After the resource has been deployed successfully, click on go to resource.

On the overview page, Go to Settings>Subnets

Then click on +Subnet.

Configure the subnet settings and save.

And that’s how to create and configure a simple Virtual Network and subnets.

A Simple Guide to Hosting a Static Website on Azure Blob Storage.

Emmanuel Akpadia — Mon, 12 May 2025 00:28:03 +0000

Azure blob storage is an object storage solution for the cloud that stores unstructured data such as text, binary data, images e.t.c. We’re going to be utilising it to host a static website.

A website template would be needed for this exercise, you can download one at **themewagon.com**.

Unzip the contents of the downloaded template and do the necessary edits.

Then on the Azure portal search for Storage accounts and click create.

On the basics tab,

Create a new resource group or select an existing one.
Name the storage account, which must be globally unique.
Select a region to deploy the resource to.
Configure the redundancy.
Then click review+create.

After the successful deployment of the resource, click go to resource.

On the overview page, click on capabilities, then Static website.

click on enable to show the options.
Match the index document name to your index.html doc for your website
Same goes for the error document path.
Click on save, A storage container $web will be created to host your website, and a primary endpoint would be assigned.
Copy the endpoint address.

Open a new browser tab, paste the address and click enter.

Note that when you try to access the endpoint address, you get an error, because the website template has not been uploaded to the $web container.

On the Storage account, go to Data storage>containers. Click on the $web container to open it.

Click upload, a sidebar opens.
Open your file explorer to the directory of the website template.
Drag all the files and folders into the sidebar and click upload.

Confirm all the files are correctly uploaded, then reload the tab with the endpoint address. It should load your content.

A Simple Guide to Deploying Azure Virtual Machine Scale Sets (VMSS)

Emmanuel Akpadia — Mon, 12 May 2025 00:24:15 +0000

Azure Virtual Machine Scale Sets are a group of load balanced VM instances that can be easily scaled up or down in response to demand or a defined schedule.

Scale sets can be deployed with Windows server image or Linux image. But for this tutorial, we’d be deploying a Linux based VMSS via the Azure portal.

Step1: On the Azure portal, search for Virtual Machine Scale Sets and select it.

Step2: On the VMSS page click create, the basics tab page shows up.

Create a new resource group for the VMSS
Create a name for the scale set.
Select a region close to you.
Availability zone: none
Orchestration mode: Uniform (create identical VMs when scaling)
Security type: Standard
Scaling mode: Manual
Instance count: 2

Then Click on configure scaling options

On the scaling configuration page, Enable forecast for predictive autoscaling.

Select Newest VM as the option for deletion in the scale in policy. Then save. This implies that the newest VM created would be the first to be deleted when scaling down.

Close and return to the basics tab.

Step 3: Configure the VM

Select the server image
Select the VM size
Authentication type: SSH public key
Set an Admin Username for logging into the VMs
SSH public key source: Generate new key pair
SSH key type: RSA SSH Format
Name the key pair that would be generated.

Then go to the next tab. We could skip the spot and disk tabs and head on to the networking tab.

By default, A virtual network and subset is already set, but we need to configure the network Interface of the VMSS to allow SSH and HTTP connections.

Click on the pencil icon highlighted in the image below.

The Edit network interface page opens,

Click on Allow selected ports for Public Inbound ports, then select the ports you want, In this case HTTP(80) and SSH(22).

Make sure the Public IP address is also enabled to facilitate connection via SSH to the VMSS, then save.

Next we configure load balancing for the VMSS.

First select Azure load balancer, then create a load balancer.

A side pane opens on the right,

We name the load balancer, and then click create.

Next, review and create.

After validation is passed, we are prompted to download a key pair before the resource is created. Click on it to continue.

When the resource is successfully deployed, click go to resource.

On the overview page, we can now see that 2 uniform VM instances have been deployed and a public IP address also assigned.

We can choose to either connect to the VMs in our scale set individually or manage them as a whole.

In this tutorial, the latter would be the case.

To do this, we locate our downloaded key pair file and copy the file path.

Then set the file permission to read only on mac using **chmod 400 , **via the terminal app. This is not required on Windows.

Then we can now connect the VMSS backend via SSH but we have to specify the frontend port range from when we created the load balancer for the VMSS.

Run the command*** ssh -i username@IPaddress -p , ***then type yes. The VMSS connects successfully.

Any updates or installations made whilst connected now would affect all VM instances running in the scale set, which makes it very easy to manage the Virtual machine scale set.

Thanks for your read.

A Simple Guide to Creating & Connecting to a Linux VM on Azure

Emmanuel Akpadia — Mon, 12 May 2025 00:23:22 +0000

First, you want to log on to your azure portal @portal.azure.com

Then search for the virtual machine resource using the search bar

Clicking on the first result opens up the Virtual Machines page, where we can create and manage our VMs.

Next, (1) Click create, then (2) Azure VM

A new page opens up with options for creating our VM

Create a new resource group for the VM.
Give the VM a name.
Select the desired region to deploy the VM.
Select the availability option, In this case no redundancy is required.
Select the security type — standard
Then select the image for the VM. Ubuntu is the choice of linux image for this VM.

Scrolling down,

Select the size of the VM based on computing demands.
The authentication type is set to SSH public key.
The username for the Administrator account is set.
select Generate a new key pair
Name the key pair.

Then click review and create.

The other settings are automatically managed when we skip them.

After the machine is successfully validated, go ahead to create the VM.

A pop-up would appear, click “download the private key and create the resource.”

The private key is then downloaded and the resource is deployed. It took less than a minute to do so, which is also dependent on the size of the resource.

Click Go to resource and copy the public IP address.

Go to your downloads folder to see the downloaded private key.

On a windows device, proceed to opening the VM via powershell or command prompt using ssh -i filepath administratorusername@IPaddress.

On a mac device, you need to set a read-only permission for the file for it to be accessible and avoid errors whilst trying to access it via terminal.

To do this, first copy the file path name, (right click on the file name and hold option, the option would then appear)

Then open the Terminal app, run the command chmod 400 “filepath.pem”

Then proceed to connect to the VM using the Linux key using ssh -i filepath administratorusername@IPaddress.

Press Enter to run, and yes to connect to the VM

The VM would then open.

Cheers!

Easy Steps to Deploying Windows 11 VM on Microsoft Azure

Emmanuel Akpadia — Mon, 12 May 2025 00:21:23 +0000

Easy Steps to Deploying Windows 11 VM on Microsoft Azure

Deploying A VM on Azure has to be one of the most seamless ways to get a VM in modern times and I’ll be showing you how to do so in no time.

First, log on to the Azure portal at portal.azure.com

Then, search for virtual machine resource from the search bar.

This would open the virtual machines page, select create, then Azure virtual machine.

By default, for free Azure accounts, a subscription would already be active, You can then go ahead and create a new resource group or select an existing one.

Then name your VM, select a region, and availability option based on vertical or horizontal redundancy requirements for your VM. If the VM doesn’t need one, No Infrastructure redundancy require is selected. The security type is set to standard.

For accounts using free subscriptions, some images won’t be available to you. I’m also on the free account, the image available is Windows 11 Enterprise, click on see all images

Then click on select, and select the image.

The VM architecture is set to x64 by default, since ARM64 is primarily used in mobile and embedded devices, while x64 (or x86–64) is dominant in desktop and server PCs.

Then VM size is selected based on workload type and usage, which in turn affects the cost of running it.

An administrator account must be created for the VM, which would be used to access the VM once it’s deployed. Next is the Disk options.

By default, these are already setup for optimal performances, but can be modified to taste.

Next is the Networking options, A virtual network is created by default, but the Public IP address might need to be modified to be dynamic as shown in the image below. Click on create new under the Public IP option.

From here, you can simply click review + create to continue with this case of a simple VM.

The VM settings are then checked and validated.

Once validation is passed, you get this overview page of all your settings before proceeding to create the VM.

Once the Deployment is complete, click go to resource.

This overview page opens, click connect to connect to the VM.

Then download the RDP file.

Open the RDP file from your downloads folder.

On windows, the RDP file opens in The Remote Desktop App by default.

But on MacOS, I had to install the new Windows App, which opens the Remote desktop tool once I open the RDP file.

A connection is established to the VM, then It asks for the Admin credentials we created whilst creating the VM.

The VM then opens successfully.

And that’s how to successfully deploy a Windows 11 VM on Microsoft Azure.

The Core Architectural Components of Azure

Emmanuel Akpadia — Mon, 12 May 2025 00:18:02 +0000

The Core Architectural Components of Azure

Azure, Microsoft’s cloud computing platform, comprises several core architectural components that work together to provide a wide range of services. It’s key components are:

Regions and Availability Zones:

Regions: Geographically distinct locations that contain multiple data centers and are designed to be isolated from each other to ensure fault tolerance and stability.

Availability Zones: Physically separate data centers within an Azure region that are designed to be isolated from failures in other zone thereby providing high availability and redundancy.

2. Resource Groups:

Logical containers used to group related resources (e.g., VMs, storage accounts, networks) for easier management, monitoring, and billing.

3. Azure Resource Manager (ARM):

The management layer that handles deployment, management and organisation of resources using templates and policies.

4. Compute Services:

Virtual Machines (VMs): scalable computing resources for running workloads.
Azure Kubernetes Service (AKS): Managed Kubernetes service for containerrized applications.
Azure Functions: Serverless compute service for running event-driven code.
App Services: Platform-as-a-Service (PaaS) for hosting web apps and APIs.

5. Storage Services:

Blob Storage: Object storage for unstructured data like text and binary data.
File Storage: Managed file shares for cloud or on-premises deployments.
Disk Storage: Persistent, high-performance disk storage for VMs.
Queue Storage: Messaging store for reliable messaging between application components.

6. Networking:

Virtual Network (VNet): Isolated, private networks in Azure.
Load Balancer: Distributes incoming network traffic across multiple VMs.
Application Gateway: Web traffic load balancer with additional features like SSL termination and web application firewall (WAF).
Azure DNS: Hosting service for DNS domains.
Content Delivery Network (CDN): Global CDN for delivering high-bandwidth content.

7. Databases:

Azure SQL Database: Managed relational database service.
Cosmos DB: Globally distributed, multi-model database service.
Azure Database for MySQL/PostgreSQL: Managed database services for MySQL and PostgreSQL.

8. Identity and Access Management (IAM):

Azure Active Directory (AAD): Cloud-based identity and access management service.
Role-Based Access Control (RBAC): Fine-grained access management for Azure resources.

9. Security and Compliance:

Azure Security Center: Unified security management and advanced threat protection.
Azure Key Vault: Secure storage for secrets, keys, and certificates.
Azure Policy: Service to create, assign, and manage policies for resource compliance.

10. Monitoring and Management:

Azure Monitor: Comprehensive monitoring solution for collecting, analyzing, and acting on telemetry data.
Azure Automation: Service for automating repetitive tasks and configurations.
Azure Advisor: Personalized recommendations to optimize Azure resources.

11. Developer Tools:

Azure DevOps: Services for CI/CD, version control, and agile planning.
Visual Studio Team Services: Cloud-based version of Visual Studio for development and collaboration.

12. AI and Machine Learning:

Azure Machine Learning: Cloud-based environment for training, deploying, and managing machine learning models.
Cognitive Services: APIs for adding AI capabilities like vision, speech, and language understanding.

13. Internet of Things (IoT):

Azure IoT Hub: Central message hub for bi-directional communication between IoT applications and devices.
Azure IoT Central: Fully managed IoT SaaS solution for connecting and managing IoT devices.

14.Integration Services:

Azure Logic Apps: Service for automating workflows and integrating apps, data, and services.
Service Bus: Messaging service for connecting applications and services.

These components collectively enable Azure to provide a robust, scalable, and secure cloud computing environment for a wide range of applications and services.