Microsoft Azure Training in Pune with Placement

Cloud computing models, the Azure global footprint (Regions, Availability Zones, region pairs, Edge sites), and the resource hierarchy that everything else in Azure inherits from — Management Groups, Subscriptions, Resource Groups. Getting that hierarchy right on day one is what makes governance and cost allocation possible later.

Every student finishes week 1 with their own subscription, MFA enforced, a budget alert configured, and both the Azure CLI and Azure PowerShell working locally. We spend a full session on cost, because an unattended VM is the single most common way a student's free credit disappears.

Identity is the control plane in Azure, so it comes before anything is deployed. Entra ID users, groups and dynamic groups; app registrations and service principals; and managed identities — system-assigned versus user-assigned — which are the answer to almost every 'where do I put this credential' question.

RBAC follows: built-in roles, custom role definitions, and the scope hierarchy that decides what an assignment actually grants. The week closes with Conditional Access, Privileged Identity Management, Azure Policy and a Defender for Cloud baseline applied to the subscription.

Building an Azure network from the address space up. VNet and subnet design with address planning that leaves room to grow, Network Security Groups and Application Security Groups, user-defined routes and forced tunnelling, and service endpoints.

Load balancing is taught by layer rather than by product name, so the choice between Azure Load Balancer (L4) and Application Gateway (L7 with WAF) is a reasoned one. Azure Firewall versus NAT Gateway closes the week, along with Azure DNS and Private DNS Zones.

Connecting the network to everything outside it. VNet Peering including the gateway-transit and non-transitive behaviour that surprises people, hub-and-spoke topology and Azure Virtual WAN, then hybrid links — Site-to-Site VPN, Point-to-Site VPN, and ExpressRoute with its circuit and peering model.

Private Endpoints and Private Link get a full session, because keeping PaaS traffic off the public internet is now a default requirement in Indian BFSI and healthcare work. Azure Front Door and Traffic Manager complete the global routing picture.

The IaaS layer. VM families and sizing, the pricing models (pay-as-you-go, reserved instances, savings plans, spot) and how to combine them, managed disks and their performance tiers, availability sets versus availability zones, and the images pipeline with Azure Image Builder and the Shared Image Gallery.

VM Scale Sets add elasticity — autoscale rules, upgrade policies, and health probes — and the lab ends with an application that stays up while instances are deliberately destroyed.

Azure's PaaS compute, which is where a large share of Pune Azure work actually happens. App Service plans and the tier decisions that govern scaling and cost, deployment slots with slot swapping for zero-downtime releases, custom domains and managed certificates, and VNet integration.

Azure Functions covers triggers and bindings, the Consumption versus Premium plan trade-off, cold starts and Durable Functions for stateful orchestration. Logic Apps closes the week as the low-code integration option, taught with an honest account of when it is and is not the right tool.

Containers on Azure across the three options a team realistically chooses between. Azure Container Registry with geo-replication, image scanning and tasks; Azure Container Apps as the managed serverless container platform with KEDA-based scale-to-zero and Dapr integration; and Azure Kubernetes Service for teams that need the full Kubernetes surface.

AKS covers cluster provisioning, AKS Automatic, Azure CNI versus kubenet, node pools, workload identity for pod-level access to Azure resources, and the AKS-specific ingress options.

Storage accounts and the four services inside them — Blob, File, Queue and Table — plus the redundancy options (LRS, ZRS, GRS, RA-GRS) that decide both durability and bill. Blob access tiers, lifecycle management, immutability policies and soft delete.

Security is covered properly: shared access signatures and their scoping, stored access policies, private endpoints, and customer-managed keys. Azure Files with SMB and Azure Data Lake Storage Gen2 close the module, along with disk types for the VM workloads from week 5.

Managed data services and the modelling decisions behind them. Azure SQL Database across single database, elastic pool and Hyperscale, plus Managed Instance for lift-and-shift; backup, point-in-time restore, failover groups and active geo-replication.

Azure Database for PostgreSQL Flexible Server covers the open-source path most new Pune projects take. Cosmos DB is taught as a distributed-systems subject — partition key design, request units, consistency levels and the multi-API surface — because that is where its cost and performance are decided.

Azure defined as code. Bicep first, as the Azure-native language — modules, parameters, outputs, deployment scopes, what-if previews and the ARM template it compiles to (covered at the level needed to read legacy templates you will inherit).

Terraform with the AzureRM provider follows, including remote state in a storage account with locking, modules, and the import workflow for adopting portal-created resources. We teach both because Pune Azure teams are genuinely split, and being fluent in one only is a hiring limitation.

Both pipeline platforms, because Pune Azure shops use both and often at once. Azure DevOps YAML pipelines — stages, jobs, templates, variable groups, agent pools, environments and approval gates, plus Azure Artifacts and Azure Repos.

GitHub Actions with OIDC federation to Entra ID covers the modern keyless pattern. Deployment strategy closes the module: slot swaps for App Service, rolling and blue-green for VM Scale Sets, and canary for Container Apps — each paired with its rollback path.

Azure Monitor as the single pipeline behind metrics, logs and alerts. Data collection rules, Log Analytics workspaces and workspace design, and the retention and cost model that a badly configured workspace will make expensive very quickly.

KQL is taught as a language rather than a set of copied snippets — filtering, summarising, joins, time-series operators and rendering — because it is the skill that separates someone who can read Azure telemetry from someone who cannot. Application Insights, distributed tracing, workbooks and alert action groups complete the module.

Security consolidated across everything already built. Azure Key Vault for keys, secrets and certificates, access policies versus RBAC, soft delete and purge protection, and rotation. Encryption at rest with Storage Service Encryption and customer-managed keys, and encryption in transit at Front Door and Application Gateway.

Defender for Cloud plans, Azure WAF and DDoS Protection, and the Cloud Adoption Framework follow. Each student then writes a Well-Architected review of their capstone against the five pillars.

Reading and reducing an Azure bill, which is a named responsibility in a growing share of Pune cloud job descriptions. Cost Management analysis, exports to storage, tagging strategy and cost allocation, budgets with automated actions, and Azure Advisor recommendations read critically rather than applied blindly.

The savings levers follow: reservations and savings plans, Azure Hybrid Benefit, spot capacity, autoscale and shutdown schedules for non-production, and the standard waste list — unattached disks, idle gateways, orphaned public IPs, over-provisioned App Service plans.

Pune Azure architects in 2026 are expected to design AI features, not just classic three-tier apps. Cover Azure OpenAI Service (model catalog, deployment types, quota and TPM management), content filtering and the Responsible AI tooling, and Azure AI Search as the managed retrieval layer.

The lab builds a retrieval-augmented generation service end to end — documents in Blob Storage, indexed by Azure AI Search, answered by an Azure OpenAI deployment behind an App Service or Container Apps front end — that you can demo in an interview.

Two weeks of full-time capstone work plus structured AZ-104 (Azure Administrator Associate) preparation. Pick one of the capstone architectures and build it with Bicep or Terraform, a CI/CD pipeline, monitoring and alerting, and a documented cost estimate.

Exam preparation runs question-bank drills across the five AZ-104 domains, scenario walkthroughs and two full-length timed mock exams. Mock interviews target Pune Azure hiring panels, and resume, LinkedIn and GitHub polish is included.