Shared Websites in Azure - azure

If there are only requests to a shared Azure website during day hours (12 hours per day) does this mean the monthly bill would be for ~375 hours? All of the calculator prices are based on 744 hours which equates to one month.
Currently the calculator shows the pricing for one shared website is the same as one small VM so why even have the shared level at all?
Edit: I just found out there was actually a bug in the Azure Calculator.

You will have to pay for every hour (minute from June) your Web site, VM, Mobile service and cloud service has been online/available. This means if you keep your site running for a month, you will have to pay for ~744 hours (average hours in a month).
Microsoft changed the Azure pricing model to a charge per minute your VM is running last month (June). Previous to last month you would also have to pay for each hour even if you VM was stopped. When you stop your VM now, you will no longer be billed for each hour the VM is stopped.
In your case, this means you would have to stop and start your website to pay less per month.
As for the pricing. As far as I know the cost for one shared website is less than the other options (extra small VM, extra small CS, etc).
For example (using the calculator for 1 instance):
Shared Website: €7,21
Extra Small VM: €11,09

Related

I selected D1(shared) for 9$ option while setting custom domain in Azure. Now will I pay those 9$?

I created a free account in Azure.com.For custom domain I chose D1(shared) option for 9$. Now the issue is, my total free credit are still 200$ how? Will I pay 9$ from my credit card? Since it's totally free account and they will not charge unless I convert my account to Pay-As-You-Go subscription. Even they delete it after the trail. I tried to talk with their support they told me that it's free and you will not be charged, but my 200$ credits are still there.
You can see in the image what option I chose:
The $9.67 is the cost of running this app for 1 month. So if you create this app on the first of the month and let it run through the 30th, then you would be left with $190.33 azure credits.
When you create the app the 9.67 is not charged upfront but rather you would be charged about $0.013 per hour.
So if the app is there for 24 hours for 30 days then that would be $0.013 * 24(hours in a day) * 30(days in a month) = $9.67 aprox.

Azure Shared Website billing

My shared instance website is costing about £20 GBP per month, and this is detailed as 'Compute Hours' in my bill.
According to Scott Gu's blog
"You pay for a shared mode web-site using the standard “pay as you go” model that we support with other features of Windows Azure (meaning no up-front costs, and you pay only for the hours that the feature is enabled). A web-site running in shared mode costs only 1.3 cents/hr during the preview (so on average $9.36/month)."
According to the azure pricing calculator a site on a shared instance should cost $9.36.
According to the Azure pricing details
"Shared Instance Model
The shared instance model provides support for custom domain names, 1
GB of storage, and unlimited outbound data transfer charged on the
terms of your Windows Azure subscription at the standard Pay-As-You-Go
rates. Up to three instances per Web site may be deployed at an
additional cost.
Under the shared instance model, you will receive the following
benefits:
The ability to assign your custom host or domain name Outbound traffic
charged at Pay-As-You-Go rates; unlimited inbound data transfer 1 GB
storage (shared by all sites) 20 MB of a third-party, MySQL database
Each Web site operated under the shared instance model will be charged
at $0.02 / hour (approx. $14.40 / month) per Web Site instance at
general availability. During preview, a 33% discount will be applied
for an effective monthly rate of $9.60 / month, per Web Site instance.
During preview, all paid shared instance hours will be billed using
the current Cloud Services small compute meter, except we will emit
1/9th of the Cloud Services small compute hours to deliver the
discounted pricing of $9.60 / month per Web Site instance. The monthly
calculation per paid shared Web Site instance is as follows: 720 hours
* 1/9 * $0.12 =$9.60."
So what I am misunderstanding? A shared website at the this moment in time (Jan 2013) should cost less than $10 per month.
EDIT MORE INFO
The price I am paying is exactly 3 times £9.60

3 Months Windows Azure Trial Disabled in 3 Weeks

