05.04.2013 Views

Pricing Overview for Windows Azure in Enterprise Programs

Pricing Overview for Windows Azure in Enterprise Programs

Pricing Overview for Windows Azure in Enterprise Programs

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

<strong>Pric<strong>in</strong>g</strong> <strong>Overview</strong> <strong>for</strong> <strong>W<strong>in</strong>dows</strong> <strong>Azure</strong> <strong>in</strong><br />

<strong>Enterprise</strong> <strong>Programs</strong><br />

This page provides <strong>in</strong><strong>for</strong>mation on how <strong>W<strong>in</strong>dows</strong> <strong>Azure</strong> is priced and billed <strong>for</strong> customers that<br />

purchase <strong>W<strong>in</strong>dows</strong> <strong>Azure</strong> <strong>in</strong> one of the follow<strong>in</strong>g programs:<br />

<strong>Enterprise</strong> Agreement (EA)<br />

<strong>Enterprise</strong> Agreement Subscription (EAS)<br />

Enrollment <strong>for</strong> Application Plat<strong>for</strong>m (EAP)<br />

Enrollment <strong>for</strong> Core Infrastructure (ECI)<br />

Enrollment <strong>for</strong> Education Solutions (EES)<br />

Enrollment <strong>for</strong> <strong>W<strong>in</strong>dows</strong> <strong>Azure</strong> (EWA)<br />

Customers and channel partners (<strong>in</strong> the case of our <strong>in</strong>direct channels) are guaranteed to receive<br />

the prices <strong>in</strong>dicated <strong>in</strong> their Customer Price Sheet (CPS) or, <strong>in</strong> the case of an Enrollment <strong>for</strong><br />

Education Solutions, their <strong>W<strong>in</strong>dows</strong> <strong>Azure</strong> Amendment. There are the follow<strong>in</strong>g <strong>in</strong>stances<br />

where updated pric<strong>in</strong>g will be provided to exist<strong>in</strong>g customers and channel partners outside of the<br />

Customer Price Sheet or the <strong>W<strong>in</strong>dows</strong> <strong>Azure</strong> Amendment:<br />

Introduction of new <strong>W<strong>in</strong>dows</strong> <strong>Azure</strong> services<br />

Price decreases that are made available to exist<strong>in</strong>g customers and channel partners<br />

Customer and channel partners can view their pric<strong>in</strong>g <strong>for</strong> an enrollment by logg<strong>in</strong>g <strong>in</strong>to the<br />

<strong>W<strong>in</strong>dows</strong> <strong>Azure</strong> <strong>Enterprise</strong> Portal and navigat<strong>in</strong>g to the price sheet page <strong>for</strong> that enrollment. If<br />

you purchase <strong>W<strong>in</strong>dows</strong> <strong>Azure</strong> <strong>in</strong>directly through one of our channel partners, you will need to<br />

obta<strong>in</strong> your pric<strong>in</strong>g updates from your channel partner.<br />

In addition to the updated pric<strong>in</strong>g, this document also provides additional details on how usage is<br />

calculated <strong>for</strong> the various <strong>W<strong>in</strong>dows</strong> <strong>Azure</strong> services.<br />

Additional Detail<br />

Introduction of new <strong>W<strong>in</strong>dows</strong> <strong>Azure</strong> services<br />

Price decreases and bill<strong>in</strong>g model changes<br />

Corrections to our pric<strong>in</strong>g<br />

Details on how usage is calculated and billed<br />

Cloud Services<br />

Data Management<br />

Virtual Mach<strong>in</strong>es<br />

Web Sites<br />

Bus<strong>in</strong>ess Analytics<br />

Network<strong>in</strong>g<br />

Data Transfers (except CDN)


Cach<strong>in</strong>g<br />

Media<br />

Messag<strong>in</strong>g<br />

<strong>W<strong>in</strong>dows</strong> <strong>Azure</strong> Active Directory (AD) Access Control<br />

Mobile Services<br />

Appendix A: Friendly Service Names


Introduction of new <strong>W<strong>in</strong>dows</strong> <strong>Azure</strong> services<br />

We are cont<strong>in</strong>ually enhanc<strong>in</strong>g <strong>W<strong>in</strong>dows</strong> <strong>Azure</strong> and periodically add new services that are priced<br />

separately from exist<strong>in</strong>g services. We will provide a m<strong>in</strong>imum of 30 days’ notice be<strong>for</strong>e<br />

charg<strong>in</strong>g <strong>for</strong> a new service and <strong>in</strong>clude the associated pric<strong>in</strong>g if you elect to utilize that new<br />

service. Customers will receive by default the pric<strong>in</strong>g associated with the price level <strong>in</strong> which<br />

they qualify. Customers can avoid charges by elect<strong>in</strong>g to not use the new service.<br />

March 15, 2013<br />

On March 15, 2013, we added our HDInsight service to the <strong>Enterprise</strong> Program price list and<br />

notified exist<strong>in</strong>g customers. Dur<strong>in</strong>g preview, the head node will be billed at a 50% discount off<br />

of the hourly rate <strong>for</strong> the standard Cloud Services Extra Large <strong>in</strong>stance and the compute node<br />

will be billed at 50% discount off of the hourly rate <strong>for</strong> the standard Cloud Services Large<br />

<strong>in</strong>stance.<br />

November 12, 2012 – <strong>W<strong>in</strong>dows</strong> <strong>Azure</strong> Support<br />

On November 12, 2012, we <strong>in</strong>troduced <strong>W<strong>in</strong>dows</strong> <strong>Azure</strong> Standard and Professional Direct<br />

Support <strong>for</strong> <strong>Enterprise</strong> customers. All <strong>Enterprise</strong> customers receive the <strong>W<strong>in</strong>dows</strong> <strong>Azure</strong><br />

Standard level of support at no charge through December 31, 2012. For more <strong>in</strong><strong>for</strong>mation, click<br />

here.<br />

September 20, 2012 – Web Sites<br />

On September 20, 2012, we <strong>in</strong>troduced the paid version of the shared <strong>in</strong>stance model.<br />

August 28, 2012 – Mobile Services<br />

On August 28, 2012, we <strong>in</strong>troduced Mobile Services <strong>in</strong> preview.<br />

June 7, 2012 – Six New Services<br />

On June 7, 2012, we <strong>in</strong>troduced the follow<strong>in</strong>g four new services <strong>in</strong> preview:<br />

Web Sites<br />

Virtual Mach<strong>in</strong>es<br />

Media Services<br />

Virtual Network<br />

The follow<strong>in</strong>g two services left preview and became generally available:<br />

Locally Redundant Storage<br />

SQL Report<strong>in</strong>g


Please review the Details section <strong>for</strong> more <strong>in</strong><strong>for</strong>mation on how usage is calculated and billed .<br />

October 1, 2011 - Cach<strong>in</strong>g<br />

On October 1, 2011, we added our Cach<strong>in</strong>g service to the <strong>Enterprise</strong> Program price list and<br />

notified exist<strong>in</strong>g customers. If you signed up <strong>for</strong> <strong>W<strong>in</strong>dows</strong> <strong>Azure</strong> prior to this date, you should<br />

have been notified of your pric<strong>in</strong>g. You can also log <strong>in</strong>to to the <strong>Enterprise</strong> Portal to view your<br />

pric<strong>in</strong>g or, <strong>in</strong> the case of our <strong>in</strong>direct customers, you can contact your channel partner.<br />

Back to top<br />

Price decreases and bill<strong>in</strong>g model changes<br />

Microsoft may change the current <strong>Enterprise</strong> Program price <strong>for</strong> <strong>in</strong>dividual <strong>W<strong>in</strong>dows</strong> <strong>Azure</strong><br />

services dur<strong>in</strong>g the term of an enrollment. We will extend the reduced rates to exist<strong>in</strong>g<br />

customers while the lower price is <strong>in</strong> effect. Prices may also <strong>in</strong>crease dur<strong>in</strong>g the term of an<br />

enrollment if an enrollment’s price was previously reduced lower than its <strong>in</strong>itial rate dur<strong>in</strong>g the<br />

enrollment. However, an enrollment’s price <strong>for</strong> a service will not <strong>in</strong>crease beyond that <strong>in</strong>itial<br />

rate. We will <strong>in</strong><strong>for</strong>m customers and <strong>in</strong>direct channel partners of price changes by email<strong>in</strong>g the<br />

enterprise and partner adm<strong>in</strong>istrators associated with the enrollment.<br />

Listed below by date are the price changes that impact the <strong>Enterprise</strong> program. Price decreases<br />

are based off retail prices and are not specific to a customer Enrollment. Customers can view<br />

their current pric<strong>in</strong>g by logg<strong>in</strong>g <strong>in</strong>to the <strong>W<strong>in</strong>dows</strong> <strong>Azure</strong> <strong>Enterprise</strong> Portal and view<strong>in</strong>g their<br />

price sheet. <strong>Enterprise</strong> Program customers that purchase <strong>W<strong>in</strong>dows</strong> <strong>Azure</strong> through a channel<br />

partner should contact their channel partner to obta<strong>in</strong> their current prices.<br />

March 1, 2013<br />

Geo Redundant and Locally Redundant Storage<br />

In order to achieve greater pric<strong>in</strong>g precision on Geo and Locally Redundant Storage, on March 1,<br />

we updated our part numbers <strong>for</strong> these two meters with ones of a greater unit of measure (i.e.,<br />

100 GB vs. 10 GB). Because the unit of measure is 10 times greater, the display price is<br />

commensurately 10 times higher as well. Due to round<strong>in</strong>g, prices may be slightly different on a<br />

per GB basis than <strong>in</strong> the prior month.<br />

Media Services Encod<strong>in</strong>g and On Demand Stream<strong>in</strong>g<br />

Media Services Encod<strong>in</strong>g and On Demand Stream<strong>in</strong>g will become charged services beg<strong>in</strong>n<strong>in</strong>g March 1,<br />

2013. Media Encod<strong>in</strong>g’s retail rate <strong>in</strong> USD is $1.99 per GB. On-Demand Stream<strong>in</strong>g Units retail rate <strong>in</strong><br />

USD is $199 each per month, calculated on a daily basis us<strong>in</strong>g the highest number of reserved units that


were active <strong>in</strong> the account <strong>in</strong> the correspond<strong>in</strong>g 24-hour period. Our <strong>Enterprise</strong> Program customers will<br />

receive their standard level discount and commitment discount off of this rate.<br />

December 1, 2012<br />

Geo Redundant and Locally Redundant Storage<br />

Effective December 1, 2012, the price <strong>for</strong> both Geo Redundant and Locally Redundant storage<br />

capacity <strong>for</strong> current <strong>Enterprise</strong> Program customers that have standard rates based on their level<br />

has been decreased by 24%. Please note that due to round<strong>in</strong>g rules, the effective percentage<br />

discount could be slightly different.<br />

Currency Exchange Rate Changes<br />

On December 1, 2012 Microsoft adjusted its pric<strong>in</strong>g to reflect currency exchange rates. Some currencies<br />

benefited from a 5% price decrease, while others experienced a 5% <strong>in</strong>crease. Exist<strong>in</strong>g customers are<br />

