FAQ

How does the Billing Model work?

Publishers will be billed on the Azure Subscription that they provided to do they deployments, they will have to pay for all running test drive instances, and for all resources that are included under "Test Drive Solution's Azure ARM Deployment Template" for those test drive instances, up to the limits that they specified in "Deployment Regions", "Maximum Number of Concurrent Instances", "Number of Hot Instances" and "Number of Warm Sessions".

These are all possible kinds of running test drive instances:

• [H-] Hot and unassigned
• [W-] Warm and unassigned
• [HA] Hot and assigned
• [WA] Warm and assigned
• [CA] Cold and assigned

For "Warm" test drive instances, there are two scenarios:

• [W-] - The publisher will have to pay full price for all resources except for VMs. For VMs, these will be put in Stopped state and the publisher will only have to pay for the price that costs to keep VMs in Stopped state.
• [WA] - The publisher will have to pay full price for all resources, because when a test drive is assigned to the user, the VM is in Running state.

The benefit of the "Warm" test drive instance is that the publisher pays full price for running VMs only when the they are assigned to a user.