 Hey, I'm here with Carmen Cliccoli and we talked a lot before, right? I know you from the Windows Server Software Defined Data Center program. It was a program, it was the Windows Server Software Defined Solutions program. Okay, and then I knew you were working on Azure Stack HCI, which both programs and both solutions were like making me super excited. So that's why I have you here as well. The Azure Stack HCI program really was an evolution from WSSD. WSSD, we launched it when we launched Windows Server 2016 and the idea was just we needed a way to get customers solutions that would work with our Software Defined Data Center software technologies that were just built into Windows Server and customers who try to build their own on hardware that was lying around had really bad experiences because it turns out building high-performance, resilient storage and networking requires specialized equipment. So rather than just put the software out there and hope customers get it right, we decided to work with the hardware ecosystem, have them build solutions based on best practices and then put them together and market them as a complete and end solution. WSSD was really kind of the start of that process and when time came to release Windows Server 2019, we decided to go all in on the investment and we relaunched it as the Azure Stack HCI program and we built a whole roadmap and plan out to make Azure Stack HCI part of our entire edge computing plan going forward. So I'm sure a lot of people have heard of Azure Stack, which is now Azure Stack Hub. We have a whole category in there and Azure Stack HCI is one of those pieces and that's going to be the direction we take this hardware solution program going forward. So I remember, I absolutely remember, I remember the time where we were building solutions based on Windows Server and Hyper-V and again the customers sometimes they just ordered some random hardware, right? So I went through that pain with drivers, validation, like doing the right setups and everything and that's exactly where I think the Windows Server software defined data center program comes in and then now Azure Stack HCI, right? That's right. And the idea, again, just remove the amount of work the customer has to do before they can even get started, right? Take care of that. And then going forward, we started it as a solution program working with OEMs to define those SKUs, but it's really a product and it's going to become more of a product as we go forward. So right now the program defines the hardware and then Windows Server is installed on top of it and that's an Azure Stack HCI solution. Okay, okay. That's really good to hear that there is a lot of investment because we see a high demand from when I talk to customers out there. I really see a high demand of like people are interested in hyperconverged solutions and they are looking for like, what are the Microsoft offerings there? And a lot of what I heard from them is like, okay, you have this Azure Stack thing, right? And they still believe kind of like, okay, there's only one thing in Azure Stack because we had Azure Stack as a name. Now it's Azure Stack Hub. So where would you say are a little bit the differences of Azure Stack Hub and Azure Stack HCI in terms of like, where would you use what? And like also, I'm also interested in like, what are the options? I know that a lot of customers know that, again, Azure Stack Hub gets delivered as an appliance, right? But which limits it down to certain configurations. Yeah. Is that the same with Azure Stack HCI or how does that work? So, well, let's start at the beginning. Like how did it differentiate it? And it's easily the most common question, right? Because when you change names and have similar names, people are like, wait a minute. There was already a thing that was called that. Why is that different? Why do I want that? So easily the most common question. And in fact, it's basically what I spent all of Ignite doing was answering that question because it was the first time we kind of ruled out the whole new family and the name for the products. And that was just what people wanted to understand is more clarity than just the announcement. Yeah. So what we say is Azure Stack Hub, which is just called Azure Stack previously is really about having cloud consistency in your data center. Meaning if you are already down the CICD pathway and you are developing cloud native applications, but you have a need to run those cloud native applications in your own data center, you need Azure Stack Hub. Because Azure Stack Hub provides the Azure Resource Manager and the APIs that you need for those cloud native apps to run there. So it handles that very specific business need. Azure Stack HCI is really about just providing a hybrid model for what I would call more traditional virtualized workloads. So if you have a virtualization farm that is just running VMs of all shape sizes and descriptions and they don't necessarily make an easy migration or fit into an IaaS world for your business, Azure Stack HCI gives you the ability to have a hybrid platform that takes advantage of cloud resources without being a cloud resource in and of itself. Okay. Right. So it helps people who are not far enough down the cloud path to really want the full cloud experience running in a rack in their data center. Which we see a lot. I mean, that's not something which is uncommon, right? It's like most companies have a history and they're not fully migrated and everything is cloud native and everything. So I see that a lot. But I also found it's like there's many, many different solutions out there, right? I think how many do we have right now in the Azure Stack HCI catalog? Last time I looked, I think we were up over 190. Okay. Different solutions from 20-something different OEMs around the world. And we obviously have all of the big players that you know, but we also have a lot of regional specific OEMs who have their loyal customer base because they provide a lot of services, a lot of value to their own customers. So we're happy to have that variety in the catalog and we can go from tiny little configurations that can sit on a desk and you wouldn't even know that there are two Xeons in those servers and it's a spailover cluster with 12 terabytes of capacity in it to gigantic systems that have multiple petabytes. So just the variety is part of the point because unlike a lot of more restricted catalogs where you just have to take what's available off the shelf, you can spec almost anything you want out of it. And listen, a lot of traditional IT people love that, right? I love that. That's the world I came out of. I've been doing this for a long time. I like having some level of involvement in the hardware and being able to spec it to my needs and seeing what the options are. I mean, also the requirements are always different, right? I mean, for a branch office, you can just go out and sometimes you just need something very small or even if you go outside of offices, right? You probably just want to have a two-node mini-systems which probably still have enough performance but you want to have a very small system. But then if you go with your data center, you either want to probably run high-performance systems or maybe even high-capacity, right? And so that's what I love about Azure Stack HCI is really it gives you that flexibility to whatever the customer need is, we can basically go out and address it. Yep. It was one of the high points of a night for us was during our director's session, Bernardo called us, he had Cosmos Darwin come out on stage at one of our PMs, one of the PMs responsible for Storage Spaces Direct and HCI. And he talked about that flexibility and he walked out on stage with a laptop bag and everyone's like, does he know that he's carrying his laptop on stage in front of 5,000 people? And while he was talking, he was like, you know, it allows for exciting new form factors and he opened up a laptop bag and he pulled out a full Xeon server from Lenovo, it's called the SE350, that they just announced for the catalog. And it's maybe, if you're familiar with like, you know, 1U pizza box servers as we call them, it's one quarter of one of those, right? So you can take four of them and put them on a sled and put them in a place where one server would have existed previously. And they have all kinds of cool mounting options, like you can just, you know, take a piece of mountain and slap it on a wall. And it is a full blown server. It can host a GPU, right? It's got 100 gig networking in it. It can do 5G, like it is a real server. And, you know, it's just not something your traditional appliance model would allow for or is, you know, makes sense even. So, yeah, the variety is very much the point of making this a broad partner ecosystem from my perspective. No, again, I'm like, I am super excited about what we have. I mean, about the whole portfolio we offer there. But now you told me you're going to work on something new, which is also still to add a stack HCI, right? But you kind of like have a new position or a new goal. Yeah, yeah, I'm not even really changing teams exactly. I'm just changing what it is I'm focusing on. So rather than running the program and working with the partners, one of the things that we've, that is very important to our engineering efforts is that we're making customer driven decisions. And so we're trying to start up a customer engineering, co-engineering program. Okay. Where we can build relationships with customers who are doing the next thing in their own environment and are interested in working with us on the development of that next thing. Okay. Right? So it's a very intimate program with direct engagement with our engineering. Right? So it's not something where we're just going to send you email updates and... Like a survey and that's it. Yeah, exactly. How happy are you? Very sad. It's none of that. It's regular syncs with our engineering teams, with our leadership. We want to understand your environment. We want your feedback about what's going on. And we're trying to get that customer muscle built up in our engineering teams, where every time they go into make a decision or make an investment of dev time and PM time into work, they're like, we're doing this because customer X said that would make a tremendous impact on their business. Okay. So we've had lots of different customer engagement mechanisms over the year. Microsoft's been around for a long time. Windows has been around for a long time. We're trying this different way to get that relationship up rather than have it be highly programmatic like the previous top programs. We're like Windows insiders, which is tremendously valuable, but it's meant to reach millions of consumers where millions of consumers are not the audience for HCI or Kubernetes, right? So there's two areas I'm most interested in right now is HCI and Kubernetes on-prem and hybrid scenarios. So if you're watching this, I'm sure that there's probably going to be my contact information shared on the screen somewhere when this gets published. Feel free to reach out to me either on Twitter or email if you can find my email or LinkedIn. If you think that sounds like you, please reach out. I'm happy to have discussions and if you're working on the next gen thing, we want to hear from you. Absolutely. So we will put out all the links and how you can reach Carmen in the description to make sure that people can actually go and engage with you. Perfect. So I have one question. For a customer, obviously, if I join, I will have these regular calls. Do I get early access to the stuff your team is doing or what is kind of like the... The goal really is we want to co-engineer with customers. So we will... This is an NDA program, right? It's not broad. There's a reason I'm not even giving you details about what we're working on. It would be... You have regular briefings with us. We share early access to technology with you. We ask that you run it and give us feedback on it. The same thing with the business direction we're taking things in, our technology focus, whether or not it meets your needs. That's the kind of focus of this type of program. And then at the end of the day, we're hoping that we make you happy enough that one, you want to run the final product. And two, that you're willing to stand on stage with us at some point and say, we worked with Microsoft on this technology. We're really thrilled. Here's what we're doing with it. We want it to be successful for both parties involved. Okay. Perfect. So I want to thank you very much for this. It was super exciting to talk about it with this because I'm really looking forward to see what is coming up. And for all the people who are out there, we're watching this video. And if you want to have early access to the Azure Stack HCI and you want to shape the future of how we do hyperconverged and all of that, reach out to Carmen. Again, you will find the links in the description underneath this video. And with that, I want to say thank you and see you in the next one.