Currently Cloud Engineer at FSP Consulting

Anand Vaidya

Portrait of Anand Vaidya, Azure Cloud Engineer

Azure Cloud EngineerServerless & IntegrationDevOps & IaC

I build serverless integrations, secure APIs and automated infrastructure on Microsoft Azure — event-driven systems that turn hours of manual processing into seconds.

Experience
3+ years engineering
Core stack
Functions · APIM · Logic Apps
Delivery
Bicep · Azure DevOps
Based in
Vadodara, India
The work is serious. The ending isn’t.
scroll to deploy

01 About

I turn slow, manual processes into event-driven systems that run themselves.

anandvaidya.in / personnel
Name
Anand Vaidya
Role
Cloud Engineer
Org
FSP Consulting
Base
Vadodara, IN
Shipping since
Feb 2023
Certified
AI-900
Education
B.Tech. CSE
Clearance
Managed Identity

I’m Anand Vaidya, a Cloud Engineer at FSP Consulting in Vadodara, India. I design and build serverless integrations on Microsoft Azure — Azure Functions, Logic Apps and API Management, secured with OAuth 2.0 and Managed Identities, and shipped through Bicep and Azure DevOps pipelines.

Before FSP, I spent two years at Atharva IT Services building a .NET Core integration layer that connected Shopify, Amazon and Walmart and automated shipping logistics. My work is moving toward platform engineering and cloud architecture: infrastructure defined as code, automated paths to production, and systems that are secure by default.

  1. Event-driven by default

    Compute that scales out with demand — and, on consumption-based plans, in to zero when idle — so bursts don’t mean lost orders and quiet hours cost little.

  2. Identity over secrets

    Managed Identities, OAuth 2.0 and RBAC instead of credentials in config files.

  3. Everything as code

    Environments declared in Bicep and ARM, versioned and reviewed like application code.

  4. An automated path to production

    Multi-stage pipelines that build, test, scan and deploy without manual steps.

02 Skills & stack

A stack built around Azure, organised the way systems are.

Select any technology to see what it does and where I’ve used it.

L1 Microsoft Azure

L2 Serverless & integration

L3 APIs & data

L4 Infrastructure as code

L5 DevOps, CI/CD & containers

L6 Programming & automation

03 Architecture lab

How the pieces fit together.

An illustrative reference architecture for the kind of serverless integration I build. It is based on patterns from my work, not a diagram of a specific production system. Pick a flow or select any service.

Illustrative

Overview

Event-driven integration on Azure

Requests enter through API Management, which authenticates and throttles them. Azure Functions run the business logic and hand long-running workflows to Logic Apps. State lands in Cosmos DB or SQL. Services authenticate with Managed Identity, and everything is provisioned from Bicep through Azure DevOps.

  • Scales with demand (on consumption-based plans, in to zero when idle)
  • No secrets stored in configuration
  • Every environment rebuilt from the same code

Entry point

Clients & partner systems

Web and mobile apps, marketplaces and carrier systems that send orders, events and webhooks.

In my work: Shopify, Amazon and Walmart order channels; FedEx, DHL and UPS carrier integrations.

Gateway

Azure API Management

A single front door for every API: OAuth 2.0 / JWT validation, rate limiting, caching and versioning, so backends stay simple and protected.

In my work: FSP Consulting’s serverless architecture and the carrier & shipping integration layer.

Compute

Azure Functions

Event-driven business logic: validate, transform and route each message. Scales out under bursts and, on consumption-based plans, in to zero when idle.

In my work: order processing, inventory sync and webhook handlers.

Orchestration

Logic Apps

Long-running and multi-step workflows with built-in connectors, retries and approvals, kept out of the request path.

In my work: approval flows, cross-system data sync and carrier dispatch.

State

Cosmos DB & SQL Server

Cosmos DB for high-throughput, low-latency order and inventory state; SQL Server for relational, transactional records.

In my work: real-time e-commerce inventory, ledgers and order history.

Security

Managed Identity

Each service gets its own Entra ID identity and least-privilege RBAC role, so nothing needs a stored password or connection string.