My 3 months trial account Windows Azure has already been disabled in 3 weeks. How's that possible? I had nothing on my project, just a simple Asp.Net web page.
I don't think anybody knew my page and made constant requests.
I can't find a statistics section on Management Portal to check what was my traffic...etc.
Does anybody know where I can check my Hosted Service's statistics?
Thanks
The trial provides 750 compute hours monthly. Once you deploy your app, the meter is ticking. That is, as long as something is deployed, it's a metered resource. Whether consuming 0% or 100% cpu/network/memory, you pay hourly.
Now: If you deployed a single Small instance for your asp.net site, you shouldn't have consumed 750 hours in 3 weeks. Is it possible you deployed with Medium instances? Or deployed with 2 Small instances? Do you have more than one Role in your deployment (since each would have at least one instance)?
One bit of advice I give, when doing dev work: at the end of the day, when you're not actively working on a project, delete the deployment (you can always re-deploy to the same place later). This helps save tremendously on consumed hours.
You aren't charged based on access to a hosted service (i.e. compute instance). As long as you have something deployed there, you are charged. No one can ever go to it and it still costs you money.
At the portal, you have to delete whatever hosted services you have there in order to preserve credits. For example if you had up both a Production and a Staging instance, they would charge you compute hours for both. You have to actually delete the instances in order to conserve compute hours on your bill.
As for stats, the only way you can get access stats that I know of is by using the azure diagnostics features. They used to have a lot more detail on their bills (in / out transfers, etc) but the bills are a lot shorter now.

cloud services payments

All cloud payments described in hours.
Let's look at situation when server spend 0.75s to generate page and only one time this month (because nobody requested website).
Here is text from AWS and Azure website
"Pay only for what you use. There is no minimum fee. Estimate your
monthly bill using the AWS Simple Monthly Calculator."
"Windows Azure Pricing No upfront costs. Pay only for what you use"
Does it mean that I will pay just for 0.75s or for entire month?
You'll have to pay for one hour:
AWS:
Pricing is per instance-hour consumed for each instance, from the time
an instance is launched until it is terminated. Each partial
instance-hour consumed will be billed as a full hour.
Azure:
Compute hours are billed based on the number of clock hours your
service was deployed multiplied by the number of equivalent small
compute instances included in your deployment. Partial compute
instance hours (prior to conversion) are billed as full compute hours
for each clock hour an instance is deployed.

What about expenses on unused resources in Windows Azure?

The main question is: do I have to pay for unused resources? For instance, Azure pricing calculator says approximately $30/month for XS box. This includes about 750 hours. What if I don't use them all? This is normal for early stage, while development is in progress.
This is just to make it clear if its cheaper to have a virtual hosting for development and beta-testing purposes.
Not exactly a programming question.
That said: Windows Azure Compute instances are metered by the hour, and metering happens when you have deployed instances (whether running or stopped). If you're doing dev work, deploy for an hour or two (or how long it takes you to test), then delete the deployment. Very easy to delete, very easy to redeploy. Just don't delete the actual hosted service definition (urlname.cloudapp.net, associated certificates, affinity group, etc.). Following this pattern, it's easy to test with 5-10 concurrent instances in a deployment throughout the month - just remember to delete the deployment after each test cycle.
#Bart is partially right about SQL Azure being billed for the month. It's actually amortized daily. This also means: If you set up a 5GB db and only have 99MB on a given day (or days), you're billed at the $4.999 monthly rate / # of days in month). That's about 17 cents daily if you stay under 100MB. And if you delete the db, you're no longer billed.
Same goes for Cache - the cost is amortized daily.
I'd look at the full pricing page here.
You do not have to pay for unused resources in SOME of the services.
In your example, if you deploy a website for 10 hours you will be billed for the 10 hours of usage. PLUS any transactions/bandwidth associated with it.
However, some the services do have a flat fee. For example, if you deploy a 5 gig DB to SQL Azure and u do not use it...u will be billed the monthly rate even if it just sits there.
Also your definition of "use it" needs to be clear. Azure will bill you, if you have ANYTHING deployed. Even if the VM is stopped, you are getting billed. Therefore, the best solution is to:
- monitor your usage (its updated multiple times per day)
- use a free trial, MSDN account or promotion to see what the charges will be
- call MIcrosoft...Azure is the hot thing now and they WILL give you a break on charges if they are within reason.

Resources