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.
Related
I am not sure if I understand how this works and if I could accidentally be charged if I do this?
I want to play around with Azure just for myself, deploy a web app, learn how it works.
I have an old Visual Studio subscription that I got years ago from a company I used to work at.
This subscription is old and disabled now, expired. I have an option to convert it into pay-as-you-go subscription. When I try to do that, it is asking for my credit card. I don't want to use any paid services, I just want to play with a basic free service plan (I believe it is called F1).
If I provide my credit card and convert that subscription to "pay-as-you-go", it is not going to charge me right away for something? I am not very familiar how this works. Thank you.
I am using the pay as you go plan and it required a credit card to subscribe.
It is possible to use the Azure subscription without paying as long as you use the F1 (Free) service plan for any of the services you use.
Once you start using the Basic, Standard or Premium plans, then you will be billed monthly to those services, and almost all those paid plan costs accumulate hourly.
It is possible to use the non-free services as well and use almost nothing as long as you remove the resources soon after use. As with any service, please do check the pricing to ensure you don't use a service longer than is needed.
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.
I am new to Azure. I have create Azure free account.
I like to migrate production database to Azure Cloud, and found Managed Instance as perfect choice (as per documentation). Before migration i want test it out, but not sure if this service is free or not.
It shows Subscription as Free Trial and
in Pricing Tier section it shows 16vCore and 32GB Storage selected.
So, my question is that - will i be charged if i create SQL Server Managed Instance in trail period?
While using the trial period your credit card won't be charged. When the trial ends, if the product is still in Preview, you will enjoy that it cost half the price. At the time of GA it will have its full price.
While you use it with the trial account, you may noticed that you cannot create a managed instance in all regions where is currently available. That is normal while you are using the trial/evaluation account.
If you are wrongly charged for any reason, create a billing support ticket which is free. You can also create a billing support ticket to confirm the information here provided.
I just activated my Visual Studio Professional with MSDN and it is telling me now that I have $200 to spend,
my question is:
is this will take $200 from my credit card after the month is over, or this is an offer, and can I use and rely on windows azure using these $200 monthly or this is a limited time offer and will expire after few months? if it is limited so I can't transfer my live websites on azure.
The information provided by #hhaggan is off a bit. If you read this page containing the benefits details for Visual Studio Professional with MSDN, you'll see the following:
For the first month after activation of your benefit, you receive $200
of Windows Azure credits. After the first month, you receive $50 of
Windows Azure credits every month
So it's not a continued $200 monthly.
I couldn't tell if you're intending to use your MSDN Azure benefit for dev/test or production. These Azure credits are for dev/test purposes, and not for production, as documented on the abovementioned web page. Under Use Rights:
Windows Azure MSDN benefit is intended for development and test
purposes. We reserve the right to suspend any instance (VM or cloud
service) that runs continuously for more than 120 hours or if we
determine that the instance is being used for production. Production
workloads must be run on regular subscriptions.
The MSDN Subscriber will have free of charge Windows Azure account that worth 200$ per month. it all depends on your usage, you can use all the resources in one day, one week or even with the best consumption use your resources for the whole month, however if you exceed the limit it will not charge you. the Credit card used here is mainly to provide a guaranteed identity. the offer should be for the whole year of subscription.
I hope this helps you let me know if you need anything else.
Our company has until bought a lot VS Pro/Premium and Ultimate Licenses, and each includes a free Azure Account.
At the Azure Info day we have been told the best way would be to bundle them into one big account
(there is just too much overhead if every developer here would register that account on his own).
Do you know how to do this ?
Is there a special account manager we should contact ?
Thanks in advance,
Mathias Held
Each MSDN subscription has its own Windows Azure subscription with a given number of resources allocated per month. Those resources cannot be combined. For example, if you have 10 developers with MSDN Ultimate subscriptions, each with 1,500 Compute hours per month, you can NOT combine them into a single account with 15,000 Compute hours.
Regarding too much overhead: The task of enabling Windows Azure resources is incredibly simple. In fact, if you go to the new Windows Azure portal and sign in with the Live ID associated with your MSDN account, the portal will recognize that there's an associated Windows Azure subscription.
If your concern is that an individual dev won't have enough Windows Azure Compute resources monthly, this is more of an educational issue. At 1,500 monthly Compute hours (and Extra Small instances running at 1/3 Compute Hour), you have enough resources to run 2 Small instances 24x7 (or 6 Extra Small). The prudent advice is to delete all deployments when not in use (e.g. after work hours or between test deployments). This will give you much more breathing room and let you run much larger VM sizes without risk of going over allotted resources.