In my work: replaced exposed credentials in legacy systems at FSP Consulting.

Infrastructure as code

Azure Bicep

In this pattern every Azure resource on the diagram is declared in Bicep, reviewed in pull requests and deployed identically to each environment. External systems (marketplaces, carriers) are outside its scope.

In my work: the zero-downtime deployment pipeline that cut release time from 2 days to 15 minutes.

Delivery

Azure DevOps pipelines

Multi-stage YAML pipelines: build, test, security scan, provision with Bicep, then promote through environments with approval gates.

In my work: blue-green, zero-downtime releases to Azure.

04 Experience

From LMS operations to cloud engineering.

  1. – Present Full-time · Vadodara

    Cloud Engineer Current

    FSP Consulting

    Modernising slow, manual on-premises processing into secure, serverless services on Azure.

    • Engineered an event-driven architecture on Azure Functions, Logic Apps and API Management, replacing manual data processing in legacy systems.
    • Secured service access with OAuth 2.0 and Managed Identities, removing exposed credentials and closing critical attack surfaces in production.
    • Reduced processing latency from hours to seconds.
    • Azure Functions
    • Logic Apps
    • Azure API Management
    • Managed Identities
    • OAuth 2.0
    • Azure Bicep
  2. – Full-time · Ahmedabad

    Junior Developer

    Atharva IT Services

    Unifying fragmented e-commerce channels behind one integration layer.

    • Developed a unified .NET Core integration layer connecting Shopify, Amazon and Walmart, backed by globally distributed Cosmos DB.
    • Eliminated manual order reconciliation and automated shipping logistics.
    • Achieved zero-downtime deployments with Docker and Azure DevOps.
    • ASP.NET Core
    • C#
    • Cosmos DB
    • Docker
    • Azure DevOps
  3. – Internship · Vadodara

    LMS Administrator Intern

    Parul University

    Keeping a university-wide learning platform available for thousands of students.

    • Managed and optimised the Moodle LMS infrastructure across fragmented legacy database systems.
    • Bridged data integrity with SQL and Active Directory authentication.
    • Zero downtime during peak exam periods; streamlined semester-to-semester user onboarding.
    • Moodle LMS
    • Active Directory
    • SQL

05 Selected work

Case studies in integration and automation.

Client projects, described without confidential detail. Diagrams are simplified to show the architecture, not exact deployments, and outcomes are as reported from each engagement. Each one has a full write-up covering the architecture, decisions and trade-offs.

02 Client project · Infrastructure as code & CI/CD

Zero-Downtime Cloud Deployment Pipeline

Problem
Manual deployment steps caused environment drift, delayed releases by days and led to frequent production rollbacks.
Architecture
A fully automated infrastructure-as-code pipeline: Azure Bicep templates deployed through Azure DevOps to provision consistent, immutable environments.
Key decisions
Infrastructure versioned alongside the application so every environment is built from the same source; redeploy rather than patch servers by hand.
  • Azure Bicep
  • Azure DevOps
  • YAML pipelines
Read the deployment-pipeline case study
  • 2 days → 15 mindeployment time
  • Zero-downtimereleases enabled
  • Eliminatedmanual configuration errors, by removing manual steps
03 Client project · API gateway & security

Carrier & Shipping Integration Layer

Problem
Dispatch teams spent hours creating shipping labels and tracking packages by hand across separate FedEx, DHL and UPS portals.
Architecture
A centralised, secure API gateway on Azure API Management with OAuth 2.0, automating carrier integrations, label generation and live webhook tracking.
Key decisions
One gateway in front of every carrier, so authentication, throttling and versioning live in one place; webhooks for live tracking updates.
  • Azure API Management
  • Azure AD B2C
  • OAuth 2.0
Read the carrier API gateway case study
  • Zero clicksreplacing a 20-minute manual process
  • 40+ hrsdispatch overhead saved per week
  • Improvedshipping SLA compliance

06 Inside my engineering mind

Four decisions, written down the way engineers record them.

Architecture decision records from the projects above: the context, the constraints, the options on the table, what I chose and what it cost. Open one to read it.

ADR-001

React to events instead of syncing on a schedule

