Azure is one of the most popular cloud platforms, and many learners are eager to get started. However, beginners often feel overwhelmed due to the wide range of services and concepts. If you have no prior experience in cloud computing or Azure, the best place to start is with Azure Fundamentals (AZ-900). In this blog series, we will cover both theoretical concepts and practical hands-on exercises to help you build a strong foundation in Microsoft Azure.

We will also provide a real-world, enterprise-level roadmap to guide your learning journey step by step.


For Phase 1 (Cloud Fundamentals) the topics I listed are sufficient to understand Azure basics, but if your goal is to prepare properly for Microsoft Certified: Azure Fundamentals (AZ-900) and to build a solid base for later phases, you should expand Phase 1 slightly. 

Think of Phase 1 as “cloud literacy + Azure platform orientation.
Below is a complete but still beginner-level Phase 1 syllabus.


Phase 1 — Azure Fundamentals (Expanded)

Focus on understanding how the Microsoft Azure ecosystem works.

Fundamentals of Azure like -

1) Fundamentals of Cloud
2) Different types of services in the cloud
3) Different types of services which are present in azure with each categories : Compute, Storage, Networking, storage services and a wide verity of other categories.

This would help you get a quick start into azure.

• Define cloud computing.
• Describe the shared responsibility model.
• Define cloud models, including public, private, and hybrid.
• Identify appropriate use cases for each cloud model.
• Describe the consumption-based model.
• Compare cloud pricing models.

Define Cloud Computing - Cloud computing is a technology with delivery of computing services over the internet and allow the user to access and use computing resources such as servers, storage, database, networking, software over the internet. Usually on a pay-as-you-go basis. 

Cloud services also expand the traditional IT offerings to include things like internet of things (IoT), machine learning (ML) and artificial intelligence (AI). Services is providing over the internet so it doesn't have to be constrained by physical infrastructure the same way that a traditional datacenter is.

If you need to increase your IT infrastructure rapidly, you don't have to wait to build a new datacenter.

CapEx vs OpEx in azure

In this CapEx capital expenditure, this is the classic old model. Its a huge onetime purchase of a physical things in company own for years. A whole building, data center build-out, fleet of vehicles, giant rack of computer servers.

These assets lose value over time. That's called depreciation. Cost type upfront, one time investment.

In this OpEx operational expenditure, this is involves paying for services ona usage-based, subscription model (eg. pay-as-you-go virtual machines, Storage costs, SaaS applications). Azure enables a shift to OpEx, enhancing flexibility, eliminating upfront costs, and improving agility.

Why shift to OpEx in azure ?

Quickly deploy resources without waiting for procurement with pay only for what we use policy, rather than buying for peak demand.

It is easily scale up or down as needs change.

☁️ Key Characteristics of Cloud Computing in Azure

when using Microsoft Azure, you get several powerful capabilities :

1. High Availability 

High availability ensures that your application are always up and running, with minimal downtime.


👉 Azure achieves this using:

• Multiple data centers (Regions)
• Redundancy (backup systems)
• Load balancing 

Example : If one server fails, another automatically takes over.


1) Redundancy - Azure provides high availability and durability by replicating data across multiple locations, protecting against hardware failures, data center outages, or regional disasters.

Storage options such as Locally Redundant Storage (LRS), Zone-redundant storage (ZRS), and Geo-redundant storage (GRS), providing flexibility to balance cost with data protection needs.


2) Load Balancer - A load balancer is service or device that distributes incoming internal traffic across multiple servers to ensure no single server becomes overwhelmed. It helps improve the availability, reliability and performance of application by balancing the load efficiently.

2. Scalability

Scalability means the ability to increase or decrease resources based on the demand.

👉 Types:

Vertical scaling -> Increase power (CPU, RAM)
Horizontal scaling -> Add more servers


📌 Example:

Your website (hackingtruth.org) gets more users -> you add more virtual machines.

3. Elasticity 

 

