How are Streaming Units is being charged; per day or per month?
Media Services pricing page shows:
~ $4.48/day ($139/mo)
Billing is prorated daily based on 31 days per month.
while pricing calculator page is based on only per month calculation.
Thanks.
Regards
It's prorated daily. So as soon as you turn it on, you are charged for the first day. The pricing calculator is only showing the monthly fee and not allowing you set it by day.
Related
Azure Notification hub free tier has 1million pushes per subscription.
My question is are 1 million pushes per month?
According to the pricing,
Free - get up to 1 million pushes per subscription a month.
Basic - get 10 million pushes per subscription a month as a baseline, with quota growth options.
Standard - get 10 million pushes per subscription a month as a baseline, with quota increase options, plus rich telemetry capabilties
All of the prices listed on this page are monthly: Notification Hub Pricing
So as of the time of writing you are correct, the 1 million pushes are evaluated monthly by subscription.
We offer a Pro Monthly Subscription where the monthly rate is $50 but we require the first 2-months to be pre-paid upfront.
Or you could rephrase another way; the first month of a Subscription is paid and the second month is pre-paid.
With another payment processor (FastSpring) we could configure a First Period Length on Subscriptions. For example, a Pro Monthly Subscription is purchased but the First Period Length is set to 2-months.
Here's a scenario:
Subscription is purchased on July 1st
First 2-months pre-paid on July 1st = $100
Next charge date is September 1st = $50
Charges ($50) continue monthly until Subscription is cancelled
We haven't found a clean way to accomplish the same First Period Length with Stripe.
Any idea how something similar could be configured with Stripe?
You can achieve this with a trial period and a one off-invoice. Here's the flow:
Create the subscription and set the trial period to 60 days: https://stripe.com/docs/api/subscriptions/create#create_subscription-trial_period_days
Create a one-off invoice to immediately charge for 2 months ($100): https://stripe.com/docs/billing/invoices/one-off
After the 2 month trial period is over, the regular monthly subscription ($50 a month) will kick in
A Product with two Pricing Plans and a scheduled change to the Subscription was a good fit for our scenario.
The first Pricing Plan (Intro) is configured with a 2-month term and $100 fee (2 * $50/month).
Second Pricing Plan is the regular monthly rate ($50/month).
When the Subscription is created the Intro plan starts on Day0 and a change is scheduled for 2-months to switch the Subscription to the regular Monthly pricing plan.
Here's the configuration in the Dashboard:
I am using Azure Pay As You Go subscription. I wanted to create Azure IOT hub with S1:Stander Tier. Cost per month is :1652.41 INR. If I use it for 8 hrs for trying some example and delete the that create IOT hub, will it charge 1652.41 INR Or hourly or daily basis?
This is answered in the FAQ at https://azure.microsoft.com/en-au/pricing/details/iot-hub/
The relevant section for these standing charges are:
How does billing work for the IoT Hub service?
The consumption of IoT Hub units is measured on a daily basis, and the billing is generated on a monthly basis. Customers are billed based on the number of IoT Hub units that have been consumed during the month.
Is the billing prorated if I purchase an additional IoT Hub unit mid-month?
You can choose to increase the number of IoT Hub units purchased at any time. If you sign up for the service mid-month, your monthly bill will be pro-rated based on the number of days remaining in the month. (For the purpose of the IoT Hub service, a month is defined as 31 days). If you increase the number of units of IoT Hub mid-month, your monthly bill will be based on the number of units available for each day during the month.
So for your example of 8 hours use in a single day will be measured as the monthly rate divided by 31.
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
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.