guaranteed their price will not raise above their <strong>in</strong>itial rate. However, if current prices are lower than an<br />

enrollment’s <strong>in</strong>itial rates, you may see a price <strong>in</strong>crease up to the amount listed <strong>in</strong> the table below:<br />

Currency Code Price Change<br />

Canadian Dollar CAD -5%<br />

Swiss Franc CHF 5%<br />

Danish Krone DKK 5%<br />

Euro EUR 5%<br />

British Pound GBP 5%<br />

Japanese Yen JPY -5%<br />

August 1, 2012 – Reduced Commitment <strong>Pric<strong>in</strong>g</strong><br />

Effective August 1, 2012, we lowered our standard commitment pric<strong>in</strong>g by <strong>in</strong>creas<strong>in</strong>g our<br />

commitment discount to 23% <strong>for</strong> all services as compared to our standard <strong>Enterprise</strong> Program


consumption rates. Previously, our commitment discounts were 10% <strong>for</strong> storage, CDN and data<br />

transfers and 20% <strong>for</strong> all other services.<br />

Enrollments can now also qualify <strong>for</strong> the follow<strong>in</strong>g additional discounts based on the volume of<br />

their annual monetary commitment:<br />

Commitment Annual Monetary Discount Off Standard Customer’s Specific<br />

Tier Commitment Units Consumption Rates<br />

<strong>Pric<strong>in</strong>g</strong><br />

Tier 1 Up to 1,799 Units 23% Commitment price on CPS<br />

Tier 2 1,800 – 4,799 Units 26% Additional 3.90%<br />

off CPS Tier 1 price*<br />

Tier 3 4,800 – 11,999 Units 30% Additional 9.09%<br />

off CPS Tier 1 price*<br />

Tier 4 12,000+ Units 35% Additional 15.58%<br />

off CPS Tier 1 price*<br />

*Additional discounts off of the Tier 1 prices only applies to rates negotiated subsequent to August 1, 2012. Exist<strong>in</strong>g enrollments<br />

do qualify <strong>for</strong> the standard lower rates, <strong>in</strong>clud<strong>in</strong>g any tiered discounts, if they are lower than their current negotiated rates.<br />

All unused monetary commitment will qualify <strong>for</strong> the discounts noted above based on an<br />

enrollments’s aggregate annual monetary commitment <strong>in</strong> effect as of the first day of that month.<br />

For example, if a customer <strong>in</strong>itially purchases 1,200 units of the monetary commitment SKU on<br />

January 1, the enrollment will <strong>in</strong>itially qualify <strong>for</strong> a discount of 23%. If later on June 15 the<br />

customer places an additional order of 600 units of the monetary commitment SKU <strong>for</strong> the last 6<br />

months of their <strong>in</strong>itial annual commitment term, the enrollment will then qualify <strong>for</strong> 26% off its<br />

standard consumption rates beg<strong>in</strong>n<strong>in</strong>g on July 1. This is on any of the enrollment’s rema<strong>in</strong><strong>in</strong>g<br />

monetary commitment balance and not just on the second order of 600 units of the monetary<br />

commitment SKU. Exist<strong>in</strong>g enrollments can qualify <strong>for</strong> these <strong>in</strong>creased discounts based on the<br />

total number of units of the monetary commitment SKU that have been purchased dur<strong>in</strong>g the<br />

current annual commitment term, effective on any unused monetary commitment balance as of<br />

August 1, 2012.<br />

Please note that an <strong>in</strong>dividual enrollment will receive the better of its negotiated price, <strong>in</strong>clud<strong>in</strong>g<br />

any tiered discounts <strong>in</strong> which it qualifies that was <strong>in</strong> effect when <strong>W<strong>in</strong>dows</strong> <strong>Azure</strong> was orig<strong>in</strong>ally<br />

purchased, or the current standard rates <strong>in</strong> which the enrollment qualifies, <strong>in</strong>clud<strong>in</strong>g any tiered<br />

discounts <strong>in</strong> effect <strong>for</strong> that month.<br />

For questions on how to convert your monetary commitment units to commitment amounts,<br />

please reference your price sheet or contact your channel partner.<br />

June 1, 2012 – CDN and Storage Transactions<br />

Effective June 1, 2012, our listed rates <strong>for</strong> CDN and Storage transactions were lowered by 90%.


March 8, 2012 – Compute Hours – Extra Small Instance<br />

Effective March 8, 2012, the cost of an extra small compute <strong>in</strong>stance was lowered by 50%.<br />

Please note that all compute hours are converted <strong>in</strong>to small <strong>in</strong>stance hours when billed. So<br />

<strong>in</strong>stead of report<strong>in</strong>g 1/3 of a small <strong>in</strong>stance hour <strong>for</strong> each elapsed hour an extra small <strong>in</strong>stance is<br />

deployed, we now are report<strong>in</strong>g 1/6 of a small <strong>in</strong>stance hour. This results <strong>in</strong> a 50% lower price.<br />

Please click here <strong>for</strong> additional details on our different compute <strong>in</strong>stance sizes.<br />

March 1, 2012 – Storage Capacity<br />

Effective March 1, 2012, the price <strong>for</strong> storage capacity <strong>for</strong> current <strong>Enterprise</strong> Program customers<br />

that have standard rates based on their level was decreased by 10.71%.<br />

February 14, 2012 – New SQL Database bill<strong>in</strong>g model<br />

Effective February 14, 2012, we <strong>in</strong>troduced a new bill<strong>in</strong>g model that lowers the cost per gigabyte<br />

as customers grow their databases. Our standard price on all SQL Databases larger than 1 GB<br />

was reduced between 30 to 86 percent, depend<strong>in</strong>g on the size of the database. We also <strong>in</strong>troduced<br />

a 100 megabyte database option <strong>for</strong> SQL Database that is priced 50% less than be<strong>for</strong>e.<br />

February 1, 2012 – Storage capacity and data transfers<br />

Effective February 1, 2012, the prices to current <strong>Enterprise</strong> Program customers that have<br />

standard rates based on their level were decreased as follows:<br />

Service Unit of Measure Percent Decrease<br />

Data Transfer Egress NA/EMEA (Zone 1) 10 GB 20%<br />

Data Transfer Egress APAC (Zone 2) 10 GB 5%<br />

Storage Capacity 10 GB 6.6%<br />

December 1, 2011 – New Service Bus bill<strong>in</strong>g model<br />

Effective December 1, 2011, Service Bus migrated to a new bill<strong>in</strong>g model based on Relay Hours<br />

and Messages. Service Bus was offered at no charge through June 30, 2012. Beg<strong>in</strong>n<strong>in</strong>g on July<br />

1, 2012, our public prices <strong>in</strong> US dollars <strong>for</strong> customers that purchase on the <strong>W<strong>in</strong>dows</strong> <strong>Azure</strong> web<br />

site are as follows:<br />

$0.10 per 100 Relay Hours<br />

$0.01 per 10,000 Messages<br />

Our <strong>Enterprise</strong> Program customers will receive their standard level discount and commitment<br />

discount off of the above rates.<br />

July 1, 2011 – Free <strong>in</strong>bound data transfers


Effective July 1, 2011, we no longer charge <strong>for</strong> <strong>in</strong>bound data transfers.<br />

Corrections to our pric<strong>in</strong>g<br />

February 2013<br />

On February 22, 2013, there was a worldwide service outage that impacted <strong>W<strong>in</strong>dows</strong> <strong>Azure</strong><br />

Storage and the follow<strong>in</strong>g dependent services:<br />

Media Services<br />

Mobile Services<br />

Service Bus<br />

Web Sites<br />

Geo Redundant Storage, Locally Redundant Storage, Storage Transactions, Media Services<br />

Encod<strong>in</strong>g and Service Bus received a 25% discount <strong>for</strong> usage <strong>in</strong> February. Because Mobile<br />

Services and Webs Sites are emitted as part of the Cloud Services, they were credited <strong>for</strong> 25% of<br />

their February usage. This credit will appear as an adjustment to the new purchase amount <strong>in</strong> the<br />

enterprise portal on the usage summary report <strong>in</strong> either February or March of 2013.<br />

December 2012<br />

From December 28-30, 2012, <strong>W<strong>in</strong>dows</strong> <strong>Azure</strong> Storage service experienced a service <strong>in</strong>terruption<br />

<strong>in</strong> a s<strong>in</strong>gle cluster <strong>in</strong> the South Central US sub region that caused a limited number of storage<br />

nodes <strong>in</strong> that particular cluster to go offl<strong>in</strong>e. For EA customers with storage accounts that were<br />

impacted, we updated their rates to not charge <strong>for</strong> Local Redundant and Geo Redundant storage<br />

as well as storage transactions <strong>for</strong> December, 2012.<br />

November 2012<br />

For Cache hours from 11/4/2012 00:00 through 11/16/2012 23:59 (UTC time), the system<br />

orig<strong>in</strong>ally overstated Cache usage by exactly 100% <strong>for</strong> reported usage dur<strong>in</strong>g this time. This<br />

usage has s<strong>in</strong>ce been properly stated and the issue that caused this problem has been fixed to<br />

prevent its reoccurrence.<br />

October 2012<br />

For compute hours and associated data transfers <strong>for</strong> the day of October 7, 2012, the system<br />

orig<strong>in</strong>ally overstated this usage by exactly 100% <strong>for</strong> 19 of the 24 hours that our system reported<br />

usage <strong>for</strong> this day. S<strong>in</strong>ce our totals are aggregated by day and to ensure no customer is<br />

overbilled, we reduced all compute hours and the data transfers associated with compute hours<br />

<strong>for</strong> October 7, 2012 by 50% of what was orig<strong>in</strong>ally reported. This results <strong>in</strong> a slight error <strong>in</strong> our<br />

customers’ favor. The underly<strong>in</strong>g issue that caused this double report<strong>in</strong>g has been corrected and<br />

appropriate controls have been implemented to avoid its reoccurrence.


Prior to August 1, 2012, we had a few pric<strong>in</strong>g errors that resulted <strong>in</strong> customers receiv<strong>in</strong>g lower<br />

rates than they should have on some services. These errors <strong>in</strong>cluded:<br />

SQL <strong>Azure</strong> Bus<strong>in</strong>ess Edition customers receiv<strong>in</strong>g an extra 90% discount off their<br />

negotiated rates through July 2012<br />

Customers receiv<strong>in</strong>g the new August 2012 commitment rates on their July 2012 usage<br />

Storage customers receiv<strong>in</strong>g an additional 10.71% discount off our standard pric<strong>in</strong>g <strong>for</strong><br />

their June and July 2012 usage.<br />

These errors have been corrected on a go <strong>for</strong>ward basis but we will enable customers to reta<strong>in</strong><br />

the benefit of these lower rates <strong>for</strong> these prior months.<br />

For customers utiliz<strong>in</strong>g CDN, we planned to report CDN data transfers separately effective June<br />

25, 2012 onward. Due to a system issue that has s<strong>in</strong>ce been corrected, this separately reported<br />

