Cloud Computing in India: AWS, Microsoft Azure, Google Cloud — Operating Entities, Registration Norms, Procurement Grounds, and GST/Compliance Claim Process

Cloud computing (IaaS/PaaS/SaaS) is now a standard way for Indian businesses to run servers, storage, databases, analytics, AI/ML, security tooling, and enterprise applications without owning physical infrastructure.

This Knowledge Base article explains, for AWS, Azure, and Google Cloud:

• Which cloud providers operate in India and how they typically contract/bill Indian customers

• How such cloud companies are generally set up/registered in India (legal + GST + OIDAR context)

• Buyer-side norms: billing, tax settings, invoice hygiene, compliance, security expectations

• How to “claim” cloud spend in India (commonly meaning GST Input Tax Credit (ITC) + audit-ready documentation)

• On what grounds to approve/procure cloud (business, control, security, compliance)

Note: This is technical + compliance guidance (not legal advice). For reverse charge/import-of-services and any special scenario, confirm with your CA/tax advisor.

---

1) Technical Overview: What “Cloud Computing” Covers

Cloud services typically fall into:

• IaaS: virtual machines, storage, networking, firewalls

• PaaS: managed databases, Kubernetes, serverless, message queues, identity services

• SaaS: email/collaboration, CRM, security platforms, monitoring, backup

Key cloud characteristics

• Metered usage (pay-as-you-go), reservations/savings plans

• Shared responsibility model (provider secures the cloud; customer secures what they run in it)

• Programmatic control via APIs/CLI/IaC (Terraform, CloudFormation, ARM/Bicep)

---

2) Which Cloud Providers Operate in India (AWS, Azure, Google Cloud)

The three primary hyperscalers serving Indian customers are:

• Amazon Web Services (AWS)

• Microsoft Azure

• Google Cloud Platform (GCP)

Contracting/Billing entities: why it matters

For compliance and GST/ITC, what matters most is the contracting/billing entity and invoice type, which can vary by account setup and product.

AWS

• If you sign up with India billing/contact address, your agreement can be with Amazon Web Services India Private Limited (AWS India) and billing can be in INR.

• AWS has India-specific tax guidance and GST behavior for customers.

• For certain digital supplies (e.g., Marketplace context), AWS also documents non-resident OIDAR handling and GST collection guidance.

Microsoft Azure

• Microsoft documentation states: for India, the Azure billing entity under Microsoft Customer Agreement invoice can be Microsoft Corporation India Private Limited.

Google Cloud

• Google Cloud provides a “contracting entity” reference and India-specific tax billing guidance (GST behavior depends on GSTIN and contracting entity such as Google Asia Pacific vs Google Cloud India, per Google’s documentation).

• Google also documents India GST behavior (e.g., GSTIN provided vs not provided).

---

3) How These Companies Are “Registered” / Operate in India (Practical View)

Cloud providers generally serve India through one or more of these structures:

1. Indian incorporated entity (Private Limited company)

2. Local reseller / partner invoices (Indian GST invoice)

3. Cross-border digital supply where applicable (includes OIDAR classification in IGST context)

OIDAR relevance for cloud

The IGST Act definition of OIDAR explicitly includes providing cloud services.
This matters for how some cross-border digital services are treated and documented in tax/compliance.

India company incorporation mechanism (context)

Software/cloud providers and partners that incorporate in India typically follow MCA incorporation processes (commonly via SPICe+ and related forms).

---

4) Norms for Buying Cloud in India (What You Must Check)

A) Tax & billing norms (for GST/ITC readiness)

Invoice hygiene checklist

• Correct Legal entity name (matches contract/billing profile)

• Correct your legal name + GSTIN + bill-to address

• Correct GST treatment (CGST/SGST vs IGST, as applicable)

• Invoice number/date, taxable value, tax amount, place of supply where required

• Keep proof of service receipt (activation email, console screenshot, usage report)

Provider-side tax settings

• AWS: Manage GSTIN and tax registrations in Billing → Tax Settings (India billing guidance exists).

