Last week I had an opportunity to meet many CIOs in “CIO conference” at Microsoft campus. Some of them have already deployed workloads on Windows Azure. In all my discussion, there was a common question on Windows Azure account management. Therefore I decided to write new blog post on Windows Azure account management.
Windows Azure account management is an integrated process involving two portals i.e. Microsoft Online Commerce Portal (MOCP) and Windows Azure Developer Portal (DevPortal).
Microsoft Online Commerce Portal (MOCP) is a Web portal you use to try or buy subscriptions to Microsoft Online Services. Windows Azure Developer Portal (DevPortal) is a web portal you use to create services and deploy your code. A subscription on MOCP is mapped to a project in DevPortal.
Windows Azure buy work flow is below:
1. Determining an “Account Owner”
The Account Owner can create and manage subscription(s), view billing and usage data and specify the “Service Administrator” for each subscription under the account. There can only be one Account Owner Windows Live ID (WLID) per Microsoft Online Customer Service Portal (MOCP) billing account. Each Service Administrator may manage resources in each subscription they are associated with (see Subscriptions and Service Administrators below)
2. Creating multiple MOCP accounts
The Account Owner can at any time create multiple MOCP accounts. A customer may choose to create multiple MOCP accounts in order to design a meaningful account structure that supports or reflects the customer or global business strategy. Some examples where you may need to create multiple MOCP accounts:
- Reflecting your geographic footprint (e.g. Europe, North America, etc.)
- Reflecting your business lines (e.g. Technology Solutions, Consulting, etc.)
- Reflecting your unique customer (e.g. Bank, Retail, MFG, etc.)
3. Subscriptions and “Service Administrators”
For each MOCP account, Owner can create one or more subscriptions. For each subscription, the Account Owner can specify a Service Administrator. This WLID can be the same or different as the Account Owner. The Service Administrator is the user that actually consumes Windows Azure platform services. Only the Account Owner can reassign a subscription’s Service Administrator.
4. Creating multiple subscriptions
The ability to create multiple subscriptions within an account gives you more flexibility in managing your business. Multiple subscriptions may give you the ability to classify your products or services in relevant classifications (e.g. development, testing, production, etc.).
5. “Project” (on the Azure portal) Definition
For each subscription, there is one project, which you can by default create up to 6 hosted services (see Services below) and 5 storage accounts per subscription. A project by default is also limited to 20 compute instances. If you need more than six applications, you can contact Windows Azure Support to request an increase. You can also create additional Windows Azure subscriptions, each of which will allow you to create up to six applications. The compute instances are shared between all the running services in the project (including Production and Staging environments), so you can have multiple services with different number of compute instances, up to the number of maximum available for that project.
6. Services Definition
You can have a total of 6 hosted services per project. The services are space where applications are deployed. Each service provides two environments: Production and Staging. This is visible when you create a service in the Windows Azure portal. A service can have a maximum of five roles per application. This is any combinations of different web and worker roles on the same configuration file up to a maximum of 5. Each role can have any number of virtual machines. See example below:
Figure 1: Standard 3 tier application: Web-Business-Data Tiers to Windows Azure Roles
In the example above, the service has 2 roles, each role with a specific worker role. The Web Role (web tier) takes care of the Web interface. The Worker Role (business tier) is responsible for the business logic. Each role can have any number of virtual machines/cores, to the maximum available on the Project. From a resources perspective, if deployed this service would be using the following resources:
1 x Service:
- Web Role = 3Small Compute Nodes (3 x Small VMs)
- Worker Role = 4 Small Compute Nodes (2 x Medium VMs)
- 2 Roles used
Total resources left on the Project:
- Services (6 -1) = 5
- Small Compute Nodes (20 – 7)= 13 small compute Instances
- Storage accounts = 5
Notes about Services: You will get billed for role resources utilized on a deployed service, even if the roles on those services are not running (i.e., “suspended”). If you don’t want to get charged for a service, you need to delete the deployments associated with the service.