CDN data transfer usage was not orig<strong>in</strong>ally <strong>in</strong>cluded <strong>in</strong> an enrollment’s usage report<strong>in</strong>g or<br />

reflected <strong>in</strong> an enrollment’s monetary commitment balance. For July 1 onward, this has been<br />

corrected and you may have recently seen a change <strong>in</strong> your usage and/or monetary commitment<br />

balance. To avoid hav<strong>in</strong>g to reopen June, we have elected not to restate usage <strong>for</strong> June 25 - 30,<br />

2012, and will not charge <strong>for</strong> CDN data transfer usage <strong>for</strong> this period. We apologize <strong>for</strong> any<br />

<strong>in</strong>convenience that this may have caused.<br />

Back to top<br />

Details on how usage is calculated and billed<br />

Cloud Services<br />

<strong>W<strong>in</strong>dows</strong> <strong>Azure</strong> Web and Worker roles are charged only when your application is deployed.<br />

When develop<strong>in</strong>g and test<strong>in</strong>g your application, developers will want to remove the compute<br />

<strong>in</strong>stances that are not be<strong>in</strong>g used to m<strong>in</strong>imize compute hour bill<strong>in</strong>g. Partial compute hours are<br />

billed as full hours.<br />

The table below summarizes the resources provided <strong>for</strong> each <strong>in</strong>stance size.<br />

Virtual Mach<strong>in</strong>e Size CPU Cores Memory<br />

Extra Small Shared 768 MB<br />

Small 1 1.75 GB<br />

Medium 2 3.5 GB<br />

Large 4 7 GB<br />

Extra Large 8 14 GB<br />

Details on the Cloud Services compute <strong>in</strong>stance sizes .


All Cloud Services compute hours are converted <strong>in</strong>to small <strong>in</strong>stance hours when presented on<br />

your bill. For example, one clock hour of a medium compute <strong>in</strong>stance would be presented as two<br />

small compute <strong>in</strong>stance hours on your bill. This table describes how each of the compute<br />

<strong>in</strong>stance sizes is converted to the number of small compute <strong>in</strong>stance hours:<br />

Compute Instance Size Clock Hours Small Instance Hours<br />

Extra Small 1 hour 1/6 hour<br />

Small 1 hour 1 hour<br />

Medium 1 hour 2 hours<br />

Large 1 hour 4 hours<br />

Extra Large 1 hour 8 hours<br />

Compute hours are billed based on the number of clock hours your service was deployed<br />

multiplied by the number of equivalent small compute <strong>in</strong>stances <strong>in</strong>cluded <strong>in</strong> your deployment.<br />

Partial compute <strong>in</strong>stance hours (prior to conversion) are billed as full compute hours <strong>for</strong> each<br />

clock hour an <strong>in</strong>stance is deployed. For example, if you deploy a small compute <strong>in</strong>stance at 10:50<br />

AM and delete the deployment at 11:10 AM, you will be billed <strong>for</strong> two small compute hours, one<br />

hour <strong>for</strong> usage dur<strong>in</strong>g 10:50 AM to 11:00 AM and another hour <strong>for</strong> usage dur<strong>in</strong>g 11:00 AM to<br />

11:10 AM.<br />

For other compute <strong>in</strong>stance sizes you deploy, your hours will be converted <strong>in</strong>to the equivalent<br />

small <strong>in</strong>stance hours by multiply<strong>in</strong>g by 1/6, 2, 4 or 8, depend<strong>in</strong>g on the compute <strong>in</strong>stance size<br />

deployed. In addition, each time you delete your deployment and redeploy your service, you will<br />

be billed a m<strong>in</strong>imum of one clock hour <strong>for</strong> each compute <strong>in</strong>stance deployed. However, any<br />

<strong>in</strong>stances deployed <strong>for</strong> less than five m<strong>in</strong>utes with<strong>in</strong> one clock hour will not be charged.<br />

Data Management<br />

SQL Database<br />

SQL Database is billed based on a graduated rate based on the size of the database. It is available<br />

<strong>in</strong> two editions: Web and Bus<strong>in</strong>ess. The Web Edition supports up to a 5 GB maximum T-SQL<br />

based relational database. The Bus<strong>in</strong>ess Edition supports up to a 150 GB maximum size T-SQLbased<br />

relational database. You are billed per database per month <strong>in</strong> Database Units based on the<br />

size of the database.<br />

For illustrative purposes, below is the price per database per month based on the size of the<br />

database us<strong>in</strong>g our Pay-As-You-Go prices <strong>in</strong> US dollars <strong>for</strong> customers that purchase <strong>W<strong>in</strong>dows</strong><br />

<strong>Azure</strong> directly from our <strong>W<strong>in</strong>dows</strong> <strong>Azure</strong> web site (with the standard 23% discount <strong>for</strong> the<br />

commitment prices):<br />

Price Per Database Per Month Database Units (DU) That<br />

Database Size<br />

Commitment Consumption Will Appear On Your bill<br />

Up to 100 MB Flat $3.846 Flat $4.995 0.5 DU<br />

Greater than 100 MB to Flat $7.692 Flat $9.99 1 DU


1 GB<br />

Greater than 1 GB to 10<br />

GB<br />

Greater than 10 GB to 50<br />

GB<br />

Greater than 50 GB to<br />

150 GB<br />

$7.692 <strong>for</strong> first GB<br />

$3.077 <strong>for</strong> each<br />

additional GB<br />

$35.385 <strong>for</strong> first 10GB<br />

$1.538 <strong>for</strong> each<br />

additional GB<br />

$96.905 <strong>for</strong> first 50GB<br />

$0.769 <strong>for</strong> each<br />

additional GB<br />

$9.99 <strong>for</strong> first GB<br />

$3.996 <strong>for</strong> each additional<br />

GB<br />

$45.954 <strong>for</strong> first 10 GB<br />

$1.998 <strong>for</strong> each additional<br />

GB<br />

$125.874 <strong>for</strong> first 50 GB<br />

$0.999 <strong>for</strong> each additional<br />

GB<br />

1 DU <strong>for</strong> first GB<br />

0.4 DU <strong>for</strong> each additional<br />

GB<br />

4.6 DU <strong>for</strong> first 10 GB<br />

0.2 DU <strong>for</strong> each additional<br />

GB<br />

12.6 DU <strong>for</strong> first 50 GB<br />

0.1 DU <strong>for</strong> each additional<br />

GB<br />

On February 14, 2012, we changed the SQL Database Bus<strong>in</strong>ess Edition and Web Edition<br />

database meters’ unit of measure from be<strong>in</strong>g per gigabyte / per database to what we refer to as a<br />

Database Unit. For exist<strong>in</strong>g customers, your commitment and overage prices <strong>for</strong> Web and<br />

Bus<strong>in</strong>ess Edition did not change but the quantity billed was lowered <strong>for</strong> all database sizes except<br />

a 1 GB Web Edition database.<br />

For example, us<strong>in</strong>g the Pay-As-You-Go price <strong>in</strong> US dollars <strong>for</strong> customers that buy from our<br />

<strong>W<strong>in</strong>dows</strong> <strong>Azure</strong> web site, the price would be $9.99 per database unit (although Bus<strong>in</strong>ess Edition<br />

utilizes a larger unit of measure of 10 Database Units):<br />

Overage Part Old Unit of New Unit of Retail<br />

Service<br />

Number Measure<br />

Measure Price<br />

Web Edition N6H-00001 1 Gigabyte 1 Database Unit $9.99<br />

Bus<strong>in</strong>ess Edition P4H-00002 10 Gigabytes 10 Database Units $99.90<br />

For databases greater than 1 GB, we bill <strong>in</strong> the next whole gigabyte <strong>in</strong>crement. You are also<br />

only charged each day <strong>for</strong> those databases that you have deployed, based on the maximum size<br />

of each database on that day. For example, if you utilize a Web Edition database of 4.4 GB <strong>for</strong><br />

only one day dur<strong>in</strong>g a bill<strong>in</strong>g month, you will be charged <strong>for</strong> a 5 GB database <strong>for</strong> that day.<br />

Below is the calculation of how you would be billed:<br />

DB<br />

Database Units<br />

Service Size<br />

(A)<br />

Web Edition 5 GB 2.6<br />

(1 DU <strong>for</strong> the first 1 GB<br />

+ 0.4 DU per GB <strong>for</strong> next 4<br />

GB)<br />

Days <strong>in</strong><br />

Month<br />

(B)<br />

Quantity<br />

Per Day<br />

(A / B)<br />

Price Per Cost Per<br />

DU Day<br />

31 0.083871 $9.99 $0.84


Storage<br />

Storage is billed <strong>in</strong> units of the average daily amount of data stored (<strong>in</strong> GB) over a monthly<br />

period. For example, if you consistently utilized 10 GB of storage <strong>for</strong> the first half of the month<br />

and none <strong>for</strong> the second half of the month, you would be billed <strong>for</strong> your average usage of 5 GB<br />

of storage.<br />

<strong>W<strong>in</strong>dows</strong> <strong>Azure</strong> storage provides two levels of redundancy:<br />

Locally Redundant Storage (LRS) - provides highly durable and available storage with<strong>in</strong><br />

a s<strong>in</strong>gle sub region.<br />

Geo Redundant Storage (GRS) - provides our highest level of durability by additionally<br />

stor<strong>in</strong>g your data <strong>in</strong> a second sub region with<strong>in</strong> the same region<br />

Storage accounts by default are set up to be geographically redundant. Customers that do not<br />

require this additional level of durability can turn off their storage accounts’ default sett<strong>in</strong>gs <strong>for</strong><br />

Geo Redundancy to obta<strong>in</strong> a reduced rate <strong>for</strong> storage.<br />

For <strong>W<strong>in</strong>dows</strong> <strong>Azure</strong> Drive storage, you will be billed only <strong>for</strong> the storage space used by the page<br />

blob and the read/write transactions to the page blob. You will not be charged <strong>for</strong> read<br />

transactions that utilize the local drive cache. <strong>W<strong>in</strong>dows</strong> <strong>Azure</strong> Drive usage is billed at the same<br />

rates as standard <strong>W<strong>in</strong>dows</strong> <strong>Azure</strong> Storage and is <strong>in</strong>cluded with <strong>W<strong>in</strong>dows</strong> <strong>Azure</strong> Storage usage <strong>in</strong><br />

your bill. There is not a separate l<strong>in</strong>e item <strong>for</strong> <strong>W<strong>in</strong>dows</strong> <strong>Azure</strong> Drive on your bill.<br />

Virtual Mach<strong>in</strong>es<br />

<strong>W<strong>in</strong>dows</strong> <strong>Azure</strong> Virtual Mach<strong>in</strong>es enable you to deploy a custom <strong>W<strong>in</strong>dows</strong> Server or L<strong>in</strong>ux<br />

image to <strong>W<strong>in</strong>dows</strong> <strong>Azure</strong>. Virtual Mach<strong>in</strong>es give developers full control over the application<br />

environment and allow easy migration of exist<strong>in</strong>g applications to the cloud. Customers can<br />

