Azure pricing

Not as cheap as I expected, but anyway here it is:

 

Windows Azure:

• Compute = $0.12 / hour (editor’s note: by the pricing I assume this is CPU time. At least I hope…)
• Storage = $0.15 / GB stored / month
• Storage Transactions = $0.01 / 10K
• Bandwidth = $0.10 in / $0.15 out / GB

SQL Azure:

• Web Edition – Up to 1 GB relational database = $9.99
• Business Edition – Up to 10 GB relational database = $99.99
• Bandwidth = $0.10 in / $0.15 out / GB

.Net Services:

• Messages = $0.15/100K message operations , including Service Bus messages and Access Control tokens
• Bandwidth = $0.10 in / $0.15 out / GB

How Comsumption is Measured

Windows Azure

• Compute time, measured in machine hours: Windows Azure compute hours are charged only for when your application is deployed. When developing and testing your application, developers will want to remove the compute instances that are not being used to minimize compute hour billing.
• Storage, measured in GB: Storage is metered in units of average daily amount of data stored (in GB) over a monthly period. E.g. if a user uploaded 30GB of data and stored it on Windows Azure for a day, her monthly billed storage would be 1 GB. If the same user uploaded 30GB of data and stored it on Windows Azure for an entire billing period, her monthly billed storage would be 30GB. Storage is also metered in terms of storage transactions used to add, update, read and delete storage data. These are billed at a rate of $0.01 for 10,000 (10k) transaction requests
• Bandwidth requirements (transmissions to and from the Azure datacenter), measured in GB: Bandwidth is charged based on the total amount of data going in and out of the Azure services via the internet in a given 30-day period. Bandwidth within a datacenter is free.
• Transactions, measured as application requests

SQL Azure

Web Edition Relational Database includes:

• Up to 1 GB of T-SQL based relational database
• Self-managed DB, auto high availability and backup
• Auto Scale with pay-as-you grow
• Best suited for Web application, Departmental custom apps.

Business Edition DB includes:

• Up to 10 GB of T-SQL based relational database
• Self-managed DB, auto high availability and backup
• Auto Scale, Pay-as- you grow
• Additional features in the future like auto-partition, CLR, fanouts etc.
• Best suited for ISVs packaged LOB apps, Department custom apps

.NET Services:

Messages (Includes Access Control, Orchestration, and Reliable Queuing for message): .NET Services allow developers to easily connect their cloud applications and databases with existing software assets and users. This connection between cloud and on-premises assets is facilitated by the exchange of messages. The consumption-based pricing model means that customers will pay only for the number of message operations that their applications use. The definition of a “message operation” includes Service Bus messages and Access Control tokens. Messages are charged to the customer in discrete blocks of 100,000 (“100k”) for each monthly billing period, meaning that

• A customer who consumed 95,000 messages would be billed for 1x100k messages (plus the bandwidth used to send messages in or out).
• A customer who uses 150,000 messages in a billing period would be charged for 2x100k messages (plus the bandwidth used to send messages in or out).
• A customer who uses 20 million messages in a billing period would be charged for 200x100k messages (plus the bandwidth used to send messages in or out).

Service Level Agreements (SLA)

Windows Azure:

Windows Azure has separate SLA’s for compute and storage. For compute, we guarantee that when you deploy two or more role instances in different fault and upgrade domains your Internet facing roles will have external connectivity at least 99.95% of the time. Additionally, we will monitor all of your individual role instances and detect within two minutes when a role instance’s process is not running and initiate corrective action (we will publish by PDC the full details of our uptime promise for individual role instances). For storage, we guarantee that at least 99.9% of the time we will successfully process correctly formatted requests that we receive to add, update, read and delete data. We also guarantee that your storage accounts will have connectivity to our Internet gateway.

Service Level Agreements (SLA)

SQL Azure:

SQL Azure customers will have connectivity between the database and our Internet gateway. SQL Azure will maintain a “Monthly Availability” of 99.9% during a calendar month. “Monthly Availability Percentage” for a specific customer database is the ratio of the time the database was available to customer to the total time in a month. Time is measured in 5-minute intervals in a 30-day monthly cycle. Availability is always calculated for a full month. An interval is marked as unavailable if the customer’s attempts to connect to a database are rejected by the SQL Azure gateway.

Service Level Agreements (SLA)

.NET Services:

Uptime percentage commitments and SLA credits for .NET Services are equivalent to those specified above in the Windows Azure SLA. Due to inherent differences between the technologies, underlying SLA definitions and terms differ for .NET Services. Using the Service Bus module of .NET Services, customers will have connectivity between a customer’s service endpoint and our Internet gateway; when our service fails to establish a connection from the gateway to a customer's service endpoint, then the service is assumed to be unavailable. In addition, the service will process correctly formatted request for the handling of messages; when our service fails to process a request properly, then the service is assumed to be unavailable. SLA calculations will be based on an average over a 30-day monthly cycle, with 5-minute time intervals. Failures seen by a customer in the form of service unavailability will be counted for the purpose of availability calculations for that customer. Additional SLA definitions and terms will be detailed at a later date.