DEV Community: samuel

Boost your Website's Performance: How to provide Seamless Storage for the Public

samuel — Sun, 30 Mar 2025 10:51:03 +0000

In today’s digital landscape, ensuring high availability for your website is crucial to providing a seamless user experience. One of the most effective ways to achieve this is through Azure’s Storage Accounts, which offer high availability and redundancy options. This guide will walk you through the process of creating a robust, publicly accessible storage solution for your website that supports images, documents, and other media files, even during a regional outage.

Step 1: Create a New Storage Account with High Availability
Start by Accessing the Azure Portal: Open the Azure Portal and search for Storage accounts. Click on + Create to begin the process.

Select Resource Group: Choose New for the resource group, and give it a unique name, such as "WebsiteResourceGroup". Click OK to continue.

Set Storage Account Name: Enter a unique storage account name, like “publicwebsite.” To ensure the name is available, you may need to add a random identifier to the end (e.g., "publicwebsite123").

Choose Default Settings: Accept the default settings for performance, replication, and security, but ensure the redundancy setting is configured for high availability.

Enable Read Access to the Secondary Region: In the Data management section, go to the Redundancy blade and select Read-access Geo-redundant storage (RA-GRS). This setting ensures that your data is replicated across regions, making it accessible even during a regional outage.

Finalize and Deploy: Review your settings and click Create. Wait for the deployment to finish and click Go to Resource.

Step 2: Enable Anonymous Blob Access for the Public Website
To make your website content accessible to everyone without requiring authentication:

Allow Blob Anonymous Access: In the storage account, navigate to the Settings section and select Configuration. Enable the Allow blob anonymous access setting and click Save.

Step 3: Create a Blob Storage Container for Website Content
Next, create a container to hold your website's files such as images and documents:

Navigate to Containers: In the Data storage section of the storage account, select Containers.

Create a New Container: Click + Container and name the container “public.” Make sure it’s set to Private (No anonymous access) initially.

Enable Public Access: After creating the container, select it, and on the Overview blade, click Change access level. Set the Public access level to Blob (anonymous read access for blobs only).

Save and Test Access: Test the public access by uploading a small file (e.g., an image or text file). Browse the file’s URL and confirm it opens or downloads correctly.

Step 4: Enable Soft Delete for Blobs
To protect your files from accidental deletion, enable the soft delete feature for blobs:

Navigate to Blob Soft Delete Settings: In the Properties section, under the Blob service category, select Blob soft delete.

Configure Retention Period: Ensure the Enable soft delete for blobs box is checked, and set the Keep deleted blobs for (in days) to 21 days. This ensures you can restore any files within 21 days if they are accidentally deleted.

Save Your Settings: Don’t forget to click Save after configuring these settings.

Step 5: Practice Restoring Deleted Files Using Soft Delete
Delete a File: Go to your public container, select a file, and click Delete.

Restore the File: After deletion, toggle the slider to Show deleted blobs. Select the deleted file and choose Undelete. This will restore the file back to the container.

Confirm Restoration: Refresh the container, and you should see the file has been restored.

Step 6: Enable Blob Versioning
To track different versions of your website documents, enable blob versioning:

Navigate to Blob Versioning Settings: In the Properties section of your storage account, go to Versioning under Blob service.

Enable Versioning: Check the Enable versioning for blobs box to ensure all versions of your documents are saved automatically. You can choose whether to keep all versions or delete older versions after a certain period.

Save Your Settings: Click Save to apply the versioning settings.

Step 7: Test Blob Versioning
Upload a New Version of a File: Upload a new version of an existing file in your container. This will overwrite the previous version.

Check Previous Versions: Go to the Show deleted blobs page, where you’ll see the old version listed. You can restore it if needed.

Conclusion
By following these steps, you've created a highly available, publicly accessible storage solution for your website that ensures high uptime, automatic redundancy, and protection against accidental deletions. You’ve also set up essential features such as soft delete and versioning to safeguard your website’s content. With these configurations, you can rest easy knowing your website’s files are safe, accessible, and ready to serve your users even in the event of a regional failure.

Mastering Azure: A Step-by-Step Guide to Creating a Storage Account

samuel — Wed, 26 Mar 2025 16:52:09 +0000

Azure provides a highly scalable and secure platform for storing data, and one of its most fundamental services is Azure Storage. Whether you are storing files, blobs, or data for your web and mobile applications, Azure Storage accounts provide a reliable and cost-effective solution. In this guide, we’ll walk you through the process of creating a storage account in Azure using both the Azure Portal and Azure CLI.

Prerequisites

Before creating an Azure Storage account, ensure that:

You have an active Azure subscription. If you don't have one, you can sign up for a free account here.
You have an Azure Active Directory (AD) account with the necessary permissions to create resources in the Azure subscription.

Step-by-Step Guide to Creating a Storage Account in Azure

Method 1: Using the Azure Portal

The Azure Portal offers a user-friendly graphical interface for managing Azure resources. Here’s how you can create a storage account using the Azure Portal:

Sign in to the Azure Portal:
- Visit portal.azure.com and log in with your Azure account credentials.

Navigate to Storage Accounts:
- In the left sidebar, click on “Create a resource.”
- In the search box, type “Storage Account” and select “Storage Account” from the list of options.

Configure the Storage Account:
- Subscription: Choose the Azure subscription you want to use.
- Resource Group: Either select an existing resource group or create a new one by clicking on “Create new.”
- Storage Account Name: Choose a unique name for your storage account. This name must be between 3 and 24 characters and can contain only lowercase letters and numbers.
- Region: Select the Azure region where the storage account will be created. Choose a region close to your users to reduce latency.
- Performance: You can choose between two performance tiers:
  - Standard: Best for most workloads and offers cost-effective performance.
  - Premium: Designed for high-performance workloads with lower latency.
- Account Kind: You can select from several account types based on your needs:
  - StorageV2 (general-purpose v2): Most versatile, supports blob, file, and table storage.
  - BlobStorage: Optimized for storing large amounts of unstructured data, such as text and binary data.
  - General-purpose v1: Older version, not recommended for new workloads.
- Replication: Choose how your data will be replicated:
  - Locally redundant storage (LRS): Data is replicated three times within a region.
  - Geo-redundant storage (GRS): Data is replicated across regions for higher availability.
  - Read-access geo-redundant storage (RA-GRS): Same as GRS but allows read access to the secondary region.

Advanced Settings (Optional):
- You can configure additional settings such as networking, access control, and encryption. For most users, the default options are sufficient.
Review + Create:
- After configuring your storage account, click “Review + Create.” Azure will validate the settings you’ve chosen.
- If everything looks good, click “Create” to start the deployment process.

Wait for Deployment:
- It will take a few moments for Azure to create the storage account. Once the process is complete, you will be notified, and you can access your new storage account from the Storage Accounts section of the Azure Portal.

Method 2: Using Azure CLI

Azure CLI is a powerful tool for managing Azure resources via the command line. If you prefer automation or scripting, here’s how to create a storage account using Azure CLI.

Install Azure CLI:
- If you haven't already, install the Azure CLI on your system.
Sign in to Azure CLI:
- Open a terminal or command prompt and log in to your Azure account by typing:
```
 az login
```

(Make sure to follow the log in link)

Create a Resource Group (if necessary):
- If you don’t already have a resource group, create one with the following command:
```
 az group create --name MyResourceGroup --location eastus
```

Replace MyResourceGroup with your desired resource group name and eastus with your preferred region.

Create the Storage Account: - Run the following command to create a storage account:

 az storage account create --name mystorageaccount --resource-group MyResourceGroup --location eastus --sku Standard_LRS --kind StorageV2

Here’s a breakdown of the parameters:

--name mystorageaccount: Specify a unique name for your storage account.
--resource-group MyResourceGroup: The resource group where the storage account will be created.
--location eastus: The region where the storage account will reside.
--sku Standard_LRS: The replication type (Standard_LRS stands for locally redundant storage).
--kind StorageV2: Specifies the account type (StorageV2 is the most flexible).

Confirm Creation:
- After running the command, you should receive a JSON output with details about your storage account, including the resource ID and location.
Access Your Storage Account:
- To manage your storage account or list the storage account details, you can use commands like:
```
 az storage account show --name mystorageaccount --resource-group MyResourceGroup
```

Conclusion

Creating a storage account in Azure is a straightforward process, whether you prefer to use the Azure Portal for a graphical interface or Azure CLI for automation and scripting. Once your storage account is created, you can start using it to store various types of data, including blobs, files, queues, and tables, depending on your needs.

Azure Storage provides excellent scalability, reliability, and security, making it ideal for storing application data, backup solutions, and much more.

Effortless Azure VM Deployment and IIS Setup Using PowerShell in Cloud Shell

samuel — Wed, 26 Mar 2025 10:50:15 +0000

Azure Cloud Shell is a sophisticated tool that lets you manage Azure resources without having to set up a local development environment. It comes with all of the necessary Azure tools preinstalled and configured, making it easy for users to run scripts right from their browser. In this post, we'll go over how to construct a Windows Virtual Machine (VM) in Azure using PowerShell and Azure Cloud Shell. In addition, we will deploy a web server (IIS) on the virtual machine and clean up the resources after use.

