Private corporate batches, live online cohorts and 1-on-1 mentoring in compute, networking, identity, data and DevOps on Microsoft Azure — taught by a practitioner who runs it in production.
20 years across DevOps, SRE and Security · 10,000+ engineers trained · Trained teams at JPMorgan Chase, Verizon, Nokia and the World Bank
Principal DevOps Engineer & Architect
Rajesh teaches Azure from the control plane outward — management groups, subscriptions, resource groups and RBAC scope before any individual service — because scope is what makes an Azure estate either governable or accidental. Sessions run live in a real subscription: managed identities replace connection strings, private endpoints replace public service firewalls, and every workload is redeployed from a pipeline so the portal clicks used to explain a concept never become the thing that ships.
Twenty years across DevOps, SRE and Security, in principal and architect roles at PayPay, SoftwareAG, ServiceNow, JDA Software, Intuit, Adobe and others. He has trained engineers at JPMorgan Chase, Verizon, Nokia, the World Bank, VMware, Oracle, Mercedes-Benz and Airbus — more than 10,000 people personally. He teaches what he runs, not what he reads.
You are booked with a named engineer, and that is who turns up. Marketplaces and larger providers rotate whoever is free, so the person who sold you the agenda is rarely the person teaching it.
The same trainer is available for the next engagement, which matters when a team builds on what it learned last time.
Your batch is assigned a named trainer before it starts, and that is who teaches it. See the full faculty.
Engagements are matched on the tool, not the calendar. For Azure that means a trainer who has run it in production — compute, networking, identity, data and DevOps on Microsoft Azure — rather than whoever is free that week. You are told who is teaching before you commit, and that person is on the discovery call that shapes the agenda.
Where a batch is large enough to need a second trainer, the pairing is declared up front. The lead trainer stays accountable for the syllabus and the assessment either way.
Principal DevOps Engineer & Architect
Twenty years across DevOps, SRE and Security in principal and architect roles at PayPay, SoftwareAG, ServiceNow, JDA Software, Intuit, Adobe, IBM/Emptoris, Ness, MindTree and Accenture. He has trained more than 10,000 engineers personally, at organisations including JPMorgan Chase, Verizon, Nokia, the World Bank, VMware, Oracle, Mercedes-Benz and Airbus. He teaches what he runs, not what he reads.
Teams of 8–30
Custom agenda, your timezone, onsite or online, NDA-friendly.
Request a quoteIndividual engineers
A private instructor and a curriculum built around your goal.
₹99,999Individuals who want peers
Scheduled batch, max 8 to 10 hours of live instruction.
₹34,999A private batch starts with a discovery call. We look at the stack you actually run — the CI system, the cloud, the constraints — and map the agenda onto it, so examples use your topology rather than a generic one.
Delivery is onsite at your premises, live online, or hybrid, scheduled around your release calendar rather than ours. Batches run 8 to 30 engineers.
Every attendee leaves with recordings, slides, lab repositories and a completion certificate. You receive an attendance and assessment report. Invoicing supports PO and GST.
Talk to us about a private Azure batchAzure is Microsoft's cloud platform: virtual machines, storage, networking, managed databases, identity, analytics, AI services and a full DevOps toolchain, consumed on demand and billed by usage. What distinguishes Azure operationally is that everything is a resource inside Azure Resource Manager. Resource groups, tags, locks, policies and role assignments apply uniformly across services, so the control plane is one consistent model rather than a per-service collection of conventions.
The organising spine is identity. Microsoft Entra ID — the directory formerly branded Azure Active Directory — authenticates users, applications and workloads, and Azure RBAC binds those principals to scopes: management group, subscription, resource group or individual resource. Managed identities remove stored credentials from application code entirely, and Key Vault holds the secrets, keys and certificates that remain. Getting this layer right is what makes the rest of an Azure estate governable.
Around that sit the workload services teams actually deploy: Virtual Machines and Scale Sets, App Service and Functions for platform-hosted applications, Azure SQL Database and Cosmos DB for data, Blob and File storage, and virtual networks with network security groups, Load Balancer and Application Gateway to control traffic. Azure Monitor, Log Analytics and Automation cover operations, while Azure DevOps supplies Pipelines and Boards for the delivery side. Azure Policy and the landing-zone pattern turn all of it from a collection of resources into an environment that can be audited.
Azure is the incumbent cloud in most large enterprises that already run Microsoft identity, licensing and Windows workloads, which makes it the platform enterprise migrations land on rather than the one greenfield startups pick. That changes what the skill is worth: the demand is concentrated in regulated, audited, multi-subscription estates where governance matters more than novelty.
That produces a specific hiring profile. Employers are not looking for someone who can create a VM in the portal — they are looking for engineers who can design a subscription and management group hierarchy, express it in Bicep or Terraform, enforce it with Azure Policy, wire workload identity so no credential is ever stored, and explain a bill by resource group and tag. Hybrid identity through Entra Connect, private endpoints, and network isolation between spokes are routine requirements rather than advanced topics.
The second driver is that Azure DevOps and GitHub Actions sit inside the same conversation as the infrastructure. Teams are expected to deliver pipelines that deploy to App Service, AKS or Functions with environment approvals and service connections scoped to managed identities. Azure skills that stop at the resource level and never reach delivery leave half the job undone.
The platform as a control plane rather than a service catalogue. Regions, availability zones, subscriptions and resource groups, the Azure Resource Manager model that everything else inherits, and the account and pricing structures that decide how an estate is billed and separated.
Topics: Overview of Azure services and service families · Azure account types, subscriptions and pricing models · Management groups, subscriptions and resource groups · Azure Resource Manager, tags, locks and policy · Portal, Azure CLI, Azure PowerShell and the REST API · Regions, availability zones and paired regions · Cost management, budgets and the pricing calculator
Infrastructure as a service, done so it survives failure. VM sizes and disk types, image and extension management, availability sets versus availability zones, then Virtual Machine Scale Sets with autoscale rules and rolling upgrade policies.
Topics: Creation and management of VMs — sizes, disks and images · Configuring networking for VMs: NICs, public IPs and NSGs · Availability sets, availability zones and SLAs · Custom images, shared image gallery and VM extensions · Virtual Machine Scale Sets and autoscale rules · Backup, snapshots and Azure Site Recovery basics · Azure Bastion and Just-in-Time VM access
Where state lives, and how it is secured. Storage account types and replication options, then the four services in detail — Blob, File, Queue and Table — with access tiers, lifecycle policies, SAS tokens versus RBAC, and the private endpoint pattern that keeps storage off the public internet.
Topics: Overview of storage options and account types · Creating and managing storage accounts, replication and redundancy · Azure Blob storage: containers, access tiers and lifecycle management · Azure File storage, file shares and Azure File Sync · Shared access signatures, access keys and RBAC on data planes · Encryption at rest, customer-managed keys and immutability · Private endpoints and storage firewalls
Reachability and isolation. Virtual networks and subnets, network security groups and the rule evaluation that decides whether traffic arrives, then the two load balancing layers — Azure Load Balancer at layer four and Application Gateway at layer seven with WAF — and how hub-and-spoke peering ties an estate together.
Topics: Virtual networks, subnets and address space planning · Network security groups and application security groups · Azure Load Balancer: frontends, backend pools, probes and rules · Azure Application Gateway, WAF and path-based routing · VNet peering, hub-and-spoke topology and Azure Firewall · Service endpoints versus private endpoints · Azure DNS, private DNS zones and name resolution · VPN Gateway and ExpressRoute for hybrid connectivity
Platform hosting without managing servers. App Service plans and the scaling and isolation each tier provides, deployment slots and swap semantics, then the application types — Web Apps, Mobile Apps, API Apps — and Logic Apps for connector-driven integration.
Topics: App Service plans, tiers, scaling and App Service Environment · Web Apps: deployment, configuration and application settings · Mobile Apps and API Apps · Logic Apps, connectors and workflow design · Deployment slots, slot settings and swap with warm-up · Custom domains, TLS certificates and managed certificates · VNet integration, private endpoints and access restrictions · Authentication with Entra ID and managed identity to backend services
Event-driven compute. The hosting plans and what each means for cold starts, scaling limits and networking; then triggers and bindings as the model that removes most integration code, and the durability and retry behaviour that decides whether a function pipeline is safe under load.
Topics: Overview of serverless computing and hosting plans — Consumption, Premium, Dedicated · Creating and deploying Azure Functions · Function triggers and bindings — HTTP, timer, queue, blob, Event Grid · Durable Functions and orchestration patterns · Scaling behaviour, cold starts and concurrency · Application settings, Key Vault references and managed identity · Retry policies, poison queues and idempotency
Relational data as a managed service. The three deployment shapes — single database, elastic pool and Managed Instance — and what each gives up; purchasing models and performance tiers; then the operational reality of backups, point-in-time restore, failover groups and geo-replication.
Topics: Creating and managing SQL databases · DTU and vCore purchasing models, serverless and Hyperscale · SQL Database elastic pools and when they pay off · Azure SQL Managed Instance and migration from on-premises · Backups, point-in-time restore and long-term retention · Active geo-replication and auto-failover groups · Security: firewall rules, private endpoints, Entra authentication, Always Encrypted · Query Performance Insight and automatic tuning
Globally distributed NoSQL, and the modelling discipline it demands. Why partition key choice is the single decision that determines whether a Cosmos workload scales or throttles, the five consistency levels and their real cost, request units as the currency of everything, and the API surfaces that let existing applications move across.
Topics: Overview of NoSQL databases and Cosmos DB positioning · Creating and managing Cosmos DB accounts, databases and containers · Cosmos DB APIs — NoSQL, MongoDB, Cassandra, Gremlin, Table · Data modeling: partition keys, denormalisation and item size · Request units, throughput provisioning, autoscale and serverless · Consistency levels and multi-region writes · Change feed and event-driven integration · Indexing policies and query cost tuning
The layer everything else depends on. Microsoft Entra ID as the directory, hybrid identity through Entra Connect, and Azure RBAC scope inheritance from management group down to individual resource. Then the part that removes credentials from code entirely: system and user-assigned managed identities, service principals and app registrations.
Topics: Azure Active Directory / Microsoft Entra ID fundamentals · Azure AD Connect and hybrid identity synchronisation · Role-based access control: built-in roles, custom roles and scope inheritance · Service principals, app registrations and OAuth flows · System-assigned and user-assigned managed identities · Conditional access, MFA and Privileged Identity Management · Groups, administrative units and access reviews
Posture, secrets and data protection. Microsoft Defender for Cloud as the security posture and recommendation engine, Key Vault for keys, secrets and certificates including rotation and access models, and the classification and labelling side of information protection.
Topics: Azure Security Center / Microsoft Defender for Cloud, secure score and recommendations · Azure Key Vault: secrets, keys, certificates and soft delete · Key Vault access policies versus RBAC, and Key Vault references from apps · Secret rotation and customer-managed keys · Azure Information Protection and data classification · Azure Policy for security guardrails and compliance initiatives · Defender plans for servers, storage, SQL and containers
Knowing what the estate is doing, and reacting without a human. Azure Monitor metrics and logs, Log Analytics workspaces and KQL as the query language that makes them useful, action groups and alert rules, then Azure Automation runbooks and update management for the operational response.
Topics: Azure Monitor: metrics, logs, diagnostic settings and data collection rules · Azure Log Analytics workspaces and KQL query fundamentals · Alert rules, action groups, dynamic thresholds and alert processing · Workbooks, dashboards and Application Insights · Azure Automation: runbooks, schedules and hybrid workers · Update management and change tracking · Service Health, Resource Health and activity logs
Closing the loop from code to running resource. Azure Pipelines with YAML, multi-stage pipelines, environments, approvals and service connections scoped to managed identities; artifact and repository management; and Boards for the planning side. Infrastructure and application delivery are treated as the same pipeline problem.
Topics: Continuous Integration and Deployment (CI/CD) on Azure · Azure Pipelines: YAML pipelines, stages, jobs and templates · Agent pools, self-hosted agents and service connections · Environments, approvals, gates and deployment strategies · Azure Repos and Azure Artifacts · Azure Boards: work items, backlogs and traceability · Deploying infrastructure with Bicep, ARM templates or Terraform from a pipeline · Secrets in pipelines: variable groups, Key Vault integration and workload identity federation
We rebuild the agenda around the tools you actually run.
Request a custom agendaBuild a management group and subscription hierarchy, apply tagging and policy, and prove that a non-compliant resource cannot be created.
Peer a hub and two spokes, force egress through a firewall, and reach storage and SQL through private endpoints with public access disabled.
Take an application that stores credentials in configuration and rebuild it on managed identity and Key Vault references, with nothing secret left in the app settings.
Model one dataset in Cosmos DB two ways, run identical query patterns against both, and measure the RU difference a partition key choice makes.
Instrument a workload with diagnostic settings, write the KQL that detects the failure condition, and wire the alert to an Automation runbook that remediates it.
Build a multi-stage Azure Pipeline that provisions infrastructure with Bicep or Terraform, deploys the application, runs approvals and can roll back.
Billed yearly at ₹9,996
Max 8 to 10 hours of live instruction
Full program, private instructor
8–30 engineers · custom agenda · onsite or online · PO and GST invoicing
Refunds. If we cancel or postpone a cohort, you get a full refund within 15 days. There is no money-back guarantee otherwise.
Terms. Course material remains licensed to the attendee. Read the terms.
Your data. We don't share it with third parties. Privacy policy.
Certificate of completion
Great learning experience from a very knowledgeable instructor with well-prepared course notes. The lab exercises on AWS instance work well to learn the hands-on side of the course.
My experience with the AIOps training was positive. The course covered important topics in a structured way, and Rajesh Kumar explained the concepts patiently. I found the practical aspects particularly helpful because they made the technical content easier to understand.
I was looking to improve my understanding of AIOps, and this training helped me achieve that goal. Rajesh Kumar explained the subject in a structured and practical manner. The sessions on different AIOps concepts were informative.
I recently did a SRE Session with Rajesh Kumar from DevOps School and the session was great. Right from 1st day till day 15, we had a very interactive session. Rajesh clarified our doubts and the tool demos were excellent without any hiccups. He simplified the concepts while sticking to the content with a fine balance between theory and practice. Am convinced he is one of the best trainers for SRE & DevOps concepts.
The Rundeck developer session was excellent and highly engaging. I appreciated how well the session was structured, with the theoretical concepts explained clearly and in simple terms. What stood out most to me was the demo — it was both informative and enjoyable. I especially liked how Rajesh walked us through not only the happy path but also the sad path, showcasing common issues and sharing practical troubleshooting tips.
Rajesh's experience and knowledge are exceptional and we learnt invaluable practical knowledge which we can apply in our production environment. Incredibly friendly and gave us a fantastic insight both in-depth and at a high level of the Rundeck product.
| What matters | YouTube + blogs | Generic online course | Freelance marketplace | DevOpsSchool |
|---|---|---|---|---|
| Named practitioner | No | Rarely | Varies per booking | Yes — same trainer each time |
| Production experience | Unknown | Unknown | Unverified | 20 years, named employers |
| Custom agenda | No | No | Sometimes | Built from your stack |
| Onsite delivery | No | No | Sometimes | Yes |
| Lab environment | None | Sandbox that expires | Varies | Your own cloud — skill goes with you |
| Assessment | None | Quiz | Rarely | Assignments + capstone per module |
| Per-attendee certificates | No | Sometimes | Rarely | Yes |
| Corporate invoicing | No | Limited | Varies | PO and GST |
| Post-training support | None | Forum, time-limited | None | Lifetime forum access |
Tell us the team, the stack and the timeline. You'll get a straight answer, not a sales sequence.
Talk to an advisorPrefer to call or email?
More ways to reach us on the contact page.