DEV Community: oluoma stella onyeukwa

Building a Windows VM on Azure and installing Windows Server (IIS) on it.

oluoma stella onyeukwa — Sun, 23 Mar 2025 20:18:08 +0000

Step-by-Step Guide for Creating a Windows VM on Azure and Installing Windows Server on it

Step 1: Create a new virtual machine (VM).

Go to the search bar and type Virtual Machine.

Click the Create button to start the virtual machine creation process. Choose Create a virtual machine hosted by Azure.

Select the appropriate subscription and create a resource group by clicking the Create resource group button. Give both the resource group and the VM a name.

Step 2: Configure the Virtual machine (VM)

Provide other information about your virtual machine, such as the operating system (Windows Server Datacenter-x64 G2), size, and other configuration settings. Leave other options as default.

Create an Administrator Account. Use Azureuser for the username and password123 for the password.
Select Inbound Port Rules. Select RDP for a Windows VM. This allows IP addresses to connect to the VM. Also select HTTP, which would help connect your virtual machine to the web.

Click Next until you reach the Boot Diagnostics in the Monitoring tab, then click on Disable.

Click Next to the tags tab and then give the VM a tag name, then click Review + Create.

Click on the Create button. If the validation passes, the deployment will proceed. If not, note any recommendations, fix them, and try again. Deployment might take 3-5 minutes.

Step 3: Access the Windows Virtual machine

Once the virtual machine is deployed, click on the Connect button in the Overview of the virtual machine blade in the Azure portal.
Click Native RDP, select, and wait for the configured sign to be displayed on the right-hand side. Download the RDP file.

Open the RDP file from your local computer and click on Connect. Enter the Admin Details created during the VM setup.

Follow the prompt and click Continue. Use the username and password created for the admin section.

Once the connection is successful, start using your virtual machine!

Step 4: Install Additional Windows Server Roles (IIS)
Click on the Start menu.
Type PowerShell and open Windows PowerShell as an administrator (right-click and select Run as administrator).

Run the following command to install the IIS role and management tools: Install-WindowsFeature -name Web-Server -IncludeManagementTools

If you need specific role services, you can specify them using their feature names.
You can verify that IIS has been installed by opening a web browser and navigating to http://localhost. You should see the default IIS welcome page.
Or just paste the IP address of the VM in a browser and verify that you installed the webserver.

Following these guidelines will have you installed Windows Server and effectively built a Windows Virtual Machine on Azure.

How to Set Up an Azure Virtual Network

oluoma stella onyeukwa — Tue, 17 Dec 2024 11:00:30 +0000

What is a virtual network?

A virtual network (VNet) is a network that exists purely in software, allowing for the establishment of isolated, secure, and adaptable networking environments within a data center or cloud architecture. It enables devices, services, or systems to interact as if they were linked over a physical network, even if they are geographically separated or housed in virtual environments.

Tasks

Create and Configure Virtual Network in Azure.
Create hub and spoke virtual networks and subnets.
Create the Hub-vnet virtual network configuration.

1. Create hub and spoke virtual networks and subnets

Sign in to the Azure portal.
Search for and select Virtual Networks.

Select + Create.

Assign to a Resource group RG11.
Set the name as app-vnet.
Region to East US.

The IPv4 address space is 10.1.0.0/16.
This virtual network requires two subnets, frontend and backend.
Set the Subnet address range of the frontend subnet to 10.1.0.0/24.
Click Add to save.

Select Add a subnet for the backend subnet.
Set the Subnet address range to 10.1.1.0/24.
Click Add to save.

Note:Leave all other settings as their defaults. When finished, select Review + create and then Create.
.

2. Create the Hub-vnet virtual network configuration. This virtual network has the firewall subnet.

Search for and select Virtual Networks again.
Select + Create.
Assign to the same Resource group as app-vnet RG11.
Set the Name as hub-vnet.
Region to East US as well.
Click Next to the IP addresses section.