Step 1: Launch Azure Cloud Shell

Azure Cloud Shell is a free browser-based shell that allows you to run Azure commands interactively. To begin, launch Cloud Shell by following these steps:

Open Cloud Shell: In the Azure portal, click the Cloud Shell symbol in the upper right corner of the page. If you're not in the portal, you can activate the Cloud Shell by visiting:(https://shell.azure.com/powershell).

Cloud Shell will launch with a preconfigured environment that is ready for use.

Step 2: Create an Azure Resource Group

A resource group is a container in Azure that holds related resources for an Azure solution. We will start by creating a resource group using the New-AzResourceGroup cmdlet. Here’s how you can do it:

New-AzResourceGroup -Name 'myResourceGroup' -Location 'eastus'

This command creates a new resource group named myResourceGroup in the East US region. You can change the name or location as per your requirements.

Step 3: Create a Virtual Machine

Now that we have a resource group, we can create a Windows Virtual Machine. The New-AzVM cmdlet allows you to create a virtual machine in Azure. It automatically handles the creation of other resources such as the network interface, virtual network, public IP, and more, as part of the VM creation process.

Run the following command to create a VM:

New-AzVm `
    -ResourceGroupName 'myResourceGroup' `
    -Name 'myVM' `
    -Location 'eastus' `
    -Image 'MicrosoftWindowsServer:WindowsServer:2022-datacenter-azure-edition:latest' `
    -VirtualNetworkName 'myVnet' `
    -SubnetName 'mySubnet' `
    -SecurityGroupName 'myNetworkSecurityGroup' `
    -PublicIpAddressName 'myPublicIpAddress' `
    -OpenPorts 80,3389

Explanation of Parameters:

-ResourceGroupName: The resource group where the VM will reside (myResourceGroup in this case).
-Name: The name of the VM (myVM).
-Location: The Azure region where the VM will be deployed (East US).
-Image: The operating system image for the VM. We’ve selected the Windows Server 2022 Datacenter edition.
-VirtualNetworkName: Name of the virtual network to which the VM will be connected.
-SubnetName: The subnet within the virtual network where the VM will be deployed.
-SecurityGroupName: The network security group to apply to the VM for controlling inbound and outbound traffic.
-PublicIpAddressName: Name of the public IP address that will be assigned to the VM.
-OpenPorts: Ports to be opened on the VM (port 80 for HTTP and port 3389 for RDP).

Once executed, the VM and all associated resources will be created.

Step 4: Install IIS Web Server

Once the VM is up and running, you can use PowerShell to run commands on the VM. Let’s install IIS (Internet Information Services) to view a basic web server in action.

To install IIS on the newly created VM, use the Invoke-AzVMRunCommand cmdlet to run a PowerShell script remotely on the VM:

Invoke-AzVMRunCommand -ResourceGroupName 'myResourceGroup' -VMName 'myVM' -CommandId 'RunPowerShellScript' -ScriptString 'Install-WindowsFeature -Name Web-Server -IncludeManagementTools'

This command installs the IIS web server along with the necessary management tools. The -ScriptString parameter specifies the PowerShell script to be executed.

Step 5: View the Web Server

After IIS has been installed, the next step is to access the web server from a browser. The VM is assigned a public IP address, which can be used to access the web server from any machine.

To get the public IP address of your VM, you can run the following command:

$publicIp = (Get-AzPublicIpAddress -ResourceGroupName 'myResourceGroup' -Name 'myPublicIpAddress').IpAddress
Write-Host "Access your web server at: http://$publicIp"

Once you have the public IP address, open a web browser and navigate to http://<public_ip>. You should see the default IIS welcome page, confirming that the IIS web server is successfully running on your VM.

Step 6: Clean Up Resources

When you're done using the virtual machine and its associated resources, it's important to clean up to avoid incurring unnecessary charges. You can easily remove the resource group, which will delete the VM and all related resources, by running the following command:

Remove-AzResourceGroup -Name 'myResourceGroup'

This command deletes the entire resource group, including the VM, networking resources, and other components, so that you are not charged for unneeded resources.

Conclusion

Creating and managing Azure resources with PowerShell is a powerful and efficient way to automate infrastructure deployment. In this guide, we demonstrated how to:

Launch Azure Cloud Shell and create a resource group.
Deploy a Windows Virtual Machine.
Install a web server (IIS) on the VM.
View the web server through a browser.
Clean up resources when no longer needed.

Using Azure Cloud Shell and PowerShell together simplifies the process of working with Azure, providing automation and control over cloud infrastructure. Following these instructions will allow you to effortlessly establish, manage, and clean up virtual machines and other Azure resources.

"Mastering High Availability: A Step-by-Step Guide to Creating a Load Balancer in Azure"

samuel — Tue, 11 Mar 2025 17:11:01 +0000

How to Create a Load Balancer in Azure

When building a scalable and highly available application in the cloud, one of the critical components to ensure efficient distribution of traffic is a load balancer. Azure provides a robust load balancing solution that can automatically distribute incoming network traffic across multiple backend resources, such as virtual machines, ensuring high availability and reliability. This article will walk you through the process of creating a load balancer in Azure.

What is a Load Balancer in Azure?

A Load Balancer is a fully managed service in Azure that enables you to distribute incoming traffic across multiple virtual machines (VMs) or services to ensure no single machine becomes a bottleneck. This improves the scalability, performance, and availability of your application. Azure Load Balancer works at the transport layer (Layer 4) of the OSI model, handling traffic on both TCP and UDP protocols.

Azure offers two types of load balancers:

Public Load Balancer: Used to distribute traffic from the internet to your virtual machines in a virtual network.
Internal Load Balancer (ILB): Used to distribute traffic among VMs within a private virtual network, typically for internal services.

Prerequisites

Before you create an Azure Load Balancer, ensure you have:

An Azure subscription (If you don’t have one, you can create a free account).
A resource group to organize your resources.
At least two virtual machines deployed within the same virtual network to simulate a real-world scenario.

Steps to Create a Load Balancer in Azure

1. Create a Resource Group (if not already created)

A resource group is a logical container that holds Azure resources. It is good practice to keep your resources organized under one resource group.

Steps:

Go to the Azure portal (https://portal.azure.com).
In the left sidebar, select Resource groups.
Click + Add to create a new resource group.
Enter the name and region of your resource group and click Review + Create.

2. Deploy Virtual Machines (VMs)

Next, you’ll need to deploy at least two VMs that will be part of your backend pool, as Azure Load Balancer will distribute traffic among them.

Steps:

Go to the Azure portal, select Virtual machines in the sidebar.
Click + Add and follow the prompts to create two VMs in the same resource group and region.
Ensure that the VMs have the same configuration (e.g., same operating system, same size).
Install a simple web server or any other test application on both VMs.

See how to create and deploy Vms on my previous article.

3. Create the Load Balancer

Now, we will create the Azure Load Balancer.

Steps:

In the Azure portal, click on Create a resource.
Search for Load Balancer in the marketplace and click on it.

Click Create to begin the process.

Configure the Load Balancer:

Name: Give your Load Balancer a unique name.
Region: Select the region where your VMs are deployed.
SKU: Choose the Standard SKU for a production-ready load balancer.
Type: Choose between Public or Internal based on your requirements.

Click Next to proceed to the Frontend IP configuration.

4. Configure Frontend IP Address

The frontend IP address is the IP address that clients use to access your application. If you are using a Public Load Balancer, this IP will be accessible over the internet.

Steps:

For Public Load Balancer, select Public IP address.
- Choose Create new for the public IP address.
- Provide a name for the public IP and choose the IP version (IPv4 is typical).
- Select Dynamic or Static depending on your needs.
For Internal Load Balancer, select Private IP address.
- Choose the virtual network and subnet for the internal IP.
- The IP will be used internally within your network.

Click Next to move on to the Backend Pools configuration.

5. Configure Backend Pools

The backend pool consists of the resources (in this case, your virtual machines) that will receive traffic from the load balancer.

Steps:

Click on + Add a backend pool.
Provide a name for the backend pool.
Click + Add to add your virtual machines to the pool.
- Select the VMs that you created earlier.
Once added, click Add to finish.

Click Next to proceed to Health Probes.

6. Configure Health Probes

Health probes help Azure determine the health of your backend VMs. These probes ensure that traffic is only directed to healthy VMs.

Steps:

Click on + Add a health probe.
Provide a name for the health probe.
Choose the protocol (TCP, HTTP, or HTTPS) based on your application.
Set the port to the port your application listens on (e.g., port 80 for a web server).
Configure the interval and unhealthy threshold based on your requirements.

Click Next to proceed to the Load Balancing Rules.

7. Configure Load Balancing Rules

Load balancing rules define how the traffic is distributed between the backend pool members.

Steps:

Click + Add a load balancing rule.
Provide a name for the rule.
Choose the frontend IP (the one you created earlier).
Set the backend pool (the one you just created).
Choose the protocol (TCP or UDP) and set the port (e.g., port 80).
Set the health probe you created earlier.
Configure the session persistence if needed (for sticky sessions).

Click Review + Create.

8. Review and Create

Azure will now validate your configurations. If everything looks good, click Create.

Azure will provision the load balancer, backend pool, health probe, and load balancing rules. Once the deployment is complete, you will have a functioning load balancer that distributes traffic to your backend virtual machines.

9. Test the Load Balancer

To verify that the load balancer is working correctly, you can:

Access the frontend IP address of the Load Balancer (the public IP or private IP depending on the configuration).
You should be routed to one of your backend virtual machines based on the load balancing rule you set.
Refresh the page or try multiple times to confirm that traffic is being distributed between the VMs.

Conclusion

Creating a load balancer in Azure ensures that your application can scale and maintain high availability by distributing traffic across multiple backend VMs. By following the steps outlined above, you can create a robust load balancing solution using Azure Load Balancer. Whether you are building a public-facing website or a private application, Azure’s load balancing features help improve the reliability and performance of your infrastructure.

Be sure to explore other advanced options such as application gateway or Azure Traffic Manager if you have more complex traffic management needs, including layer 7 load balancing, global distribution, or content-based routing.

Creating an Azure Compute Gallery and Capturing the Image of a Virtual Machine (VM)

samuel — Fri, 07 Mar 2025 13:43:50 +0000

Azure Compute Gallery is a powerful feature in Azure that enables users to efficiently manage and share VM images across multiple subscriptions and regions. It provides a centralized location to store images and simplifies the deployment of consistent environments across your organization or across your Azure infrastructure. In this article, we will walk through the steps of creating an Azure Compute Gallery and capturing the image of a VM, with an emphasis on the state of the VM being specialized. We’ll also discuss when you might want to generalize the VM instead.

Prerequisites:

Before beginning, make sure you have the following:

An active Azure subscription.
Azure CLI or Azure PowerShell installed and configured.
Basic understanding of Azure Virtual Machines and image creation.
A VM in Azure that is in the desired configuration for capturing.

Step 1: Create an Azure Compute Gallery

First, let’s set up the Azure Compute Gallery to store and manage your VM images.

Navigate to Azure Portal: Go to the Azure Portal and log into your account.

Create a Compute Gallery:
- In the search bar at the top, search for "Azure Compute Gallery" and click on "Create."

Fill out the required details:
- Subscription: Choose the subscription in which the gallery will be created.
- Resource Group: Select an existing resource group or create a new one.
- Gallery Name: Provide a unique name for the gallery.
- Region: Select the region where the gallery will be created (it’s recommended to place the gallery in a region close to where most of your VMs reside).
Click on Review + Create and then Create to deploy the gallery.

Step 2: Prepare the Virtual Machine (VM)

Before capturing an image, ensure the VM is configured and ready to be captured. It’s essential that the VM is in the correct state.

Access the VM:
- In the Azure Portal, navigate to your VM, ensuring it is in the desired state, with all necessary applications, configurations, and updates installed.

Configure the VM for Image Capture:
- If you want the VM to be specialized, it means the machine has unique configurations like specific user settings, applications, and data. The specialized state is typically required if you intend to use the image for subsequent VM deployments where those customizations should persist.

Specialized vs. Generalized VM:
- Specialized VM: This is a VM that has been fully configured with custom settings. It is generally used when the machine will act as a template for an environment that needs to maintain specific configuration or software settings. It is not suitable for creating images that will be used across multiple tenants or environments.
- Generalized VM: This is a VM that has been generalized to remove any unique configurations like user accounts or specific machine-specific data, making it ideal for creating reusable, uniform VM images that can be used to create new VMs. A generalized VM is prepared by running the command sysprep in Windows or deprovision in Linux.

Step 3: Capture the Image of the Specialized VM

Ensure the VM is in Specialized State:
- If the VM is configured correctly, and you want to capture it as a specialized image, leave the VM in its current state. If it is generalized, refer to the next section for instructions on how to generalize it.
Capture the Image:
- To capture the image of the VM, follow these steps:
  - In the Azure Portal, go to the VM and select Capture from the top menu.

 - Name your image, and select the **Compute Gallery** you just created.
 - Choose the **Image version** (this is how you will track different versions of your image).

 - Make sure to check the box that indicates the VM is **specialized** and **not generalized**.

 - Confirm that you understand the implications of capturing a specialized image.
 - Click **Create** to capture the image.

The VM image is now stored in your Azure Compute Gallery and can be used to deploy new VMs with the same configuration.

When to Generalize a VM

While we focused on capturing a specialized image, there are situations where you may want to generalize the VM instead. The primary use case for generalizing a VM is when you need to create a reusable, standardized image for scaling purposes.

Generalizing the VM: To generalize the VM, use the following process (for Windows VMs, the sysprep tool is used, while Linux VMs use the deprovision command):

For Windows VMs:
- Open the Command Prompt inside the VM.
- Run the following command:
```
   sysprep /oobe /shutdown /generalize