choose between a <strong>W<strong>in</strong>dows</strong> and Non-<strong>W<strong>in</strong>dows</strong> Virtual Mach<strong>in</strong>e (VM). The <strong>W<strong>in</strong>dows</strong> Virtual<br />

Mach<strong>in</strong>e <strong>in</strong>cludes <strong>W<strong>in</strong>dows</strong> Server licens<strong>in</strong>g costs. The Non-<strong>W<strong>in</strong>dows</strong> Virtual Mach<strong>in</strong>e allows<br />

you to separately license and deploy a non-<strong>W<strong>in</strong>dows</strong> host operat<strong>in</strong>g system. Virtual Mach<strong>in</strong>es<br />

are charged at 33% off of your Cloud Services Compute rate dur<strong>in</strong>g preview. The Virtual<br />

Mach<strong>in</strong>es prices displayed <strong>in</strong> the <strong>Enterprise</strong> Portal will be effective the date these services<br />

become generally available. See the Preview and General Availability rates below <strong>for</strong> more<br />

details.<br />

For illustrative purposes, below are the prices dur<strong>in</strong>g preview and GA <strong>for</strong> <strong>W<strong>in</strong>dows</strong> and Non-<br />

<strong>W<strong>in</strong>dows</strong> Virtual Mach<strong>in</strong>es us<strong>in</strong>g our Pay-As-You-Go prices <strong>in</strong> US dollars <strong>for</strong> customers that<br />

purchase <strong>W<strong>in</strong>dows</strong> <strong>Azure</strong> directly from our <strong>W<strong>in</strong>dows</strong> <strong>Azure</strong> web site:<br />

<strong>W<strong>in</strong>dows</strong> Non-<strong>W<strong>in</strong>dows</strong><br />

Compute CPU<br />

price/hour<br />

price/hour<br />

<strong>in</strong>stance size Cores Memory Preview GA* Preview GA*<br />

Extra Small Shared 768 MB $0.013 $0.020 $0.013 $0.020<br />

Small 1 1.75 GB $0.080 $0.115 $0.080 $0.085<br />

Medium 2 3.5 GB $0.160 $0.230 $0.160 $0.170<br />

Large 4 7 GB $0.320 $0.460 $0.320 $0.340


Extra Large 8 14 GB $0.640 $0.920 $0.640 $0.680<br />

*General Availability date has not yet been announced.<br />

Our <strong>Enterprise</strong> Program customers will receive their standard level discount and commitment<br />

discount off of the above rates.<br />

Customers can also deploy a <strong>W<strong>in</strong>dows</strong> Virtual Mach<strong>in</strong>e with a SQL Server 2012 Evaluation<br />

copy from the image gallery dur<strong>in</strong>g preview on <strong>in</strong>stance sizes of medium or larger. To use SQL<br />

Server 2012 <strong>Enterprise</strong> capabilities, SQL Server 2012 Evaluation should be deployed on a large<br />

or x-large <strong>W<strong>in</strong>dows</strong> <strong>Azure</strong> Virtual Mach<strong>in</strong>e. There is no cost <strong>for</strong> the SQL Server 2012<br />

Evaluation copy, but customers will be charged our standard preview Virtual Mach<strong>in</strong>es rates.<br />

For illustrative purposes, below are the rates <strong>for</strong> the usage of a VM gallery image conta<strong>in</strong><strong>in</strong>g<br />

SQL Server us<strong>in</strong>g our Pay-As-You-Go prices <strong>in</strong> US dollars <strong>for</strong> customers that purchase<br />

<strong>W<strong>in</strong>dows</strong> <strong>Azure</strong> directly from our <strong>W<strong>in</strong>dows</strong> <strong>Azure</strong> web site:<br />

Compute<br />

<strong>in</strong>stance size<br />

CPU<br />

Cores<br />

<strong>Enterprise</strong> Web Standard<br />

2012 Evaluation<br />

Copy<br />

2008 R2 & 2012 2008 R2 & 2012<br />

Preview Only GA* GA*<br />

Extra Small Shared Not Supported N/A N/A<br />

Small 1 Not Supported $0.045 $0.55<br />

Medium 2 No Charge $0.045 $0.55<br />

Large 4 No Charge $0.045 $0.55<br />

Extra Large 8 No Charge $0.09 $1.10<br />

*General Availability date has not yet been announced. Standard <strong>W<strong>in</strong>dows</strong> VM rates will be charged <strong>in</strong> addition to<br />

the SQL Server rates noted above.<br />

Our <strong>Enterprise</strong> Program customers will receive their standard level discount and commitment<br />

discount off of the above rates.<br />

All Virtual Mach<strong>in</strong>e compute hours are converted <strong>in</strong>to small <strong>in</strong>stance hours <strong>in</strong> the same manner<br />

and ratios as described <strong>in</strong> the Cloud Services section. The one exception is that dur<strong>in</strong>g preview,<br />

<strong>W<strong>in</strong>dows</strong> and Non-<strong>W<strong>in</strong>dows</strong> Virtual Mach<strong>in</strong>es will be billed at 33% less compute hours aga<strong>in</strong>st<br />

the exist<strong>in</strong>g compute SKUs to deliver the discounted preview pric<strong>in</strong>g. For example, let’s say<br />

you currently are be<strong>in</strong>g charged at $1.20 per 10 hours <strong>for</strong> small compute hours and you <strong>in</strong>cur 120<br />

hours of either <strong>W<strong>in</strong>dows</strong> or Non-<strong>W<strong>in</strong>dows</strong> Virtual Mach<strong>in</strong>es. Your bill will show 33% less (i.e.,<br />

80 hours) <strong>for</strong> a total charge of $9.60 (8 X $1.20). Your detail usage records will <strong>in</strong>dicate which<br />

compute hours represent Virtual Mach<strong>in</strong>es, so you will be able to easily gross these hours back<br />

up by divid<strong>in</strong>g by two-thirds to state the actual hours of Virtual Mach<strong>in</strong>es that you utilized.<br />

Compute hours are charged whenever the Virtual Mach<strong>in</strong>e is deployed, irrespective of whether it<br />

is runn<strong>in</strong>g or not. Compute hours do not <strong>in</strong>clude any <strong>W<strong>in</strong>dows</strong> <strong>Azure</strong> Storage costs associated<br />

with the image runn<strong>in</strong>g <strong>in</strong> <strong>W<strong>in</strong>dows</strong> <strong>Azure</strong> Virtual Mach<strong>in</strong>es. These costs are billed separately.


For a full description of how compute hours are calculated, please refer to the Cloud Services<br />

section.<br />

<strong>W<strong>in</strong>dows</strong> <strong>Azure</strong> has a similarly named service, the VM Role Beta (stateless), which was released<br />

at PDC10. If you are still us<strong>in</strong>g the VM Role Beta, it will cont<strong>in</strong>ue to be charged at the same<br />

compute rates <strong>for</strong> Cloud Services <strong>in</strong>stances as noted <strong>in</strong> the Cloud Services section.<br />

When you upload your on-premises <strong>W<strong>in</strong>dows</strong> Server images to <strong>W<strong>in</strong>dows</strong> <strong>Azure</strong>, Microsoft<br />

provides the <strong>W<strong>in</strong>dows</strong> Server license keys <strong>for</strong> any runn<strong>in</strong>g <strong>in</strong>stances. Your on-premises<br />

<strong>W<strong>in</strong>dows</strong> Server license does not transfer with the uploaded image. If you then download the<br />

uploaded image to run back on-premises, you will then be required to supply a license to this<br />

image. The license provided <strong>in</strong> <strong>W<strong>in</strong>dows</strong> <strong>Azure</strong> is non-transferrable to on-premises.<br />

Microsoft License Mobility through Software Assurance on <strong>W<strong>in</strong>dows</strong> <strong>Azure</strong><br />

With License Mobility through Software Assurance, you can:<br />

Deploy certa<strong>in</strong> server application licenses purchased under your Volume Licens<strong>in</strong>g<br />

agreement <strong>in</strong> <strong>W<strong>in</strong>dows</strong> <strong>Azure</strong> data centers;<br />

Extend the value of your server application licenses by deploy<strong>in</strong>g them on-premises or <strong>in</strong><br />

the cloud; and<br />

Take advantage of the low cost comput<strong>in</strong>g <strong>in</strong>frastructure <strong>for</strong> chang<strong>in</strong>g bus<strong>in</strong>ess priorities.<br />

More program benefit details and <strong>in</strong><strong>for</strong>mation can be found here.<br />

Web Sites (Preview)<br />

<strong>W<strong>in</strong>dows</strong> <strong>Azure</strong> Web Sites makes it easy to develop, test, deploy, and run web sites <strong>in</strong> the cloud.<br />

Dur<strong>in</strong>g our preview of <strong>W<strong>in</strong>dows</strong> <strong>Azure</strong> Web Sites, you can enable an exist<strong>in</strong>g subscription to<br />

receive up to 10 web sites at no charge <strong>for</strong> one year, and scale your application as traffic grows<br />

to either a paid shared or reserve <strong>in</strong>stance model. Go to our Preview Features page to sign up.<br />

Free Instance Model<br />

With the <strong>W<strong>in</strong>dows</strong> <strong>Azure</strong> Web Sites free <strong>in</strong>stance model, you will receive the follow<strong>in</strong>g at no<br />

charge:<br />

10 free web sites per sub region* on the <strong>Azure</strong>WebSites.net doma<strong>in</strong><br />

Limited to 165GB of Egress per day per sub region and all data transferred are<br />

billed at your normal rates.<br />

1 GB of storage per sub region (shared by all web sites)<br />

20 MB of a third-party MySQL database per sub region <strong>for</strong> the first 12 months<br />

(charges may apply thereafter)<br />

* Sub regions currently available are US West, US East, Europe North, and Europe West.


By default, your free web sites on the <strong>Azure</strong>WebSites.net doma<strong>in</strong> are configured <strong>in</strong> a free shared<br />

<strong>in</strong>stance model, runn<strong>in</strong>g alongside other users’ web sites and shar<strong>in</strong>g web server resources. You<br />

can elect at any time to upgrade to either a paid version of the shared <strong>in</strong>stance model or the<br />

reserved <strong>in</strong>stance model.<br />

Shared Instance Model<br />

The shared <strong>in</strong>stance model provides support <strong>for</strong> custom doma<strong>in</strong> names, 1 GB of storage, and<br />

unlimited outbound data transfer charged at your normal rates. Up to three <strong>in</strong>stances per Web site<br />

may be deployed at an additional cost.<br />

Under the shared <strong>in</strong>stance model, you will receive the follow<strong>in</strong>g benefits:<br />

The ability to assign your custom host or doma<strong>in</strong> name<br />

Outbound traffic charged at your normal rates; unlimited <strong>in</strong>bound data transfer<br />

1 GB storage (shared by all sites)<br />

20 MB of a third-party, MySQL database<br />

Our standard public price <strong>for</strong> shared <strong>in</strong>stance hours will be $0.02 / hour (approx. $14.40 / month)<br />

per Web Site <strong>in</strong>stance at general availability. Dur<strong>in</strong>g preview, a 33% discount will be applied <strong>for</strong><br />