Elasticity is automatic scaling in real-time.

Difference from scalability :

Scalability -> manual or planned
Elasticity -> automatic and dynamic


📌 Example:

Traffic spikes during a sale -> Azure auto-scales resources -> traffic drops -> resources reduce automatically.

4. Fault Tolerance 

 

Fault tolerance ensures that a system continues to operate even if part of it fails.


Azure uses :

• Replication
• Availability zones
• Backup systems

📌 Example:

If one component crashes, the system still works without interruption.




5. Disaster Recovery (DR)

Disaster recovery is the ability to recover data and systems after a major failure.

👉 Covers events like:

Natural disasters
Data center outages
Cyber attacks


📌 Azure solutions:

Backup services
Geo-redundancy
Site-recover

📌 Example:

Entire region goes down -> your app is restored in another region.

Describe the shared responsibility model

Shared responsibility model in Microsoft azure defines who is responsible for what when using cloud services.

It is handles some part of security, and you as a customer handle the rest.


With the shared responsibility model, these responsibilities get shared between the cloud provider and the consumer. Physical security, power cooling, and network connectivity are the responsibility of the cloud provider. just opposite at the same time consumer is responsible for data and the information stored in the cloud. The consumer is also responsible for access security, meaning you only give access to those who need it.

Even for some things, the responsibility depends on the situation. If you're using a cloud SQL database.

• Microsoft manages the cloud infrastructure.
• You (customer) manage what you deploy and configure.

⚙️ Responsibilities Breakdown

☁️ Microsoft (Azure) is responsible for:

• Physical data enters.
• Hardware (servers, storage, networking)
• Physical Security
• Power, cooling, and networking infrastructure.

👉 This is often called:
“Security OF the cloud”




👤 You (Customer) are responsible for:

• Data (your files, databases)
• User access & identify (who can log in)
• Application you deploy
• Configuration of services

👉 This is often called:
“Security IN the cloud”


With an on-premises datacenter, you're responsible for everything. With cloud computing, those responsibilities shift. 

• IAAS (Infrastructure as a service)
• PAAS (Platform as a service)
• SAAS (Software as a service)

1) IAAS - Infrastructure as a service places the most responsibility on the consumer, with the cloud provider being responsible for the basics of physical security, power and connectivity.

2) SAAS - Software as a service places most of the responsibility with cloud provider. 

 

3) PAAS - Platform as a service being a middle ground between IaaS and SaaS, rests somewhere in the middle and evenly distributes responsibility between the cloud provider and the consumer.


IaaS (Infrastructure as a service) 

Example: Virtual Machines

Azure -> Hardware, network
You -> OS, updates, apps, security

👉 You have maximum control + maximum responsibility

2. PaaS (platform as a service)

Example: App services, Azure SQL

Azure -> OS, runtime, infrastructure
You -> Application + data

👉 Balanced responsibility

3. SaaS (Software as a service)

Example: Microsoft 365

Azure -> almost everything
You -> data + user access

👉 Least responsibility for you

📊 Simple Analogy

Think of it like housing:

• On-premises → You own the whole house 🏠
• IaaS → You rent a house (you manage inside)
• PaaS → You rent a furnished apartment
• SaaS → You stay in a hotel

🧾 Final One-Line Summary

👉 Azure secures the infrastructure, you secure your data and configurations.

Cloud Models 

The cloud models define the deployment type of cloud resources. The main cloud models are: public, private and hybrid



1. Public Cloud - A public cloud is owned and operated by a third party cloud provider, where services and resources are delivered over the internet. 



👉 Examples:

 Gmail, Microsoft Azure, Dropbox etc.


✅ Key Features:

No upfront hardware cost
Pay-as-you-go pricing
Highly scalable
Managed by provider

📌 Example:

Hosting a website on Azure without owning any servers.

2. Private Cloud

