Header Place holder

Azure Time Series Insights

Instantly explore and analyze time series data in IoT solutions

Apply for trial Buy Now

Pricing Details

Data Processing Unit PREVIEW = ¥ 299.3 per unit per month (Each unit allows customers to process up to 100 GB/month)

Additional Data Processed PREVIEW = ¥ 2.035 per GB

Meta Data Storage PREVIEW = ¥ 0.407 per MB

*The following prices are tax-inclusive.

WARM DATA ANALYSIS (USED TO ANALYZE DATA ON AD-HOC BASIS) COLD DATA ANALYSIS (USED TO ANALYZE TIMESERIES-OPTIMIZED DATA)PREVIEW
StoragePREVIEW ¥ 30.528/GB Blob pricing*
Queries PREVIEW No charge (limited to 10 concurrent queries) ¥ 0.102/GB
*Cold data is stored in customers’ own Storage Account that customers can configure during Time Series Insights set up. Customers will see additional blob transaction charges for data reads and writes that Time Series Insights service will be doing over data stored in the customer-owned Azure Storage account.
Note: Cold Data Analysis capabilities are immediately available in public preview. Warm data analysis which folds in the current in-market GA service capabilities will light up in the next few months within the same service offering.
Customers can continue to use Time Series Insights with the old pricing model for warm, adhoc data analysis. However, we highly encourage you to use the updated offering as it offers many new capabilities with timeseries-optimized analytics as well as Pay-As-You-Go pricing, cost savings and flexibility to scale as per customer needs.
*The following prices are tax-inclusive.

*Monthly price estimates are based on 744 hours of usage per month.
S1 S2
Storage per unit2 30 GB or 30 million events1 300 GB or 300 million events1
Daily ingress per unit2,3 1 GB or 1 million events1 10 GB or 10 million events1
Maximum retention5,6 13 months5 13 months5
Queries Unlimited Unlimited
Maximum number of units4 10 10
Price (per unit/month) ¥ 1526.4 ¥ 13737.6
1 An event is a single unit of data with a timestamp. For billing purposes, we count events in 1-KB blocks. For example, a 0.8-KB actual event is billed as one event, but a 2.6-KB event is billed as three events. The maximum size of an actual event is 32 KB.

2 Ingress and total storage are measured by the number of events or data size, whichever comes first.

3 Ingress is measured per minute. S1 can ingress up to 720 events/minute/unit and S2 can ingress 7,200 events/minute/unit.

4 An environment can be scaled up to 10 times by adding more units.

5 The data is retained in Time Series Insights based on the selected retention days or maximum limits.

6 Retention is configurable in the Azure portal. The longest allowable retention period is a rolling year of 12 months + 1 month, which is defined as 400 days.

FAQs

Expand
  • Why is Azure introducing a new business model?

    Customers have provided feedback that they would prefer pricing that allows them to scale data processing, storage and querying independent of each other. As we introduce the revamped Time Series Insights service with the new set of industrial IoT insights capabilities, we are introducing a new business model that aligns pricing with our customer usage patterns.

  • What happens to the current in-market S1 and S2 SKUs?

    Azure will continue to support customers who are using the S1 and S2 SKUs. However, we encourage customers move to the new business model as it offers several benefits - new set of industrial IoT insights capabilities that come with lower price points, lower total cost of solution, flexibility to pay-per-use and ability to control costs by changing data storage and querying patterns.

  • What is included in the new Time Series Insights SKU?

    The new SKU introduces the new timeseries-optimized cold path analytics while continuing to support warm path ad-hoc data exploration capabilities. The service, at the time of public preview launch will start by supporting the cold path analytics scenarios. The service will be updated in the coming months to fold in the in-market warm path, ad-hoc analytics with the ability to route timeseries data to either one or both storage layers as your business requires.

    The user experience for setting up your time series environment will include the current S1/S2 SKUs as well as the updated new SKU for the time being. We expect that over time, as the warm adhoc analytics capabilities get folded into the new SKU, we will encourage customers to move away from S1/S2 SKUs into the single, unified SKU and capabilities in the Time Series Insights offering to leverage the updated pricing benefits as well as more comprehensive capabilities of the end-to-end solution.

  • What's included in the Time Series Insights S1 SKU?

    Each unit of S1 includes a maximum of 30 GB of total storage or 30 million events (whichever comes first), as well as maximum daily ingress and configurable retention. Also included is the Time Series Insights visualization experience. There is no limit on the number of users or queries that can be conducted.

    For example, If you provision 1 unit of S1, you can configure your environment to retain data for up to 400 days of retention. If configured to 400 days retention, you cannot exceed an average daily ingress of 1/400th of the allotted environment (for 1 unit of S1, 30 GB). In this example, 1/400th of the total storage capacity per day is .075 GB or 75 MB.

    Another example-if you configure your environment to retain data for 180 days with one S1 unit, you cannot exceed daily ingress of .166 GB (166 MB) per day. If your ingress rate exceeds .166 GB per day, your data will not be stored for 180 days. If, for example, your ingress rate averaged .189 GB per day, you would realize just over 158 days of retention (30 GB/.189 = 158.73 days of retention).

    If you want to maximize your daily ingress, you can ingress up to 1 GB per day, and retain that data for up to 30 days.

  • What's included in the Time Series Insights S2 SKU?

    Each unit of S2 includes a maximum of 300 GB or 300 million events (whichever comes first) of total storage and configurable daily ingress and retention. Also included is the Time Series Insights visualization experience. There is no limit on the number of users or queries that can be conducted.

    For example, if you provision 1 unit of S2, you will achieve 400 days of retention if you configure the environment to retain for 400 days and your average daily ingress is 1/400th of 300 GB (.75 GB or 750 MB per day) or less.

    Another example-if you configure your environment to retain data for 180 days with one S2 unit, you will achieve 180 days of retention so long as you do not exceed daily ingress of 1.66 GB (1,660 MB) per day. If your ingress rate exceeds 1.66 GB per day, your data will not be stored for 180 days. If for example, your ingress rate averaged 1.89 GB per day, you would achieve just over 158 days of retention (300 GB/1.89 = 158.73 days of retention).

    If you want to maximize your daily ingress, you can ingress up to 10 GB per day, and retain that data for up to 30 days.

  • What happens if I want to send events larger than 1 KB using the S1 or S2 SKU?

    An event is a unit of data up to 1 KB. Larger events are counted in multiples of 1 KB. For example, 0.8 KB is billed as one event, but a 2.6 KB event is billed as three events. Events larger than our maximum, 32 KB, will be rejected.

  • How does billing work for the S1 and S2 SKUs?

    You will be billed on a daily prorated basis. A day commences at midnight UTC for the purposes of billing. The billing is generated on a monthly basis. For instance, if a customer uses three units of Time Series Insights S1 for a total of 5 days, the customer is billed at the end of the month for 3 units x 5 days x (¥ 1526.4/31) = ¥ 738.581.

    Similarly, if a customer uses three units of Time Series Insights S2 for a total of 5 days, the customer is billed at the end of the month for three units x 5 days x (¥ 13737.6/31) = ¥ 6647.226.

Support & SLA

If you have any questions or need help, please visit Azure Support and select self-help service or any other method to contact us for support.

To learn more about the details of our Service Level Agreement, please visit the Service Level Agreements page.