```
- This command prepares the VM by removing unique machine-specific data and settings. The VM will shut down once the process is completed.
For Linux VMs:
- Open the terminal inside the VM.
- Run the command to deprovision the VM:
```
   sudo waagent -deprovision+user -force
```
- This will remove any user-specific data and settings, preparing the VM for image capture.

Capture the Image After Generalization:
- Once the VM is generalized, you can proceed with capturing the image by following the same steps we used to capture the specialized image, but this time, the VM image will be available for widespread deployment and will not contain unique data.

Step 4: Use the Image from the Azure Compute Gallery

Once you have captured the image, whether specialized or generalized, it’s available in your Azure Compute Gallery. You can use it to deploy new virtual machines within the same region or across different regions.

Deploying VMs from the Compute Gallery:
- In the Azure Portal, go to the Compute Gallery and select the image you captured.

Choose Create VM to initiate the deployment process.

Follow the prompts to configure the VM settings, such as size, network, and storage.

Conclusion

Creating an Azure Compute Gallery and capturing a VM image is a vital part of managing and scaling virtual machines in Azure. Deciding whether to generalize or specialize the VM depends on your use case. Specialized images are ideal when you need to maintain unique machine configurations, while generalized images are more suitable for creating multiple identical VM instances. Azure Compute Gallery provides an efficient, organized way to manage these images, improving the overall efficiency of your cloud infrastructure.

Unlocking Extra Storage: How to Create, Initialize, and Use a Data Disk on Your Azure VM

samuel — Thu, 06 Mar 2025 02:04:27 +0000

Azure is a powerful cloud platform that allows you to create and manage virtual machines (VMs) and storage resources easily. In many scenarios, you may need to attach an additional data disk to a VM for increased storage capacity. This article walks you through the process of creating a VM data disk, initializing it, and making it usable in an Azure VM.

Certainly! Below is a step-by-step guide on how to create a VM, attach a data disk, initialize it, and make it usable using RDP (Remote Desktop Protocol) on Azure.

Step 1: Create a Virtual Machine (VM) on Azure

Before you can attach a data disk to a virtual machine, the virtual machine must first be created. Here's how you can do it:

1.1 Sign In to Azure Portal

Visit the Azure Portal.
Sign in with your Azure credentials (Microsoft account or Azure Active Directory).

1.2 Start the VM Creation Process

In the left-hand navigation pane, click "Create a resource".
In the Search the Marketplace box, type "Virtual Machine" and select Virtual Machine.

Click on Create to begin the creation of your new virtual machine.

1.3 Configure Basic Settings

Subscription: Choose the Azure subscription under which the VM will be created.
Resource Group: Select an existing resource group or create a new one.
VM Name: Give your VM a unique name (e.g., MyAzureVM).
Region: Choose the region where you want your VM to be located.

Image: Choose the desired operating system. For example, choose Windows Server for a Windows-based VM.

Size: Choose the appropriate VM size based on your needs (CPU, RAM, etc.).

Authentication Type: Choose Password for simpler access or SSH public key if you're familiar with SSH keys. Since we're using RDP, select Password and set an administrator username and password.

1.4 Configure Networking and Storage

Virtual Network (VNet): Azure will create a default VNet or allow you to choose an existing one.
Subnet: Choose a subnet or accept the default option.
Public IP: Select "Yes" to assign a public IP if you need remote access.
Network Security Group (NSG): Ensure RDP (TCP/3389) is enabled.
OS Disk: Choose the disk type, such as Standard SSD.

1.5 Review and Create

Review all the configurations.
Click "Create" to start the deployment. It will take a few minutes to deploy the VM.

Once the VM is deployed, it will be listed in the Virtual Machines section of the Azure Portal.

Step 2: Attach a Data Disk to the VM

After the VM is created, we can attach a data disk for additional storage.

2.1 Navigate to Your Virtual Machine

Go to Virtual Machines in the Azure portal.
Click on the VM you just created.

2.2 Attach a Data Disk

In the VM's settings, find and click on Disks in the left-hand menu.

Under Data Disks, click on Add data disk.

To create a new data disk, select Create and attach a new disk.
- Choose a Disk Type (Standard HDD, Premium SSD, etc.).
- Set the Size based on your storage needs.

Click Save to attach the new data disk to your VM.

Azure will now attach the data disk to your VM.

Step 3: Initialize the Data Disk Using RDP

Now that the data disk is attached, you need to initialize and format it before you can use it.

3.1 Connect to the VM via RDP

In the Azure Portal, go to Virtual Machines and select your VM.

On the VM's page, click on Connect at the top.

Select RDP (Remote Desktop Protocol).

Download the RDP file and enter the username and password you set when creating the VM.

3.2 Initialize and Format the Data Disk (Windows)

Once you are connected to the Windows VM via RDP, follow these steps to initialize the new data disk:

Open Disk Management:
- Press Win + X and select Disk Management (or type diskmgmt.msc in the search box and press Enter).

Initialize the New Disk:
- When Disk Management opens, you should see your new disk listed as "Disk 1" or "Disk 2" (depending on how many disks you already have attached). It will be marked as Unallocated.

Right-click on the unallocated space and select Initialize Disk.
Choose GPT (GUID Partition Table) if your disk is large (greater than 2TB) or MBR (Master Boot Record) for smaller disks. Click OK.

Create a New Volume:
- Right-click on the unallocated space and select New Simple Volume.

The New Simple Volume Wizard will appear. Follow the wizard to set up the volume:

Select the size of the partition (the default is the entire disk).

Assign a drive letter (e.g., E:).

Choose the NTFS file system (recommended for Windows).

You can name the volume (e.g., "Data Disk").

Complete the Wizard:
- Click Next and then Finish. The disk will now be formatted and mounted as a new volume.

Once done, you can access the new disk from This PC as a new drive (e.g., E:).

Step 4: Make the Data Disk Usable

Now that the data disk is initialized and formatted, it is ready for use.

For Windows VMs: The new data disk should now be available as a new drive in This PC (e.g., E:).
- You can now start using the disk to store files, install applications, or perform other tasks.

Conclusion

Now you've successfully set up a virtual machine on Azure, connected a data disk, formatted and initialized the disk, and enabled it for use. Because it enables you to scale your storage capacity as needed, this is a crucial ability when working with cloud settings. With Azure, you can easily expand your VM’s capacity by adding more data disks or resizing existing ones to meet the demands of your workloads.

How to Create a Resource Group in Microsoft Azure.

samuel — Tue, 04 Mar 2025 00:17:45 +0000

Introduction:
Microsoft Azure is a cloud computing platform and service that allows developers and businesses to create, launch, and manage apps and services through data centers managed by Microsoft. It offers a variety of cloud-based services, such as databases, networking, storage, and processing power.

In Azure, a Resource Group is a container that houses connected Azure solution resources. Virtual computers, databases, storage accounts, and networking elements are a few examples of these resources. It is simpler to deploy, monitor, and remove resources that share a lifespan when they are arranged and managed as a resource group.

Why it's beneficial

Simplifies management: Administration is made simpler by grouping related resources together, which makes monitoring and administration simpler.

Access control: The entire resource group is subject to security and access regulations.

Resource lifecycle: As part of a single project, you can deploy, update, and remove resources together.

Cost management: It assists in monitoring and controlling expenses for a certain set of project resources.

This tutorial will guide you through the process of creating a new resource group in Azure, helping you get started with organizing and managing your cloud resources effectively.

Step 1: Navigate to the Azure Portal

Open your web browser and go to the Azure Portal.

If you're not logged in already, enter your credentials (email and password) associated with your Microsoft Azure account.

Step 2: Log In
After you land on the Azure Portal page, enter your login credentials. If you don’t have an account, click on “Create one!” and follow the instructions.

Note: Ensure you have the proper access level to create resources within the Azure portal.

Step 3: Search for Resource Groups
Once logged in, you'll be on the Azure Dashboard.
On the top search bar, type “Resource Groups” and click on it from the dropdown menu. This will take you to the "Resource Groups" page.

Step 4: Create a Resource Group
On the "Resource Groups" page, click on the “+ Create” button at the top of the page.

Fill out the necessary information:
Subscription: Choose your subscription. This refers to the Azure plan you're using.
Resource Group Name: Enter a name for your resource group. Ensure it’s unique within your subscription.
Region: Select a region where your resource group will reside (for example, East US, West Europe, etc.).

After filling out the details, review everything.
Click on “Review + Create” to validate your configurations.
Once the validation is complete, click “Create” to finalize the creation of your new resource group.

Step 5: Confirm Resource Group Creation
After the deployment process is completed, you’ll see a notification stating that your resource group has been successfully created.

You can now go back to the “Resource Groups” page to view your newly created group listed there.

Azure resource groups are essential for effective cloud management, as they allow businesses to group resources for improved visibility, access control, cost tracking, and operational efficiency. By experimenting with different resource groups for various projects, you can gain hands-on experience in organizing and managing cloud environments, troubleshooting, scaling, and utilizing Azure's automation and monitoring tools to build reliable, scalable solutions.

Mastering CloudOps: Key Concepts Every Business Should Know

samuel — Fri, 28 Feb 2025 03:31:45 +0000

In today's virtual-first world, businesses are rapidly turning to cloud operations (CloudOps) to amplify performance, optimize workflow, and deliver flawless user experiences. But with the rapid shift to the cloud, understanding key CloudOps theory has never been more important. Whether you're a tech enthusiast, entrepreneur, or just diving into cloud computing, mastering the basics plays avital role in informed decision-making. From virtualization and scalability to global reach and fault tolerance, these concepts are the building blocks of efficient, reliable, and agile cloud infrastructures. In this article, we'll break down these core principles in simple terms and explain how they shape the future of cloud computing. Let’s dive in!

What is Virtualization?

Virtualization is the process of creating virtual (rather than physical) versions of resources, such as servers, storage devices, or networks. It allows businesses to run multiple instances of operating systems or applications on a single physical machine. Think of it as creating “virtual” spaces inside a single machine, optimizing the hardware and improving efficiency. For example, by using virtualization, businesses can run several different operating systems on one server, each acting like a separate, independent machine. This leads to resource optimization, cost savings, and better scalability.

Scalability

Scalability refers to the ability of a system or network to grow and handle increased demand. In cloud environments, scalability is crucial, as it allows businesses to adjust resources (such as CPU, storage, or memory) based on the workload. There are two main types of scalability:

Vertical Scaling (Scaling Up): Adding more resources (e.g., CPU, memory) to an existing server.
Horizontal Scaling (Scaling Out): Adding more servers to distribute the workload. Scalability ensures that as business needs grow, the infrastructure can handle more traffic, data, or users without compromising performance.

Agility

Agility in CloudOps refers to the ability to quickly adapt to changes and innovations. It means businesses can rapidly deploy, manage, and scale applications or services to meet evolving needs. In a cloud environment, agility is about being able to quickly provision resources, make changes to the infrastructure, and deploy new features. The faster a company can react to market changes or customer demands, the more competitive and successful they become. Cloud services enable agility through automation, on-demand resources, and DevOps practices, making businesses more flexible and responsive.

High Availability

High availability (HA) is a design approach that ensures a system or service is consistently operational, minimizing downtime. In CloudOps, high availability means your applications and services are designed to stay online even in the event of hardware failures, network issues, or other disruptions. Achieving high availability often involves redundant systems, load balancing, failover mechanisms, and geographically distributed servers to ensure continuous uptime and reliability. Cloud providers typically offer multiple availability zones across different regions to ensure that even if one region fails, the application remains accessible from another.

Fault Tolerance

Fault tolerance refers to the ability of a system to continue functioning correctly even if some of its components fail. In CloudOps, fault tolerance is achieved through the use of redundancy, where critical components have backups that can take over if something goes wrong. For example, if a server fails, a redundant server or system can automatically take over, ensuring the application remains operational without disruption. This minimizes downtime and prevents data loss, ensuring that services remain reliable and available at all times.

Global Reach

Global reach refers to the ability to deliver cloud services and applications across the globe, regardless of the user's location. By leveraging the infrastructure of cloud providers, businesses can deploy applications in multiple regions or countries, ensuring a faster and more reliable experience for users worldwide. This global distribution helps in reducing latency, improving performance, and meeting regional compliance requirements. It also allows businesses to expand into new markets without the need to invest in physical data centers in every region.

Elasticity vs. Scalability:
What’s the Difference?

While both elasticity and scalability are important concepts in CloudOps, they have distinct meanings:

Scalability refers to the ability to increase or decrease resources to meet growing or shrinking demands. It can happen either manually or automatically over time. If your business experiences an increase in traffic, scaling up or out ensures that you can handle the extra load.

Elasticity is the ability to automatically adjust resources in real-time, based on demand. Elasticity allows cloud systems to expand or contract resources dynamically, providing flexibility to businesses. For example, during peak hours, your cloud service might automatically add more servers to handle the increased load, then reduce the resources when traffic decreases.

In essence, while scalability is about the potential to grow, elasticity ensures that growth happens automatically and in real-time, optimizing costs and resources.

Conclusion

Understanding these key CloudOps concepts—virtualization, scalability, agility, high availability, fault tolerance, global reach, and the difference between elasticity and scalability—is fundamental to leveraging cloud computing effectively. CloudOps is about creating an efficient, adaptable, and reliable infrastructure that can scale with business needs while maintaining availability and performance. With these concepts in mind, organizations can better harness the power of the cloud to support their operations and drive success.