Summary

  • India now requires a distinct network authorisation for a provider that hosts telecom equipment or network functionality for an already authorised carrier.
  • The framework recognises a regulated intermediary; it does not turn a general cloud contract into a telecom licence or transfer the carrier’s service authority.

India’s new telecom rules name a participant that used to disappear inside the supplier contract: the company hosting a carrier’s network equipment or functions. The Department of Telecommunications (DoT) has created a separate authorisation for a cloud-hosted telecommunication network provider. That is a consequential boundary decision. The rules were notified as G.S.R. 644(E); the official Gazette text is the governing instrument. A cloud operator can now be regulated for building and supplying parts of a telecom network, while the licensed carrier remains the party authorised to provide the service.

The distinction is narrower than “cloud is regulated.” Rule 54 describes a cloud-hosted telecom network as one built on cloud-computing principles, with network functions virtualised as software on standard hardware. Its service definition covers three different layers: physical infrastructure that houses a customer’s telecom equipment; cloud-hosted telecom equipment used in that customer’s network; and network functionality used by the customer to provide telecom services. The DoT’s live cloud-authorisation page repeats that scope.

The eligible customer is not any business buying compute. Rule 54 ties the service to another “new authorised entity” or licensee that holds an authorisation permitting it to use the network for telecom services or for establishing, operating, maintaining or expanding a network. The host’s permission therefore follows a regulated use case and a defined customer. It does not, on its face, cover ordinary hosting of an unrelated application, nor does it grant the host a blanket right to supply public telecom services.

That separation sits inside a six-part network authorisation framework. The DoT rules index lists the 2026 rules alongside the new authorisations for principal telecom services and migration. The network rules distinguish infrastructure providers, digital connectivity infrastructure providers, internet exchange points, satellite earth-station gateways, cloud-hosted networks and mobile-number portability. Five categories are national; mobile-number portability is organised by zone. A host cannot assume that one permit authorises every network function: Rule 54(3) confines it to its approved scope, and a different network category may require a separate authorisation.

The commercial entry terms look deliberately lighter than a carrier licence. DoT lists a ₹10 lakh entry fee, a ₹10,000 processing fee and no initial guarantee for the cloud-hosted category; the service page also says there is no annual authorisation fee. Eligibility still requires a company, FDI compliance, no pending dues, an auditor’s certificate and no fully overlapping authorisation. The government may issue a letter of intent before granting the permit, which specifies scope, network area, duration and effective date. The published service page says duration may extend to 20 years, as specified at grant.

The economic signal is mixed. No annual fee lowers the cost of keeping the authorisation, but the entry payment, eligibility test, audit trail and continuing security duties make this more than a low-cost label for a cloud product. For a specialist telecom cloud, the permit could formalise a market that otherwise depended on bespoke interpretations of carrier licensing. For a hyperscaler or systems integrator, the risk is whether its product crosses the rule’s line from general compute into equipment or functionality that constitutes a telecom network.

The rule gives the regulator categories, but it does not publish a bright-line test for every managed service.

The authorisation also does not move responsibility neatly from carrier to host. A provider may supply network-as-a-service under a mutual agreement on fair and non-discriminatory terms. But the customer must itself hold a service or network authorisation that permits that use. Contracting for the host’s work cannot create a service right the carrier does not possess.

Conversely, the new host has its own obligations as an authorised entity: the general rules require network systems and associated data, logs and information to be kept within India; set Indian-residency conditions for specified network and security roles; require ownership and control reporting; and permit inspection and audit. These obligations attach to the authorised network activity, not automatically to every cloud service sold in India.

DoT has moved the regime into its eServices portal. Its implementation notice says new applications and migrations under the Telecommunications Act, 2023 have been routed to the authorisation portal since 25 June 2026, after new legacy applications under the Indian Telegraph Act framework stopped. That proves the administrative channel is operating. It does not show how many cloud-network authorisations have been sought, granted or deployed. No adoption count or measured security outcome appears in the reviewed public material.

The practical test is now contractual as much as legal. A carrier considering hosted core, virtualised network functions or managed network operations must map each component to the authorisation held by the supplier and preserve its own service obligations. A supplier must decide whether it is selling generic infrastructure or network functionality, identify the permitted customer and document the line between the two. Procurement teams should ask who controls configuration, who can see logs, where systems and records reside, who meets personnel rules, and which party answers a regulator’s inspection.

The licence defines a perimeter; it does not settle how control is divided inside it.

Heng Lu’s Note 73 warns against mistaking participation in a system for authority over its decisions. The same discipline helps here: being the carrier’s essential technology supplier does not make a cloud host the authorised service principal, and calling the host a vendor does not erase the duties attached to its own regulated network role. India has formalised the intermediary. The operating contracts and the first published authorisations will show whether that boundary creates accountable specialisation or simply adds a new compliance layer.