Forem: daniel shaibu

Perform basic Self-Service Password Rest (SSPR) tasks in Microsoft-Entra-Management-Tasks

daniel shaibu — Tue, 10 Mar 2026 18:08:06 +0000

In this exercise you will learn where the self-service password reset feature is located in Microsoft Entra and explore the process to configure it.

Open the Microsoft Entra admin center at https://entra.microsoft.com.
Log in using the credentials for your tenant.
From the menu on the left, open Protection submenu and then select Password reset.
Find the Self service password enabled bar.

Value What it means
None No users can use the SSPR feature
Selected Only members of the selected group(s) can use SSPR
All All users can use the SSPR feature

Set the value to Selected.
Select the text No groups selected.
Mark the Project23 group we created previously.
Use the Select button to complete your choice.
Save your configuration.

Perform basic Password Protection tasks in Microsoft-Entra-Management-Tasks

daniel shaibu — Tue, 10 Mar 2026 10:52:13 +0000

In this exercise you will explore the capabilities Microsoft Entra ID offers in protecting your password. You will see how you can automate and enforce a strong password, and use login restrictions to prevent password attacks.

View lock settings, and review duration and threshold values

Open the Microsoft Entra admin center at https://entra.microsoft.com.
Log in using the credentials for your tenant.
From the menu on the left, select Protection submenu and then select Authentication methods.

Note - You could also search on Password protection in the search bar at the top.

Select Password protection from the list.
Set the Custom smart lockout with the following values.

Field Value Description
Lockout threshold 5 How many times can you fail to login with

a password before your account locks.
Lockout duration 30 How many second the account should lock

when the threshold is reached.

Note - You can also configure a custom banned password list here.

Set Enforce custom list to Yes.
Enter the following values:
Contoso
London
Widget
Lab Tip - Your lab is being performed for a company called Contoso, located in London, and it makes Widgets. By enter these three words you block them from being part or a whole of a password.
Set the value for Mode to Enforced.
Select the Save item at the top of the screen.

Get-started-Microsoft-Entra-Management-Tasks

daniel shaibu — Sat, 07 Mar 2026 14:03:01 +0000

Overview of the Exercise
This exercise teaches you how to perform foundational identity tasks in Microsoft Entra ID, including:

Creating users

Assigning licenses

Resetting passwords

Deleting and restoring users

These are core admin skills for any cloud or IT role.

1. Create a New User
You begin by creating a standard cloud‑only user.

Steps