an effective monthly rate of $9.60 / month, per Web Site <strong>in</strong>stance. Dur<strong>in</strong>g preview, all paid<br />

shared <strong>in</strong>stance hours will be billed us<strong>in</strong>g the current Cloud Services small compute meter,<br />

except we will emit 1/9th of the Cloud Services small compute hours to deliver the discounted<br />

pric<strong>in</strong>g of $9.60 / month per Web Site <strong>in</strong>stance. The monthly calculation per paid shared Web<br />

Site <strong>in</strong>stance is as follows: 720 hours * 1/9 * $0.12 = $9.60.<br />

As your web site traffic grows, you can seamlessly upgrade to the reserved-<strong>in</strong>stance model with<br />

private virtual mach<strong>in</strong>e <strong>in</strong>stances dedicated solely to your apps.<br />

Reserved-Instance Model<br />

The reserved-<strong>in</strong>stance model provides dedicated virtual mach<strong>in</strong>e <strong>in</strong>stances <strong>for</strong> all of your web<br />

sites and 10 GB of storage <strong>for</strong> your content. With the reserved-<strong>in</strong>stance model, you get unlimited<br />

outbound data transfers, charged at your normal rate.<br />

When you upgrade to the reserved-<strong>in</strong>stance model, all your web sites will run on dedicated<br />

virtual mach<strong>in</strong>es assigned just to you. You will receive the follow<strong>in</strong>g benefits per month:<br />

Ability to assign all of your web sites a custom host or doma<strong>in</strong> name<br />

Unlimited outbound data transfers charged at your normal rates; unlimited<br />

<strong>in</strong>bound data transfers<br />

10 GB of storage (shared by all sites)


20 MB of a third-party MySQL database<br />

The table below details the reserved-<strong>in</strong>stance model public pric<strong>in</strong>g based on the size of the<br />

reserved <strong>in</strong>stance selected:<br />

Reserved<br />

Instance Size<br />

CPU Cores Memory Preview* price per<br />

hour (33% Discount)<br />

Small 1 1.75 GB $0.08 $0.12<br />

Medium 2 3.5 GB $0.16 $0.24<br />

Large 4 7 GB $0.32 $0.48<br />

*Web Sites is currently <strong>in</strong> preview. The general availability date has not been announced yet.<br />

General Availability<br />

price per hour<br />

All reserved <strong>in</strong>stance-hours are converted to small-<strong>in</strong>stance hours <strong>in</strong> the ratios noted below:<br />

Reserved-Instance Size Clock Hours Small-Instance Hours<br />

Small 1 1 hour<br />

Medium 1 2 hours<br />

Large 1 4 hours<br />

Dur<strong>in</strong>g preview, all reserved <strong>in</strong>stance hours will be billed us<strong>in</strong>g the current Cloud Services<br />

compute meter, except we will bill 33 percent fewer compute hours to deliver the discounted<br />

pric<strong>in</strong>g noted above.<br />

Web Site Offer<strong>in</strong>g Feature Comparison<br />

Feature Free Shared Reserved<br />

Custom doma<strong>in</strong><br />

name<br />

No Yes Yes<br />

Sites 10 per sub region 100 per sub region 100 per sub region<br />

Storage 1 GB per sub region 1 GB per sub region 10 GB per sub region<br />

Storage<br />

transactions<br />

Relational<br />

database<br />

Data transfer<br />

<strong>in</strong>bound<br />

Data transfer<br />

outbound<br />

CPU<br />

Price Free<br />

Included at no charge Included at no charge Included at no charge<br />

20 MB of MySQL<br />

database per sub region.<br />

Shared by all web sites<br />

20 MB of MySQL database<br />

per sub region. Shared by all<br />

web sites<br />

Free Free Free<br />

Limited to 165MB per<br />

day per sub region<br />

Up to 60 m<strong>in</strong>utes of<br />

CPU cycles per day<br />

20 MB of MySQL database<br />

per sub region. Shared by<br />

all web sites<br />

Billed at your normal rates Billed at your normal rates<br />

Up to 240 m<strong>in</strong>utes of CPU<br />

cycles per day<br />

1/9 off of your normal Cloud<br />

Services small compute rates<br />

Dedicated CPU <strong>in</strong>stances<br />

1/3 off of your normal<br />

Cloud Services small


Web Site Offer<strong>in</strong>g Feature Comparison<br />

Feature Free Shared Reserved<br />

(preview)<br />

compute rates (preview)<br />

1/6 off of your normal Cloud<br />

Services small compute rates<br />

(general availability)<br />

Normal Cloud Services<br />

small compute rates<br />

(general availability)<br />

For <strong>W<strong>in</strong>dows</strong> <strong>Azure</strong> Web Sites, we reserve the right to suspend service <strong>for</strong> nonuse or <strong>in</strong>activity.<br />

We will determ<strong>in</strong>e such nonuse or <strong>in</strong>activity <strong>in</strong> accordance with the follow<strong>in</strong>g criteria: no<br />

adm<strong>in</strong>istrative action or end-user access <strong>for</strong> more than 90 days. We may use other reasonable<br />

criteria at our discretion from time to time. We will give you at least 30 days' notice be<strong>for</strong>e<br />

suspend<strong>in</strong>g service.<br />

Both the free and paid versions of the shared-<strong>in</strong>stance model operate <strong>in</strong> a multitenant<br />

environment, <strong>in</strong> which server resources such as CPU and memory are shared between all the<br />

subscribers with Web Site deployments. There<strong>for</strong>e, quotas are en<strong>for</strong>ced per web site or across all<br />

web sites, which may result <strong>in</strong> a temporary disruption of service if one or more of your sites are<br />

us<strong>in</strong>g more than the allowed quota <strong>for</strong> a given resource.<br />

More about Web Sites<br />

Bus<strong>in</strong>ess Analytics<br />

SQL Report<strong>in</strong>g<br />

SQL Report<strong>in</strong>g is offered at no charge <strong>for</strong> bill<strong>in</strong>g periods beg<strong>in</strong>n<strong>in</strong>g prior to August 1, 2012. For<br />

bill<strong>in</strong>g periods beg<strong>in</strong>n<strong>in</strong>g after July 31, 2012, SQL Report<strong>in</strong>g will be charged <strong>for</strong> each clock hour<br />

of a report<strong>in</strong>g <strong>in</strong>stance. If runn<strong>in</strong>g your reports spans a clock hour, you will be billed a m<strong>in</strong>imum<br />

of one report<strong>in</strong>g <strong>in</strong>stance to complete the execution of your reports.<br />

Report<strong>in</strong>g <strong>in</strong>stance hours are charged only when your service is deployed. A customer is billed a<br />

m<strong>in</strong>imum of a s<strong>in</strong>gle hour (a “Report<strong>in</strong>g Instance Hour”) while they have SQL Report<strong>in</strong>g<br />

deployed. This base charge covers up to 200 reports each clock hour. Dur<strong>in</strong>g each clock hour<br />

that you generate more than 200 reports, you will be billed another Report<strong>in</strong>g Instance Hour <strong>for</strong><br />

each additional block of 200 reports, rounded up.<br />

For example, if you deployed one report<strong>in</strong>g <strong>in</strong>stance <strong>for</strong> one day dur<strong>in</strong>g the bill<strong>in</strong>g cycle and<br />

dur<strong>in</strong>g that one day you stayed with<strong>in</strong> 200 reports <strong>for</strong> every hour except <strong>for</strong> one hour, where you<br />

<strong>in</strong>itiated 250 reports. You would be billed <strong>for</strong> two hours <strong>for</strong> that hour you exceeded 200 reports<br />

<strong>for</strong> a total of 25 Report<strong>in</strong>g Instance Hours <strong>for</strong> that day.<br />

Network<strong>in</strong>g


Virtual Network<br />

<strong>W<strong>in</strong>dows</strong> <strong>Azure</strong> Virtual Network is currently available <strong>in</strong> preview at no charge. The date <strong>for</strong><br />

general availability of this service has not yet been announced. For illustrative purposes, when<br />

the service is generally available, it will be priced at $0.05 per VPN connection-hour us<strong>in</strong>g our<br />

Pay-As-You-Go prices <strong>in</strong> US dollars <strong>for</strong> customers that purchase <strong>W<strong>in</strong>dows</strong> <strong>Azure</strong> directly from<br />

our <strong>W<strong>in</strong>dows</strong> <strong>Azure</strong> web site. Our <strong>Enterprise</strong> Program customers will receive their standard<br />

level discount and commitment discount off of this rate.<br />

When you create a hardware VPN connection <strong>for</strong> your virtual network with a VPN gateway, you<br />

will be charged <strong>for</strong> each VPN connection hour that the connection is provisioned and available.<br />

When you term<strong>in</strong>ate your VPN connection, the charges <strong>for</strong> that connection will cease. Partial<br />

VPN connection-hours are billed as full hours. All data transferred over the VPN connection is<br />

charged at <strong>Azure</strong>’s standard data transfer rates. All resources consumed with<strong>in</strong> the provisioned<br />

private network(s) are charged at regular <strong>Azure</strong> prices <strong>for</strong> the resource (e.g. compute, storage<br />

etc.)<br />

Connect and Traffic Manager<br />

<strong>W<strong>in</strong>dows</strong> <strong>Azure</strong> Connect and Traffic Manager are currently <strong>in</strong> Community Technology Preview<br />

(CTP) and available at no charge.<br />

Data Transfers (except CDN)<br />

All <strong>in</strong>bound data transfers (i.e. data go<strong>in</strong>g <strong>in</strong>to W<strong>in</strong>dow <strong>Azure</strong> datacenters) are free. Data<br />

transfers are charged based on the total amount of data mov<strong>in</strong>g out of <strong>W<strong>in</strong>dows</strong> <strong>Azure</strong><br />

datacenters via the <strong>in</strong>ternet <strong>in</strong> a given bill<strong>in</strong>g period. Data transfers between <strong>W<strong>in</strong>dows</strong> <strong>Azure</strong><br />

services located with<strong>in</strong> the same sub-region are not subject to charge. Data transfers between<br />

sub-regions are charged at normal rates on both sides of the transfer. A sub-region is the lowest<br />

level geo-location that you may select to deploy your applications and associated data.<br />

Below is a list of our regions and sub-regions <strong>for</strong> normal data transfers (except <strong>for</strong> CDN).<br />

Regions Sub Regions<br />

North Europe<br />

Western Europe<br />

East US<br />

Zone 1<br />

North Central US<br />

South Central US*<br />

West US<br />

East Asia<br />

Zone 2<br />

Southeast Asia<br />

*Unavailable <strong>for</strong> storage and compute on new subscriptions<br />

Cach<strong>in</strong>g


CDN<br />

Content Delivery Network (CDN) charges are <strong>in</strong>curred <strong>for</strong> the data requests the CDN receives<br />

and <strong>for</strong> the data it transfers out to satisfy these requests. CDN charges do not <strong>in</strong>clude charges<br />

associated with transferr<strong>in</strong>g data from <strong>W<strong>in</strong>dows</strong> <strong>Azure</strong> Storage to CDN. Any data transfers and<br />

