Azure Stream Analytics pricing

A real-time stream processing service in the cloud

Azure Stream Analytics is an event-processing engine in the cloud that uncovers insights from data generated by devices, sensors, cloud infrastructure services and applications in real time. With out-of-the-box integration for Azure IoT Hub and Azure Event Hubs, Azure Stream Analytics can simultaneously ingest and process millions of events per second and can deliver actionable insights or alerts with ultra-low latencies, rich visual dashboards, and can kick off actions to other services.

Pricing details

Azure Stream Analytics is priced by the number of Streaming Units provisioned. A Streaming Unit represents the amount of memory and compute allocated to your resources. You can learn more about how many Streaming Units are required.

Standard streaming unit

Standard Dedicated
Resource Type Stream Analytics Job Stream Analytics Cluster
Streaming unit $-/hour with a 1 SU minimum $-/hour with a 36 SU minimum*
Virtual Network support No Yes
C# User-defined functions Limited to West Central US, North Europe, East US, West US, East US 2 and West Europe All regions
Custom deserializers Limited to West Central US, North Europe, East US, West US, East US 2 and West Europe All regions

*In the future, additional charges may apply for private endpoints created and related inbound and outbound charges. See Private Link Service pricing page for more details.

Azure Stream Analytics on IoT Edge

Azure Stream Analytics on IoT Edge enables you to run your stream processing jobs on devices with Azure IoT Edge. Create your stream processing jobs in Azure Stream Analytics and deploy them to devices running Azure IoT Edge through Azure IoT Hub.

Azure Stream Analytics on IoT Edge extends all of the benefits of its unique streaming technology from the cloud down to devices. It enables you to run Complex Event Processing (CEP) closer to IoT devices and run analytics on multiple streams of data on devices or gateways.

Price per job $-/device/month

If you want to run Azure Stream Analytics on IoT Edge on more than 5,000 devices, please contact Microsoft.

Note: Billing starts when an ASA job is deployed to devices, no matter what the job status is (running/failed/stopped).

Support and SLA

  • We provide technical support for all Azure services released to general availability, including Stream Analytics, through Azure Support, starting at $29/month. Billing and subscription management support is provided at no cost.
  • SLA – We guarantee at least 99.9 per cent availability of the Stream Analytics API. We guarantee that 99.9 per cent of the time, deployed Stream Analytics jobs will be either processing data or available to process data. Learn more about our SLA.


  • A standard streaming unit is a blend of compute, memory and throughput.

  • Streaming units can be selected via the Azure portal or Stream Analytics management APIs.

  • The primary factors that affect streaming units needed are query complexity, query latency and the volume of data processed. Streaming units can be used to scale out a job in order to achieve higher throughput. Depending on the complexity of the query and the throughput required, more streaming units may be necessary to achieve your application’s performance requirements.

  • Streaming units are billed hourly, based on the maximum number of units selected during this hour.

  • There is a default quota and if needed you can request a larger number of streaming units by filing a support ticket.

  • Azure Event Hubs or Azure IoT Hub are recommended as scalable event brokers for your stream analytics solution. However, Stream Analytics also supports getting data from Azure Blobs.

  • Azure Stream Analytics’ standard streaming units offer richer capabilities like running custom code (written in JavaScript) and Geospatial functions, Visual Studio integration, and have removed ingress throttling limits. The older model is no longer available.

  • On 1 February 2017, existing streaming jobs were migrated without any interruption to the standard streaming model. Contact us, if you have any questions.

  • Azure Stream Analytics on IoT Edge is charged based on the number of devices the engine is running on and not on the number of sensors or total devices in your architecture. For example, if you have 100 sensors and use a single gateway to run Stream Analytics on IoT Edge, only a single device is counted for billing purposes.

  • Azure Stream Analytics on IoT Edge Preview is priced by the number of jobs that have been deployed on a device. For instance, if you have two devices and the first device has one job, whereas the second device has two jobs, your monthly charge will be (1 job)x(1 device)x($-/job/device)+(2 jobs)x(1 device)x($-/job/device) = $-+$- = $- per month.

    All billing is pro-rated. For instance, if a job is deployed only for a partial month, the billing for that job is pro-rated.

    A job on Azure Stream Analytics on an IoT Edge device can use one CPU core. We don’t limit the volume of data that can be processed by this job.

    If you want to run Azure Stream Analytics on IoT Edge on more than 50 devices, please contact Microsoft.

  • Creation, test and preparation of the job in the Azure Stream Analytics portal is free. Deployment of the job and monitoring of your job will require the use of messages that will count towards your IoT Hub allowance. Deployment of a job with also requires the use of Azure blob storage.

    You can choose to update a job multiple times a month without incurring extra charges from the Stream Analytics service. Updates and deployment are provided using standard messaging capability via IoT Hub.


Estimate your monthly costs for Azure services

Review Azure pricing frequently asked questions

Learn more about Azure Stream Analytics

Review technical tutorials, videos and more resources

Added to estimate. Press 'v' to view on calculator

Talk to a sales specialist for a walk-through of Azure pricing. Understand pricing for your cloud solution.

Get free cloud services and $200 in credit to explore Azure for 30 days.