The IPv4 address space is 10.0.0.0/16.
Select Add a subnet.
Name the subnet AzureFirewallSubnet.
.
Set the Subnet address range to 10.0.0.0/26.
Click Add to save.
Select Review + create and then Create.

3. Configure a peer relationship between the virtual networks

Search for and select the app-vnet virtual network.
In the Settings blade, select Peerings.
+ Add **a peering between the two **virtual networks.

Set the Remote peering link name to app-vnet-to-hub.
The Virtual network peered to hub-vnet.

Set the local virtual network peering link name to hub-to-app-vnet.
Leave all other settings as their defaults.
Select Add to create the virtual network peering.

Once the deployment completes, verify the Peering status is Connected.

Creating an Amazon EC2 instance and installing the IIS web server.

oluoma stella onyeukwa — Sun, 08 Dec 2024 19:52:55 +0000

This tutorial shows how to build an EC2 instance on Amazon Web Services (AWS) and install the IIS web server on it.

What is AWS?

AWS is a comprehensive and popular cloud platform with a global presence that provides safe and affordable cloud computing services, including computation, storage, databases, machine learning, networking, and more, based in data centers spread across the globe. A virtual server in the AWS cloud environment is called an Amazon EC2 (Elastic Compute Cloud) instance.

The three simple steps to create an Amazon EC2 console are as follows:.

Step 1: Sign in to the AWS management console and create the EC2 instance.
Step 2: Connect to the instance.
Step 3: Create the IIS web server.

Step 1: Sign in into AWS management console and create the EC2 instance.

go to Google and search for AWS management console.

Sign in to the console or create a profile.

Search for EC2 on the home page.

Select EC2 and scroll down and launch instance.

Give the instance a name and add tags.

In the Application and OS Images under the Quick Start tab, select an OS image for your instance.
Select Windows.

Select the free Microsoft Windows server 2025 Base as the Amazon machine image.

select t3.micro under instance type.

For key pair, Create new key pair.

Give the keypair a name, ensure key pair type is RSA then craete a key pair. Notice the keypair file is downloaded.

Scroll down to Firewall (security groups), select Ensure RDP from anywhere and Allow HTTP from the internet are both selected. This will ensure your server can be accessed anywhere over the internet.
Launch instance and wait for it to be successful.

Step 2: Connect to the instance and create the IIS web server

Connect to instance.

Select the RDP Client tab, check the Connect using RDP and Download the RDP file.
Wait for the file to download.

Select Get password.

Upload private key file, navigate and select the key file downloaded previously.

Decrypt password.

Copy password.

Open the RDP file that was downloaded and Connect.

Paste the password previously copied. Ok

Step 3: Create the IIS web server.

Search for PowerShell on the desktop, run as Admin.

Enter the command Install-WindowsFeature -Name Web-Server -IncludeManagementTools. Press Enter.

Wait for it to finish loading.

Notice the Exit Code says successful.
Exit the remote desktop to the AWS management console. Select the instance, copy the public IP address.

Paste the IP address in a new tab on your browser.

Press Enter and observe the web server that was deployed.

Notice the IIS web server was successfully accessed from the public internet.
To ensure you dont run out your credit on AWS, Terminate and delete Instance immediately after usage.

How to use managed identity and role-based access control to provide security and storage for a new company app .

oluoma stella onyeukwa — Tue, 29 Oct 2024 17:51:38 +0000

Skilling tasks

Step 1: Create the storage account and managed identity.
Step 2: Secure access to the storage account with a key vault and key.
Step 3: Configure the storage account to use the customer managed key in the key vault.
Step 4: Configure an time-based retention policy and an encryption scope.

Step 1: Create the storage account and managed identity

1 .Provide a storage account for the web app.

In the portal, search for and select Storage accounts.
Select + Create.

For Resource group select Create new. Give your resource group a name and select OK to save your changes.
Provide a Storage account name. Ensure the name is unique and meets the naming requirements.

Move to the Encryption tab.
Check the box for Enable infrastructure encryption.
Notice the warning, This option cannot be changed after this storage account is created.
Select Review + Create.
Wait for the resource to deploy.

