I have a monthly spending limit of $150 Azure credit on my subscription and it is for free. However, I just went over it and I am wondering what happen to my charges and subscription? Will I get charged separately from $150? Will Azure services shut down in order to stop incurring charges?
Will Azure services shut down in order to stop incurring charges?
Yes. Once you exceed your spending limit, your subscription will be disabled and as a result of that your services will become inaccessible. Your subscription will be enabled automatically on your next billing start date.
Related
I am thinking of purchasing a 3 year reserved app service plan on azure.
For my site, normally 1 or 2 instances are just good enough, but in the busy time, I have rules to autoscale the site out to 10 instances.
If I buy a 3 year reserved app service plan and my site auto scale out, will I be charged by the reserved price or pay as you go price?
from their doc, my feeling is that I will be charged by pay as you go price.Is it right?
You are right, the reservation agreement is just a discount that will apply to the number of running instances that match the reservation scope and attributes. So any extra instances will be charged using your standard rate.
This rate will depend on the type of subscription you use for paying for the reservation. If you have an individual pay-as-you-go subscription, extra app services will be charged by pay-as-you-go price. However, if you have an enterprise agreement, the price will be different and will depend on the agreement.
I am new to Azure and while trying things I have created and deleted several resources and now my subscription is disable because I do not have any credits left.
I thought when I delete a resource I have created by mistake the credit will restore as well, its not true?
what should I do now?
When you create a new Azure Resource you start getting billed.
When you delete a resource the billing for that resource stops, but remember you will be charged for the time the resource was active.
If the total of all the charges exceeds your limit, the account will ask for Credit Card details to start charging it.
You can go the Cost Management + Billing section in Azure portal to get details of all the charges incurred for that Subscription.
I'm trying to create an Azure policy which would deny creation of any resource that's not covered by my MSDN subscription 130€ monthly quota. What happens is that I inadvertently create a resource which is not covered by MSDN subscription monthly quota, which leads to my Azure subscription being disabled the next day, and it remains disabled until the end of the monthly billing cycle. I raised a support issue with Microsoft, but they refused to help (because they are tring to get customers credit card data, which would remove the spending limit, and that's something I don't want to do).
Azure policy is not design to enforce billing quotas billing, it more for setting guidelines/policies about what can be deployed in subscriptions in your tenant.
MSDN account will cap at a certain amount, you can keep use the 'budgets' option on the subscription to keep track of how much you are spending.
Most 'enterprise' cloud providers are Pay-As-You-Go so no one is going to guarantee you a fixed price. You can also use the Azure Calculator to get an idea of what setup and consumption will let you stay under the MSDN quota.
Problem
We deploy a mixed SaaS, PaaS, IaaS solutions on Micorosft Azure. Recently our account was suspended due to a Microsoft credit limit.
1) The account billing and technical contact received no warning of the approaching credit limit. When the account was suspended alerts were raised instantly. In response I simply lifted the credit limit and the account was accessible again.
2) All VMs could then be started again within seconds and thrid party add-ons were operational automatically.
3) Cloud Services were displayed but all the web/worker role instances in each were stopped. On attempting to start it was clear the deployments had been deleted !
Questions
Does any one know or understand why the deployment packages are removed when an Azure account subscription has been disabled ?
VM, storages accounts, add-ons are persist so why delete the cloud service instances / deployment packages ?
Anyway to mitigate this issue ?
Result is 60 min downtime to upload and deploy packages from source control. Examining enterprise accounts and invoicing.
Thank you for any advice.
Scott
Currently, subscriptions which has monthly credits such as MSDN, MPN and Bizspark plus has a feature called spending limit. This feature is enabled by default to prevent any charges on your credit card. When this sending limit is triggered, the subscription is disabled for the remaining billing cycle and will be automatically re-enabled when the credit is reset which is on the start of the new billing cycle.
When the subscription is disabled, Cloud services (web and worker role) deployments are deleted as only the deployment file is uploaded on Azure and the source file would still be available by the developer. However, Virtual machines are created within Azure platform, hence VMs are stopped de-allocated when the subscription is disabled. The web services deployments are dealt with differently i.e they are deleted it’s a legacy of how the platform was built and is scaled.
The Azure portal shows the credit utilized and remaining balance for the subscription and notifying the credit status over email is still not available. However, when the subscription is disabled, a notification is sent to the account owner.
Possible mitigation involves:
moving to standard payment terms , away from pay-as-you-go account.
remove the credit limit
possibly a continuous deployment strategy via Team Foundation Server or the like could automate redeployment (no doubt there are other automation methods too).
Unfortunately if the Azure subscription is suspended service deployments are deleted and must be uploaded again. If you have multiple large deployment packages this could take many hours.
Hope that helps someone.
Additionally, if you have shared websites, they will get suspended. There is no way to resume them until the credit period is reset, so you need to delete and recreate them.
From the link below, it seems like bizspark subscribers can use azure for dev/testing and production use. So the $150 monthly recurring credit is usable for both dev/test and production. I am unclear as to if the 120 hour limit applies to bizspark subscribers. There is a mention of the limit to msdn subscribers.
"
If you're with the bizspark program, the benefits page makes no mention of the "no production" or 120 hour detection thing that the regular benefits page does. However, there is still no SLA.
"
http://weblogs.asp.net/scottgu/archive/2013/06/03/windows-azure-announcing-major-improvements-for-dev-test-in-the-cloud.aspx
BizSpark members retain production rights completely. This is detailed in the offer here: http://azure.microsoft.com/en-us/offers/ms-azr-0064p/. It sounds confusing, but the associated BizSpark MSDN account does not have the dev/test restriction.
Key phrase:
In addition, BizSpark members retain production use rights under this Azure benefits offer.
I have a BizSpark startup LLC that I've been using for over 1.5 years just fine on this program including long-running production IaaS VMs.
I have been using BizSpark account for production purposes for our company. We get $150.00 credit per month towards Azure resources consumption. Currently because of some reasons we have enabled spending cap but you can very well remove spending cap and you get charged for whatever you have spent over this $150.00. So if your monthly consumption comes out to be $200.00 for example, you get charged $50.00. As a part of being a BizSpark member you get MSDN subscription as well though I am not sure that you can get 120 hours separately for MSDN subscription than your BizSpark credits.