Order processing · Azure Functions, Cosmos DB
Context
Inventory was synchronised between Shopify, Amazon and Walmart about every five minutes — long enough for the same item to sell on two channels at once.
Constraints
Three marketplaces with different payload formats, order traffic that arrives in bursts, and no new manual reconciliation work.
Options on the table
  • Not chosen: Keep the scheduled sync. Whatever the interval, there is still a window in which the same item can sell twice.
  • Not chosen: Fixed, always-on servers. Sized for the bursts and paid for while idle.
  • Chosen: Event-driven Azure Functions. React to each change as it happens; scale out with order bursts and, on consumption-based plans, in to zero while idle.
Decision
Event-driven Azure Functions behind every channel, one normalised inventory model shared by all of them, and order and inventory state in Cosmos DB.
Trade-off accepted
Events can arrive twice or out of order, so every handler is idempotent and updates are ordered per item.
Outcome
Sync latency from about 5 minutes to under 2 seconds, overselling eliminated, and $150k+ of previously lost quarterly revenue recovered.
ADR-002

Give services identities, not stored secrets

Security · Managed Identity, OAuth 2.0, RBAC
Context
Legacy on-premises processing at FSP Consulting relied on exposed credentials, and the carrier gateway needed callers to authenticate without holding carrier API keys.
Constraints
Production systems; carrier API keys must stay out of client applications.
Options on the table
  • Not chosen: Credentials in configuration files. Secrets to store, rotate and leak.
  • Not chosen: Shared credentials handed to every caller. Every client holds the keys.
  • Chosen: Managed Identities, OAuth 2.0 and least-privilege RBAC. Each service gets its own Entra ID identity and only the role it needs; callers present short-lived tokens.
Decision
Services authenticate with Managed Identities and least-privilege RBAC roles; callers use OAuth 2.0 tokens validated at the gateway.
Trade-off accepted
Token issuance and app registrations add setup, and every client has to handle expiring tokens gracefully.
Outcome
Exposed credentials removed and critical attack surfaces closed in production; carrier API keys stay out of client applications.
ADR-003

Make the templates the only source of truth

Delivery · Azure Bicep, Azure DevOps
Context
Releases depended on manual deployment steps. Environments drifted apart, a release could take days, and the differences surfaced in production as frequent rollbacks.
Constraints
Every environment has to match, releases must not take the service down, and data in stateful resources has to survive a redeployment.
Options on the table
  • Not chosen: Keep applying changes by hand. This is where the drift comes from.
  • Not chosen: Hand-written ARM JSON. Full coverage of Azure resource types, but long and hard to review.
  • Chosen: Azure Bicep templates in the same repository as the code. Compiles to ARM, far shorter to review, and every environment can be rebuilt from a known commit.
Decision
Environments are declared in Bicep and deployed through multi-stage Azure DevOps pipelines. A change is a fresh deployment, never an edit to a running server.
Trade-off accepted
Changes made in the portal are overwritten on the next deployment, databases need separate handling, and Bicep is Azure-specific.
Outcome
Deployment time from 2 days to 15 minutes, zero-downtime releases enabled, and manual configuration errors eliminated by removing the manual steps.
ADR-004

Put one gateway in front of every carrier

Integration · Azure API Management, webhooks
Context
Dispatch teams created labels and tracked packages by hand across separate FedEx, DHL and UPS portals — twenty minutes at a time, holding back shipping SLA compliance.
Constraints
Three carrier APIs, carrier keys kept out of dispatch apps, and tracking that stays current without anyone checking.
Options on the table
  • Not chosen: Keep the portals. Twenty minutes of clicking per shipment.
  • Not chosen: Integrate each carrier into every dispatch app. Three integrations, three sets of keys, and authentication and throttling duplicated everywhere.
  • Chosen: Azure API Management in front of every carrier, with tracking webhooks. Dispatch integrates once; token validation, throttling, versioning and logging live in one place.