storage transactions <strong>in</strong>curred to get data from <strong>W<strong>in</strong>dows</strong> <strong>Azure</strong> Storage to the CDN will be<br />

charged separately at your Data Transfer and Storage transaction rates.<br />

<strong>W<strong>in</strong>dows</strong> <strong>Azure</strong> CDN data transfer charges are based on the data center location from which the<br />

traffic was served - not the end user's location. Below is a table that maps the data center<br />

locations to their associated bill<strong>in</strong>g zone.<br />

Bill<strong>in</strong>g Regions Geographic Location<br />

North America<br />

Zone 1<br />

Europe<br />

Asia Pacific<br />

Zone 2 Lat<strong>in</strong> America<br />

Middle East / Africa<br />

Developers cannot control which locations are used to deliver content, so bills may reflect<br />

delivery charges from any of the <strong>W<strong>in</strong>dows</strong> <strong>Azure</strong> CDN bill<strong>in</strong>g regions. User requests are<br />

directed to CDN nodes based on their Internet Service Provider's rout<strong>in</strong>g tables as well as<br />

network conditions. Users may be routed to locations that are preferred by their ISP, and/or<br />

nodes that are judged as "closer" <strong>in</strong> a logical sense. These nodes will not necessarily be <strong>in</strong><br />

physical proximity. For example, if a developer deploys content on the CDN and end users are<br />

<strong>in</strong> both Europe and Asia Pacific, the developer would likely see charges <strong>for</strong> delivery <strong>in</strong> both<br />

Zone 1 and Zone 2. However, some users may be served from one of our other geographic<br />

locations such as North America, based on rout<strong>in</strong>g tables and network status, if <strong>for</strong> example an<br />

Asia Pacific CDN node became unreachable. In this example, the developer would be charged<br />

<strong>for</strong> data transfers at Zone 1 rates <strong>for</strong> those users.<br />

When the <strong>W<strong>in</strong>dows</strong> <strong>Azure</strong> CDN receives a request <strong>for</strong> an object it does not have at an edge<br />

location, it will make a standard request of <strong>W<strong>in</strong>dows</strong> <strong>Azure</strong> Storage to obta<strong>in</strong> the data. CDN<br />

charges do not <strong>in</strong>clude fees associated with transferr<strong>in</strong>g this data from <strong>W<strong>in</strong>dows</strong> <strong>Azure</strong> Storage<br />

to CDN. Any data transfers and storage transactions <strong>in</strong>curred to get data from <strong>W<strong>in</strong>dows</strong> <strong>Azure</strong><br />

Storage to CDN will be charged separately at our normal <strong>W<strong>in</strong>dows</strong> <strong>Azure</strong> Storage rates. CDN<br />

charges are <strong>in</strong>curred <strong>for</strong> data requests it receives and <strong>for</strong> the data it transfers out to satisfy these<br />

requests.<br />

Availability of content <strong>in</strong> the <strong>W<strong>in</strong>dows</strong> <strong>Azure</strong> CDN's local caches (often called "cache efficacy"<br />

or "offload") is nondeterm<strong>in</strong>istic but is <strong>in</strong>fluenced by multiple factors <strong>in</strong>clud<strong>in</strong>g:<br />

Expiration ("max-age") header values<br />

Overall total size of the developer's content library (how much could be cached)<br />

Active work<strong>in</strong>g set (how much is currently cached)<br />

Traffic (how much is be<strong>in</strong>g served)<br />

Cache churn (how often are objects be<strong>in</strong>g added to cache, or ag<strong>in</strong>g out)


For example, a developer with a large ("wide") library with high churn and high traffic will have<br />

less cache efficacy than other users, because cache turnover is higher, so objects will be swapped<br />

<strong>in</strong> and out more frequently. This developer's overall <strong>W<strong>in</strong>dows</strong> <strong>Azure</strong> Storage data transfer<br />

charges will be proportionally higher, s<strong>in</strong>ce more orig<strong>in</strong> requests are required. The overall enduser<br />

experience <strong>in</strong> this example will also be slightly slower on average s<strong>in</strong>ce fewer requests are<br />

served from cache. The ma<strong>in</strong> cost control <strong>for</strong> developers to affect cache efficacy is the "maxage"<br />

HTTP header. Longer max-age headers allow the CDN to hold objects longer, reduc<strong>in</strong>g the<br />

need to make orig<strong>in</strong> requests.<br />

Cach<strong>in</strong>g<br />

<strong>W<strong>in</strong>dows</strong> <strong>Azure</strong> Cach<strong>in</strong>g delivers data closer to application logic. As user load <strong>in</strong>creases, the<br />

Cache helps applications be more responsive and allows your applications to scale. Choose<br />

between two deployment options –a managed, multi-tenant shared cache (Shared Cach<strong>in</strong>g) or a<br />

cache that uses your exist<strong>in</strong>g or dedicated web/worker roles – called the Cach<strong>in</strong>g (Preview).<br />

With the shared cache, cache resources are used from a shared pool across all tenants who<br />

subscribe to the service. With the Cach<strong>in</strong>g (Preview), a cache uses the memory <strong>in</strong> compute<br />

resources (Web or Worker roles) that are specifically provisioned <strong>for</strong> a s<strong>in</strong>gle tenant. You can<br />

use exist<strong>in</strong>g compute resources or create dedicated resources just <strong>for</strong> use by the cache.<br />

Shared Cach<strong>in</strong>g (Managed Service)<br />

Shared Cach<strong>in</strong>g is priced per cache size per month, no matter how much cache you actually use.<br />

You will also be charged <strong>for</strong> data transfers that go outside of the data center <strong>in</strong> which your<br />

services are provisioned.<br />

Once you provision a specific cache size, the service limits the amount of data you put <strong>in</strong> the<br />

cache to that size. Your application might temporarily have more data <strong>in</strong> the cache than the size<br />

<strong>for</strong> which you signed up, but the system will soon take corrective action and delete data from<br />

your cache to keep your cache size with<strong>in</strong> the provisioned size.<br />

In order to make sure there is fair usage of resources, the service might en<strong>for</strong>ce limitations based<br />

on the number of transactions be<strong>in</strong>g made aga<strong>in</strong>st the cache, the total data transfer be<strong>in</strong>g<br />

consumed, or the number of concurrent connections be<strong>in</strong>g used. If you exceed the limitations<br />

en<strong>for</strong>ced by the service, your application will be notified by receiv<strong>in</strong>g an exception specify<strong>in</strong>g<br />

the specific quota limit you have reached.<br />

The table below provides a general guidel<strong>in</strong>e that can help you plan your usage of the service.<br />

This guidel<strong>in</strong>e is a high-level estimate and is subject to revision <strong>in</strong> the future.<br />

Cache Size Transactions Per Hour Data Transfers Per Hour (MB)<br />

Concurrent<br />

Connections<br />

128MB 400,000 1,400 10<br />

256MB 800,000 2,800 10<br />

512MB 1,600,000 5,600 20<br />

1GB 3,200,000 11,200 40<br />

2GB 6,400,000 22,400 80<br />

4GB 12,800,000 44,800 160


Please note that a consistent bill<strong>in</strong>g unit of measure of 128 MB is utilized <strong>for</strong> all the different<br />

sizes of cache. So, <strong>for</strong> example, if you were to deploy a 1 GB cache, you would see a quantity<br />

of 8 on your bill.<br />

Cach<strong>in</strong>g (Preview)<br />

<strong>W<strong>in</strong>dows</strong> <strong>Azure</strong> Cach<strong>in</strong>g (Preview) can be deployed as a service alongside other application<br />

code <strong>in</strong> your Web or Worker roles or you can choose to have Worker roles specifically dedicated<br />

to the cache. The cache is distributed across the compute resources you select and <strong>in</strong>tegrated<br />

<strong>in</strong>to the <strong>W<strong>in</strong>dows</strong> <strong>Azure</strong> SDK. Once deployed <strong>in</strong> Web or Worker roles, there is no additional<br />

charge <strong>for</strong> cach<strong>in</strong>g above and beyond normal Cloud Services rates which vary by the type of role<br />

and the role size.<br />

Media Services Encod<strong>in</strong>g<br />

Encod<strong>in</strong>g us<strong>in</strong>g <strong>W<strong>in</strong>dows</strong> <strong>Azure</strong> Media Services will be billed based on data processed <strong>in</strong><br />

gigabytes. The total gigabytes processed are equal to the data <strong>in</strong>put to the encoder, plus the data<br />

output from the encoder calculated <strong>for</strong> a bill<strong>in</strong>g-cycle month. Both <strong>in</strong>put and output data will be<br />

stored <strong>in</strong> the Media Services customer’s storage account, <strong>for</strong> which the standard <strong>W<strong>in</strong>dows</strong> <strong>Azure</strong><br />

Storage and Data Transfer charges will apply. Media Encod<strong>in</strong>g will rema<strong>in</strong> free of charge until<br />

March 1, 2013, when it will be billed at $1.99 per GB.Our <strong>Enterprise</strong> Program customers will<br />

receive their standard level discount and commitment discount off of this rate.<br />

Media Services Encod<strong>in</strong>g Reserved Unit<br />

You may choose to purchase Encod<strong>in</strong>g Reserved Units to get parallel process<strong>in</strong>g of media tasks.<br />

The number of media tasks that will be processed <strong>in</strong> parallel will be equal to the number of<br />

reserved units purchased. Media Services Encod<strong>in</strong>g Reserved Units is available at no charge<br />

until February 1, 2013, when it will be billed at $99 each per month, calculated on a daily basis<br />

us<strong>in</strong>g the highest number of reserved units that are provisioned <strong>in</strong> the account <strong>in</strong> the<br />

correspond<strong>in</strong>g 24-hour period. For example, if you purchase five Encod<strong>in</strong>g Reserved Units at<br />

11:00, and then br<strong>in</strong>g the number down to 3 Reserved Units at 15:00, you will be charged <strong>for</strong><br />

five Reserved Units <strong>for</strong> that day. If you purchase five Encod<strong>in</strong>g Reserved Units at 23:00, and<br />

then br<strong>in</strong>g the number down to three Reserved Units at 10:00 the next day, you will be charged<br />

<strong>for</strong> five Reserved Units <strong>for</strong> day one and also <strong>for</strong> day two s<strong>in</strong>ce you had five Reserved Units <strong>for</strong><br />

the first 10 hours of that day. Our <strong>Enterprise</strong> Program customers will receive their standard level<br />

discount and commitment discount off of this rate.<br />

Media Services Packag<strong>in</strong>g<br />

Packag<strong>in</strong>g us<strong>in</strong>g <strong>W<strong>in</strong>dows</strong> <strong>Azure</strong> Media Services is currently available at no charge.<br />

Media Services On-Demand Stream<strong>in</strong>g


Media Services On-Demand Stream<strong>in</strong>g will be free until March 1, 2013. After March 1, 2013,<br />

On-Demand Stream<strong>in</strong>g Units will be $199 each per month, calculated on a daily basis us<strong>in</strong>g the<br />

highest number of reserved units that were active <strong>in</strong> the account <strong>in</strong> the correspond<strong>in</strong>g 24-hour<br />