A private cloud is used exclusively by a single organization. Private cloud provides much greater control for the company and its IT department. However, it also comes with greater cost and fewer of the benefits of a public cloud deployment. Finally, a private cloud may be hosted from your on site datacenter. 

It can be:

• On-premises (your own data center)
• Or hosted by a cloud provider

Key features:

• Full control over infrastructure 
• Higher security and customization
• More expensive than public cloud

📌 Example:

A bank running its own secure data center.



3. Hybrid Cloud 

A hybrid cloud is a combination of public cloud + private cloud, allowing data and applications to be shared between them.

Key features:

• Flexibility
• Data control + scalability
• Best of both worlds

📌 Example:

• Sensitive data -> private cloud
• Web apps -> public cloud

📊 Visual Diagram (Blog-Ready)

🧾Final Takeaway

• Public Cloud → Best for scalability and cost
• Private Cloud → Best for control and security
• Hybrid Cloud → Best for flexibility

Dell Command | Update error  

Your screen shows Dell Command | Update error because Dell Client Management Service (DCMS) is missing. And the “dell.com not found” is happening due to a wrong/blocked link or network issue.

Let’s fix both properly 👇


 

🔧 ✅ Step 1: Use Correct Download Method (Don’t click that link)

Instead of clicking the popup link, do this manually:

Open browser

Go to:

👉 https://www.dell.com/support/home 

 and Type your Service Tag number ((from BIOS or sticker))

You will get System Model and Support Services and Warranty details - like basic support ended on november 27 2024. Dell command update error , dell driver and software download

Go to:
👉 Drivers & Downloads.

Scroll down and you will get Troubleshooting and Diagnostics where you can download  drivers or software updates.    laptop

Click on it. 

Search and install:

• Dell Command | Update
• Dell Client Management Service

After that again search on windows Dell command update  then we got it. 

Disclaimer

What is WDS with installation steps? 

Let me demonstrate a complete lab setup for you right here. Look—suppose we have a server; this is our physical server, within which we have already configured Active Directory. 


It hosts AD DS—meaning AD is running, DNS is running, and the AD DS role is active. It also requires DHCP; the DHCP services are present. With this foundation, we can proceed to configure WDS on this server. Let's explore the benefits we gain from configuring WDS. Imagine you have brought in a large number of client machines—say, 50 computers acquired from the market—on which you need to install a Windows operating system. 

This could be any Windows operating system—Windows 7, Windows 8, Windows 10, or any other version. If you need to install the same Windows operating system on 50 or 100 computers simultaneously, doing so manually using bootable media—such as a pen drive, CD, or DVD—would be an extremely time-consuming process. It would take a significant amount of time and prove quite difficult to perform on each machine individually. Microsoft devised a solution to this problem by enabling a specific feature within their server operating systems. If we look back at Server 2003 or 2008, this feature was known as RIS (Remote Installation Services); however, starting with Server 2008 R2, it was renamed WDS—Windows Deployment Services.

Installation Steps

With the help  Dell DA310 USB-C Mobile Adapter, 7-in-1 , Type C Laptop Compatible - Dock and Adapter we will do installation of windows 11. 

 After connecting dock with ethernet cable and connect Dock's C with C type laptop (we have a dell laptop without ethernet port so we are using this one).

Restart the system and when logo will come then continuously press F12 (according to dell) and this interface will come so choose NIC (IPv4) or Onboard NIC(ipv4).

 then it is automatically detect server IP address and installation path.

Here write your computer name as you want and then domain name and click next. 

Change your timezone according to your timezone. click next.

Then we will choose E3 - MS office Enterprise. Click next. 

from my side no change simple click next. as it not necessary. 

In the last step click finish. then it will automatically installation here we go then restart. after open system update with dell command in windows search and also search in windows check update and done.

 Check with Dell update if you got error - CLICK HERE 

Disclaimer

Microsoft-365-L1-Desktop-Support-guide