Decision
One gateway on Azure API Management, protected with OAuth 2.0, automating label generation, with carriers pushing tracking updates as webhooks.
Trade-off accepted
The gateway becomes a critical dependency, so its tier, scaling and availability are planned like any production service; webhook endpoints verify senders and handle retries and duplicates.
Outcome
A 20-minute manual process reduced to zero clicks, 40+ hours of dispatch work saved every week, and significantly improved SLA compliance.

07 Education & certifications

Credentials

Education

B.Tech. Computer Science & Engineering

Parul University, Vadodara

2019 – 2023 First Class with Distinction

Certification

Microsoft Certified: Azure AI Fundamentals

Microsoft · AI-900

May 2025 Verified

Course

Python Data Science & Masterclass

Parul University & Udemy

Course

Deep Web — The Complete Introduction

Udemy

08 FAQ

Quick answers

The questions recruiters and engineering managers ask most often.

Who is Anand Vaidya?

Anand Vaidya is a Cloud Engineer at FSP Consulting in Vadodara, Gujarat, India, with 3+ years of engineering experience. He builds serverless integrations, secure APIs and automated infrastructure on Microsoft Azure.

What does Anand work on as a Cloud Engineer?

Event-driven architectures on Azure Functions, Logic Apps and API Management, secured with OAuth 2.0 and Managed Identities, with infrastructure defined in Bicep and ARM templates and delivered through Azure DevOps pipelines.

Does Anand do DevOps and infrastructure as code?

Yes. He builds multi-stage YAML pipelines in Azure DevOps for build, test, security scanning and blue-green deployments, and provisions environments with Azure Bicep. One such pipeline cut deployment time from 2 days to 15 minutes.

How can I contact Anand Vaidya?

Email anand.svaidya24@gmail.com, call +91-9913013470, or connect on LinkedIn (in/vaidya-anand). His code is on GitHub (anandvaidyaa).

09 Prefer a shell?

Explore this profile from the command line.

Type help, or tap a command. Everything here mirrors the page content.

anand@portfolio: ~

Portfolio shell. Type help to list commands.

10 Contact

Let’s build cloud systems that run themselves.

Cloud engineering, integration or DevOps roles and projects — the fastest way to reach me is email.

Send a message

This opens your email app with the message ready to send.

02:17 After hours / 001

You’ve explored the systems. Now it’s your turn to play.

sysidle · pick a room

  • NOC-01Strategy · 5 missions

    Packet Pilot

    Network operations chamber

    Keep a live network delivering while links congest, routers fail and critical traffic arrives.

  • LAB-404Investigation · 3 sectors

    Bug Hunter 404

    Corrupted laboratory

    Restore a corrupted system: isolate the real defects, leave intended behaviour alone, find the root cause.

  • REL-7Decisions · 4 scenarios

    Deploy Rush

    Release control room

    Run a release through real prerequisites, then make the call when production starts to hurt.

  • SKY-30Precision · 3 modes

    Cloud Stack

    Construction deck above the skyline

    Build a tower through wind and special platforms. A bright band shows exactly what survives each drop.

Fictional engineering simulations. Your progress stays in this browser; nothing is sent anywhere.

30-second profile

Anand Vaidya

Azure Cloud Engineer · FSP Consulting · Vadodara, India

3+ years building serverless integrations, secure APIs and automated infrastructure on Microsoft Azure — event-driven systems that turn hours of manual processing into seconds.

Experience

  1. Cloud Engineer · FSP Consulting
  2. Junior Developer · Atharva IT Services
  3. LMS Administrator Intern · Parul University

Core skills

  • Azure Functions
  • API Management
  • Logic Apps
  • Managed Identity & OAuth 2.0
  • Bicep & ARM
  • Azure DevOps CI/CD
  • Cosmos DB
  • ASP.NET Core & C#

Selected work · reported outcomes

Credentials

  • Azure AI Fundamentals (AI-900)
  • B.Tech. CSE · First Class with Distinction

Prefer the long version? How I make engineering decisions · Contact

control plane · access granted

You found the control plane.

Everything is healthy. Nothing is on fire. Here is the whole stack in one breath:

Client APIM Functions Logic Apps Data deployed by Bicep + Azure DevOps · secured by Managed Identity

Secret commands also work in the terminal. Try sudo.