Create a digital twin of a physical space on Azure Digital Twins to help organisations analyse how space is used and optimise it to better serve people’s needs at every level – from energy efficiency to employee satisfaction and productivity.
US government entities are eligible to purchase Azure Government services from a licensing solution provider with no upfront financial commitment or directly through a pay-as-you-go online subscription.
Important: The price in R$ is merely a reference; this is an international transaction and the final price is subject to exchange rates and the inclusion of IOF taxes. An eNF will not be issued.
Azure Germany is available to customers and partners who have already purchased this, doing business in the European Union (EU), the European Free Trade Association (EFTA) and in the United Kingdom (UK). It provides data residency in Germany with additional levels of control and data protection. You can also sign up for a free Azure trial.
The price below represents a 50% preview discount
|Message Pricing||$-/1M messages|
Support and SLA
- Free billing and subscription management support.
- Flexible support plans starting at $29/month. Find a plan
- No SLA is available during preview, but will be available during general availability.
Any component connected to an Azure Digital Twins spatial intelligence graph is considered a node. In the graph, this includes all spaces, devices, sensors and users. As you model the real world in Azure Digital Twins, those nodes which store metadata and real-time data are the nodes for which you will be billed. Let’s look at two examples of smart building solutions built on Azure Digital Twins:
- Scenario A: 1 tenant, 1 building, 2 floors, 4 rooms per floor, 1 device per room and 2 sensors per device. In this scenario, there are 36 nodes.
- Scenario B: 1 tenant, 10 buildings, 3 floors per building, 50 rooms per floor, 1 device per room and 2 sensors per device. In this scenario, there are 6,041 nodes.
Messages count three things: API calls to the Azure Digital Twins APIs, incoming (ingress) messages sent to device and sensor nodes in Azure Digital Twins or messages sent from Azure Digital Twins (egress) to other systems. All of these are counted for billing purposes.
Pricing per node
In Scenario B, there are 6,041 nodes and the cost for that would be $- per month with discounted pricing, or $- per month with full pricing.
Pricing per message volume
If the devices send 1 message per minute, that would be 64,800,000 messages in a 30-day month (1440 * 1500 * 30) and that would be 64.8 million messages at a rate of $- per million results, using the 50% discounted pricing, which would result in $- per month, or $- per month with full pricing.
In the examples given above, the customer would be charged for the number of nodes, added to the customer’s messaging volume.
Total price = Pricing per node + Pricing per message volume
Discounted: $- + $- = $-
Full price: $- + $- = $-
Per-node pricing is prorated on an hourly basis. During an hour, if there is fluctuation in the number of nodes connected to Azure Digital Twins, the highest number of connected nodes for that hour will be billed.
Changing which devices send data and how often those devices send data will affect the overall pricing.
Estimate your monthly costs for Azure services
Review Azure pricing frequently asked questions
Learn more about Azure Digital Twins
Review technical tutorials, videos and more resources