This article is designed as a practical, real-world L1 Desktop Support guide focused on troubleshooting Microsoft Outlook within a Microsoft 365 and Exchange Online environment. The goal is to help support engineers understand not just what to fix, but how to think during real helpdesk scenarios — from basic configuration to admin-level checks. Each section is structured around common ticket categories faced in enterprise environments. Whether you are preparing for an IT support role, improving troubleshooting workflow, or strengthening Microsoft 365 operational knowledge, this series will provide structured, actionable guidance. The content bridges the gap between end-user issues and Microsoft 365 Admin Center/Exchange Online workflows used by support teams daily. Outlook License Issue

I will write article on each topic for single single blog -

I’ll break into real helpdesk categories:

1. Account & License Management
2. Outlook Configuration
3. Send/Receive Issues
4. Profile & OST/PST Issues
5. Performance Issues
6. Mailbox & Storage
7. Archive & Backup
8. Exchange Admin Checks
9. Authentication/Login Problems
10. Common Errors & Fixes

Today we will see step by step Account & License Management  

Outlook Slow Performance

As per ITIL approach -

Step 1 - user verification 
step 2 - Initial L1 checks
step 3 - TroubleShooting
step 4 - Escalation 

 
Check:

OST size > 10GB
Too many add-ins
Indexing problem
Antivirus scanning emails
Large mailbox


Fix:

Disable add-ins
Compact PST
Repair Outlook
Rebuild profile


= Disable unnecessay add-ins.
= clerar cache and temporary files 
= update outlook to the lates version.

but in OST cache file 
go this this directory 
C:\Users\%username%\AppData\Local\Microsoft\Outlook

but do not delete simply 
RENAME Only
mailbox.ost → mailbox_old.ost
Reopen Outlook → fresh sync.

Use when:

Outlook very slow
Sync issues
Large mailbox lag


-----

Steps:

Open Microsoft Outlook
Click File
Go to Options
Select Add-ins (left side)

You will see:

Active Add-ins
Inactive Add-ins
COM Add-ins

Disable Add-ins:

At bottom → Manage: COM Add-ins
Click Go
and disable unnecessary plugins - zoom, Skype, Adobe PDF etc 

OR 

= Disable unnecessay add-ins.
Win + R
outlook.exe /safe


For Outlook slow performance I will check File → Options → Add-ins → Manage COM Add-ins and disable unnecessary plugins. I will also verify performance using Outlook Safe Mode.”

Disclaimer

How to delete disable the user account ?

Lets start with types of user account in windows. Here we are write few types of windows account - 

• Administrator
• user_standard / Local / Domain / Microsoft / Network etc
• Guest 

The account we create at the time of installation is called as user with administrative rights.

Administrator Account - The account have the full control over the system, can install / uninstall software, change system setting, manage users and modify security, This account will be used by the individual to manage, monitor and troubleshoot the account.  

Standard User Account (Local User) - This account is having limited permission, allows basic task like running application and changing personal settings ,This cannot install software or change system wide settings. This account is allowed for doing its daily basic task, what it is allowed for  

Guest Account (Deprecated in newer version) - Designed for temporary access with minimal permission.

Local Account - This account which, exist on a specific computer and is not connected to a network domain. This can a administrator or standard user account we also call as a standalone user.

Domain User Account - This is account managed by a domain controller in an active directory environment. This allows users to log in from any computer within the domain using the same credentials. This is generally controlled by IT administrator for security and access management.

How to delete disable the user account ?

 -- Press win + r and type  "lusrmgr.msc" without quotes.

-- After open click on "users"

-- Then go to "users" >  right click on that user account that you are looking to disable >  Then click on the option "properties" > check the box > account is disable > Click on apply > then  after "OK". 

 -- If you want to delete then follow this one after disabling the account. Then again right click on the user account > then select the option "delete" > one dialog box will appear click on the option "confirm" Here you deleted the account.

Disclaimer

Microsoft-365-L1-Desktop-Support-guide

