>>Live from Orlando, Florida. It's the cube covering Microsoft ignite brought to you by Cohesity. >>Welcome back everyone to the cubes live coverage of Microsoft ignite. I'm your host, Rebecca Knight, along with my cohost. We are joined by Jeffrey Snuffer. He is a technical fellow, Oh three 65 intelligence substrate at Microsoft. Most famous for being the father of PowerShell and one of the key architects of the window server. Thank you so much for coming on, for returning to the show. Yeah, thanks. It's great to be back. So first of all, define your, you're relatively new to this role, so tell us a little bit about what you're doing and what is the intelligent substrate. >> Yes, so you know, a lot of people get this confused as intelligence substrate. There's all three 65 the Microsoft graph. And when I do, as I say, Hey, the best way to think about this as an analogy to an operating system, operating systems are complex, but at the end of the day, they're really, really simple. >>They only do three things. They manage and protect resources. They provide services for developers, right services, API APIs and common controls. And then they provide a base set of applications and a way to get additional applications. So windows manage, CPU, memory, the services when 32 API eyes and then the applications like the browser, et cetera. So all three 65 can really be viewed as an operating system. Sounds strange. Why? Because most operating systems have been operating systems for devices, an operating system for phone, an operating system for a PC and operating system for a server. This is an operating system for people and organizations. So when we think about those three responsibilities, resources and you know, protecting and managing resources, these are the resources for people in organizations. So it's their identity, their, their emails, their chats, their documents, services for developers. These where there's wind 32 for windows, we have ms graph, that's our public API, but then we have services to be able to create, collaborate and communicate documents and interactions. >>And then the applications are things like teams and outlook, et cetera. And so then, Oh, sorry. Then the substrate, the substrate, sort of at the core of it. That's one of our core services. It is storage and then a set of services to manage that and set of services. So the storage is basically a planetary scale, no sequel data store. So every time you create a chat and email document or whatever, it gets stored in the substrate and then three additional copies are created, one of them at least 250 miles away. That's why our date availability and high availability are one thing. So everything gets stored there and then that allows us to do common services like search against it. Does that make sense, >>Jeffrey? Well, one of the biggest challenge people have is when you learn about something and then it has changed an awful lot. Yeah. I think back to the first time I used Microsoft word, Microsoft Excel, it wasn't connected to the internet exactly. Let alone talking about the era of global scale in AI and all of these things that can do in. So maybe give us a fresh as if I'm a brand new person and I, you know, I don't have the, you know, all of the legacy history with the Microsoft office family. What, what is the new, you know, people O us that you're talking about? >>Yeah. So I like to think of it as a back to the original office 1.0, if you remember the original office 1.0, you'd had word, Excel and PowerPoint. And I like to joke, I say it was integrated with the advanced technology at that day of called cardboard, right? We just took the, the, the floppy disks from each one of those products, put it in a cardboard box and said it's a suite. But then it was a vision to a vision of how things should work together to help the individual. And then after that version one, then we reorganized the organization to have common technology teams. And that's when we started to get common controls, common user experience, et cetera, common file formats. Uh, and then it became a true integrated suite. Same thing happened when we went to the cloud. We had all these products that would have a front end couple to a back end, another front end, couple to a back end, another front end coupled a backend. >>Each one would have one or more SDKs, et cetera. And when we first brought them to the cloud, it was the same sort of thing, integrate it with an offering and a name. But there was a vision there. And then that vision drove the reality. And what we did was we said, Hey, let's figure out how to have a common storage for these things. Common backend, a common way to communicate, a common way to do messaging. And then that took a number of years. But that's what drives this consistency. And so that's why when you go and you say, I would like to search for something, you'll find that term, whether it's in your word documents or it's in your emails or your team chats or anything. It's that commonality that makes it answered question. It >>does. Um, so it's, I think about, you know, the era of collaboration and, you know, there were competitors to Microsoft that came out that were built on the internet and you know, deliver those solutions. So this week we've talked to, we haven't dug deep deep into teams, but everyone we've talked to that's using it, it's like, no, really this is a really great product and almost like, you know, forget about some of the things you might have remembered through some of those iterations and changes and things not working together. You know, teams has been built and is allowing some great collaboration, communication with remote workers, smaller businesses, the likes. So it's tough because especially if you're using one tool and you've gone over to some other tool set, it's like, Oh, I don't, why would I go back to that? But it's a very different, uh, Microsoft productivity suite today than, than we might have used in the past. >>That's exactly correct. And then the, into the, uh, uh, intelligent substrate is this layer of AI on top of the substrate, right? So part of that is search, but then we're also doing natural language processing. So basically imagine you saw a store of file in in a one drive that gets stored in one drive and a workflow gets kicked off and that workflow then goes and analyzes the contents of that file and create search terms, et cetera. So we then have common search and then we've got natural language processing that'll go and find, Hey, what are the key points for that document? How do I summarize that document? So then if you see it somewhere you can say, Oh, show me the file card. And I'll say, here's this document. You don't have to read the whole thing. Here are the three key points about it. >>And so the, this is, so to answer the question, why would a, why would a platform guy be working in office? It turns out that to build this AI infrastructure, it's really sort of a platform play. There's key advances that need to be made in, in AI. But actually when you get involved in AI, what you realize is what we really need is more engineering than more science. We need more science, no doubt about it. But boy, is there a need for engineering? Like I need to figure out how to get three to five to seven orders of magnitude more volume of AI going through the system. So when you talk about these key advances in AI that need to be made in terms of of applying them to O three 65 describe them for us and talk about how they will change the future of work and the way we collaborate with our team members in the way we communicate with our team members and, and in our productivity. >>Yeah. So this is where I get so excited about Microsoft's play, right? Because when I decided at the end of last year that I was gonna make a new change, I had a number of opportunities both inside and outside the company. And so the, the thing that really made me say, this is where I want to go was, well, one, it was most important new technology, AI on our most precious business asset, our customers data. So that was very exciting for really got me over the edge was Microsoft's approach to AI. Microsoft takes a very different approach to AI than our competitors, right? The heart of most AI is trying to figure out you and you to achieve some result. Now our competitors do that to try and get you to click a button to buy an ad or to buy something you don't need or subvert some government that they want subverted, right? >>That's none of our peg objectives. We want to understand you for exactly one reason to make you successful, right? How do we, like in the past, people would throw the rock at Microsoft, say, Oh, you know, when I use Microsoft products, I got to understand the Microsoft org chart. You know, you ship my org chart. What they're really saying is that they have to understand the tools to get their job done. They have to navigate the tools. What we're trying to do is have the tools understand the person to help the person, help that person get their job done. So there's this great show, I think it was called the remains of day today, the movie with Anthony Hopkins, he played a Butler. And in that he did some research and he talked to the Butler of Buckingham palace who'd been there for 50 years and he said the essence of a great Butler is that he makes the room emptier when he enters. >>What's that mean? Well, when the, when someone sits down the magazine that they want, is there, the drink that they want is there. It just, it just all works out. Well, that's not my experience with computers today. I mean, how many times do you, you know, you end up at the end of the day and you're like, your spouse says, what'd you do to you day? You're like, wow, I dunno. I dunno. I'm just exhausted. Well, it shouldn't, doesn't have to be that way. What we want to do is to have the computer understand you, understand your objectives and not have some big splashy AI. It just, Oh, things just work. Oh, I'm coming to this meeting. Oh, the information I need for that meeting is just there. Oh, it prepped me and knew that I had a few minutes. And so it gave me a few minutes where it's a prep and things just flow. And at the end of the, you know, success will be when you end the day with more energy than you start it. Like that's a big tall tale, a big tall effort. But that's where we're going for that. Get stalled. >>Yeah. Well we, we found that the, the word that has summarized this week for us is one that Satya said over and over again and it was trust. So in today's day and age, there's a lot of cynicism and especially looking at big tech companies, you did a presentation talking about AI in social responsibility. You tease out a little bit of it there as to why you believe Microsoft is well intentioned with AI, but maybe share a little bit more about that vision for social responsibility and you know, where we need to go with AI as an industry as a whole. >>Yeah, exactly. So there's kinda two key points. First is I think there's a, a very vast, uh, misunderstanding of the state of AI Kang. It really is best understood as software 2.0 and we've been at software 1.0 for about 75 years and I don't think anybody thinks we're doing a particularly great job at event. I think we've started to make progress starting around the 1990s with the, with the core principles of, of uh, the worldwide web. That's when we started to really make some progress. But we still have lots of world's problems. So we're at software 2.0 we're at the very beginning of the beginning of the beginning. Now here's the point. The innovators set the field, the innovators set the path. And in AI it's important for Microsoft to be one of the key innovators here because of our approach, because we're standing up and saying, wait, there's great promise. >>There's great challenges, right? There are privacy challenges. There's data bias challenges, there's inclusivity challenges. There are things that really need to be addressed by governments, local legislation and global governments. Brad Smith has been particularly vocal on this and the need for a digital, the only way you're going to solve the problem of autonomous killer robots, which is a real thing, is by a digital Geneva convention. We, Microsoft can't solve that. IBM can solve that. Google can't solve that. Governments need to solve that. And so Microsoft is being very proactive in engaging the communities around these problems. For myself, for instance, I've been working with some of the security researchers to say, okay, well, software 2.0 how do you do threat model on machine learning? Nobody knows. Like literally nobody knows. And so we've been working over the course of the last year to produce a taxonomy of attacks. Now this is the initial thing, but it sparks a conversation as we've shown it to various government people and other, uh, competitors. Uh, they're very excited about this, about trying to join this in, to identify the class of attacks. Because once you can understand the class of attacks, then you begin understanding, well, how do I defend against those? But literally it doesn't exist. So, >>so talking about autonomous killer robots, I'm very worried now. So how do you, Jeffrey said you're talking about Microsoft's more measured approach and as you said, you are working with governments and work in reaching out to policy makers and regulators to talk about these things. Maybe unlike some other technology companies that aren't doing that. How do, are you a tech optimist at the end of the day or are you, but does it keep you up at night these, these, Nope. Nope, >>not at all. Not at all. No. I'm a wild Technomic dumbest people like are very pessimistic and I just like, yeah. You know, no. Like, let me give you an example, right? There's this, this thing that says, Oh, an autonomous car turns the corner at a high speed and it has to decide between killing two old man and a and a woman in a baby carriage. Right? And it's wide. This is a Philip philosophic philosophy problem called the trolley problem. Oh, a trolley driver has to pull a switch a, uh, and it was like over a hundred years old in the a hundred plus years that that's upon posited, there's been exactly zero trolley drivers ever put in this position. Just, it's just not an issue. Look, there are real issues. We do have to work these things. I'd say the biggest worry is not these killer robots or the autonomous cars going wild. >>It is complacency. It is overconfidence. It says, Oh, I got something to work. Let's just ship it. Like there's a lot of brittleness in these AI systems, right? Like, Oh, this works and it can be spectacular, but then this is a complete disaster and that's a complete disaster. So how do we get that taxonomy of like, Hey, when do we know when we're done? How do we test these things? How do I have like a, a secure supply chain for the data models as well as the code itself? You know, so. So I think that software one no doubt does not provide us any of the answers to the challenges of software 2.0 but I do believe that software 1.0 and its challenges tell us the areas that we need to apply our, our mindset to. And that's what we're doing. So >>Jeffrey, before we let you go, we do need to get the update on PowerShell. I have to say, ever since I've first talked to you, I feel like more and more when I go to shows, I hear people just talking about how it's helping their career, helping their business and in doing it, I don't know if it's just because you know, it was brought to the front of the mind and it's like, Oh no, I'm used to seeing that car model out there. But can you give us the latest on power shell even though you're no longer in that group? Oh yeah. I continue to meet with them all the time. >>I'm very active in PowerShell. So we took power shell and made a cross platform to run analytics. We've talked about that and I don't know where we were when we talked about that, but basically we sort of did it for our own purposes, right? We need to manage the world's estate and so we want to have a common infrastructure for doing that. And the joke was that the point is like, look, we're not confused. We don't think that the Unix people are going to greet us as liberator's. Like all, thank heavens, you know, I've been dying under this bash and such. Thank God Microsoft came to save us, right? There's no confusion. We'll surprise. We shifted and then the vast majority, the numbers are crazy. How many Linux people are using PowerShell. It's just insane and we don't really understand it. We're out there talking to people, but they just love it. >>So anyway, so PowerShell version seven is coming out. It'll come out officially at the end of the year, beginning of next year, and this really is the tool that then you can use to manage everything. Both windows and Linux. We have parallel for each, so you can do massive scale. But that's the one that really just brings all the pieces together and gains the critical mass. So we're very excited about it. always a scintillating conversation when you come on the show. Thank you so much for coming on. Thank you. I'm Rebecca Knight for Stu Miniman. Stay tuned for more of the cubes live coverage of Microsoft ignite.