AWS & Azure Cloud Pricing Changes: What Indian SMBs Must Recheck

Your cloud bill probably went up last year and nobody on your team can say exactly why. The invoice from AWS or Azure shows a line item in rupees or dollars, the finance team asks why it moved, and the answer usually involves a mix of egress charges, a region you chose three years ago without much thought, and a few instances nobody remembers launching. Now both hyperscalers are expanding and reshaping their Indian footprint, which means the region you picked may no longer be the best choice, and pricing that looked fine in 2023 may not survive the next renewal.

For a 20-person company in Pune or a 60-seat BPO in Coimbatore, cloud spend is no longer a rounding error. We regularly see SMBs paying for compute in Singapore or Mumbai while their users sit in Hyderabad, or running nightly backups across regions because nobody set a retention policy. Fixing that takes an afternoon, not a re-architecture. This article walks through what to recheck in your cloud spend and region choice in 2026, how to weigh latency, compliance and cost against each other, and a worked example of a migration that actually paid off.

The article covers why the Indian region map is changing, how to build a comparison before you move anything, a case study with real numbers, a provider comparison table, a step-by-step review you can hand to your vendor, the mistakes we see most often, and an FAQ for the questions owners ask us most.

Key Takeaways

• Recheck your region choice before you recheck your instance sizes. A workload in the wrong Indian region can cost more in latency and egress than the compute it runs on.
• Data egress and cross-region replication are the hidden lines in most SMB bills. Pull a 90-day cost breakdown by service, not by account.
• Map each workload to its compliance class (RBI, DPDP Act, sector rules, or none) before deciding where it can live.
• Reserved capacity and savings plans pay off only for steady workloads. Be honest about which of your servers are steady.
• Budget a parallel-run period of two to four weeks for any migration. Cutting over on a Friday is where most of the regret comes from.
• Get pricing quoted in INR with GST treatment clear from the start. Currency swings and GST input credit rules change the real comparison.

Why cloud pricing in India for SMBs needs a fresh look in 2026

The short answer is that the hyperscalers have been building more capacity inside India, and the way they price, route and bill workloads has shifted with it. Both AWS and Azure have expanded in Mumbai, Hyderabad and, in Azure's case, additional Indian locations, with regional services becoming available in more places over time. What matters to you is not the press release but what changes on your bill: which services are available locally, which still route through Singapore or elsewhere, and how traffic between regions is charged.

Two things usually go unnoticed. First, a service you use may have become available in-region, but your workload still points at the old endpoint, so you keep paying cross-region transfer fees for something that could be local. Second, a managed service may be cheaper in a newer region than in the one you chose at launch. Neither changes automatically. You have to check.

There is also a compliance dimension that has sharpened. The Digital Personal Data Protection Act, 2023 and its rules are rolling out in stages, and sectoral regulators like RBI for payment and financial data already expect specific handling. Some customers, especially government-linked buyers and regulated enterprises, now ask suppliers where data physically sits. That question affects which region you should use, not just what you pay.

The exchange rate and GST layer

Most hyperscaler invoices arrive in USD and are converted at the billing rate. A 2 per cent move in the rupee changes your rupee bill by roughly the same amount, and it compounds across a year of renewals. For budgeting, convert at a conservative planning rate and track the variance monthly rather than treating the invoice as fixed.

On GST, the key question is whether you can claim input tax credit on your cloud invoices. If your cloud provider or reseller bills you with GST that you can claim against your output tax, the effective cost is lower than the sticker price suggests. If you buy through a reseller that charges differently, or you are not GST-registered in the way you thought, the comparison changes. Confirm this with your CA before you sign anything. A reseller margin of 8 per cent can be worth paying if it gives you clean GST invoicing and local support; it can be a waste if you could have contracted directly and claimed credit.

How to compare latency, compliance and cost before you migrate

The mistake we see most is comparing providers on the price of a single virtual machine. Real cloud cost is the sum of compute, storage, egress, managed service fees, support plans, and the engineering time spent running it. Latency and compliance then decide which options are even allowed on the list. Work through the three in this order.

Step 1: Classify your workloads by compliance

Make a table with every system you run: the ERP, the website, the CRM, the file share, the backup target, the internal analytics database, the WhatsApp integration, the payroll tool. For each, note what personal or financial data it holds, which regulator or customer contract governs it, and whether there is a stated data residency requirement. Many SMB workloads have no requirement at all. A marketing site with no personal data can run almost anywhere. A system storing customer PAN, bank details or health information needs a closer look.

Step 2: Measure latency where your users actually are

Latency matters most for interactive systems: a billing application used by staff in three offices, a point-of-sale system, a voice bot answering callers. It matters less for batch jobs and backups. Measure from your real locations. A simple test is to run ping and a basic HTTP timing check from your Gurgaon or Bengaluru office to candidate regions, and to log the round-trip time for a real transaction, not just ICMP. Round-trip times inside India between a Mumbai office and a Mumbai or Hyderabad region are typically low enough for interactive work; the difference shows up when the region is abroad or when the application makes many chatty calls per screen.

Step 3: Model the full cost, including egress

