Azure SignalR Service cost: per unit per day, by tier

Quick answer

Azure SignalR Service bills per provisioned unit per day on the Standard tier, where each unit supports a set number of concurrent connections (about 1,000) and daily messages (about 1 million), with a Free tier for small use and autoscaling on Premium. Cost scales with the units you provision, so right-sizing units to real concurrent connections and enabling autoscaling rather than provisioning for peak are the levers.

Azure SignalR Service provides managed real-time messaging (WebSockets and fallbacks) so you do not run your own connection servers. It is priced by provisioned unit, where each unit supports a capacity of concurrent connections and messages, so the cost is the units you run, and over-provisioning for a rare peak is the common waste.

Units and tiers

Tier	Billing
Free	Limited connections and messages, no SLA
Standard	Per unit per day (~1,000 connections + ~1M messages each)
Premium	Per unit, with autoscaling and availability zones

The Free tier covers development and small applications. Standard bills per unit per day, each unit handling about 1,000 concurrent connections and 1 million messages, so you provision units to cover peak concurrency. Premium adds autoscaling and zone redundancy at a higher per-unit cost.

Right-size and autoscale

The overspend is provisioning units for peak concurrency that occurs rarely, paying for that capacity all day every day. Right-size units to typical concurrency and use autoscaling (on Premium) to add units during genuine peaks rather than running peak capacity constantly. Monitor concurrent connections and message rate to set units accurately.

Controlling SignalR cost

Right-size provisioned units to real concurrent-connection and message needs, use autoscaling on Premium to handle peaks without running peak capacity constantly, use the Free tier for development, and reduce unnecessary messages (do not broadcast to connections that do not need updates). Because cost is per provisioned unit, sizing to actual concurrency is the lever, the same provisioned-capacity discipline as other unit-based services like Event Hubs.

FAQ

How is Azure SignalR Service priced?

Per provisioned unit per day on the Standard tier, where each unit supports about 1,000 concurrent connections and 1 million daily messages, with a Free tier for small use and autoscaling on Premium. Cost scales with the number of units you provision to cover your peak concurrency.

How do I reduce Azure SignalR cost?

Right-size provisioned units to real concurrent-connection and message needs, use autoscaling on Premium to handle peaks without running peak capacity constantly, use the Free tier for development, and reduce unnecessary messages by not broadcasting to connections that do not need updates. Sizing units to actual concurrency is the main lever.

What is a SignalR unit?

The billing and capacity unit for the Standard tier, each supporting about 1,000 concurrent connections and 1 million daily messages. You provision units to cover your peak concurrency, and pay per unit per day. More units handle more connections and messages at proportionally higher cost.

Why over-provision SignalR units is wasteful?

Because you pay per provisioned unit per day whether or not the capacity is used, so provisioning units for a peak concurrency that occurs rarely means paying for that capacity all day every day. Right-sizing to typical concurrency and using autoscaling for genuine peaks avoids paying for constant peak capacity.

Should I run my own SignalR or use the managed service?

The managed SignalR Service removes the operational burden of running and scaling your own WebSocket connection servers, which is significant. For real-time features at any meaningful scale, the managed service is usually worth its per-unit cost versus building and operating connection infrastructure yourself. Right-size units to keep it economical.

Does C3X estimate SignalR cost?

C3X prices the SignalR Service resource and its tier and unit count from your Terraform, so the provisioned cost appears before deploy. Actual unit needs depend on concurrent connections and message volume, which you size from usage.

What to do next

Size your real-time messaging before you deploy. C3X reads your Terraform and prices your resources against a live catalog. Start with the quickstart.