2 .Provide a managed identity for the web app to use. Learn more about managed identities.

Search for and select Managed identities.

Select Create.
Select your resource group.
Give your managed identity a name.

Select Review and create, and then Create.
Assign the correct permissions to the managed identity. The identity only needs to read and list containers and blobs. Learn more about how to assign Azure roles.
Search for and select your storage account.
Select the Access Control (IAM) blade.
Select Add role assignment (center of the page).

On the Job functions roles page, search for and select the Storage Blob Data Reader role.

On the Members page, select Managed identity.
Select Select members, in the Managed identity drop-down select User-assigned managed identity.
Select the managed identity you created in the previous step.
Click Select and then Review + assign the role.

Select Review + assign a second time to add the role assignment.
Your storage account can now be accessed by a managed identity with the Storage Data Blob Reader permissions.

Step 2:Secure access to the storage account with a key vault and key

To create the key vault and key needed for this part of the lab, your user account must have Key Vault Administrator permissions. Learn more about how to provide access to Key Vault keys, certificates, and secrets with an Azure role-based access control

In the portal, search for and select Resource groups.
Select your resource group, and then the Access Control (IAM) blade.
Select Add role assignment (center of the page).

On the Job functions roles page, search for and select the Key Vault Administrator role.

On the Members page, select User, group, or service principal.
Select Select members.
Search for and select your user account. Your user account is shown in the top right of the portal.
Click Select and then Review + assign.
Select Review + assign a second time to add the role assignment.
You are now ready to continue with the lab.

2.Create a key vault to store the access keys.

In the portal, search for and select Key vaults.
Select Create.

Select your resource group.
provide the name for the key vault. The name must be unique.

Ensure on the Access configuration tab that Azure role-based access control (recommended) is selected.
Select Review + create.
Wait for the validation checks to complete and then select Create.

After the deployment, select Go to resource.
On the Overview blade ensure both Soft-delete and Purge protection are enabled.

3.Create a customer-managed key in the key vault.

In your key vault, in the Objects section, select the Keys blade.

Select Generate/Import and Name the key.
Take the defaults for the rest of the parameters, and Create the key.

Step 3:Configure the storage account to use the customer managed key in the key vault

Before you can complete the next steps, you must assign the Key Vault Crypto Service Encryption User role to the managed identity. Learn more about how to use a system-assigned managed identity to authorize access

In the portal, search for and select Resource groups.
Select your resource group, and then the Access Control (IAM) blade.
Select Add role assignment(center of the page).

On the Job functions roles page, search for and select the Key Vault Crypto Service Encryption User role.

On the Members page, select Managed identity.
Select Select members, in the Managed identity drop-down select User-assigned managed identity.
Select your managed identity.
Click Select and then Review + assign.

Select Review + assign a second time to add the role assignment.

2.Configure the storage account to use the customer managed key in your key vault. Learn more about customer managed keys on an existing storage account.

Return to your the storage account.
In the Security + networking section, select the Encryption blade.
Select Customer-managed keys.

Select a key vault and key. Select your key vault and key.
Select to confirm your choices.
Ensure the Identity type is user-assigned.
Select an identity.
Select your managed identity then select Add.
Save your changes.

If you receive an error that your identity does not have the correct permissions, wait a minute and try again.

Step 4: Configure an time-based retention policy and an encryption scope.

1.The developers require a storage container where files can’t be modified, even by the administrator. Learn more about blob immutable storage.
Navigate to your storage account.
In the Data Storage section, select the Containers blade.
Create a container called hold. Take the defaults. Be sure to Create the container.

Upload a file to the container.

In the Settings section, select the Access policy blade.
In the Immutable blob storage section, select +Add policy.
For the Policy type, select time-based retention.
Set the Retention period to 5 days.
Be sure to Save your changes.

Try to delete the file in the container.
Verify you are notified failed to delete blobs due to policy.

2.The developers require an encryption scope that enables infrastructure encryption. Learn more about infrastructure encryption.