Pull a 90-day billing export and group it by service, by region and by data transfer type. Look for three things: data transferred out of the cloud to the internet, data transferred between regions, and data transferred between availability zones inside one region. Egress and cross-region charges often surprise owners. Also look at storage tiers: objects that are never read should not sit in the hot tier. Only after this breakdown should you run the price comparison, because the answer depends on how your traffic flows, not on list prices.

Worked example: a 15-person logistics firm in Gurgaon

A logistics firm with 15 office staff and a fleet dispatch team of about 40 field users was running its dispatch and tracking system on four physical servers in a rented rack in a Gurgaon colocation facility. The monthly cost, including power, the colocation share, the hardware amortisation and a part-time system administrator's time, came to roughly ₹45,000 a month. The servers were three years old, the backup process was manual, and the owner wanted a DR plan he could actually test.

We started with a workload inventory. The dispatch database held customer names, delivery addresses and phone numbers, which put it under the DPDP Act's personal data obligations, though there was no sector-specific residency requirement. The tracking API was latency-sensitive: field staff were updating status from phones on patchy mobile networks, and the app made several calls per update. The reporting database and the document archive were not interactive at all.

We moved the dispatch and tracking application and its database into an in-India region on AWS, sized to the real peak load rather than the old hardware's capacity. We used a single-region deployment across two availability zones, a managed database with automated backups, and a reserved-instance commitment on the steady base load with on-demand capacity for peaks. The reporting database moved to a smaller instance on a schedule, running only during business hours. The document archive went to object storage with a lifecycle rule that moved files older than 90 days to a cheaper tier and deleted backups beyond the retention policy the owner had agreed to.

The migration took about six weeks from assessment to cutover, with a two-week parallel run where both the old and new systems received dispatch updates. The new monthly run cost came to roughly ₹18,000 including support, and the owner dropped the colocation contract. The savings were real, but the bigger gains were a tested backup and restore process and a recovery time the owner could describe in minutes instead of days.

The honest caveat: the saving depended on retiring the hardware and the colocation contract on time. Two of the four servers ran a legacy reporting job that nobody wanted to touch, and that job ran for three extra months, costing about ₹9,000 extra in duplicate hosting before someone rewrote it. Budget for the things you think you can turn off.

Cloud provider comparison for Indian SMBs

The right choice depends on your existing skills, your software licences and your support needs. The table below is a practical starting point rather than a verdict; prices change, and you should confirm current rates on each provider's pricing calculator with an INR or GST-aware quote.

Criteria	AWS	Microsoft Azure	Google Cloud	Local managed provider (reseller)
In-India regions	Mumbai, Hyderabad	Multiple Indian locations	Mumbai, Delhi NCR	Depends on the upstream provider
Best fit	Broadest service catalogue, mature tooling	Organisations already on Microsoft 365 and Windows Server	Data and analytics-heavy workloads, Kubernetes	Owners wanting local invoicing and hands-on support
Licensing fit with existing Microsoft estate	Possible, but needs care	Strongest, including hybrid benefits	Weaker	Depends on contract
Billing and GST invoicing	Direct or via reseller	Direct or via reseller	Direct or via reseller	Usually simplest, with a margin
Skills availability in Indian market	Very high	High	Moderate	Varies with the partner
Typical fit for an SMB with no in-house cloud team	Good with a managed partner	Good with a managed partner	Good for data-led teams	Often the easiest start

If you are already paying for Microsoft 365 or Windows Server licences, check the hybrid and licence-mobility terms before assuming AWS is cheaper. Often the Azure comparison looks better once existing licences are counted. If you are a small team with no cloud specialist, a managed partner who handles billing, patching and backups is usually worth the margin. eDarpan's cloud migration and managed services cover exactly this, and our IT consulting team can run the workload classification and cost model before you commit to a provider.

How do I review my cloud spend and region choice step by step?

Work through this sequence with your vendor or internal team. Each step produces a document you can share with finance.

1. Export 90 days of billing data. Group by service, region and transfer type. Save the file; you will refer to it repeatedly.
2. Build the workload inventory. One row per system: owner, data types held, compliance class, user locations, peak load, RTO and RPO targets.
3. Measure latency from real user sites. Test with actual transactions, not just ping. Record the results against each candidate region.
4. Identify idle and oversized resources. Look for stopped-but-billed volumes, unattached disks, old snapshots and instances running below 20 per cent utilisation for 30 days.
5. Check for cross-region and egress charges. Find which services talk across regions or send large volumes to the internet, and whether they can be co-located.
6. Decide commitment strategy. Apply reserved capacity or savings plans only to the steady base. Keep on-demand for peaks and experiments.
7. Model two or three scenarios. Current state, optimised in place, and migrated to a candidate region or provider. Include engineering time, licensing and support in each.
8. Plan a parallel run. Schedule two to four weeks with both environments live, define the cutover criteria in writing, and name the person who can call a rollback.

Common mistake and pro tip

Common mistake: Moving everything to the newest Indian region because it is closest to head office, without checking whether each service you need is actually offered there. Several managed services arrive in a region later than compute, and a workaround that routes calls back to another region can quietly add both latency and egress cost. Check the service availability page for your exact services before you plan the move.

