Embed Size (px)
Citation preview
• Benefit overview• Getting started• Activating the monetary credit Azure subscription• Activating the dev/test PAYG Azure subscription• Adding the benefit to an existing Azure account• Common activation errors• Using the benefit• Managing the benefit• Getting help• Frequently asked questions
Azure is an open and flexible cloud platform that enables you to quickly build, deploy and manage applications across a global network of Microsoft-managed datacenters.
You can build applications using any language, tool or framework.
And you can integrate your public cloud applications with your existing IT environment.
1
2
$50PER MONTH
VS Pro w/MSDNVS Test Pro w/MSDN
$100PER MONTH
VS Premium w/MSDNMSDN Platforms
$150PER MONTH
VS Ultimate w/MSDN
1 Credit cannot be used for any Visual Studio Online service (ex. user plans, Build, Load Testing, and future services), Azure Store, Support contracts, 3rd party VMs (SAP, Oracle, etc.).2 Excludes Windows client and Windows Server. MSDN subscribers can run Windows Server or Windows client VMs where these are offered but must pay the fees associated with running these VMs since Windows Server and Windows client are not included as part of MSDN cloud use rights.
Dev/Test subscription with monthly credit Dev/Test PAYG subscription
OverviewSubscription with up to $150 per month to use on any
service for dev/testPAYG subscription specifically designed for dev/test
When to useDesigned for individuals
Enables you to try out Azure and run small projects
Designed for teams
Enables you to separate out projects into different Azure
subscriptions
# of subscriptions
per subscriberOne Unlimited
Payment requiredCredit card or invoicing required for usage beyond the
creditCredit card or invoicing required
Features
Discounted dev/test rates
Cloud use rights for MSDN software*
MSDN image gallery
Discounted dev/test rates
Cloud use rights for MSDN software*
MSDN image gallery
* Excludes Windows client and Windows Server. MSDN subscribers can run Windows Server or Windows client VMs where these are offered but must pay the fees associated with running these VMs since Windows Server and Windows client are not included as part of MSDN cloud use rights.
$100PER MONTH
VS Premium w/MSDNMSDN Platforms
1. Determine whether it makes sense for your business to set a policy for which kind of user account should be used to activate the benefit• Organizational account is an account created by an organization’s administrator to enable a member of
the organization to access to all Microsoft cloud services such as Microsoft Azure, Windows Intune or Office 365. An Organizational account can take the form of a user’s organizational email address, such as [email protected], when an organization federates or synchronizes its Active Directory accounts with Azure Active Directory.
• Microsoft account is an account created by a user and not connected to an organization. The Microsoft account is the combination of an email address and a password that a user uses to sign in to all consumer-oriented Microsoft products and cloud services such as Outlook (Hotmail), Messenger, OneDrive, MSN, Windows Phone or Xbox LIVE, as well as MSDN subscriptions. If your user already has an activated MSDN subscription, then they already have a Microsoft account set up.
We encourage you to consider establishing an internal policy for using
Organizational accounts if you answer yes to either of the following questions:• Do you want to transfer benefits between different employees of the same organization, like when
employee's change roles or leave the company?
• Are you concerned about business risk if a subscriber leaves your company?
2. Once a policy has been determined, verify the following have been completed: • Subscriber Downloads must be assigned to the user in VLSC.
• The user must have activated their subscription on the MSDN subscriptions portal.
3. Check to see whether the user has set up the EA Azure subscription with the same ID associated with the MSDN subscription.• If the user has already associated an EA Azure subscription with the same ID they will use to activate the MSDN
benefit, they will receive an error message when attempting to set up either the monetary credit subscription or MSDN Azure PAYG subscription. The subscriber can still take advantage of their MSDN benefits by following one of these workarounds.
4. The user is now able to start the activation process. Note: • The user have a phone number that can receive either a text message or a phone call – this is part of the
activation verification process.
• No credit card is required to activate the Azure subscription with the monetary credit and the spending limit is automatically set to $0, so no surprise charges.
• A credit card or invoice is required to set up the dev/test PAYG subscription.
4. Once activated:• The subscriber can add other MSDN subscribers within their organization to their Azure subscription.
• The monetary credit resets every 30 days and any remaining balance does not carry over.
• Monetary credits cannot be pooled.
Activating the Azure subscription with the monthly credit
MSDN subscribers receive up to $150 per month to use on any Azure service they want for dev/test
Additional resources:• http://aka.ms/msdn_activatevideo for a
step-by-step tutorial for activating the Azure benefit with a Microsoft account
The user will need to read the sign in page to determine which account type the login is for. In this case, the login screen is for Microsoft account.
The user can switch the sign in page if they’re using the other type of account. In this case, they can switch to sign in with their organizational account.
Designed for teams
Enables you to separate out projects into
different Azure subscriptions
The user will need to read the sign in page to determine which account type the login is for. In this case, the login screen is for Microsoft account.
The user can switch the sign in page if they’re using the other type of account. In this case, they can switch to sign in with their organizational account.
• Does the existing Azure account have an EA subscription associated with it? If yes:• The system is designed in such a way that an EA Azure subscription and a MSDN Azure subscription cannot associated to the
same Azure account.
• See the EA activation error section for workarounds.
• Does the Microsoft account used for their Azure account match the Microsoft account used for their MSDN subscription? If yes:• Activate the Azure MSDN benefit using that Microsoft account.
• Is the Microsoft account used for their Azure account different than Microsoft account used for their MSDN subscription? If yes:• Activate the Azure MSDN benefit.
• Once set up, contact Azure support to have the subscription transferred under the other Microsoft account.
• Is an organizational account used for the existing Azure account? If yes:• The user will need to link an Organizational account, then can move forward with activating the benefit under that same account.
1. Did you link your organizational account or is an incorrect Microsoft account displayed? a) If you see an incorrect account, click on the down arrow and select Sign Out.
b) You will land on the Microsoft Azure account portal. Click on Sign In.
c) On the login screen, use the Microsoft account associated with your MSDN subscription. OR if you linked your organizational account to Azure, switch to the organizational account login screen and log in.
…Or switch to the organizational account sign in page if you set up your Azure benefit with an organizational account
Log in here with the Microsoft accountassociated with your MSDN subscription….
Does the correct ID display here? If not, sign out.
2. If the account is correct, do you see Microsoft Azure listed as a benefit on the My Account portal? • To check, log into the MSDN My Account portal. If Microsoft Azure is not listed, please contact your MSDN administrator to
enable Software Downloads as this is a requirement to be able to access your Azure benefit.
• If you do not have access to the MSDN My Account portal, please contact your MSDN administrator.
• Cause: there is already an Azure EA subscription associated with the Azure account. The system is designed in such a way that an EA Azure subscription and a MSDN Azure subscription cannot associated to the same Azure account.
• Workaround: • Option 1: Set up a new Microsoft account
1. Create a pay-as-you-go Azure subscription using a new Microsoft account. Do this by going to http://aka.ms/azuretrial and setting up a free trial. Step by step instructions are available in the appendix.
2. Contact Azure billing support and ask them to convert the PAYG subscription to your MSDN Azure benefit. Support information is available at http://azure.microsoft.com/support - just click on Get Support (and make sure you’re logged into your new Microsoft account so you can see the options).
3. Once the conversion has been performed, you can access your MSDN Azure benefit on this new Microsoft account.
• Option 2: Link the Azure benefit to your Organizational account, assuming it’s not being used for the EA Azure subscription
1. Step by step instructions
2. Complete instructions on linking Organizational accounts are available at http://aka.ms/msdnorgacct.
Once the benefit is activated, the subscriber can get started right away with using Azure - remember to log in with the Microsoft or Organizational account used to set up the Azure benefit.
• Azure management portal: https://manage.windowsazure.com• Use and disable Azure services – spin up VM’s, set up databases, etc
• Check the remaining balance on your monthly monetary credit.
• Add co-administrators
• Account dashboard: https://account.windowsazure.com• View the Azure subscriptions set up under the account
• Add new Azure subscriptions, including pay-as-you-go and MSDN dev/test pay-as-you-go subscriptions
• Check the remaining balance on your monthly monetary credit
• Check out the current charges on your MSDN dev/test subscriptions
• Remove the spending limit off of the Azure subscription with the monetary credit
• Change the payment method
Many resources are available to learn more about using Azure, including:• Video: http://aka.ms/msdn_spinupVM
• Training: http://www.microsoftvirtualacademy.com/product-training/microsoft-azure
• Documentation: http://azure.microsoft.com/documentation
• Events: http://azure.microsoft.com/community/events
• Dear Azure Q&A: http://www.dearazure.com
• Azure Friday: http://azure.microsoft.com/documentation/videos/azure-friday
• Microsoft Azure blog: http://azure.microsoft.com/blog
• MSDN Magazine: http://msdn.microsoft.com/magazine
• Twitter: @Azure & @VisualStudio
• Facebook: https://www.facebook.com/microsoftazure & https://www.facebook.com/visualstudio
• There is no central portal to manage MSDN Azure subscriptions • Setting an internal policy to use Organizational accounts to activate the benefit will enable you to transfer Azure subscriptions
between subscribers as employee’s move in and out of your organization. For more details, see Getting Started.
• To track usage of your subscribers and ensure no surprise charges:• Add a co-administrator to the subscriber’s Azure account - they will be able to log in and check usage. Note, if this person will
also be taking advantage of the Azure services, discounts, etc included with the subscription, they must also be an MSDN subscriber.
• Set up a company usage guidelines – for instance:
• Subscription with monthly credit: no spending beyond the monthly credit, controlled by leaving the $0 spending limit in place.
• Dev/Test PAYG subscription: Type of payment method to use (corporate card, personal credit card, invoice, etc) and how much can be spent each month.
1. The user with the Azure subscription signs into the Azure Management portal at http://manage.windowsazure.com.
2. On the navigation pane on the left, click Settings (you may need to use the scroll bar to locate Settings).
3. Click Administrators from the top navigation pane.
4. Click Add from the lower navigation pane.
5. Type in the new co-admin’s email address, select the subscription(s) you want the user to access, and then click the check mark.
6. A confirmation message will display.
7. The co-admin will now be able to access the subscription by logging in with their Microsoft account.
2
3
4
5
6
Option 1: Use your MSDN professional technical support benefitDepending on the MSDN subscription level, subscribers receive 2-4 professional technical support incidents as a benefit.
1. Set up your MSDN Technical Support contract, if you haven’t already: http://aka.ms/msdn-techsupport.
2. Submit your Azure incident online at http://azure.microsoft.com/support:1. Select Get Support.
2. Select Microsoft Professional Contract Support.
3. Describe your issue using the form, then click Continue.
4. Select the Professional Support Contract or enter your Access and Contract ID’s and click Add.
1
2
3
4
Option 2: Use your MSDN Forum Priority Support benefitMSDN subscribers receive unlimited priority support in select MSDN Forums. A Microsoft engineer will respond within 2 business days to your posting if the community hasn't already provided the answer.
1. Go to http://aka.ms/priorityforums.
2. Review the supported forums, and select the relevant forum for the issue (note: this is not a comprehensive list of all available forums, however is a list of forums where MSDN subscribers receive priority support).
3. You will be routed to the selected Azure forum. Search to see if there is an existing question.
4. If no solution is found, submit your own question.
2
34
Billing support is available at no cost; an MSDN Technical Support contract is not needed.1. Submit your Azure incident online at http://azure.microsoft.com/support.
1. Select Get Support.
2. Select the MSDN Azure subscription from the drop down and verify the additional fields are correct.
3. Click on the check mark next to ‘CREATE TICKET’.
4. Select the problem type and category, the click Continue.
5. Fill out the contact information and click Continue.
6. Provide a description of the problem, then select severity and contact preference. Click Submit.
1
3
2
4
5
6
• How do I know how much credit I have remaining for the month?• There’s a ‘credit status’ bar at the top of the management portal (http://manage.windowsazure.com). Click on it to see how much
remains and when it will reset. You can also log into the account portal for the same information.
• What happens when I hit the monetary cap for the month?• Your subscription will be stopped until your subscription anniversary date (the day the monetary credit resets), or until you
remove the monetary cap and add a pay instrument.
• Do co-administrators need to be MSDN subscribers?• The deeply discounted development and test rates that are part of the MSDN benefits require every account owner and co-
administrator to be MSDN subscribers.
• My organization has multiple MSDN subscribers. Can their Azure credits be pooled? • Credit pooling is not available, as the benefit is designed for individual subscriber usage.
• My organization decided to standardize using Organizational accounts for the Azure benefit, however I already set it up using my Microsoft account. What do I do?• Contact Microsoft Azure Billing Support at http://www.windowsazure.com/support to have the account changed.
• If the MSDN subscription is deleted (user changed role, left company, etc…) what is Microsoft’s process for removing the VMs that the subscriber had in Azure?• Organizational account: when a user leaves the company, an admin of the Azure Active Directory can take over those
subscriptions (and the contained VMs) and the user can no longer sign-in. More information is available at http://aka.ms/msdnorgacct.
• Microsoft account: the account admin (the person who set up the benefit) needs to contact Microsoft Azure Billing Support at http://www.windowsazure.com/support and request an account transfer to a different Microsoft account or Organizational account. The account admin needs to agree to the ownership transfer. If the admin no longer has an active email address, thensomeone within the company must contact Microsoft Azure Billing Support for the transfer.
• Can the MSDN administrator assign Subscriber Downloads without the Azure benefit to the subscriber?• No, the Azure benefit is tied to enabling Subscriber Downloads.
• Can the MSDN administrator assign the Azure benefit without Subscriber Downloads to the subscriber?• No, Subscriber Downloads must also be enabled. A current workaround for enabling Azure without providing Subscriber
Downloads is to:
• Enable Subscriber Downloads via the VLSC portal.
• Have the user activate their MSDN subscription and immediately activate Azure.
• Upon their confirmation that Azure has been activated, remove Subscriber Downloads access via the VLSC portal.
• Can my MSDN subscribers run Windows client under our Azure EA agreement?• No, Windows client can only be run in MSDN Azure subscriptions.
• Are there any limitations on what the monthly credit can be used for?• The monthly credits do not apply to: Visual Studio Online services, 3rd party VMs, support contracts, or Azure Store purchases.
• What happens to the subscriber’s MSDN Azure subscription when they try to run a 3rd party VM?
• If the subscriber removed the spending limit then charges will be incurred on the payment method on file.
• If the subscriber has not removed their spending limit (i.e. it’s set to $0), then the Azure subscription and all services are shut down until the monthly credit resets on the billing anniversary date.
• What’s the process to administer organizational accounts to eligible organizational members?• The administrator signs up as an organization to a Microsoft cloud service such as Microsoft Azure, Windows Intune or Office
365.
• A cloud based tenant is provisioned automatically in Azure Active Directory to represent the organization.
• Once this tenant has been provisioned, the administrator issues Organizational accounts to each one of its members.
• More information is available at http://azure.microsoft.com/documentation/services/active-directory.
• When should I have my users use the Azure EA subscription or their MSDN Azure subscriptions?
Azure MSDN benefit Azure EA
Do not want to enter credit card or set up separate invoicingMonetary subscription if
stay under the credit•
Running a large project and want to charge against the EA •
Want users within the org to try out Azure on a small scale •
Centrally manage utilization, balances, and overages •
Usage reporting •
• Is there a way to restrict what a subscriber deploys to their MSDN Azure subscription?• No, there is no way to restrict this. We recommend adding a co-administrator to the account if this is an area of concern; they will
be able to see what the subscription is being used for.
• Is there a way to restrict the VM’s accessible to subscribers in Azure?• No, we recommend adding a co-administrator to the account if this is an area of concern; they will be able to see what the
subscription is being used for.
• Can an organization pool the payment (for PAYG or monetary credit subscription) into one bill? • Pooled billing is not available. Each subscriber can set up invoicing, and have a centralized source within their organization pay
the invoice. However, the individual subscriber is still liable for the bill if it goes unpaid. More information on invoicing is available here.
• How do I set up invoicing to pay for the costs incurred on MSDN Azure subscriptions?• You can set up invoicing for each subscriber by following the process outlined on http://azure.microsoft.com/pricing/invoicing.
Note this invoicing is not connected to EA Azure agreements, but is paid separately.
• Can the MSDN admin activate the Azure benefit on behalf of their subscribers? Or activate in bulk?• No, the Azure benefit must be activated by the individual subscriber. The following steps need to be taken:
• MSDN admin assigns a subscription to user in VLSC. Note: Subscriber Downloads must be enabled to enable the Azure benefit.
• User activates their MSDN subscription.
• Subscriber activates their MSDN benefit. As part of this process, they'll need pass the mobile verification and accept the terms of use.
• Can an enterprise customer who uses an SCE or other enterprise agreement for Azure commitments get blanket coverage for the T&Cs for MSDN-based Azure?• No, each individual subscriber must accept the Azure T&C’s during the benefit activation process.
2
1
3
4