Navigate back to your storage account.
In the Security + networking blade, select Encryption.
In the Encryption scopes tab, select Add.
Give your encryption scope a name.
The Encryption type is Microsoft-managed key.
Set Infrastructure encryption to Enable.
Create the encryption scope.

Return to your storage account and create a new container.
Notice on the New container page, there is the Name and Public access level.
Notice in the Advanced section you can select the Encryption scope you created and apply it to all blobs in the container.

Setting up a shared file storage for the company offices

oluoma stella onyeukwa — Sun, 27 Oct 2024 08:23:08 +0000

Step 1: Create and configure a storage account for Azure Files..
Step 2: Create and configure a file share with directory..
Step 3: Configure and test snapshots..
Step 4: Configure restricting storage access to selected virtual networks..

Step 1:Create and configure a storage account for Azure Files.

1 . Create a storage account for the finance department’s shared files. Learn more about storage accounts for Azure Files deployments.

In the portal, search for and select Storage accounts.

Select + Create.

For Resource groupselect Create new. Give your resource group a name and select OK to save your changes.
Provide a Storage account name. Ensure the name meets the naming requirements.
Set the Performance to Premium.
Set the Premium account type to File shares.
Set the Redundancy to Zone-redundant storage.
Select Review and then Create the storage account.

wait for the resource to deploy.
Select Go to resource.

Step 2: Create and configure a file share with directory.

Create a file share for the corporate office. Learn more about Azure File tiers.

In the storage account, in the Data storage section, select the File shares blade.
Select + File share and provide a Name.
Review the other options, but take the defaults.

Select Create

2.Add a directory to the file share for the finance department. For future testing, upload a file.

Select your file share and select + Add directory.
Name the new directory finance.
Select Browse and then select the finance directory.
Notice you can Add directory to further organize your file share.

Upload a file of your choosing.

Step 3: Configure and test snapshots

Similar to blob storage, you need to protect against accidental deletion of files. You decide to use snapshots. Learn more about file snapshots.

Select your file share.
In the Operations section, select the Snapshots blade.
Select + Add snapshot. The comment is optional. Select OK.

Select your snapshot and verify your file directory and uploaded file are included.

2.Practice using snapshots to restore a file.

Return to your file share.
Browse to your file directory.
Locate your uploaded file and in the Properties pane, select Delete. Select Yes to confirm the deletion.

Select the Snapshots blade and then select your snapshot.
Navigate to the file you want to restore,
Select the file and the select Restore.

Provide a Restored file name.

Verify your file directory has the restored file.

Step 4: Configure restricting storage access to selected virtual networks.

This tasks in this section require a virtual network with subnet. In a production environment these resources would already be created.

Search for and select Virtual networks.

Select Create. Select your resource group.and give the virtual network a name.

Take the defaults for other parameters, select Review + create, and then Create.
Wait for the resource to deploy.

Select Go to resource.

In the Settings section, select the Subnets blade.
Select the default subnet.
In the Service endpoints section choose Microsoft.Storage in the Services drop-down.
Do not make any other changes.

Be sure to Save your changes.

2.The storage account should only be accessed from the virtual network you just created. Learn more about using private storage endpoints..

Return to your files storage account.
In the Security + networking section, select the Networking blade.
Change the Public network access to Enabled from selected virtual networks and IP addresses.
In the Virtual networks section, select Add existing virtual network.

Select your virtual network and subnet, select Add.
Be sure to Save your changes.
Select the Storage browser and navigate to your file share.

Verify the message not authorized to perform this operation. You are not connecting from the virtual network.

Setting Up a Private Storage account for a Company

oluoma stella onyeukwa — Sat, 26 Oct 2024 22:24:03 +0000

Step-to-step guide on how to create private storage for internal use

The company requires storage for its offices and departments. This information is confidential to the company and should not be shared without permission. This storage requires high availability in the event of a regional outage. The company intends to use this storage to back up its public website.

Skilling tasks

1: Create a storage account for the company private documents.
2 : Configure redundancy for the storage account.
3 : Configure a shared access signature so partners have restricted access to a file.
4 : Back up the public website storage.
5 : Implement lifecycle management to move content to the cool tier.