This article is designed as a practical, In enterprise environments, user account lockouts are one of the most common tickets handled by L1 Desktop Support teams. These issues typically occur due to multiple incorrect password attempts, expired credentials, VPN authentication failures, or cached password mismatches. As an L1 engineer, your responsibility is to perform proper user verification, validate the account status in Active Directory Users and Computers (ADUC), and resolve the issue without causing security risks. This guide explains the standard real-world workflow followed in IT helpdesk environments.

I will write article on each topic for single single blog -

I’ll break into real helpdesk categories:

1. Unlock user
2. Reset password
3. Enable / Disable account
4. Create new user
5. Add user to group
6. Remove user from group
7. Check login issues
8. Move user to correct OU
9. Basic permission via groups

Today we will see step by step Account & License Management  

👤 SCENARIO 1 — User Account Locked

 

✅ Step 1 — User Verification (Call / Ticket Triage)



Before accessing Active Directory, gather clear information from the user.


Ask the following:

• What exact error message are you receiving?
• Are you seeing “Account Locked” or “Incorrect Password”?
• Since when did the issue start?
• Are you trying to login to:
• Windows domain login?
• VPN?
• Outlook / Microsoft 365?
• Did you recently change your password?
• Are you logged into multiple devices (laptop + mobile)?

🎯 Objective:

• Confirm whether this is:
• A simple password mistake
• A cached credential issue
• A real domain account lockout

✅ Step 2 — Initial L1 Check in Active Directory

Now verify the account status.

Navigate to:

Tools → Active Directory Users and Computers (ADUC)
(Available on Domain Controller or Admin machine with RSAT tools installed)

Steps:

Search for the user account.

Right-click on the user.

Select Properties.

Check the Following:

✔ Is the account locked?
✔ Is the account disabled?
✔ Is the password expired?
✔ Check Account expiration date

✅ Step 3 — Troubleshooting & Resolution

If the account is locked:

Go to:

Right-click User → Properties → Account Tab

Perform Required Action:

✔ Tick Unlock Account
✔ Click Apply / OK

If password reset is required:

✔ Click Reset Password
✔ Set temporary password
✔ Select User must change password at next logon



⚠ Important Best Practice:


Always confirm user identity before resetting passwords (Employee ID / Manager confirmation / Ticket validation).

• 🔎 Additional Checks (If Required)
• If the account locks again immediately:
• Check if user is connected to VPN.
• Ask user to log out from mobile email apps.
• Clear cached credentials in Windows Credential Manager.
• Check mapped drives using old password.
• Verify scheduled tasks running under old credentials.
• Repeated lockouts often indicate:
• Background service using outdated password
• Mobile device syncing with old password
• Stored credentials on another machine

🚨 Step 4 — Escalation Criteria

• Escalate to L2 / AD Team if:
• Account locks repeatedly within minutes
• Possible brute force attack suspected
• Multiple failed login attempts from unknown IP
• Domain Controller replication issue
• Security policy conflict
• Account locked across multiple domain controllers
• Document before escalation:
• Time of unlock
• Event Viewer logs (if checked)
• Number of failed attempts
• User device details

📝 Real Helpdesk Documentation Format Example

Issue: User unable to login – Account Locked
Root Cause: Multiple incorrect password attempts
Action Taken: Verified identity → Unlocked account in AD → Reset password → Advised password change

Status: Resolved

🎯 L1 Engineer Interview Tip

If asked: “How do you handle a locked user account?”


You can say:

“First, I verify the issue with the user and confirm the error message. Then I check the account status in Active Directory Users and Computers. If the account is locked, I unlock it under the Account tab and reset the password if necessary. If the account locks again, I investigate possible cached credentials or background authentication attempts. If it appears to be a security concern or domain issue, I escalate to L2.”

✅ Quick Checklist Summary

✔ Verify user
✔ Check ADUC
✔ Unlock account
✔ Reset password if required
✔ Monitor repeated lockouts
✔ Escalate if suspicious

