Book Image

Building Hybrid Clouds with Azure Stack

Book Image

Building Hybrid Clouds with Azure Stack

Overview of this book

Azure Stack is all about creating fewer gaps between on-premise and public cloud application deployment. Azure Stack is the logical progression of Microsoft Cloud Services to create a true hybrid cloud-ready application. This book provides an introduction to Azure Stack and the cloud-first approach. Starting with an introduction to the architecture of Azure Stack, the book will help you plan and deploy your Azure Stack. Next, you will learn about the network and storage options in Azure Stack and you'll create your own private cloud solution. Finally, you will understand how to integrate public cloud using the third-party resource provider. After reading the book, you will have a good understanding of the end-to-end process of designing, offering, and supporting cloud solutions for enterprises or service providers.
Table of Contents (19 chapters)
Title Page
Credits
About the Authors
About the Reviewer
www.PacktPub.com
Customer Feedback
Preface

Billing with Azure Stack


Finally, as we all need to make money with our data center solution, another important concept is how to handle the billing: pay per use or pay per ordered resource? Depending on your business model and your customer, the answer is always, "it depends."

If you are acting as a service provider with customers who want to control their costs by powering their resources on or off, the pay per use model is the best. If you have customers who need to plan their budget, pay per ordered resource is the best.

Both these models are basically possible with Azure Stack licensing itself, because you could pay for your license per use (like with Azure) or pay per yearly buyout, which means you could just set a price per resource, and if you order it, you will need to pay for it whether it is online or offline.

So as you can see, both solutions are fine and you could also cover the licenses for Microsoft with them.

The next question is, how we could count the used resources automatically...