period. Standard <strong>W<strong>in</strong>dows</strong> <strong>Azure</strong> Data Transfer charges apply <strong>for</strong> all data mov<strong>in</strong>g out of the<br />

<strong>W<strong>in</strong>dows</strong> <strong>Azure</strong> data centers. Our <strong>Enterprise</strong> Program customers will receive their standard level<br />

discount and commitment discount off of this rate.<br />

More about Media Services<br />

Messag<strong>in</strong>g<br />

Service Bus<br />

Beg<strong>in</strong>n<strong>in</strong>g on June 1, 2012, our public prices <strong>in</strong> US dollars <strong>for</strong> customers that purchase on the<br />

<strong>W<strong>in</strong>dows</strong> <strong>Azure</strong> web site are as follows:<br />

$0.10 per 100 Relay Hours<br />

$0.01 per 10,000 Messages<br />

Our <strong>Enterprise</strong> Program customers will receive their standard level discount and commitment<br />

discount off of the above rates.<br />

Messages are charged based on the number of messages sent to, or delivered by, the Service Bus<br />

dur<strong>in</strong>g the bill<strong>in</strong>g month. This <strong>in</strong>cludes delivery of “null” messages <strong>in</strong> response to receive<br />

requests aga<strong>in</strong>st empty queues/subscriptions. Messages over 64KB <strong>in</strong> size will be charged an<br />

additional message <strong>for</strong> each additional 64KB of data (rounded up).<br />

Relay Hours will be charged from the time of creation to deletion (from when the first listener<br />

opens to when the last listener closes on the endpo<strong>in</strong>t) and rounded up to the next whole hour.<br />

There is no relay hour charge if you are only us<strong>in</strong>g Service Bus Queues and Topics.<br />

In addition to the prices noted above <strong>for</strong> Service Bus, you will also be charged <strong>for</strong> the associated<br />

Data Transfers <strong>for</strong> Egress outside the data center that your services are provisioned.<br />

Mobile Services (Preview)<br />

For <strong>W<strong>in</strong>dows</strong> <strong>Azure</strong> Mobile Services, a Mobile Service is best conceptualized as the back end of<br />

an application. Thus, each application can utilize every available Mobile Services feature. For<br />

example, one Mobile Service could <strong>in</strong>clude structured storage, user authentication via Facebook,<br />

and push notifications. Each <strong>W<strong>in</strong>dows</strong> <strong>Azure</strong> subscription receives 10 free Mobile Services<br />

runn<strong>in</strong>g on shared <strong>in</strong>stances.


At this time, we have no plans to charge <strong>for</strong> the first 10 Mobile Services runn<strong>in</strong>g on shared<br />

<strong>in</strong>stances, other than your <strong>W<strong>in</strong>dows</strong> <strong>Azure</strong> SQL Database usage, which is billed separately. If<br />

our plans change, you will receive 30 days’ notice of that change.<br />

You can visit our Preview Features page to enroll <strong>in</strong> the Mobile Services preview and start<br />

build<strong>in</strong>g, deploy<strong>in</strong>g, and runn<strong>in</strong>g up to 10 shared <strong>in</strong>stances of Mobile Services at no charge.*<br />

The Mobile Services shared-<strong>in</strong>stance model provides the follow<strong>in</strong>g services at no charge:<br />

Mobile Services: Up to 10 Mobile Services*<br />

Data Transfers: 165 MB of outbound data transfers per day per subscription; unlimited<br />

<strong>in</strong>bound data transfers<br />

* Use of Mobile Services requires a SQL Database, which is charged at your normal rates.<br />

By default, your free 10 Mobile Services are configured <strong>in</strong> a shared-<strong>in</strong>stance model, runn<strong>in</strong>g <strong>in</strong> a<br />

shared compute environment alongside other users’ Mobile Services and shar<strong>in</strong>g the server<br />

resources.<br />

You can elect at any time to upgrade to the reserved-<strong>in</strong>stance model, which provides up to three<br />

dedicated server <strong>in</strong>stances <strong>for</strong> all of your Mobile Services at an additional cost. When you switch<br />

to the reserved-<strong>in</strong>stance model, you can create and manage up to 100 Mobile Services.* In<br />

addition, with the reserved-<strong>in</strong>stance model, you are not restricted <strong>in</strong> the amount of outbound data<br />

transfers that you can use each day, but you will be charged at your normal rates.<br />

Please note that Mobile Services deployed to a given sub region scale up or down as a group, and<br />

groups are charged <strong>in</strong>dependently. For example, if you upgrade one Mobile Service <strong>in</strong> the West<br />

US data center to a reserved <strong>in</strong>stance and one Mobile Service <strong>in</strong> the East US data center to a<br />

reserved <strong>in</strong>stance, you will be charged <strong>for</strong> two reserved <strong>in</strong>stances of Mobile Services.<br />

Additionally, if you deploy multiple Mobile Services to a sub region and upgrade one of those<br />

Mobile Services to a reserved <strong>in</strong>stance, you must upgrade all the other Mobile Services that you<br />

have deployed <strong>in</strong> that sub region. For example, if you have three Mobile Services deployed to<br />

US West and one deployed to US East, upgrad<strong>in</strong>g one Mobile Service <strong>in</strong> US West will<br />

automatically upgrade the other two Mobile Services <strong>in</strong> that sub region, but not the Mobile<br />

Service <strong>in</strong> US East. If you upgrade the s<strong>in</strong>gle Mobile Service <strong>in</strong> US East, the Mobile Services <strong>in</strong><br />

US West will not be affected.<br />

Dur<strong>in</strong>g the <strong>W<strong>in</strong>dows</strong> <strong>Azure</strong> Mobile Services preview, under the reserved-<strong>in</strong>stance model, you<br />

will receive the follow<strong>in</strong>g services per month:<br />

Mobile Services: Up to 100 Mobile Services<br />

Data Transfers: Unlimited outbound data transfers charged at your normal rates;<br />

unlimited <strong>in</strong>bound data transfers


Mobile services deployed under the reserved-<strong>in</strong>stance model are currently available only <strong>in</strong> the<br />

small virtual mach<strong>in</strong>e size powered by 1 CPU core and 1.75 GB of memory. Multiple small<br />

<strong>in</strong>stances may be purchased if your needs exceed this capacity.<br />

Mobile Services is currently <strong>in</strong> preview. Dur<strong>in</strong>g preview, all reserved-<strong>in</strong>stance hours will be<br />

billed us<strong>in</strong>g the current Cloud Services compute meter, except we will bill 33 percent fewer<br />

compute hours to deliver the discounted public pric<strong>in</strong>g of $0.08 per hour. Upon general<br />

availability of Mobile Services (date to be announced), the public price will be $0.12 per hour.<br />

For Mobile Services, we reserve the right to suspend service <strong>for</strong> nonuse or <strong>in</strong>activity. We will<br />

determ<strong>in</strong>e nonuse or <strong>in</strong>activity us<strong>in</strong>g the follow<strong>in</strong>g criteria: no adm<strong>in</strong>istrative action or end-user<br />

access <strong>for</strong> more than 90 days. We may use other reasonable criteria at our discretion from time to<br />

time. We will give you notice be<strong>for</strong>e suspend<strong>in</strong>g service.<br />

More about Mobile Services<br />

Back to top


Appendix A: Friendly Service Names (<strong>for</strong> current part numbers)<br />

Table 1: Commitment Part Numbers<br />

Commitment Name<br />

AppFabricAccessCtrl ShrdSvr ALNG SubsVL<br />

Service Friendly Name Commitment<br />

Part Number<br />

MVL 100KTrnsctn Commit Access Control Service Transactions P6H-00003<br />

AppFabricCache ShrdSvr ALNG SubsVL MVL<br />

128MB Commit 128MB Cache 128 MB 3SK-00005 128 MB<br />

AppFabricCache ShrdSvr ALNG SubsVL MVL<br />

1GB Commit 1GB Cache 1 GB 3SK-00001 128 MB<br />

AppFabricCache ShrdSvr ALNG SubsVL MVL<br />

256MB Commit 256MB Cache 256 MB 3SK-00008 128 MB<br />

AppFabricCache ShrdSvr ALNG SubsVL MVL<br />

2GB Commit 2GB Cache 2 GB 3SK-00007 128 MB<br />

AppFabricCache ShrdSvr ALNG SubsVL MVL<br />

4GB Commit 4GB Cache 4 GB 3SK-00004 128 MB<br />

AppFabricCache ShrdSvr ALNG SubsVL MVL<br />

512MB Commit 512MB Cache 512 MB 3SK-00011 128 MB<br />

Commitment<br />

Quantity Per Unit<br />

100,000<br />

Transactions<br />

AppFabricSrvcBsnss ShrdSvr ALNG SubsVL<br />

MVL 1000RlyHrs Commit Service Bus Relay Hours P5H-00023 1,000 Relay Hours<br />

AppFabricSrvcBsnss ShrdSvr ALNG SubsVL<br />

MVL 1MMsgs Commit Service Bus Messages P5H-00021 1,000,000 Messages<br />

SQL<strong>Azure</strong>Bsnss ShrdSvr ALNG SubsVL MVL<br />

10DtbaseUnt Commit SQL <strong>Azure</strong> Bus<strong>in</strong>ess 10 DU P4H-00011 10 DU<br />

SQL<strong>Azure</strong>Bsnss ShrdSvr ALNG SubsVL MVL<br />

10InstanceHrs Commit SQLRptg<br />

SQL <strong>Azure</strong> Bus<strong>in</strong>ess 10 Instance<br />

Hours Report<strong>in</strong>g P4H-00005 10 Instance Hours<br />

SQL<strong>Azure</strong>Web ShrdSvr ALNG SubsVL MVL<br />

1DBUnit Commit SQL <strong>Azure</strong> Database Web Edition N6H-00005<br />

W<strong>in</strong><strong>Azure</strong>CDN ShrdSvr ALNG SubsVL MVL<br />

10GB Commit DtaTrnsfrsZn1<br />

W<strong>in</strong><strong>Azure</strong>CDN ShrdSvr ALNG SubsVL MVL<br />

10GB Commit DtaTrnsfrsZn2<br />

W<strong>in</strong><strong>Azure</strong>CDN ShrdSvr ALNG SubsVL MVL<br />

10MTrnsctns Commit<br />

W<strong>in</strong><strong>Azure</strong>Compute ShrdSvr ALNG SubsVL<br />

MVL 100hrs Commit VirtNtwrk<br />

W<strong>in</strong><strong>Azure</strong>Compute ShrdSvr ALNG SubsVL<br />

MVL 100hrs Commit VrtMchnRole(NW)<br />

W<strong>in</strong><strong>Azure</strong>Compute ShrdSvr ALNG SubsVL<br />

MVL 100hrs Commit VrtMchnRole(W)<br />

W<strong>in</strong><strong>Azure</strong>Compute ShrdSvr ALNG SubsVL<br />

MVL 10hrs Commit SmallInstance<br />

W<strong>in</strong><strong>Azure</strong>Compute ShrdSvr ALNG SubsVL<br />

MVL DataPrcssdGB Commit MdiaSrvcs<br />

