Introducing Microsoft Azure Stack

[Introducing Microsoft Azure Stack] >> Hello, thank you for joining us. Glad you could make it. My name is Mark Russinovich. [Jeffrey Snover CHIEF ARCHITECT, ENTERPRISE CLOUD Mark Russinovich CTO, MICROSOFT AZURE] I'm CTO of Microsoft Azure. [Jeffrey Snover CHIEF ARCHITECT, ENTERPRISE CLOUD Mark Russinovich CTO, MICROSOFT AZURE] >> Male: And howdy, I'm Jeffrey Snover, [Jeffrey Snover CHIEF ARCHITECT, ENTERPRISE CLOUD Mark Russinovich CTO, MICROSOFT AZURE] I'm the Chief Architect of the Enterprise Cloud group. So I'm all things enterprise, infrastructure, and IT. [Jeffrey Snover CHIEF ARCHITECT, ENTERPRISE CLOUD] And we're so glad you could join us in our webcast today. Unlike our road shows in the past or industry shows, you don't have to travel long distance to get this great information. And today, Mark and I are gonna talk about a number of topics that we're very passionate about, in particular around business transformation, new applications enabled by the cloud. And in particular, we're gonna focus in on the hybrid cloud and how the hybrid cloud is able to bring you the full realization of the cloud, bringing the power of the cloud to your datacenters. >> So speaking of not having to travel, [Mark Russinovich CTO, MICROSOFT AZURE] Jeffrey and I have been doing a ton of travel over the last year. [Mark Russinovich CTO, MICROSOFT AZURE] We've been going around the world for Azure road shows [Mark Russinovich CTO, MICROSOFT AZURE] and a whole bunch of other events. And while we both really enjoy travel, we get to meet new people, we get to experience different cultures, there are some challenges when it comes to travel, for example, time zone differences. I've several times almost missed a meeting because I'm thrown off by time zone difference. Or signage that we don't understand, different languages that are spoken, even having to drive on the different side of the road, for example. >> You almost said wrong. >> Yeah, wrong for my... >> Now, didn't you have an issue in London with water or something, what's that? >> Yeah, there was... There was one time I was desperately thirsty, so I go into a shop to get some water, pull up a few bottles, I take it to the counter and I give the guy my American Express card. He says they don't accept that. So then I pull out my Visa card, and that gets declined after a few minutes because apparently, I'm traveling and so it's raised some kind of flag. So all I have are dollar bills and I pull those out hoping he'll accept those, and it's no deal, so... >> No water for you. >> No water for me. >> Well, you know, that's the thing, you know, when you're doing this travel, you're trying to accomplish some objective, right? You're trying to meet with some people, you're trying to conduct some business, you're trying to do something. And often, these frictions, these, you know, things that are incidental to that really kind of get in your way of transacting and meeting your objective. >> Yeah, so wouldn't it be great if when you traveled, you could have a consistent experience for all these things that are mostly just getting in the way and not really enriching the time that you're spending or letting you meet your objectives? If you could have a consistent currency everywhere, if there was no time zone difference, if the signs were all in the language that you natively speak, then you could accomplish a lot more a lot more quickly, a lot more efficiently, and really enjoy the travel that you're doing. >> Yeah, so as Mark and I discussed this, we realized that these differences in travel [Enterprise, Dedicated infrastructure for each application] and differences in countries is very similar to the differences we see in enterprises. [Enterprise, Purpose-built hardware] And this is perfectly natural because in the past [Enterprise, Distinct infrastructure and operations teams] what we would do is we'd give you a set of components [Enterprise, Customized processes and configurations] and then you'd have to take those components to deliver your custom application, right? And so what ends up happening is you end up with custom infrastructure, custom hardware, custom people, and custom processes, all to deliver some application. And each group ends up with their own enterprise-specific language or even group-specific language and what you find is that that makes you a little less agile than you need to be. So in particular, if you want to hire in some talent, it makes it hard to hire in that talent because they're not... It takes them a while to come up to speed or get trained. If you need some excess capacity or new capacity to run your application, it makes it very difficult to get additional capabilities from your partners because they have a custom design of their own. And so too, if you have some excess capacity, it's hard to lend that to another team because it's very custom to your application. So effectively, it's very static and very brittle. It's not agile enough. [Cloud, Loosely coupled apps and micro-services] So we believe that the cloud is a model, the cloud is not a location. [Cloud, Industry-standard hardware] >> So what has really driven the agility of the cloud? [Cloud, Service-focused DevOps teams] For one, it is loosely coupled apps and micro-services. [Cloud, Standardized processes and configurations] The ability to create applications very quickly and evolve them very quickly to meet ongoing business demands as opposed to the old monolithic style of traditional IT applications. [Cloud] Another one is consistent hardware. [Cloud] So the environment is very elastic and applications can grow [Cloud] and shrink and consume the resources that other applications were using [Cloud] a minute earlier for maximum efficiency. [Cloud] Then there's of course service-focused DevOps [Cloud] which is required for that agile application delivery. Those applications that are being updated frequently need to be operated and monitored by the people developing them so they can quickly react to changes, react to problems in the application and get them updated. [Cloud] And then finally, you need standard processes and configuration. [Cloud] You need automation to be able to run quickly [Cloud] and at large scale as the way the cloud providers do. [Cloud] >> Yes, so make no mistake about it. The cloud is the natural evolution of computing. It is our future. And many of you are already embracing that to some degree today. A number of you are embracing something Gartner calls Bimodal IT where you have existing systems that stay as they are and then you're adopting some flavor of fast self-service delivery. We can do this. So we want you to be the change agent in your organization to drive and lead your organization to the cloud and we're gonna help you do that. And so Microsoft has been on this journey for the cloud for quite a long time and with our hyperscale datacenters. And so we can help you shortcut some of those lessons. >> So I'll briefly talk a little bit about [Microsoft Azure] Microsoft Azure, [Microsoft Azure] Microsoft's own hyperscale cloud platform which has been incredibly successful. [Microsoft Azure] In terms of adoption, [Azure Momentum, > 90,000 New Azure customer subscriptions/month] we've got numbers to show the kind of scale that we've gotten to. [Azure Momentum, > 1.4 Million SQL Databases running on Azure] For example, 500 million users in our Azure Active Directory identity service, [Azure Momentum, > 500 Million Users in Azure Active Directory] we're ingesting more than 1.5 trillion events per month in our IoT event ingestion system. >> Was that with a T or B? Trillion? >> T. Trillion. >> Trillion. [Azure Momentum] >> We've got over 777 trillion transactions per day [Azure Momentum] in our Azure storage system. So these numbers are just monstrous and we can only achieve that through all of those standard ways of operating in the microservices type of applications that we've been talking about. But most importantly, we're running our own businesses on top of Microsoft Azure. We're running Skype, we're running Bing, we're running Xbox, we're running Office 365 on top of Azure. >> Yeah, that's amazing stuff. [Enterprise Microsoft Azure] But clearly, we know having talked to you that not all businesses [Enterprise Microsoft Azure] are ready for 100 percent pure public cloud play. [Enterprise Microsoft Azure] And so we want to do, you know, [Enterprise Microsoft Azure] is we realize that a one size fits all approach isn't gonna work for everyone. So we want to enable the cloud on your terms and it's time for us to bring the cloud to you [Microsoft Azure Stack Power of Azure in your datacenter] directly into your datacenters. [Microsoft Azure Stack Power of Azure in your datacenter] >> And that's exactly what Microsoft Azure Stack's all about. [Microsoft Azure Stack Power of Azure in your datacenter] It's about bringing the consistency of the hyperscale public cloud Azure platform to your own datacenter, about enabling your developers to create the applications that will run in both places unchanged, about enabling your end users to interact with those applications in the same way in both environments. It is literally the first hybrid cloud platform product on the market and the only one that brings hyperscale public cloud environment to your own datacenter. But before we talk about what it is, let's talk about why we decided it was so important to create it for you. >> The answer's really quite simple. And the answer is, you told us to. [The case for hybrid cloud platform, Business requirements] We spent a lot of time talking to you and finding out about your needs [The case for hybrid cloud platform, Application flexibility] and you were the ones that told us that you really wanted the power of Azure, [The case for hybrid cloud platform, Inadequate alternatives] but you wanted Azure running in your datacenter. [The case for hybrid cloud platform] So there are a number of reasons for this. First is around business concerns. A number of people were concerned about things like data sovereignty, some people were in regulated industries, some people were concerned about the latency and control they'd have. [The case for hybrid cloud platform] >> One of the things that we've heard customers asking us [The case for hybrid cloud platform] for several years now is wouldn't it be great if we could just choose to embrace modern native cloud application development and then have those applications land wherever they needed to be according to the business requirements? >> And then also a lot of people are concerned, you know, they're basically finding [The case for hybrid cloud platform] that the alternatives are inadequate. [The case for hybrid cloud platform] >> Yeah. [The case for hybrid cloud platform] Take AWS, for example, a hyperscale public cloud, but with no focus on bringing that consistency to on-premises. So no compatibility for APIs or environment or developers or end user experience for on-premises offered by them. >> Right, like OpenStack. OpenStack is very complex, it's a highly fragmented ecosystem and then lastly, there's VMware and their virtualization model. And virtualization is great, virtualization provides meaningful cost optimization for the traditional way, you know, traditional applications. It's a very good model. However, it is not the basis for cloud-first applications, that's not the right mindset, etcetera. So Mark and I are committed to this cloud-first mindset and so we're working together to bring the power of Azure and making sure that it runs on your hardware in your datacenter. >> So ultimately we've recognized that every company's gonna go through a cloud transformation at a different pace, at their own pace, that's driven by their own business needs and requirements. And we want to be there to support you whether you're gonna go to the cloud in one year, two years, five years, ten years, or whether you're gonna remain with one foot on-prem and one foot in the cloud indefinitely. >> Yeah. I got to say, that's one of the things I love working at Microsoft is we have, we're gonna help the customer no matter what they want to do. You know, some of our competitors, all they have is a public cloud, so they go around badmouthing the private cloud, trying to make people feel bad about their business concerns, about why they want to be on the private cloud. Other people, all they have is the private cloud, so they go around badmouthing and trying to do scare tactics around the public cloud. >> Or CloudWatch their private cloud. >> Yeah, exactly. And so it's so great that, you know, we don't have a dog in this fight. You know, we know that both of these make sense for customers and we're gonna help you pick whichever makes sense for you at whatever time and another thing I love about our play is that it's okay if customers are wrong, you know, you don't always have perfect foresight. So you could say, "Hey, we're gonna start off conservative, do it in the private cloud on premises." And then when you say, "Oh, you know, why am I being so conservative?" You can transform to the public cloud or vice versa, if you've done it in the public cloud and decide you want to bring it on-premises. So I think we've got a great position there. It's one of the things I love about what we're doing here. >> Yeah, really helping the customer. >> Absolutely. Yeah, right, it's customer focused. Yeah. >> So imagine the things you can do [Imagine the app innovation possibilities] with this consistent environment from an application perspective. [Imagine the app innovation possibilities] I talked about some of the scenarios that you get right out of the box, [Imagine the app innovation possibilities] your developers create an application, it can span on-prem and the cloud, [Imagine the app innovation possibilities] it can start in the cloud as dev test and then move back to on-prem for production or it can start on-prem now and then in a year or two or whenever the requirements of the cloud meet your needs, then it can move up into the cloud. >> Yeah, you know, I actually heard a new one. Talked to a customer a couple days ago and they were talking about how they want to run their applications in the public cloud, but then you use the Blobstore in the private cloud. So they could retain all their informational locally. So that was pretty interesting. [Imagine the app innovation possibilities] >> One of the things that we've heard customers asking us is, "The cloud is our future, [Imagine the app innovation possibilities] how do we develop applications that will eventually make it to the cloud, that might start on-prem today but we want to migrate to the cloud and we want to not have to go rewrite them when we move that." [Imagine the app innovation possibilities] The other one is, "We'd like to create applications [Imagine the app innovation possibilities] so we can do dev test in the cloud [Imagine the app innovation possibilities] and then have those easily moved back to on-premises." [Imagine the app innovation possibilities] And then finally, applications that might span on-premises in the cloud. [Imagine the app innovation possibilities] So what this will do, this consistent environment, [Imagine the app innovation possibilities] is relieve that pressure that you've got today for those developers to bypass you with shadow IT and go directly to the cloud. They can achieve their business objectives on your own infrastructure, in your own datacenter with this level of consistency, with the true power of the cloud in their own datacenter. Not just that, but they'll be able to take advantage of not just the agility of infrastructure services, but also higher level PaaS services that will come as part of Azure stack. For example, database as a service. And you'll see more and more of those higher level PaaS services that are truly empowering for those application developers where they don't have to worry about the infrastructure underneath those services, but rather let the cloud platform take care of that for them. >> Right, they're able to build their applications on these higher level services and just go, go, go. >> That's right. [What does a hybrid cloud platform look like?] >> So we've mentioned to you that the cloud is not a location, it's a model. [What does a hybrid cloud platform look like? End user experiences, Cloud application model] So what is the model? [What does a hybrid cloud platform look like? Infrastructure services, Platform services] And this is the model. [What does a hybrid cloud platform look like? Cloud infrastructure, Private | Hosted | Public] So this is the common model, independent of whether it's the public cloud or the private cloud. You get the same end user experiences, portals, [What does a hybrid cloud platform look like?] self-service portal, DevOps tools. [What does a hybrid cloud platform look like?] You have a cloud application model, then you have infrastructure services [What does a hybrid cloud platform look like?] and platform services and then built on cloud infrastructure. [What does a hybrid cloud platform look like?] And again, that model is gonna be available both in public cloud, private cloud and then hosted cloud. So we haven't talked about hosted cloud. What's hosted cloud? Hosted cloud is hosters being able to take the Azure Stack and offer it as a service to people. So if you don't want to have the public cloud and you have a great relationship with the hoster, who's a trusted advisor, they can provide Azure Stack as a service to you. [Microsoft's hybrid cloud platform Power of Azure in your datacenter, Portal | PowerShell | Dev-Ops tools] >> Male: So more concretely, in the context of Microsoft Azure Stack, [Microsoft's hybrid cloud platform Power of Azure in your datacenter, Azure Resource Manager] Microsoft's hybrid cloud platform, what we're talking about is at the top level, [Microsoft's hybrid cloud platform Power of Azure in your datacenter, Azure IaaS | Azure PaaS] you have the Azure Portal, you've got PowerShell and the Dev-Ops tooling [Microsoft's hybrid cloud platform Power of Azure in your datacenter, Cloud-inspired infrastructure] that comes with Azure. [Microsoft's hybrid cloud platform Power of Azure in your datacenter, Microsoft Azure Stack] You've got Azure Resource Manager as the cloud developer interface to the platform. [Microsoft's hybrid cloud platform Power of Azure in your datacenter, Private | Hosted] And underneath that, you've got the infrastructure services [Microsoft's hybrid cloud platform Power of Azure in your datacenter] that I mentioned as well as Microsoft Azure platform services. [Microsoft's hybrid cloud platform Power of Azure in your datacenter] Platform as a service services that I mentioned. [Microsoft's hybrid cloud platform Power of Azure in your datacenter] At the bottom, instead of running the cloud infrastructure [Microsoft's hybrid cloud platform Power of Azure in your datacenter] that we power the hyperscale public cloud with, [Microsoft's hybrid cloud platform Power of Azure in your datacenter] you run a different fabric that is powering the smaller scale environments [Microsoft's hybrid cloud platform Power of Azure in your datacenter] of your own on-premises environment with the hardware [Microsoft's hybrid cloud platform Power of Azure in your datacenter] that you've provisioned there. [Microsoft's hybrid cloud platform Power of Azure in your datacenter] >> We should explain why that's the case. So I mean, I think you can clear it up with one question. So what's... When you do an Azure Stack, an Azure storage build out, what's the minimum stamp size you have? >> The minimum is about 1,000 servers. >> About 1,000 servers, right? So you can see how that isn't appropriate for on-premises datacenters. So that's why there's a cloud-inspired set of infrastructure. So you'll see, we took the design model and design thinking and then have a different implementation of that for on-premises. >> So what Azure Stack really provides you are three value propositions. [Microsoft's hybrid cloud platform Power of Azure in your datacenter, Developers, One Azure ecosystem] One, Azure services in your own datacenter. [Microsoft's hybrid cloud platform Power of Azure in your datacenter, Developers, Unified application development] The other one is unified application development that you get on top of that platform, [Microsoft's hybrid cloud platform Power of Azure in your datacenter, Developers, Azure services in your datacenter] and then finally you get one Azure ecosystem [Microsoft's hybrid cloud platform Power of Azure in your datacenter] because we're talking about bringing the Azure resources, the templates, the virtual machines to your own datacenters. So you'll be able to take advantage of that ecosystem, the hyperscale public could ecosystem in your own infrastructure. >> Right, and then for developers it's great 'cause... >> Well, you develop a cloud native application once and you can run it in either place. >> Exactly, and IT pros love it because now all of a sudden we get to enable our business to get to the cloud and we still have a seat at the table, right? 'Cause IT needs a seat at the table as you go to the cloud because with the shadow IT, we talked a little bit about that, that's where developers when they aren't getting what they need from their IT organization, bypass IT and go directly to a public cloud. Now that's great for the business 'cause they get what they need done. However, it's actually bad for the business because IT, we're the guardians of the policies, the data, making sure that our customers' data is secure and private. And so this model of being able to offer our datacenter resources as a cloud service ensures our business can go to the cloud while maintaining all the things that we're responsible for. >> And I want to mention that this brings true cloud to your own datacenter. Not just some aspects of cloud, this brings, if you take a look at the definition of what a cloud is, on demand self-service and elastic, it is multi-tenant, resource pooling. So you get these kinds of capabilities that are truly modeled on what we've got in Public Azure in your own datacenter measure and metered so that you can keep track of resource consumption by user, by application, those kinds of capabilities come with this as well. [Microsoft's hybrid cloud platform Power of Azure in your datacenter] So speaking of those Azure services, the ones that are gonna come in [Microsoft's hybrid cloud platform Power of Azure in your datacenter] the first release of Azure Stack include the base infrastructure [Microsoft's hybrid cloud platform Power of Azure in your datacenter] compute, network, and storage. That includes disk storage as well as blob storage and table storage as well as Azure service fabric and as well as Azure app service, which includes Azure web apps, mobile apps, API apps and notification applications. Of course, we'll be continuing to add to this portfolio of services that are gonna be available to you in Azure Stack, but this is a first solid starting point which will give you an ecosystem of this fundamental capabilities to create applications. >> So we've talked about how Azure Stack enables IT pros to deliver their datacenter resources as a cloud delivery service. [Azure services in your datacenter Transform datacenter resources into cloud services, Self-service IaaS-Virtual Machines, Virtual Network, Storage, Docker-enabled containers] So let's talk a little bit more about that in detail. [Azure services in your datacenter Transform datacenter resources into cloud services, Self-service Paas--App service*, Service Fabric**] You're able to take your hardware and present it using the self-service IaaS. [Azure services in your datacenter Transform datacenter resources into cloud services, Flexible service delivery with Azure-based management and automation tools] This is great for traditional applications like SQL or Exchange. So you have virtual machines, virtual networking, virtual storage and then we also support self-service PaaS [Azure services in your datacenter Transform datacenter resources into cloud services] as Mark was mentioning. [Azure services in your datacenter Transform datacenter resources into cloud services] So here we're talking about app service, these are web applications, [Azure services in your datacenter Transform datacenter resources into cloud services] Service Fabric, Docker integration with containers. [Azure services in your datacenter Transform datacenter resources into cloud services] And this enables your developers to provision themselves [Azure services in your datacenter Transform datacenter resources into cloud services] access to these resources and allows them to build these applications very, very quickly. [Azure services in your datacenter Transform datacenter resources into cloud services] Lastly, you have the same tools that we use internally to provision services, [Azure services in your datacenter Transform datacenter resources into cloud services] you get those tools and you're able to provision services for your users. [Azure services in your datacenter Transform datacenter resources into cloud services] >> Now let's talk a little bit about the unified application development model that you get with this kind of consistency. And what we're talking about is the next generation Azure platform, the one that is built on top of Azure Resource Manager, which is the common control plane across all Azure services. What Azure Resource Manager gives you is a couple of powerful capabilities. One of them is template-based deployment of applications. So when you deploy a cloud application, it typically consists of multiple resources, a website and a database, maybe a cache. With Azure Resource Manager templates you can describe that declaratively and then place it a marketplace or gallery like we've got in Public Azure. Developers can create these things, end users can go deploy them with a few clicks, parameterize their configuration specific to their deployment, and within minutes, they have that complex application up and running. [Unified app development Write once, deploy to Azure or Azure Stack] is unified role-based access control. [Unified app development Write once, deploy to Azure or Azure Stack] So with both Azure and Azure Stack, you can use Azure active directory roles [Unified app development Write once, deploy to Azure or Azure Stack] and user assignments to give users appropriate access [Unified app development Write once, deploy to Azure or Azure Stack] to the resources, the applications and their resources that they need [Unified app development Write once, deploy to Azure or Azure Stack] and that is all enforced in a common way across all Azure services [Unified app development Write once, deploy to Azure or Azure Stack] using Azure Resource Manager. So with this kind of model, you can take a template, develop an application on-premises, then go take that same template and deploy it in the cloud or vice versa, or take an application and decompose it into multiple templates, part of the application on the cloud, part on-prem, and then have a unified role-based access control model across both those environments. [Unified app development Write once, deploy to Azure or Azure Stack] Further, Azure is an open source platform. [Unified app development Write once, deploy to Azure or Azure Stack] We embrace open source as a first class citizen in Azure [Unified app development Write once, deploy to Azure or Azure Stack] and that same applies to Azure Stack. [Unified app development Write once, deploy to Azure or Azure Stack] So whether you're a developer in PHP, [Unified app development Write once, deploy to Azure or Azure Stack] Ruby, Python, all of those environments, or Linux, [Unified app development Write once, deploy to Azure or Azure Stack] of course, all of those different application platforms [Unified app development Write once, deploy to Azure or Azure Stack] and runtimes that are available in Azure will be available on Azure Stack as well. And I think one thing that is critical to emphasize here, this isn't some shim layer that abstracts away differences. You are gonna be programming to the exact same SDK whether you're targeting Public Azure or Azure Stack to give you true portability across those environments. >> Right, so it's the APIs, but then also the tools. Right, all the Dev-Ops tools that work in the public cloud or work on-premises. >> Of course, I see you teeing it up here, PowerShell. >> Well, since you brought it up. >> All the PowerShell commandlets in the Azure CLI which works on MAC and Linux. You simply point it at Azure Stack or Azure public cloud and the same APIs and commandlets work. >> Of course, it's all about PowerShell, but actually I was referring to the other things, the chefs, the puppets, the ansibles, all those tools that integrate in with Azure, you'd be able to use those same tools in your on-premise datacenter. So that's a really powerful story. [One Azure ecosystem Jump-start your Azure Stack efforts with the rich Azure ecosystem, Azure Resource Manager templates] So as Mark was saying, the consistent set of APIs basically allows [One Azure ecosystem Jump-start your Azure Stack efforts with the rich Azure ecosystem, Windows Server and Linux VM images] many people be able write things to the public cloud or the private cloud. [One Azure ecosystem Jump-start your Azure Stack efforts with the rich Azure ecosystem, Third party services and extensions] So really what we're talking about here [One Azure ecosystem Jump-start your Azure Stack efforts with the rich Azure ecosystem, GitHub to store and share above application components] is a platform, right, that's what Microsoft's DNA is, [One Azure ecosystem Jump-start your Azure Stack efforts with the rich Azure ecosystem] we're a platform company. And the great thing about platforms is they enable ecosystems. So what's going on with that? Well, the answer is this API, this platform allows people to do their best work on the platform with the lowest amount effort. That's why people love the platform. And so now you're able to do that, you're able to do your best cloud work on our platform. And so doing that gives customers the widest range of choice because there are so many people building on this platform, there's lots of choices. So that's the real power of the platform is to enable the ecosystem. And guess what? [One Azure ecosystem Jump-start your Azure Stack efforts with the rich Azure ecosystem] You're part of that ecosystem too, right? [One Azure ecosystem Jump-start your Azure Stack efforts with the rich Azure ecosystem] So as you need to hire people, now all of a sudden you can go out [One Azure ecosystem Jump-start your Azure Stack efforts with the rich Azure ecosystem] and hire people with the skill set and make them [One Azure ecosystem Jump-start your Azure Stack efforts with the rich Azure ecosystem] more productive with less training more instantaneously. Or if you need to move somewhere, sometimes we have people that need to move across the country or around the globe because of family or personal situations, well, now you have a skill set that enables you to go to other places, knock on a door, and have a lot of people say, "Wow, that's exactly what I was looking for." So the power of the ecosystem is fantastic with Azure. [One Azure ecosystem] >> And as far as the Azure ecosystem [One Azure ecosystem] that we're talking about, Azure today is in 22 regions publicly, [One Azure ecosystem] with another 6 that are coming in the next 12 months. [One Azure ecosystem] >> Wow, and then we expect with Azure Stack, [One Azure ecosystem] we'll have hundreds of service providers take Azure Stack [One Azure ecosystem] and offer Azure as a service across the globe. [One Azure ecosystem] Then, as customers deploy that, we expect thousands of enterprises to be [One Azure ecosystem] running Azure in their own datacenters. [One Azure ecosystem] So you will be able to get Azure [One Azure ecosystem] anywhere you want with this fantastic, vibrant ecosystem. [One Azure ecosystem] >> It's gonna be one big family. >> It is. Mi casa es tu casa. >> As our Spanish friends would say. >> Yes indeed. >> We're committed to delivering Azure innovation everywhere. [Demo: Azure Stack in action] >> Sounds great, right? [Demo: Azure Stack in action] Well, let's do some demos to see what this puppy can really do. >> This is the Azure portal. From the portal, you can create and manage your cloud resources. And Azure Resource Groups are used to contain a group of related resources that typically make up a larger application. For example, a website and a database could be grouped into a single resource group. The portal is organized around resource groups. So that way you can manage those collections and related resources together. If we take a look at this resource group, you can see a virtual machine and all the resources that make it up, including a network adapter. You can see the operations you can take on the virtual machine and you also, when you click on a network adapter, you can see the detailed information about it. Here's the Azure Stack portal. It's the exact same code as we've got running in Azure, so it's gonna look and behave exactly the same way. Here are resource groups just like we saw in the Azure portal. And you can browse them in the same way. And here's a virtual machine that was created in the same way we created that one in Azure. So it has the same collection of resources including a network adapter that when we click on, we see information about just like we saw in Azure. But we've taken the consistency between Azure and Azure Stack deeper than just the UI. >> We've taken consistency to the API level. With this, investments made against Azure can apply to Azure Stack. Let's look at one of those automations. This is a deployment script that does three things. It connects to an Azure environment, sets the region like US West, North Europe, or East Asia, and finally, deploys a template to the cloud. Here we're gonna connect to Azure. Next, we'll specify the region in Azure that we want to deploy to, in this case US West. Next, we'll run the deployment specifying the parameters of the machine we want to create. There goes the deployment, creating that VM in Azure. Now we're gonna take the same script and change it to connect with an Azure Stack deployment. We're gonna set the region we want to deploy to. And then run exactly the same deployment steps. And there it goes, creating that virtual machine now in an Azure Stack deployment. Enabling developers to go fast means that they have access to the resources from the tools they need to get their job done. >> This is a Visual Studio project that's using the Azure SDK. The project that's open is one that can be deployed to an Azure cloud. So from their development environment, a developer can deploy their work and choose to deploy to the Azure cloud that they're subscribed to. Here you can see the Azure subscriptions available to this user as well as the Azure Stack subscriptions available. Once the developer's made their choice, they simply finish setting up the deployment and deploy the application. The deep consistency between Azure and Azure Stack means that the ecosystem of tools and templates that work against one work against the other. >> Let's take a look at one of those tools. >> Azure Stack has the same Blob storage capabilities as Azure. If we look at our storage accounts in this Azure Stack deployment... There is a storage container called myphotos. Currently that container is empty. This is the Azure storage explorer. It's a community tool for working with storage in Azure. With no changes to the tool itself, all we did was connect it to a storage account that is in Azure Stack and see that the myphotos container is available. We can upload a life to the Blob storage, in this case, a photo. When we switch back to Azure Stack portal and refresh the container... The photo we uploaded is now in the cloud. We can copy a URL to that photo and paste it into a browser. And now we see the picture we uploaded to the Azure Blob storage running in the datacenter. So as we talk to customers, there are lots of questions about Azure Stack and what it is, so let's go through some of the most common ones. [Common customer questions, Which Azure services can I experience in Technical Preview 1?] >> So one of the questions you probably have [Common customer questions, Which Azure services can I experience in Technical Preview 1?] are which services are gonna be [Common customer questions, Which Azure services can I experience in Technical Preview 1?] included in Technical Preview 1? [Common customer questions, Which Azure services can I experience in Technical Preview 1?] And that includes the core set of infrastructure, compute, network, and storage services. Specifically with compute, it's virtual machines and virtual machine extensions as well as the ability to run containers inside of virtual machines. For networking, it includes virtual networks, which is a way to encapsulate groups of virtual machines together in a network, as well as the software defined load balancer, as well as virtual network gateways. And for storage, it includes the Blob's service as well as the table service. For higher level platform as a service offerings, it will include web apps, which is a component of the overall app service. It will also include some fundamental cross cutting services including the Azure portal, as well as the Azure resource manager control plane that is the interface to the service that I just mentioned. [Which Azure services will be available at GA?] Now as far was what services will be available at the time of GA of Azure Stack, [Which Azure services will be available at GA?] beyond what's included in TP 1, that will be the rest of the app services, [Which Azure services will be available at GA?] including logic apps, API apps and mobile apps. [Which Azure services will be available at GA?] Service Fabric will also be there though it will be in preview form at the time Azure Stack goes GA. >> Yeah, that's an important thing to note. This is Azure, right? And so Azure always has a set of things that are in production and then a set of things that are in preview. It's gonna be exactly the same way on-premises. At any given point, we'll be delivering you things that are in production and things that are in preview. >> And, of course, we'll continue to iterate on the quality and richness of TP 1 as we head towards GA. [Common customer questions] >> So a number of people have asked, [What is the thought process on the prioritizing which Azure services will come on-premises?] what was our thought process [What is the thought process on the prioritizing which Azure services will come on-premises?] in picking the services that are going to be [What is the thought process on the prioritizing which Azure services will come on-premises?] available in the first version of Azure Stack? [What is the thought process on the prioritizing which Azure services will come on-premises?] And the answer is really quite simple, talking to you. So we talked to you and found out what your most pressing needs were and we also have the benefit of the Azure metrics. So we found out what things you were actually using in the public cloud. So those combination along with what was technically feasible [Common customer questions] drove the list of things we're delivering for version 1. [Common customer questions] Another question [How does Azure Stack relate to Windows Server, System Center, and Azure Pack?] I get a lot is how does Azure Stack [How does Azure Stack relate to Windows Server, System Center, and Azure Pack?] relate to Windows Server, System Center, and the Azure Pack? [How does Azure Stack relate to Windows Server, System Center, and Azure Pack?] And the answer is that the Azure stack is all focused in on the cloud. Right, we're taking literally the Azure code and making it available on-premises. The Windows Server, System Center, Azure Pack, that's great for virtualization. Here we're focused in on giving you the same experience of Azure in the public cloud making that available in the private cloud, and thus giving you hybrid cloud solution. [Common customer questions] Another question [How will Azure Stack be updated and serviced?] I get a lot is how will Azure Stack be updated and serviced. [How will Azure Stack be updated and serviced?] So here it's important to step back and think about what it is we're doing. [How will Azure Stack be updated and serviced?] And what we're doing is we're creating a cloud ecosystem, cloud ecosystem of the public cloud, of hosted clouds and private clouds, and so it's important for everyone to be on a consistent set of APIs. And so that's what we're gonna be doing. We're gonna be updating Azure Stack at a cloud cadence. Now, Azure updates very, very frequently, we'll update less frequently, probably a couple times a year and we'll articulate when that is, so you'll have predictable timetables, etcetera, but at any given point, you'll know that you're consistent with Azure. [Common customer questions] And, of course, the questions everyone wants [Release timelines?] to know the answer to, when can I get it? [Release timelines?] And the answer is we're targeting release of Azure Stack for the fourth quarter of this year, 2016. We have the technical preview out and we will be updating the technical preview multiple times throughout the year. [What's next?] So what's next? [What's next?] And the answer is [Lead your organization to adopt the cloud model] we want to partner with you for you to be the change agent [Lead your organization to adopt the cloud model] to bring your organization to the cloud. We want you to be the hero. >> One of the things you do to [What's next?] get ready for this is to [Ramp up on the Azure application model today] start learning about the Azure application model, which is found on Azure Resource Manager, the core interface for both the Public Azure cloud as well as Azure Stack. [Run Azure Stack Technical Preview 1 and give us feedback] >> Absolutely, and you want pick up the technical preview, kick the tires, [Run Azure Stack Technical Preview 1 and give us feedback] let us know what's working for you, where we can do a better job. [This is just the beginning of a longer journey. Let's all come together!] >> And remember, this is just the first big step on a journey [This is just the beginning of a longer journey. Let's all come together!] we're taking with you to bring the power of Azure into your own datacenter. [Follow along Mark Russinovich CTO, MICROSOFT AZURE] So we encourage you to follow us along on Twitter, there's my handle there on the right. [Follow along Jeffrey Snover CHIEF ARCHITECT, ENTERPRISE CLOUD ] >> And there's mine on the left. [Follow along Jeffrey Snover CHIEF ARCHITECT, ENTERPRISE CLOUD Mark Russinovich CTO, MICROSOFT AZURE] And if you can only follow one, follow me. >> Follow me. >> No. >> Follow me. >> Me. >> So we want to thank you for joining us and want to wish you the best of luck on your journey to the cloud. >> Thanks for joining us today. [Thank You] [Microsoft]