Disclaimer

Microsoft-365-L1-Desktop-Support-guide

This article is designed as a practical, in enterprise environments, user account lockouts are one of the most common tickets handled by L1 Desktop Support teams. These issues typically occur due to multiple incorrect password attempts, expired credentials, VPN authentication failures, or cached password mismatches. As an L1 engineer, your responsibility is to perform proper user verification, validate the account status in Active Directory Users and Computers (ADUC), and resolve the issue without causing security risks. This guide explains the standard real-world workflow followed in IT helpdesk environments.

I will write article on each topic for single single blog -

I’ll break into real helpdesk categories:

1. Unlock user
2. Reset password
3. Enable / Disable account
4. Create new user
5. Add user to group
6. Remove user from group
7. Check login issues
8. Move user to correct OU
9. Basic permission via groups

Today we will see step by step Account & License Management  

👤 SCENARIO 1 — User Account Locked

✅ Step 1 — User Verification (Call / Ticket Triage)



Before accessing Active Directory, gather clear information from the user.

Ask the following:

• What exact error message are you receiving?
• Are you seeing “Account Locked” or “Incorrect Password”?
• Since when did the issue start?
• Are you trying to login to:
• Windows domain login?
• VPN?
• Outlook / Microsoft 365?
• Did you recently change your password?
• Are you logged into multiple devices (laptop + mobile)?

🎯 Objective:

• Confirm whether this is:
• A simple password mistake
• A cached credential issue
• A real domain account lockout

✅ Step 2 — Initial L1 Check in Active Directory

Now verify the account status.

Navigate to:

Tools → Active Directory Users and Computers (ADUC)
(Available on Domain Controller or Admin machine with RSAT tools installed)

Steps:

• Search for the user account.
• Right-click on the user.
• Select Properties.

Check the Following:

• ✔ Is the account locked?
• ✔ Is the account disabled?
• ✔ Is the password expired?
• ✔ Check Account expiration date

✅ Step 3 — Troubleshooting & Resolution

If the account is locked:

Go to:

Right-click User → Properties → Account Tab

Perform Required Action:

✔ Tick Unlock Account
✔ Click Apply / OK

If password reset is required:

✔ Click Reset Password
✔ Set temporary password
✔ Select User must change password at next logon

⚠ Important Best Practice:

Always confirm user identity before resetting passwords (Employee ID / Manager confirmation / Ticket validation).

🔎 Additional Checks (If Required)

• If the account locks again immediately:
• Check if user is connected to VPN.
• Ask user to log out from mobile email apps.
• Clear cached credentials in Windows Credential Manager.
• Check mapped drives using old password.
• Verify scheduled tasks running under old credentials.
• Repeated lockouts often indicate:
• Background service using outdated password
• Mobile device syncing with old password
• Stored credentials on another machine

🚨 Step 4 — Escalation Criteria

• Escalate to L2 / AD Team if:
• Account locks repeatedly within minutes
• Possible brute force attack suspected
• Multiple failed login attempts from unknown IP
• Domain Controller replication issue
• Security policy conflict
• Account locked across multiple domain controllers
• Document before escalation:
• Time of unlock
• Event Viewer logs (if checked)
• Number of failed attempts
• User device details

📝 Real Helpdesk Documentation Format Example

Issue: User unable to login – Account Locked
Root Cause: Multiple incorrect password attempts
Action Taken: Verified identity → Unlocked account in AD → Reset password → Advised password change
Status: Resolved

🎯 L1 Engineer Interview Tip

If asked: “How do you handle a locked user account?”


You can say:

“First, I verify the issue with the user and confirm the error message. Then I check the account status in Active Directory Users and Computers. If the account is locked, I unlock it under the Account tab and reset the password if necessary. If the account locks again, I investigate possible cached credentials or background authentication attempts. If it appears to be a security concern or domain issue, I escalate to L2.”

Disclaimer