Step 1: Create a storage account and configure high availability.

1.Create a storage account for the internal private company documents.

In the portal, search for and select Storage accounts.

Select + Create.

Select the Resource group created in the previous lab.
Set the Storage account name to private.
Add an identifier to the name to ensure the name is unique.
Select Review, and then Create the storage account.

Wait for the storage account to deploy, and then select Go to resource.

2.This storage requires high availability if there’s a regional outage. Read access in the secondary region is not required. Configure the appropriate level of redundancy.

In the storage account, in the Data management section, select the Redundancy blade.

Ensure Geo-redundant storage (GRS) is selected.

Refresh the page.

Review the primary and secondary location information.

Save your changes.

Step 2 : Create a storage container, upload a file, and restrict access to the file.

Create a private storage container for the corporate data.

In the storage account, in the Data storage section, select the Containers blade.
Select + Container.
Ensure the Name of the container is private.
Ensure the Public access level is Private (no anonymous access).
As you have time, review the Advanced settings, but take the

Select Create.

2.For testing, upload a file to the private container. he type of file doesn’t matter. A small image or text file is a good choice. Test to ensure the file isn’t publically accessible.

Select the container.
Select Upload.
Browse to files and select a file.
Upload the file.

Select the uploaded file.
On the Overview tab, copy the URL.

Paste the URL into a new browser tab.
Verify the file doesn’t display and you receive an error.

3.An external partner requires read and write access to the file for at least the next 24 hours. Configure and test a shared access signature (SAS).

Select your uploaded blob file and move to the Generate SAS tab.

In the Permissions drop-down, ensure the partner has only Read permissions.
Verify the Start and expiry date/time is for the next 24 hours.
Select Generate SAS token and URL.

Copy the Blob SAS URL to a new browser tab.

Verify you can access the file. If you have uploaded an image file it will display in the browser. Other file types will be downloaded

Step 3 : Configure storage access tiers and content replication.

To save on costs, after 30 days, move blobs from the hot tier to the cool tier.

Return to the storage account.
In the Overview section, notice the Default access tier is set to Hot.

In the Data management section, select the Lifecycle management blade.
Select Add rule.

Set the Rule name to movetocool.
Set the Rule scope to Apply rule to all blobs in the storage account.

Select Next.
Ensure Last modified is selected.
Set More than (days ago) to 30.
In the Then drop-down select Move to cool storage.
As you have time, review other lifecycle options in the drop-down.

Add the rule.

2.The public website files need to be backed up to another storage account.

In your storage account, create a new container called backup. Use the default values. Refer back to Lab 02a if you need detailed instructions.

Navigate to your publicwebsite storage account. This storage account was created in the previous exercise.

In the Data management section, select the Object replication blade.

Select Create replication rules.
Set the Destination storage account to the private storage account.
Set the Source container to public and the Destination container to backup.

Create the replication rule.
Optionally, as you have time, upload a file to the **public **container.

Return to the private storage account and refresh the backup container. Within a few minutes your public website file will appear in the backup folder.

How to Create a High Availability Storage Account for a Public Website.

oluoma stella onyeukwa — Thu, 26 Sep 2024 10:09:37 +0000

Table of contents
Step 1: Create a storage account with high availability.
Step 2: Create a blob storage container with anonymous read access
Step 3: Practice uploading files and testing access.
Step 4: Configure soft delete
Step 5: Configure blob versioning

Step guide on how to setup storage for public website

Step 1: Create a storage account with high availability.

Create a storage account to support the public website.

In the portal, search for and select Storage accounts.

Select + Create.

For resource group select new. Give your resource group a name and select OK.
Set the Storage account name to publicwebsite. Make sure the storage account name is unique by adding an identifier.
Take the defaults for other settings.
Select Review and then Create.

Wait for the storage account to deploy, and then select Go to resource.

2.This storage requires high availability if there’s a regional outage. Additionally, enable read access to the secondary region,

