Telstra Sells a Network Slice for Microsoft Teams

Telecoms.com's Nick Wood reported on 7 September that Telstra has launched Dynamic 5G for Video Calling, a business service that directs Microsoft Teams traffic onto a dedicated slice of its 5G network so that calls do not compete with other traffic during peak periods. Telstra's own description is that it "represents a move toward application-aware, business-grade connectivity, designed to prioritise performance for selected traffic, not just speeds." The operator names construction, utilities, transport and logistics as the sectors it is aimed at, where staff are on the move, temporarily located or in the field. Dynamic 5G is the umbrella brand Telstra launched for business slicing in 2025, and its distinguishing feature is a proof-of-value engine that monitors slicing traffic continuously and checks whether the customer is receiving the service promised; if it falls short, the customer does not pay. Telecoms.com sets the launch against T-Mobile US's SuperMobile business tariff, Deutsche Telekom's gaming and video-calling slices, EE's Fast Lane and VodafoneThree's SuperMobile in the UK, and cites ABI Research's forecast that the slicing market will grow from $6.1 billion in 2025 to $67.5 billion in 2030. No price, no slice parameters and no customer count were published.

3 slicing products in 3 weeks, sold 3 ways

Since 20 August, 3 operators have put differentiated network quality on sale in 3 different forms. EE sells a priority lane to consumers as a handset tariff, which I covered when Fast Lane launched. Vodafone sells a quality profile to developers through an API in Germany, without a price or a published profile. Telstra sells a slice to enterprises per application, with the application chosen by the operator and the enterprise buying the outcome. These are the 3 channels through which an operator can sell the same underlying capability, and it is useful to have all 3 on the market at once because they will produce different evidence. The tariff channel will produce an attach rate. The API channel will produce a call volume. The enterprise channel will produce a contract with a service commitment in it, and that is the only one of the 3 that forces the operator to state what the slice delivers.

The SLA clause is the news

When Vodafone launched quality on demand yesterday I wrote that the first thing a serious enterprise buyer would ask for was a service level, because a priority is not a reservation and a profile without published parameters tells the buyer nothing about what it is paying for. Telstra's answer is the proof-of-value engine. It does not publish the parameters either, at least not in what has been reported, but it commits to measuring the slice against what was promised and to not charging when the promise is missed. That is a commercially meaningful difference. It converts a best-effort improvement into a product with a defined failure condition, and it means Telstra is now generating, internally, a number no slicing launch to date has disclosed: how often a commercial slice fails to deliver what the customer bought. The pay-out rate of that engine is the honest measure of whether slicing works on a live network, and Telstra has built the instrument that produces it. Whether it will ever publish it is another matter, but the number now exists somewhere, which was not true of any of the other launches.

Application-aware means the operator picks the application

The product is sold for Teams, and only Teams. That is a practical choice, since Microsoft publishes the network endpoints its services use, which is what allows an operator to steer that traffic onto a slice without inspecting its content, and it is the application that a construction firm's site manager or a utility's field crew is most likely to be on. But it also shows where the operator's own control ends. Telstra decides which application qualifies, does the classification itself, and holds the only billing relationship. Microsoft is not a party to the arrangement, and the customer cannot extend the slice to another application without Telstra adding it. This is the same pattern that Fast Lane and the Vodafone API follow: the service is possible because it stays inside 1 administrative domain, with no counterparty to negotiate with and no shared model to agree. An enterprise that wants its own collaboration tool, its own robotics controller or its own agent to request the slice on demand, and to verify for itself that the promise was kept, is asking for the coordination layer that I argued no runtime supplies. The proof-of-value engine is a step toward it, because it is an audit trail, but it is Telstra's audit trail, read by Telstra, and the customer sees only the invoice it produces.

When Will We See Slicing as a Service?

I have been arguing for years that the natural fulfillment of the differentiated connectivity 5G promise would be slicing as a service. Specifically, network operators who will find themselves with ample capacity should create a platform that would allow third party to discover, configure, reserve and consume network resources on demand. Enterprise and government CIOs know better than telecom operators what their connectivity needs are and how they are going to evolve. They do not want to select a pre packaged slice that my correspond to some conditions or services at some point in time. They do not want to spend time educating the operator about their needs, because some of them are proprietary and become differentiating factors and they evolve over time. They are used to configuring cloud services. It is time for connectivity services to catch up.