W<strong>in</strong><strong>Azure</strong>PDT ShrdSvr ALNG SubsVL MVL<br />

10GB Commit EgressZone1<br />

W<strong>in</strong><strong>Azure</strong>PDT ShrdSvr ALNG SubsVL MVL<br />

10GB Commit EgressZone2<br />

W<strong>in</strong><strong>Azure</strong>PDT ShrdSvr ALNG SubsVL MVL<br />

10GB Commit IngressAPAC<br />

<strong>W<strong>in</strong>dows</strong> <strong>Azure</strong> CDN 10 GB Data<br />

Transfers Zone 1 P3H-00024 10 GB<br />

<strong>W<strong>in</strong>dows</strong> <strong>Azure</strong> CDN 10 GB Data<br />

Transfers Zone 2 P3H-00021 10 GB<br />

<strong>W<strong>in</strong>dows</strong> <strong>Azure</strong> CDN 10M<br />

Transactions P3H-00027<br />

1 Database Unit<br />

(DU)<br />

10,000,000<br />

Transactions<br />

<strong>W<strong>in</strong>dows</strong> <strong>Azure</strong> Compute 100 Hrs<br />

Virtual Network N7H-00018 100 Hours<br />

<strong>W<strong>in</strong>dows</strong> <strong>Azure</strong> Compute 100 Hrs<br />

VM (Non-<strong>W<strong>in</strong>dows</strong>) N7H-00014 100 Hours<br />

<strong>W<strong>in</strong>dows</strong> <strong>Azure</strong> Compute 100 Hrs<br />

VM (<strong>W<strong>in</strong>dows</strong>) N7H-00023 100 Hours<br />

<strong>W<strong>in</strong>dows</strong> <strong>Azure</strong> Compute Hours -<br />

Small Instance N7H-00013 10 Hours<br />

<strong>W<strong>in</strong>dows</strong> <strong>Azure</strong> Compute Data<br />

Processed (GB) Media Services N7H-00016 1 GB<br />

<strong>W<strong>in</strong>dows</strong> <strong>Azure</strong> Data Transfer Egress<br />

Zone 1 Q5H-00010 10 GB<br />

<strong>W<strong>in</strong>dows</strong> <strong>Azure</strong> Data Transfer Egress<br />

Zone 2 Q5H-00009 10 GB<br />

<strong>W<strong>in</strong>dows</strong> <strong>Azure</strong> Data Transfer<br />

Ingress APAC Q5H-00011 10 GB


Commitment Name Service Friendly Name Commitment<br />

Part Number<br />

W<strong>in</strong><strong>Azure</strong>PDT ShrdSvr ALNG SubsVL MVL<br />

10GB Commit IngressNA/EMEA<br />

<strong>W<strong>in</strong>dows</strong> <strong>Azure</strong> Data Transfer<br />

Ingress NA/EMEA Q5H-00012 10 GB<br />

W<strong>in</strong><strong>Azure</strong>Strg ShrdSvr ALNG SubsVL MVL<br />

10GB Commit Capacity Geo Redundant Storage N9H-00005 10 GB<br />

W<strong>in</strong><strong>Azure</strong>Strg ShrdSvr ALNG SubsVL MVL<br />

10GB Commit Non-GeoRplctd Locally Redundant Storage N9H-00006 10 GB<br />

W<strong>in</strong><strong>Azure</strong>Strg ShrdSvr ALNG SubsVL MVL<br />

10MTrnsctns Commit<br />

<strong>W<strong>in</strong>dows</strong> <strong>Azure</strong> Storage 10M<br />

Transactions N9H-00008<br />

Commitment<br />

Quantity Per Unit<br />

10,000,000<br />

Transactions


Table 2: Consumption Part Numbers<br />

Consumption Name<br />

AppFabricAccessCtrl ShrdSvr ALNG Fee MVL<br />

Service Friendly Name Consumption<br />

Part Number<br />

100KTrnsctn Ovrg Access Control Service Transactions P6H-00004<br />

AppFabricCache ShrdSvr ALNG Fee MVL<br />

128MB Ovrg 128MB Cache 128 MB 3SK-00006 128 MB<br />

AppFabricCache ShrdSvr ALNG Fee MVL<br />

1GB Ovrg 1GB Cache 1 GB 3SK-00002 128 MB<br />

AppFabricCache ShrdSvr ALNG Fee MVL<br />

256MB Ovrg 256MB Cache 256 MB 3SK-00009 128 MB<br />

AppFabricCache ShrdSvr ALNG Fee MVL<br />

2GB Ovrg 2GB Cache 2 GB 3SK-00003 128 MB<br />

AppFabricCache ShrdSvr ALNG Fee MVL<br />

4GB Ovrg 4GB Cache 4 GB 3SK-00010 128 MB<br />

AppFabricCache ShrdSvr ALNG Fee MVL<br />

512MB Ovrg 512MB Cache 512 MB 3SK-00012 128 MB<br />

Consumption<br />

Quantity Per Unit<br />

100,000<br />

Transactions<br />

AppFabricSrvcBsnss ShrdSvr ALNG Fee MVL<br />

1000RlyHrs Ovrg Service Bus Relay Hours P5H-00024 1,000 Relay Hours<br />

AppFabricSrvcBsnss ShrdSvr ALNG Fee MVL<br />

1MMsgs Ovrg Service Bus Messages P5H-00022 1,000,000 Messages<br />

SQL<strong>Azure</strong>Bsnss ShrdSvr ALNG Fee MVL<br />

10DtbaseUnt Ovrg SQL <strong>Azure</strong> Bus<strong>in</strong>ess 10 DU P4H-00012<br />

SQL<strong>Azure</strong>Bsnss ShrdSvr ALNG Fee MVL<br />

10InstanceHrs Ovrg SQLRptg<br />

10 Database Units<br />

(DU)<br />

SQL <strong>Azure</strong> Bus<strong>in</strong>ess 10 Instance<br />

Hours Report<strong>in</strong>g P4H-00006 10 Instance Hours<br />

SQL<strong>Azure</strong>Web ShrdSvr ALNG Fee MVL<br />

1DBUnit Ovrg SQL <strong>Azure</strong> Database Web Edition N6H-00006<br />

W<strong>in</strong><strong>Azure</strong>CDN ShrdSvr ALNG Fee MVL<br />

10GB Ovrg DtaTrnsfrsZn1<br />

W<strong>in</strong><strong>Azure</strong>CDN ShrdSvr ALNG Fee MVL<br />

10GB Ovrg DtaTrnsfrsZn2<br />

W<strong>in</strong><strong>Azure</strong>CDN ShrdSvr ALNG Fee MVL<br />

10MTrnsctns Ovrg<br />

W<strong>in</strong><strong>Azure</strong>Compute ShrdSvr ALNG Fee MVL<br />

100hrs Ovrg VirtNtwrk<br />

W<strong>in</strong><strong>Azure</strong>Compute ShrdSvr ALNG Fee MVL<br />

100hrs Ovrg VrtMchnRole(NW)<br />

W<strong>in</strong><strong>Azure</strong>Compute ShrdSvr ALNG Fee MVL<br />

100hrs Ovrg VrtMchnRole(W)<br />

W<strong>in</strong><strong>Azure</strong>Compute ShrdSvr ALNG Fee MVL<br />

10hrs Ovrg SmallInstance<br />

W<strong>in</strong><strong>Azure</strong>Compute ShrdSvr ALNG Fee MVL<br />

DataPrcssdGB Ovrg MdiaSrvcs<br />

W<strong>in</strong><strong>Azure</strong>PDT ShrdSvr ALNG Fee MVL<br />

10GB Ovrg EgressZone1<br />

W<strong>in</strong><strong>Azure</strong>PDT ShrdSvr ALNG Fee MVL<br />

10GB Ovrg EgressZone2<br />

W<strong>in</strong><strong>Azure</strong>PDT ShrdSvr ALNG Fee MVL<br />

10GB Ovrg IngressAPAC<br />

W<strong>in</strong><strong>Azure</strong>PDT ShrdSvr ALNG Fee MVL<br />

10GB Ovrg IngressNA/EMEA<br />

<strong>W<strong>in</strong>dows</strong> <strong>Azure</strong> CDN 10 GB Data<br />

Transfers Zone 1 P3H-00023 10 GB<br />

<strong>W<strong>in</strong>dows</strong> <strong>Azure</strong> CDN 10 GB Data<br />

Transfers Zone 2 P3H-00022 10 GB<br />

<strong>W<strong>in</strong>dows</strong> <strong>Azure</strong> CDN 10M<br />

Transactions P3H-00028<br />

1 Database Unit<br />

(DU)<br />

10,000,000<br />

Transactions<br />

<strong>W<strong>in</strong>dows</strong> <strong>Azure</strong> Compute 100 Hrs<br />

Virtual Network N7H-00019 100 Hours<br />

<strong>W<strong>in</strong>dows</strong> <strong>Azure</strong> Compute 100 Hrs<br />

VM (Non-<strong>W<strong>in</strong>dows</strong>) N7H-00015 100 Hours<br />

<strong>W<strong>in</strong>dows</strong> <strong>Azure</strong> Compute 100 Hrs<br />

VM (<strong>W<strong>in</strong>dows</strong>) N7H-00022 100 Hours<br />

<strong>W<strong>in</strong>dows</strong> <strong>Azure</strong> Compute Hours -<br />

Small Instance N7H-00001 10 Hours<br />

<strong>W<strong>in</strong>dows</strong> <strong>Azure</strong> Compute Data<br />

Processed (GB) Media Services N7H-00017 1 GB<br />

<strong>W<strong>in</strong>dows</strong> <strong>Azure</strong> Data Transfer Egress<br />

Zone 1 Q5H-00003 10 GB<br />

<strong>W<strong>in</strong>dows</strong> <strong>Azure</strong> Data Transfer Egress<br />

Zone 2 Q5H-00002 10 GB<br />

<strong>W<strong>in</strong>dows</strong> <strong>Azure</strong> Data Transfer<br />

Ingress APAC Q5H-00004 10 GB<br />

<strong>W<strong>in</strong>dows</strong> <strong>Azure</strong> Data Transfer<br />

Ingress NA/EMEA Q5H-00005 10 GB<br />

W<strong>in</strong><strong>Azure</strong>Strg ShrdSvr ALNG Fee MVL 10GB<br />

Ovrg Capacity Geo Redundant Storage N9H-00001 10 GB


Consumption Name Service Friendly Name Consumption<br />

Part Number<br />

W<strong>in</strong><strong>Azure</strong>Strg ShrdSvr ALNG Fee MVL 10GB<br />

Ovrg Non-GeoRplctd Locally Redundant Storage N9H-00007 10 GB<br />

W<strong>in</strong><strong>Azure</strong>Strg ShrdSvr ALNG Fee MVL<br />

10MTrnsctns Ovrg<br />

<strong>W<strong>in</strong>dows</strong> <strong>Azure</strong> Storage 10M<br />

Transactions N9H-00009<br />

Consumption<br />

Quantity Per Unit<br />

10,000,000<br />

Transactions

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!