Pro tip: Ask your provider or partner for the bill for a month in which you ran a restore test. Restores generate read traffic and temporary compute that never shows up in the planning spreadsheet. If the restore bill is large, your backup design needs changing before you go live, not after.

What should an SMB watch for in its cloud contract?

Read the support plan carefully. The cheapest tier often has response times that are not usable for a business-critical system, and the mid-tier may be the minimum that gives you a named contact. Check the data processing terms, the sub-processor list, the stated data residency, and how the provider handles requests from authorities. Ask for the exit terms too: how long it takes to get your data back, in what format, and whether there is an egress charge for leaving. A contract that is easy to enter and hard to leave is expensive in ways that do not appear on the first invoice.

Also check whether your contract is in the name of the right legal entity. We have seen companies that restructured or merged discover that the cloud account was still tied to a director's personal billing details, which made GST claims and audits messy. Confirm the billing entity, the GSTIN on the invoices, and the authorised signatories in writing.

Frequently asked questions

Is cloud hosting in India always cheaper for an SMB?

No. In-India regions are not automatically cheaper than other regions for every service, and the total cost depends on egress, support and engineering time. The right comparison is the full cost of the workload in each candidate region, including the traffic it generates. Run the model before deciding.

Does the DPDP Act require my data to stay in India?

The DPDP Act and its rules set obligations on handling personal data, and the transfer provisions allow certain cross-border flows subject to conditions the government may specify. Sector regulators can impose stricter rules. Check with a lawyer or your CA for your specific data and sector, rather than assuming either way.

How much can I realistically save by moving off on-prem servers?

It depends on what you retire. A rack, power, hardware amortisation and administrator time can be significant, but cloud bills grow if you do not right-size. The worked example above saved about 60 per cent on running costs, but that required retiring hardware and the colocation contract on schedule.

Should I buy cloud directly or through a reseller?

Buy directly if your team can handle billing, support tickets and account management and you can claim GST input credit cleanly. Use a reseller if you want local invoicing, phone support and someone to manage the account, and you accept the margin. Compare the total cost, not only the headline price.

How long does a cloud migration take for a small business?

For a single application with a database and modest traffic, four to eight weeks from assessment to cutover is typical, including a parallel run. Larger estates with legacy dependencies take longer. Be suspicious of any plan that promises a full migration in days.

What is the single most useful thing I can do this month?

Export your last 90 days of cloud billing, group it by service and region, and find the top three line items. Most SMBs find at least one clear saving within an hour of doing this, usually an idle resource or an expensive transfer path.

Do I need to change my cloud setup for the new Indian regions?

Not necessarily. Staying put is a valid choice if your latency, compliance and cost are acceptable. Change only when the numbers show a benefit. The point of the review is to decide deliberately, not to move for its own sake.

Where eDarpan fits in

If you want an independent view before committing, the review above is what we do for SMB clients: a billing breakdown, a workload and compliance map, latency tests from your offices, and a written recommendation with the migration plan. You can start with a consulting engagement if you want the analysis first, or move straight to cloud migration and managed services if the answer is already clear. If your business is also reviewing its productivity suite, our notes on Google Workspace licensing and Microsoft 365 licensing cover how those costs interact with cloud decisions.

Cloud decisions also connect to other parts of the stack. If you run customer messaging, your WhatsApp Business API and bulk SMS volumes may generate traffic that belongs in the same cost model. If you are building custom applications, the custom software development and mobile app development teams can tell you early whether a feature will push data across regions.

For further reading, these posts cover adjacent parts of the same decision:

• Cloud Market Hits $2T: What Indian SMBs Should Check Before Picking AWS, GCP or Azure sets out a provider checklist that complements the table above.
• AWS and Azure Eye India Data Centre Shift: What Indian SMBs Should Check looks at the regional expansion in more depth.
• Sovereign Cloud Data Centres in India: What SMBs Gain and Lose covers the residency trade-offs.
• Windows 10 End of Support: Upgrade Costs for Indian SMBs in 2026 is useful if your cloud review overlaps with a device refresh.
• Rohit Patel's Office Suite Startup: What Indian SMBs Should Watch helps if you are choosing an office suite alongside your cloud platform.

If you want help putting numbers against your own estate, contact eDarpan and tell us roughly what you run, where your people sit, and what your current bill looks like. We will tell you honestly whether a change is worth making. You can also read more about who we are and how we work before you reach out.

Cloud pricing India SMB 2026: the decision in one paragraph

Treat your region choice and your cloud pricing as one decision, reviewed together. Start with billing data and a workload map, test latency from your real offices, check compliance per system, and only then compare providers on total cost. Commit to reserved capacity only for the steady base, plan a parallel run, and keep the contract exit terms in view from day one. A review like this takes a few weeks and usually pays for itself in the first quarter, whether the answer is to stay, optimise in place, or move.

Image credit: Innovate Maryland Emerging Technology Center by MDGovpics via flickr (BY 2.0), sourced through Openverse.