Chris Houdeshell

Azure Stack Technical Preview 1 - Thoughts
Jan 28, 2016
2 minutes read

On Tuesday, Microsoft announced that the first Technical Preview of Azure Stack will be available Friday, January 29. Like many others, I’ve already provisioned a machine. The thought of true private-public hybrid cloud excites me. While information is currently limited, here are my thoughts before the release.

  • Working for a small business, costs are always a concern. While the cloud enables us to provision outside of our data center and respond to change quickly, fluid costs limit the full potential of us using the cloud. Hopefully, Russinovich and Snover cover licensing early, allowing small business to budget for Azure Stack and bring more of a fixed cost to the (hybrid) cloud.
  • DocumentDB should be delivered early in the Technical Preview cadence. DocumentDB is one of few Azure services that doesn’t have a great on-premise alternative. While this may be due to the .NET-isms native to DocumentDB, releasing an early Azure Stack version, Microsoft will finally erase one of DocumentDB’s few downsides.
  • Azure Active Directory B2C. With Microsoft pounding nail after nail into AD ACS’ coffin and officially deprecating it, an on-premise alternative is needed. It is a given that Azure Stack TP1 will include at least some AD integration, due to the portal relying on AD ACLs.
  • Early Azure fail-over/scale-out. Azure Resource Manager templates are the currently touted orchestration tool for Azure. I hope Azure Stack can automatically produce these templates and deploy a copy of the resource group to Azure in case of a local failure or for hybrid cloud scale-out.

Back to posts