Figure 2: this diagram shows the relationship between all components of account setup process. The current diagram shows the current configuration:
- The components in “blue” are the ones that are upgradable.
- The 20 small computes instances could be any combination of VM sizes so long as the total number of cores across all slots and services within the project does not exceed 20.
7. Business Rules
- Once SA is assigned for a subscription on MOCP.
- AO will have no access to DevPortal
- SA will have no access to billing information in MOCP
- Both the AO and SA can change SA any time
- By default, the account owner is listed as the service administrator.
2. Account owner can buy multiple subscriptions at MOCP.
- Each subscription will result in a project on the DevPortal
- Each subscription can be assigned an SA (May be different for each subscription)
3. Account owner can use credit card or invoice (in some instances) to pay for a subscription.
- AO can buy multiple subscriptions
- Each subscription can be paid using one or more cards or invoice
- Billing details against subscription can be changed any time by AO
4. Qualification for purchase by Invoice
- Minimum account level commitment $500 in USA ($250 outside USA)
- Enhancements coming in mid-June via the MOCP 1.7.1 release
- Enable switching from credit card to invoice if account meets invoice criteria OR customer is flagged as pre-approved.
- Pre-approved customer will be able to sign up for new subscription on invoice
- Customer may be subject to credit check
5. The “Purchase Order No.” input field in the payment options page can be used by customer to identify their subscriptions
6. We are sending notifications to users when they are approaching their offer limits each month (which will reduce surprises)
7. We’ll send daily notifications to customers that reach 75%, 100% and 125% of the amount included in their offer (based on the first meter to hit one of these thresholds).
8. Request a Quota Increase
Please refer to our support page for instructions: http://www.microsoft.com/windowsazure/support/
To process your request, we will need the following information:
- The Subscription ID associated with your service.
- The Windows Live ID associated with the Account Owner of your subscription.
- The resource(s) for which you desire a quota increase.
- Large quota requests may require a credit check, an additional questionnaire filled out and review/approval by our capacity team
9. Team development scenarios
Scenario 1
- Joe has a team of developers to work on a project
- Joe buys subscription using his live id Joe@live.com (AO) and credit card
- Joe assigns SA to a live ID Joe-team@live.com . Credential shared among developers
- Joe is responsible for billing.
- Development team is responsible for creating services and deployment.
Scenario 2
- Joe has two projects that need to be billed to separate cost centers in his company.
- Joe can buy two subscriptions linked to different credit cards or POs.
- Joe will receive two separate monthly billing statements or two entries in his credit card
10. Best Practices
- Only deploy when you are absolutely ready to do so – it is a very expensive operation (1 hour of CPU/instance – no matter how long you use it).
- Staging and Production apps cost the same… don’t assume that you’re not being charged because the app is in staging
- When an application isn’t used – DELETE IT – don’t just suspend it. Suspended apps cost the same as running apps.
- Use the minimal number of VMs – particularly when testing. Fastest way to blow through your hours is to deploy a single app with 20 instances… that deployment just blew away all of your free hours for the month, even if you only had it up for 1 minute. If you don’t have an explicit reason to use multiple instances, don’t.
- Track your usage diligently on MOCP (https://mocp.microsoftonline.com )… but note, it’s 12-24 hours behind in the data that is shown.
- SQL Azure and AppFabric have separate (but linked) dev portals with separate provisioning experiences.
- Consider using the Neudesic cost calculator or our AppFabric calculator for interpreting SQL Azure and AppFabric bills.
11. Windows Azure Support
When some asks you for help, please direct them to the standard support process via one of the links below. This will ensure that the issue is tracked by the team and addressed appropriately. This is very important so we can track the top issue drivers and to ensure that our support process is efficient and painless.
http://www.microsoft.com/windowsazure/support/
To create support tickets you can use the following links directly:
Developer – Work with a Windows Azure platform technical person to troubleshoot development of your application
- https://support.microsoft.com/oas/default.aspx?prid=13496&st=1
Live Site Issue – Report an operational issue with your application or the Windows Azure Portal
- https://support.microsoft.com/oas/default.aspx?prid=13185&st=1
Account Issues – Obtain answers to billing questions and get assistance with managing subscription(s)
- https://mocp-support.custhelp.com/cgi-bin/mocp_support.cfg/php/enduser/ask.php?p_sid=inGOEwXj
Phone Support – If you prefer calling support directly select the relevant support phone number from the page below
- http://go.microsoft.com/fwlink/?LinkId=139808
12. Windows Azure Offer comparision
|
Introductory Special |
Development Accelerator Core |
Development Accelerator Extended |
MSDN Special |
Consumption |
| Windows Azure |
|
|
|
|
|
| Compute |
25 hours (small compute instance) |
750 hours (small compute instance) |
750 hours (small compute instance) |
750 hours (small compute instance) |
$0.12 per hour (small compute instance) |
| Storage |
500 MB of storage |
10 GB of storage |
10 GB of storage |
10 GBs of storage |
$0.15 per GB stored per month |
| Storage Transactions |
10,000 storage transactions |
1,000,000 storage transactions |
1,000,000 storage transactions |
1,000,000 storage transactions |
$0.01 per 10,000 storage transactions |
| SQL Azure |
|
|
|
|
|
| Web databases |
1 Web Edition DBs** ≤ 1 GB RDB |
N/A |
N/A |
3 Web Edition DBs** ≤ 1 GB RDB |
$9.99 per database per month ≤ 1 GB RDB |
| Business databases |
N/A |
N/A |
1 Business Database ≤ 10 GB relational database |
N/A |
$99.99 per database per month ≤ 10 GB RDB |
| AppFabric |
|
|
|
|
|
| Access Control transactions |
100,000 Access Control transactions |
1,000,000 Access Control transactions |
1,000,000 Access Control transactions |
1,000,000 Access Control transactions |
$1.99 per 100,000 transactions* |
| Service Bus connections |
2 Service Bus connections |
1 pack of 5 Service Bus connections |
1 pack of 5 Service Bus connections |
1 pack of 5 Service Bus connections |
$3.99 per connection on a “pay-as-you-go” basis* |
|
|
|
|
|
$9.95 for a pack of 5 connections* |
|
|
|
|
|
$49.75 for a pack of 25 connections* |
|
|
|
|
|
$199.00 for a pack of 100 connections* |
|
|
|
|
|
$995.00 for a pack of 500 connections* |
| Data Transfers (per Region)*** |
|
|
|
|
| North America and Europe |
.5 GB in / .5 GB out |
7 GB in / 14 GB out |
7 GB in / 14 GB out |
7 GB in / 14 GB out |
$0.10 per GB in / $0.15 per GB out |
| Asia Pacific |
.5 GB in / .5 GB out |
2.5 GB in / 5 GB out |
2.5 GB in / 5 GB out |
2.5 GB in / 5 GB out |
$0.30 per GB in / $0.45 per GB out |
| Commitment Term |
|
|
|
|
|
|
N/A |
6 months |
6 months |
N/A |
N/A |
| Savings |
|
|
|
|
|
|
N/A |
Represents 54% off normal consumption rates |
Represents 52% off normal consumption rates |
Includes 5% discount on overage |
N/A |
| Base Unit Price |
|
|
|
|
|
|
No Charge |
$59.95 |
$109.95 |
No Charge for MSDN members |
Pay as you go |
|
|
|
|
|
|
| *AppFabric rates are effective for usage beginning on April 9, 2010 at 12:00 AM GMT. All usage for AppFabric prior to this date will not be charged. |
|
|
| **Web db is for first 3 months. Any usage in excess of the amount included with the subscription will be charged at the standard rates. This introductory special will end on June 30, 2010 and all usage will then be charged at the standard rates. |
| ***Inbound data transfers during off-peak times through June 30, 2010 are at no charge. Prices revert to our normal inbound data transfer rates after June 30, 2010. |
|
|
| NOTE: MPN prices are 5% less on all items except storage and data transfers. |
|
|
|