• Google: GSTIN submission affects GST treatment (documented in Google billing tax pages).

• Azure: invoices are downloadable from Azure portal and billing entity varies by country; India entity is documented.

---

B) ITC norms (GST Input Tax Credit)

Under CGST Act Section 16, ITC eligibility is subject to conditions and time limits.
Under Section 17, ITC can be restricted or apportioned for non-business/exempt usage (and blocked credits apply in specified cases).

Practical buyer rules

• Cloud spend must be used or intended to be used in the course/furtherance of business (core ITC principle).

• Ensure invoice/credit note timing and claiming deadlines are respected (Section 16(4) timing rules are critical).

In most organizations, “claim” = (1) claim GST ITC (if eligible) and (2) keep audit-ready evidence (contract + invoice + usage).

---

C) Security and governance norms (minimum baseline)

For any cloud approval, enforce:

• Identity: SSO/MFA, role-based access control (RBAC), least privilege

• Logging: audit logs enabled, centralized log storage, retention policy

• Network security: segmentation, firewall policies, private endpoints where needed

• Data protection: encryption at rest + TLS in transit, key management

• Backup/DR: backup policy + restore testing evidence

• Vendor/contract: SLA, support model, data residency needs, exit plan

---

5) On What Grounds Should You Procure Cloud (AWS/Azure/GCP)?

Use these “grounds” to justify cloud procurement internally (approvals/audits):

A) Business grounds

• Faster delivery of infrastructure and applications (reduced lead time)

• Elastic scaling during seasonal peaks

• Pay-as-you-go cost alignment with actual usage

B) Control & audit grounds

• Centralized access control and audit trails

• Change management through IaC and approvals

• Standardized environments reduce configuration drift

C) Compliance grounds

• Better logging/retention options than ad-hoc on-prem setups

• Easier implementation of security baselines and policy enforcement

• Enables business continuity plans without large capex

D) Security & risk grounds

• Consistent patching and managed services reduce operational risk

• Central key management and strong identity patterns

---

6) Step-by-Step Implementation (Procurement → Setup → Audit/Claim)

Step 1: Decide the consumption model

• Pay-as-you-go (best for variable workloads)

• Reserved capacity / Savings plans (best for steady usage)

• Partner/reseller billing (if you want consolidated invoicing and managed services)

Step 2: Create account structure (landing zone)

• Separate accounts/subscriptions/projects for Prod / Non-prod / Sandbox

• Central billing + cost controls

• Central logging and security monitoring account/project

Step 3: Configure tax and billing settings (India)

AWS (console steps)

• Billing & Cost Management → Tax Settings

• Add/update GSTIN(s) for the relevant billing entities/accounts

Azure (invoice operations)

• Use Azure portal billing to download invoices and reconcile charges

• India billing entity (per Microsoft documentation) is Microsoft Corporation India Private Limited

Google Cloud

• Provide GSTIN in billing/tax settings as documented (GST behavior differs if GSTIN is absent/present).

Step 4: Implement cost governance (mandatory)

• Budgets + alerts

• Resource tagging/labels for cost centers

• Commitment strategy (reserve only after usage stabilizes)

Step 5: Implement security baseline

• MFA mandatory

• No shared admin accounts

• Central logging, alerting, and security posture checks

• Backup + restore drill documentation

Step 6: Create “Claim & Audit” evidence pack

Maintain a single folder (per month/quarter):

• Contract/Order form (or console subscription proof)

• Tax invoice(s) and credit notes

• Payment proofs

• Usage exports / cost reports

• Screenshot evidence of GSTIN/tax settings (if required)

• Internal approval note (ground + business justification)

---

7) Commands / Examples (Useful for Evidence, Automation, and Audits)

A) AWS: Cost and usage evidence

Enable/verify Cost and Usage Report (CUR) (conceptual; CUR setup is console-based)
AWS CLI identity check (audit trail support):

aws sts get-caller-identity

B) Azure: Subscription context and usage

az account show
az account list --output table

C) Google Cloud: Project + billing linkage checks

gcloud config list
gcloud projects list
gcloud beta billing accounts list