In the storage account, in the Data management section, select the Redundancy blade.
Ensure Read-access Geo-redundant storage is selected.

Review the primary and secondary location information.

3.Information on the public website should be accessible without requiring customers to login.

In the storage account, in the Settings section, select the Configuration blade.
Ensure the Allow blob anonymous access setting is Enabled.

Be sure to Save your changes.

Step 2: Create a blob storage container with anonymous read access

The public website has various images and documents. Create a blob storage container for the content.

In your storage account, in the Data storage section, select the Containers blade.
Select + Container.
Ensure the Name of the container ispublic.

Select Create.

2.Customers should be able to view the images without being
authenticated. Configure anonymous read access for the public container blobs.

Select your public container.
On the Overview blade, select Change access level.
Ensure the Public access level is Blob (anonymous read access for blobs only).

Select OK.

Step 3: Practice uploading files and testing access.

For testing, upload a file to the public container. The type of file doesn’t matter. A small image or text file is a good choice.

Ensure you are viewing your container.
Select Upload.
Browse to files and select a file. Browse to a file of your choice.
Select Upload.

Close the upload window, Refresh the page and ensure your file was uploaded.

2.Determine the URL for your uploaded file. Open a browser and test the URL.

Select your uploaded file.
On the Overview tab, copy the URL.
Paste the URL into a new browser tab.

If you have uploaded an image file it will display in the browser. Other file types should be downloaded.

Step 4: Configure soft delete

It’s important that the website documents can be restored if they’re deleted. Configure blob soft delete for 21 days. L

Go to the Overview blade of the storage account.
On the Properties page, locate the Blob service section.