Sign in to the Microsoft Entra admin center. (https://entra.microsoft.com)
In the left menu, select Identity → Users.
Select All users → New user.
Choose Create new user.

Enter the required details: Username Name Password settings

2. Select the Properties tab
Set the values for
first and
last name:
User type to Member If you pick Guest, it will restrict the users capabilities.
Usage location to United States
Select the Review + create button
Select Create.

Select Create.

This adds the user to your directory.

Subtask 1 - Log in to confirm user

Open an InPrivate browsing window.
Connect to the Microsoft Entra admin center at the link https://entra.microsoft.com.

Task 2 - Add a license to the user

Open a new tab in your browser.
Connect to the Microsoft 365 admin center at https//:admin.microsoft.com.
If prompted, log in using the credentials for your tenant.
Find the menu on the left side of the screen.
Open the Billing item in the menu.
Select Licenses from the list.
When the list of licenses appears, select Microsoft Power Automate Free.
Select the + Assign licenses item.
Choose Brogeswar from the list (user created in previous task).
Select the Assign button at the bottom of the page.
Notice the message that you have successfully assigned a license.
Close the tab with Microsoft 365 admin center.

Task 3 - Invite an external user to your tenant

If not already open - Open a browser and connect to the Microsoft Entra admin center at https://entra.microsoft.com.
If prompted, log in using the credentials for your tenant.
In the left menu find the Identity section. Open it if not already opened.
Select Users then select All users.
Choose the option to Invite external user from the dropdown.
Enter the information for your new external user:

Field: Value
Email: ExtUser@testemail.com
Display name: External User
Message Thank you for joining the company for this short work project. We look forward to building this project together.

Select the Review + Create button.

Task 4 - Assign a role to a user

If not already open - Open a browser and connect to the Microsoft Entra admin center at https://entra.microsoft.com.
If prompted, log in using the credentials for your tenant.
In the left menu find the Identity section. Open it if not already opened.
Select Users then select All users.
Choose the user Bhogeswar Kalita create in the earlier task.
From the newly opened menu select Assigned roles.
At the top of the screen select + Add assignment.
From the Select role dropdown menu chose the role Attribute Definition Reader.
Select the Next button when it becomes available.
Choose the option Eligible for Assignment type. 11`. Select Assign.

How to Create a VPC in AWS

daniel shaibu — Thu, 26 Feb 2026 12:01:49 +0000

A Virtual Private Cloud (VPC) is the foundation of every AWS network. It lets you define your own IP ranges, create public/private subnets, attach gateways, and control traffic flow. VNet (Azure) serves a similar purpose in Azure — it’s the foundation of Azure networking, enabling communication between Azure resources, on-premises networks, and the internet. VNets define the overall address space and can be segmented into subnets. Security is managed using Network Security Groups (NSGs), which combine AWS SG and NACL functionality, and VNets support peering and VPN/ExpressRoute for hybrid connectivity.
Subnets exist within a VPC or VNet and divide the network into smaller, manageable segments. Each subnet has its own IP address range (CIDR block) and can be associated with specific route tables and security rules. In AWS, subnets are AZ-specific and can be public or private depending on routing to an Internet Gateway. In Azure, subnets are not tied to physical zones but are logical divisions of the VNet, often used for tiered application design and traffic isolation .

Key distinctions:

Scope: VPC/VNet define the entire virtual network, subnets are segments within them.

Function: VPC/VNet handle global network configuration (address space, connectivity), subnets handle resource grouping and traffic control.

Connectivity: VPC/VNet connect to other networks (on-premises, internet), subnets control internal segmentation.

Security: VPC (AWS) uses SG + NACL; VNet (Azure) uses NSG; subnets inherit and apply these rules at their level.

Example: For a 3-tier app —

VPC/VNet: Encompasses all tiers.

Subnets: Separate ones for web, application, and database layers for isolation and security.

AWS: VPC (10.0.0.0/16)
├── Public Subnet (10.0.1.0/24) - Web servers
├── Private Subnet (10.0.2.0/24) - App servers
└── Private Subnet (10.0.3.0/24) - Database
Azure: VNet (10.1.0.0/16)
├── Subnet-Frontend (10.1.1.0/24)
├── Subnet-App (10.1.2.0/24)
└── Subnet-DB (10.1.3.0/24)
Copy
This layered approach ensures security, scalability, and efficient traffic management in both AWS and Azure environments.

Step‑by‑Step Guide on How to Create a VPC in AWS

Step 1 — Open the Amazon VPC Console

Sign in to the AWS Management Console.
In the search bar, type VPC and open Amazon VPC.
On the left menu, select Your VPCs.

Step 2 — Start the VPC Creation Wizard
AWS provides two options:

VPC and more (recommended — creates subnets, route tables, and gateways automatically)
VPC only (creates only the VPC)

For most tutorials and DEV articles, choose Create VPC → VPC and more.

Step 3 — Configure VPC Settings
Fill in the following fields:

VPC Settings
Name tag: my-vpc

IPv4 CIDR block: 10.0.0.0/16 (common beginner-friendly range)

Tenancy: Default

Subnets
Choose:

Number of Availability Zones: 1

Public subnets: 1

Private subnets: 1

Gateways & Routing
Make sure these are enabled:

Create an Internet Gateway

Create a NAT Gateway (for private subnet outbound access)

Step 4 — Review and Create

Step 5 - create subnet ( you create the subnet inside the VPC)
In the search bar, search for subnet

click on create subnet

configure the subnet

create subnet

Step 6 - create an internet gateway
on the search bar, search for internet gateway

click on create internet gateway

Configure the internet gateway

Step 7 - create a route table
in the search bar, search for route table

Click on the create route table

Give it a name and select the VPC and click on create route table

Create and Configure Network Security Groups (NSGs)

daniel shaibu — Tue, 17 Feb 2026 21:56:57 +0000

This exercise focuses on securing traffic inside app‑vnet by using Network Security Groups (NSGs) and Application Security Groups (ASGs). You’ll create rules for frontend web servers and backend database servers, then deploy two VMs to test the configuration.

Scenario
Your organization needs tighter control over traffic inside the virtual network. The requirements are:

Frontend subnet hosts web servers accessible from the internet
These servers must be grouped using an Application Security Group (ASG)
Backend subnet hosts database servers
Backend traffic must only be reachable from the frontend servers
Two Ubuntu VMs (VM1 and VM2) will be deployed for testing

Step-by-Step Instructions
1. Deploy the Required Virtual Machines
The lab provides an ARM template to deploy VM1 (frontend) and *VM2 *(backend).

Open Azure Cloud Shell (PowerShell).
Run the deployment command :
Create two VMs (vm1 & vm2) windows and ubutu respectively

2. Create the Application Security Group (ASG)

In the Azure portal, search for Application security groups.
Select + Create.
Configure:
Resource group: RG1
Name: app-frontend-asg
Region: Norway East

3. Associate the ASG with VM1

Open VM1 in the Azure portal.
Go to Networking → Application security groups.
Select Add application security groups.
Choose app-frontend-asg → Add.

This step ensures VM1 is part of the frontend ASG, as required in the exercise

4. Create the Network Security Group (NSG)

Search for Network security groups.
Select + Create.
Configure:
Resource group: RG1
Name: app-vnet-nsg
Region: Norway East
Select Review + create, then Create

5. Associate the NSG with the Backend Subnet
Open app-vnet-nsg.
Go to Subnets → + Associate.
Select:
- Virtual network: app‑vnet
Subnet: backend
- Select OK.

6. Create the NSG Rule to Allow Frontend → Backend Traffic

Open app-vnet-nsg.
Go to Inbound security rules → + Add.
Configure the rule:
Source: Application security group
Source ASG: app-frontend-asg
Destination: Any
Service: SSH (as defined in the lab)
Action: Allow
Priority: 100
Name: AllowSSH

Save the rule.

[Boost]

daniel shaibu — Sat, 14 Feb 2026 13:54:25 +0000

Create and configure virtual networks

daniel shaibu ・ Feb 14

#devops #cloud #aws #github

Create and configure virtual networks

daniel shaibu — Sat, 14 Feb 2026 13:22:52 +0000

This exercise walks you through building a simple hub‑and‑spoke network architecture in Azure. You’ll create two virtual networks, configure subnets, and establish secure VNet peering between them.

Scenario
Your organization is migrating a web-based application to Azure. To prepare the environment, you must:

Create two VNets: app‑vnet (spoke) and hub‑vnet (hub)

Add subnets for frontend, backend, and firewall

Peer the VNets so they can communicate privately

Step-by-Step Instructions

ii. In the search bar, type Virtual Networks and open the service.

**

Create the app‑vnet Virtual Network**
Select + Create.
Configure the VNet using the following values:

Property: Value
Resource group: RG1
Virtual network name: app-vnet
Region: East US
IPv4 address space: 10.1.0.0/16

Add the **frontend **subnet:

Name: frontend
Address range: 10.1.0.0/24

Add the **backend **subnet:

Name: backend
Address range: 10.1.1.0/24

Leave all other settings at their defaults.
Select Review + create, then Create.

3. Create the hub‑vnet Virtual Network
Repeat the creation process with these values:

Property Value
Resource group: RG1
Name: hub-vnet
Region: East US
IPv4 address space: 10.0.0.0/16
Subnet name: AzureFirewallSubnet
Subnet range: 10.0.0.0/26

Once deployed, verify both VNets and their subnets appear in the Virtual Networks list.

4. Configure VNet Peering
Now connect the two VNets so they can communicate privately.

Open app‑vnet.

In the left menu, select Peerings.

Choose + Add.

Configure the peering:

Property Value
Remote peering link name: app-vnet-to-hub
Virtual network: hub-vnet
Local peering link name: hub-to-app-vnet

Leave all other settings as default.
Select Add.

After deployment, confirm the Peering status shows Connected.

Create a new Azure Key Vault

daniel shaibu — Mon, 26 Jan 2026 12:18:38 +0000

To create a new Azure Key Vault, use the Azure portal to define your vault’s name, region, and access controls. This secure store helps manage secrets, keys, and certificates for cloud applications.

Step-by-Step: Creating an Azure Key Vault via Azure Portal

Sign in to the Azure portal using the same credentials you used to activate the Azure Sandbox.
Select Create a resource. The Create a resource pane appears.
In the Search services and marketplace, search for and select Key Vault to find the Azure Key Vault service. The Key Vault pane appears. Select Create. The Create key vault pane appears.
On the Basics tab, enter the following values for each setting. Setting Value Subscription: From the dropdown, select your subscription. Resource group: From the dropdown, select your resource group.

Instance details

Key vault name: Enter a globally unique name for the new vault. Vault names must be 3-24 characters long and contain only alphanumeric characters and dashes. The exercise uses the example name of VaultamortDiary for the new vault.
Region: Accept default.
Pricing tier: Accept default.

Select Review + create.
After validation passes, select Create to create the Azure Key Vault.

After the deployment is complete, select Go to resource. Your Key vault pane appears

Add a secret

In the left menu pane, under Objects, select Secrets. The Secrets pane appears for your key vault.
In the top menu bar, select Generate/Import. The Create a secret pane appears.
Enter a name, value, and (optional) content type and Select Create to add the secret. The Secrets pane reappears.

Show the secret
Finally, verify that the secret value has been set.

Select your secret from the list. The Versions pane appears for your secret.
Select the CURRENT VERSION of the secret. The Secret Version pane appears.
Select Show Secret Value to see the value assigned to the secret.

Configuring Microsoft Defender for Cloud for Enhanced Protection

daniel shaibu — Mon, 26 Jan 2026 11:46:15 +0000

To configure Microsoft Defender for Cloud for enhanced protection, start by enabling Defender plans for your workloads, setting security policies, and activating threat detection features. This setup strengthens your cloud security posture across Azure, hybrid, and multi-cloud environments.

*Step-by-Step Guide to Configuring Microsoft Defender for Cloud
*

Start a browser session and sign-in to the Azure portal menu.
In the Azure portal, in the Search resources, services, and docs text box at the top of the Azure portal page, type Microsoft Defender for Cloud and press the Enter key
On the Microsoft Defender for Cloud, Management blade, go to the Environment settings. Expand the environment settings folders until the subscription section is displayed, then click the subscription to view details.

In the Settings blade, under Defender plans, expand Cloud Workload Protection (CWP).
From the Cloud Workload Protection (CWP) Plan list, select Servers. On the right side of the page, change the Status from Off to On, then click Save.

Auto Scaling Role & Azure Virtual Machine Scale Sets (VMSS)

daniel shaibu — Fri, 09 Jan 2026 16:18:29 +0000

Both AWS and Azure need a way for their scaling services to perform actions on your behalf—like creating, deleting, or managing virtual machines.
They just implement it differently.

AWS: Auto Scaling Service‑Linked Role
In AWS, Auto Scaling uses a service‑linked IAM role.
This role allows Auto Scaling to:

Launch and terminate EC2 instances
Attach/detach load balancers
Read CloudWatch alarms
Update scaling groups

It’s an IAM role automatically created and only Auto Scaling can assume it.

Think of it as:
“Auto Scaling’s permission slip to manage EC2 resources.”

Azure: VM Scale Sets (VMSS) + Managed Identity
Azure doesn’t use IAM roles the same way.
Instead, VM Scale Sets use a Managed Identity (system‑assigned or user‑assigned).

This identity allows VMSS to:
Access Azure APIs
Pull secrets from Key Vault
Interact with storage accounts
Register with load balancers
Perform scaling operations.
It’s the Azure equivalent of giving VMSS a secure identity to act on your behalf.

How to Create a VM Scale Sets (VMSS)
A VM Scale Set lets you deploy and manage a group of identical virtual machines that automatically scale based on demand.
1. Create a Resource Group
A resource group is the logical container for your VMSS.

In Azure search for resources group and select resource group
click on create and fill the name, location and select region the click on review & create and then create.

2. Create the VM Scale Set
az vmss create \
--resource-group vmssResourceGroup \
--name myScaleSet \
--image windows\
--upgrade-policy-mode manual\
--admin-username azureuser \
--generate-ssh-keys

Note: This command creates:
A VM Scale Set
A load balancer
A default number of VM instances
SSH access

Scale In or Out Manually

Go to setting in the overview and select availability + scaling and select scale

**Steps to Create an Auto Scaling Group (AWS)

Create a launch template This defines how each EC2 instance should look (AMI, instance type, key pair, security group, etc.).

Go to: EC2 Console → Launch Templates → Create launch template

Name: e.g. web-server-template

Source template: None (for first time)

AMI: Choose your OS (e.g. Amazon Linux 2)

Instance type: e.g. t3.micro

Key pair: Select or create one

Network settings: Security group allowing HTTP (80) + SSH (22) if needed

User data (optional): Add bootstrap script (e.g. install nginx)

Click Create launch template

This template will be referenced by the Auto Scaling Group.

Open the AWS and search for Auto scaling group and select
Select Get started

How to Create an Elastic Beanstalk Application (Step‑by‑Step)

daniel shaibu — Tue, 06 Jan 2026 12:31:11 +0000

intro: Elastic Beanstalk is one of AWS’s easiest ways to deploy applications because it automatically handles provisioning, load balancing, scaling, and monitoring for you. You focus on your code — AWS handles the infrastructure.
According to AWS documentation, Elastic Beanstalk lets you deploy, monitor, and scale web applications with minimal setup.
Key Uses
Deploying web applications easily
You upload your code, and Elastic Beanstalk automatically handles provisioning EC2 instances, load balancers, scaling groups, and monitoring.

Automating infrastructure setup
It configures compute, load balancing, auto‑scaling, and health checks for you, reducing operational complexity.

Running apps in multiple languages:
Supports Go, Java, .NET, Node.js, PHP, Python, and Ruby out of the box.

Processing background tasks
It offers worker environments for processing SQS messages—useful for asynchronous or long‑running jobs.

Handling scaling automatically
It dynamically scales your environment based on demand, so your app can grow without manual intervention.

Note: In Azure, the closest equivalent to AWS Elastic Beanstalk is Azure App Service.

*1. Open the AWS Elastic Beanstalk Console
*

Sign in to the AWS Management Console
Search for Elastic Beanstalk
Click Create Application

*2. Create an Application
*

Application Name

3. Choose a Platform
Elastic Beanstalk supports multiple platforms, including:
Node.js, Python, Java, .NET, PHP, Go, Docker

4. Upload Your Application Code
You have two options:

Option A: Use a Sample Application
Great for testing.
Elastic Beanstalk will deploy a pre‑built demo app.

Option B: Upload Your Code
Upload a .zip file containing your application source bundle.

5. Configure Your Environment
Elastic Beanstalk environments are collections of AWS resources (EC2, load balancers, scaling groups) that run your app

Service role: click on create role
A service role is an IAM role that Elastic Beanstalk itself assumes so it can manage your environment on your behalf. Think of it as the permissions Elastic Beanstalk needs to do its job. the service role is required so Elastic Beanstalk can: Create and manage AWS resources (like EC2 instances, load balancers, Auto Scaling groups), Monitor environment health, Write logs and metrics to CloudWatch, Access S3 buckets for application versions, Perform updates and deployments, Interact with other AWS services securely and automatically. Elastic Beanstalk cannot perform these actions unless it has a service role with the correct IAM managed policies attached.
Without a service role: Your environment cannot be created,
Elastic Beanstalk cannot provision or update resources, Health monitoring and logging will fail, Deployments may not work.
It’s essentially the “administrator badge” Elastic Beanstalk uses to operate your environment safely and automatically.
Go back to the Configure service access page and click on the refresh button and the role will automatically appear
Creating an EC2 instance profile: click on create

An EC2 instance profile is simply the identity your EC2 instance uses to access AWS services securely without storing credentials on the server. An EC2 instance profile gives your EC2 instance the permissions it needs to interact with other AWS services. It is the bridge between the EC2 instance and an IAM role.
Depending on the permissions in the attached IAM role, the instance can: Read/write objects in S3, Send logs to CloudWatch Logs, Pull secrets from Systems Manager Parameter Store, Access DynamoDB tables, Use X-Ray for tracing, Register with Elastic Load Balancing, Communicate with Elastic Beanstalk during deployments.

Note: Service Role → Permissions for Elastic Beanstalk itself.
Instance Profile → Permissions for the EC2 instance running your app.

EC2 key pair - optional: open a AWS in a new tab and type key pair in the search bar. An EC2 key pair is used to securely connect to your EC2 instance. It acts as your login credential for the server.

Go back and select the key just created
Select default VPC
Enable Public IP address and select on subnet and click on next
select everything as default
Leave as default and select next
On Monitoring, Health reporting choose Enhanced and select and CloudWatch Custom Metrics and CloudWatch Custom Metrics - Environment then scroll down and click next

Wait for Environment Health = “OK” Once the environment is ready, you’ll see: Health: OK A green checkmark A link to your running application Click the link to open your deployed app in the browser.

How to Deploy and Configure Azure Monitor

daniel shaibu — Thu, 01 Jan 2026 19:31:35 +0000

Intro: Azure Monitor is Microsoft’s unified monitoring solution for collecting metrics, logs, and insights across your Azure resources. To configure it properly, you typically follow these stages:

1. Prepare Your Azure Environment
From the Azure Portal:

Search Resource Groups
Select Create
Name it rg-alpha
Region: East US
Click Review + Create → Create

note: This group will hold all the resources Azure Monitor will observe.

**2. Create a Security Group (Optional but used in the **lab)
This group is used for log access permissions.

Search *Azure Active Directory / Entra ID *
Go to Groups → New Group
Group type: Security
Name:** App Log Examiners**
Create the group

3. Deploy Virtual Machines to Monitor
Azure Monitor needs resources to collect data from. The lab deploys two VMs:
A. Deploy Windows VM (WS‑VM1)

Search Virtual Machines → Create
Name: WS-VM1
Region: East US
Image: Windows Server 2022 Datacenter
Size: Standard_D4s_v3
Admin user:** prime**
Password: (your secure password)
Allow inbound port: RDP 3389
Create the VM

Configure Networking

Wait for the deployment to complete. Once deployment completes choose Go to resource.
On the WS-VM1 properties page, choose Networking.
On the Networking page, select the RDP rule.
On the RDP rule space, change the Source to My IP address and choose Save. This restricts incoming RDP connections to the IP address you’re currently using.
On the Networking page, choose Add inbound port rule.
On the Add inbound security rule page, configure the following settings and choose Add:
Source:** Any**
Source: **** *
Destination: Any
Service: HTTP
Action: Allow
Priority: 310
Name: AllowAnyHTTPInbound
On the WS-VM1 page, choose Connect.
Under Native RDP, choose Select.
On the Native RDP page, choose Download RDP file
and then open the file. Opening the RDP file opens the Remote Desktop Connection dialog box
On the Windows Security **dialog box, choose **More Choices and then choose Use a different account.
Enter the username as .\prime and the password as the secure password you chose in Step 3, and choose OK
When signed into the Windows Server virtual machine, right-click on the Start hint and then choose Windows PowerShell (Admin).
At the elevated command prompt, type the following command and press Enter. Install-WindowsFeature Web-Server -IncludeAllSubFeature -IncludeManagementTools
When the installation completes run the following command to change to the web server root directory. cd c:\inetpub\wwwroot\
Run the following command. Wget https://raw.githubusercontent.com/Azure-Samples/html-docs-hello-world/master/index.html -OutFile index.html
When signed into the Windows Server virtual machine, right-click on the Start hint and then choose Windows PowerShell (Admin).
At the elevated command prompt, type the following command and press Enter. Install-WindowsFeature Web-Server -IncludeAllSubFeature -IncludeManagementTools
At the elevated command prompt, type the following command and press Enter. Install-WindowsFeature Web-Server -IncludeAllSubFeature -IncludeManagementTools
When the installation completes run the following command to change to the web server root directory. cd c:\inetpub\wwwroot\

4. Deploy a Linux VM (Linux‑VM2)
Create the VM

Name: Linux-VM2
Resource Group: rg-alpha
Availability options: No infrastructure redundancy required
Image: Ubuntu Server 20.04 LTS
Size: Standard_D2s_v3
VM architecture: x64
Username: prime, Password: (your secure password)

Review the information and choose Create.

Add Monitoring Extension

After the VM deploys, open the VM properties page and choose Extensions + Applications under Settings
Choose Add and select the Network Watcher Agent for Linux. Choose Next and then choose Review and Create. Choose Create.

Deploy a web app with an SQL Database

In your browser, open a new browser tab and navigate to https://github.com/Azure/azure-quickstart-templates/tree/master/quickstarts/microsoft.web/web-app-sql-database
On the GitHub page, choose Deploy to Azure.
A new tab opens. If necessary, re-sign into Azure with the account that has Global Administrator privileges.
On the Basics page, select Edit template.
In the template editor, delete the contents of lines 158 to 174 inclusive and delete the “,” on line 157. Choose Save.
On the Basics page, provide the following information and choose Next.
Subscription: Your subscription
Resource Group: rg-alpha
Region: East US
Sku Name: F1
Sku Capacity: 1
Sql Administrator Login: prime
Sql Administrator Login Password : [Select a unique secure password] P@ssw0rdP@ssw0rd
Review the information presented and select Create.
Review the information presented and select Create
After the deployment completes, choose Go to resource group.