Tip: Save CLI outputs (with timestamps) into your monthly audit folder to demonstrate account ownership and scope.

---

8) How to “Claim” Cloud Computing Costs in India (GST ITC + Audit)

A) Claiming GST ITC (most common meaning of “claim”)

Your CA/tax team will typically require:

• Valid tax invoice

• Proof of service receipt/usage

• Business purpose justification

• Compliance with Section 16 conditions and Section 17 restrictions

Key legal anchors

• Section 16: eligibility + time limits

• Section 17: apportionment/restrictions for non-business/exempt usage

B) Common billing/tax scenario patterns

Google’s documentation explicitly describes India GST behavior for customers contracted with certain entities and GSTIN submission effects.
Microsoft documents India billing entity for Azure invoices.
AWS documents India billing setup and India tax settings process.

---

9) Common Issues & Fixes

Issue 1: GSTIN not reflected on invoice / wrong billing address

Fix

• Update tax profile (AWS Tax Settings / Google tax info / Azure billing profile)

• Request corrected invoice/credit note where required

• Reconcile before ITC claim

AWS tax settings steps are documented.
Google GSTIN submission is documented.

Issue 2: Multiple GSTINs across states (branch billing)

Fix

• Decide whether you want centralized billing or per-state billing

• Ensure “bill-to state” and GSTIN alignment; don’t mix GSTINs on a single billing profile unless provider supports it correctly

Issue 3: Unexpected high bill (runaway resources)

Fix

• Implement budgets/alerts day 1

• Enforce tagging/labels and policy controls

• Use quota limits for risky services in non-prod

Issue 4: Security incident due to leaked keys

Fix

• Rotate keys immediately, use short-lived credentials

• Enforce MFA and SSO

• Implement secret manager + scanning

• Restrict outbound access and enable anomaly detection

---

10) Security Considerations (Minimum Controls Checklist)

• Identity: SSO + MFA, least privilege, break-glass accounts

• Logging: admin activity logs, API logs, immutable storage for logs

• Network: private networking for sensitive workloads, WAF for public apps

• Data: encryption at rest + in transit; key rotation policy

• Backup/DR: backups + quarterly restore test; RPO/RTO documented

• Compliance: retention + access review; vendor contract clauses (SLA, breach notification, data export)

---

11) Best Practices

• Start with a landing zone pattern (accounts/projects/subscriptions separation)

• Enforce cost guardrails before deploying workloads

• Document business purpose per environment (Prod vs Dev)

• Keep an audit pack monthly: invoices, usage, approvals, tax settings proof

• Review ITC eligibility periodically; apply Section 17 apportionment if any non-business/exempt usage exists

• Prefer managed services where it reduces operational risk (but evaluate lock-in and exit strategy)

---

Conclusion

AWS, Azure, and Google Cloud operate in India with India-specific contracting and tax/billing behaviors. A successful cloud program in India combines:

1. correct account/billing/tax setup,

2. strong security baseline,

3. cost governance, and

4. clean documentation for GST ITC and audits under Section 16/17 principles.

#CloudComputing #AWS #Azure #GoogleCloud #CloudIndia #CloudBilling #GST #ITC #CGST #IGST #OIDAR #TaxCompliance #InvoiceReconciliation #CostManagement #FinOps #CloudSecurity #IAM #RBAC #MFA #SSO #AuditLogs #Logging #SIEM #Encryption #KMS #Backup #DisasterRecovery #RPO #RTO #LandingZone #Governance #PolicyAsCode #InfrastructureAsCode #Terraform #CloudFormation #AzureCLI #AWSCLI #gcloud #VPC #VNet #Kubernetes #Serverless #ManagedServices #DataProtection #RiskManagement #VendorDueDiligence #Procurement #BusinessContinuity #CostOptimization #Budgets #Tagging

---

cloud computing India AWS India Azure India Google Cloud India hyperscalers India cloud billing India cloud invoice GST GST on cloud services ITC on cloud services input tax credit cloud CGST Section 16 ITC CGST Section 17 blocked credit appor