Select the Blob soft deletesetting.
Ensure the Enable soft delete for blobs is checked.
Change the Keep deleted blobs for(in days setting is 21.
Notice you can also Enable soft delete for containers.

Don’t forget to Save your changes.

2.If something gets deleted, you need to practice using soft delete to restore the files.

Navigate to your container where you uploaded a file.

Select the file you uploaded and then select Delete.

Select OK to confirm deleting the file.

On the container Overview page, toggle the slider Show deleted blobs. This toggle is to the right of the search box.

Select your deleted file, and use the ellipses on the far right, to Undelete the file.
Refresh the container and confirm the file has been restored.

Step 5: Configure blob versioning

1.It’s important to keep track of the different website product document versions.

Go to the Overview blade of the storage account.
In the Properties section, locate the Blob service section.
Select the Versioning setting.

Ensure the Enable versioning for blobs checkbox is checked.
Notice your options to keep all versions or delete versions after.

Don’t forget to Save your changes.

As you have time experiment with restoring previous blob versions.

Upload another version of your container file. This overwrites your existing file.

Your previous file version is listed on Show deleted blobs page

CREATING AN AZURE RESOURCE GROUP AND CLOUD STORAGE

oluoma stella onyeukwa — Wed, 18 Sep 2024 12:27:12 +0000

Guide to Creating an Azure resource group and Storage Account

What is Azure resource groups
What is Azure cloud storage
Step 1: Create a resource group and a storage account.
Step 2: Configure simple settings in the storage account.

Azure Resource Groups
In Azure, resource groups are logical containers that contain connected Azure resources. They provide more efficient resource management and organization. This is how they work:
Organization: Resources such as virtual machines, storage accounts, and databases can be grouped together to make management easier.
Deployment: Resources inside a resource group can be deployed, updated, and deleted as a group. This streamlines resource and lifecycle management.
Access Control: Resource groups allow you to control user or application permissions using Role-Based Access Control (RBAC).
Cost management: Logically organizing resources can help with cost tracking and management as well as budgeting and analysis.
Resource management is made easier by classifying resources according to their intended use or environment (development, staging, production, etc.).

Azure Cloud Storage
Azure Cloud Storage offers scalable, secure cloud storage options. It provides numerous storage services, including:

Blob storage is ideal for storing massive amounts of unstructured data, such as text and binary files. It has three categories (hot, cool, and archive) that minimize costs based on data access frequency.

File Storage: Provides fully managed file shares in the cloud that may be accessed using the Server Message Block (SMB) protocol. Useful for scenarios requiring file-sharing capability.
Queue Storage: Offers a messaging repository for dependable communication between application components. It allows you to disconnect and scale application components.
Table Storage: A NoSQL store for semi-structured data with a schema-free design for applications that require fast and flexible data access.
Disk Storage: Offers persistent storage for Azure Virtual Machines, including regular and premium SSD options.

In conclusion, resource groups make it easier to arrange and manage Azure resources, while Azure Cloud Storage provides a range of choices for cloud data storage and management. Please feel free to ask any specific questions you may have or for further information on how to use or handle these!

Step 1: Create a resource group and a storage account

1.Create and deploy a resource group to hold all your project resources.
In the Azure portal, search for and select Resource groups.

[Select + Create.]

Give your resource group a name. For example,storagerg.
Select a region. Use this region throughout the project.
Select Review and Create to validate the resource group.

Select Create to deploy the resource group.

Create and deploy a storage account to support testing and training.

In the Azure portal, search for and select Storage accounts.

[Select +Create.]

On the Basics tab, select your Resource group.
Provide a storage account name. The storage account name must be unique in Azure.
Set the performance to standard.
Select Review, and then Create.
Wait for the storage account to deploy and then Go to resource.

Step 2: Configure simple settings in the storage account.

1.The data in this storage account doesn’t require high availability or durability. A lowest cost storage solution is desired.
In your storage account, in the Data management section, select the Redundancy blade.
Select locally redundant storage(LRS) in the Redundancy drop-down.
Be sure to save your changes.

Refresh the page and notice the content only exists in the primary location .

2.The storage account should only accept requests from secure connections.

In the Settings section, select the Configuration blade.
Ensure Secure transfer required is Enabled.

Developers would like the storage account to use at least TLS version 1.2.
In the Settings section, select the Configuration blade.
En sure the Minimal TLS version is set to Version 1.2.

4.Until the storage is needed again, disable requests to the storage account.

In the Settings section, select the Configuration blade.
Ensure Allow storage account key access is Disabled.

Be sure to Save your changes.

5.Ensure the storage account allows public access from all networks.

In the Security + networking section, select the Networking blade.
Ensure Public network access is set to Enabled from all networks.

Be sure to Save your changes.

DEV Community: oluoma stella onyeukwa

Building a Windows VM on Azure and installing Windows Server (IIS) on it.

How to Set Up an Azure Virtual Network

What is a virtual network?

Tasks

1. Create hub and spoke virtual networks and subnets

2. Create the Hub-vnet virtual network configuration. This virtual network has the firewall subnet.

3. Configure a peer relationship between the virtual networks

Creating an Amazon EC2 instance and installing the IIS web server.

Table of contents

Step 1: Sign in into AWS management console and create the EC2 instance.

Step 2: Connect to the instance and create the IIS web server

Step 3: Create the IIS web server.

How to use managed identity and role-based access control to provide security and storage for a new company app .

Step 1: Create the storage account and managed identity

Step 3:Configure the storage account to use the customer managed key in the key vault

Step 4: Configure an time-based retention policy and an encryption scope.

Setting up a shared file storage for the company offices

Table of contents

Step 1:Create and configure a storage account for Azure Files.

Step 2: Create and configure a file share with directory.

Step 3: Configure and test snapshots

Step 4: Configure restricting storage access to selected virtual networks.

Setting Up a Private Storage account for a Company

Skilling tasks

Step 1: Create a storage account and configure high availability.

Step 2 : Create a storage container, upload a file, and restrict access to the file.

Step 3 : Configure storage access tiers and content replication.

How to Create a High Availability Storage Account for a Public Website.

Step 1: Create a storage account with high availability.

Step 2: Create a blob storage container with anonymous read access

Step 3: Practice uploading files and testing access.

Step 4: Configure soft delete

Step 5: Configure blob versioning

CREATING AN AZURE RESOURCE GROUP AND CLOUD STORAGE

Table of contents