Tyler Radke:
Good afternoon everybody. My name's Tyler Radke. Thanks for joining day two of the Citi Tech Conference. I co-head the software sector here. I know we got a super packed room. I believe most seats are taken, but if you have one open, feel free to raise your hand and folks can continue to filter in. We're happy to kick off the afternoon sessions with Microsoft. Really excited to have this discussion around everything. Azure, data management. With me today, I have Arun Ulag, who's the Coporate Vice President of Azure Data.

Arun, I thought just to kick things off, for folks who haven't met you, everyone here knows who Microsoft is, but you've had a really interesting career, I think, at Microsoft, more than 20 years running security, SQL Server, and now Azure Data Platform. Give us an overview of your journey at Microsoft and what are the areas you're focused on.

Arun Ulag:
Awesome. Well, thank you so much, Tyler. Thank you for having me, and thank you so much for showing up. So I started my career as an entrepreneur in Silicon Valley, building a telecom network management startup. Did that for six years, was an engineer selling to engineers. I sold it, went to Business school, and I came to Microsoft because I figured it'll teach me a few things and I'll go back to Silicon Valley and do another startup. Well, I really loved it here, and it's been 20 plus years. The last decade has been entirely in the data space.

So I started running Power BI, which is our business intelligence platform from its early days. That's been really exciting. Power BI is very, very widely used today. A few years ago, I took ownership of big data analytics and that led to the launch of Microsoft Fabric last year. And then, very recently, I started taking on our operational database as well. So I run all of the data services for Microsoft, but engineering, product management, cloud operations. So that's what I do.

Tyler Radke:
Awesome, awesome. And look, there's a ton of products within your purview and particularly within Azure data, databases, data integration products. You talked about Power BI, some of the business intelligence products. Give us the vision for how all these products come together. What are sort of the elements of unification that you're working towards?

Arun Ulag:
Yeah, absolutely. Before I talk about our product strategy, I'd love to just share a few thoughts about what we're seeing from customers.

Tyler Radke:
Sure.

Arun Ulag:
Every customer recognizes that AI is transformative for their business, and they also recognize that their data needs estate needs to be in shape to be able to leverage all of the power of AI, because the best AI models, if you put garbage in, most likely you're going to get garbage out. So it's become critically important for customers to get their data estate ready for AI. Unfortunately, it's a lot harder than it needs to be. I like to say there's good news and bad news. The good news is there's been a lot of innovation in the data and AI space. The bad news is there's been a lot of innovation in the data and AI space because it's created so much fragmentation and complexity.

There's literally hundreds and hundreds of products and technologies out there, and the burden falls on customers. They have to figure out which products to use, which ones work together, how are their prices and licensed, and put them together to get to business value. And so, when I talk to customers, the message I often hear is this, "Please simplify. I want to be the chief information officer, not the chief integration officer. Help me unleash AI on my data estate." And that's exactly what we're doing here at Microsoft. So if you look at our approach, I would say it's three things. One is we have a very comprehensive portfolio of data products and AI products. 

Everything from the world's leading operational databases with Azure SQL and Cosmos, DB and PostgreSQL and MySQL to big data analytics solutions to data integration, etc. So we have a very comprehensive portfolio that we've invested in over a long period of time.

The second is we are bringing all of these capabilities on the data side together with Fabric. And what we are doing with Fabric is we are really integrating this together so that customers get a unified product delivered as software as a service. And this is very different from the industry today because most of the data components are available as platform, as a service, or PaaS components. And if I were to use an analogy, if you're using PaaS services, you go to a dealership, and you want to buy a car, they give you a whole bunch of parts, and it's your job to go assemble the parts together and assemble the car before you can start driving. What we're doing with Fabric is all of it's available as SaaS, which means that the developer doesn't have to put anything together. They don't have to wire things together, they don't have to worry about infrastructure. They're just focused on business value, and that really resonates with customers.

The third thing that's unique about Microsoft is really our focus on business users, because all of the data really is in the service of business, otherwise what's the point of data sitting beautifully in a data lake or a database? And one of the things that we're doing is we're taking all of the data and making it available to where business users are, whether that's Excel, whether that's Teams, that's Power BI, that's SharePoint, all of the Office products and making the data available in a secure and governed way. So this really resonates with customers because it gives them an ability to move quickly, democratize access, drive down costs, and really get down to business value.

Tyler Radke:
I love how you led off with the customer example, because I think that's what a lot of folks in the room are sort of interested in. And I guess I'd love your perspective on sort of comparing this rush to modernize your data state now, relative to other data things like 10, 15 years ago, it was all about big data, then it was about cloud. What is different this time about those types of conversations with customers? And, obviously, what's sort of different on the product side too, in terms of Fabric and how you're approaching it?

Arun Ulag:
Yeah, I'd say, hey, today AI is top of mind for customers. It's not news to anybody here. Gen AI is front and center and customers see the potential. They're trying to translate that into business outcomes. And what it means for us is, we see a lot of opportunity to help customers accelerate their AI journey by bringing the data estate together. When we think about our strategy with Fabric, we really think about very similar to what we did. If I were to go back a few decades, there was a time in which we had Word competing with WordPerfect. Then we had Excel competing with Lotus 1-2-3. And then we saw the opportunity was with productivity, and then we put Office together as a single integrated product. And then even today, decades later, Office has a very substantial market presence, and we see the same opportunity with data.

We see really the opportunity to bring everything together into a single unified stack, so developers can focus on business value. When we think about Fabric, we think about maybe four promises. 

The first is really a complete data platform so that customers get all of the capabilities they need, whether it's data integration or data engineering or data warehousing or business intelligence or data lakes. It's all available in a single unified product. The second opportunity we see is really embracing what we refer to as lake-centric and open, embracing open source data formats. One of the things that really gets in the way of customers is all the data silos that exist in organizations. There's so many different data silos, and every data product out there has their own proprietary data formats. So customers see the data locked into so many different places, which really makes it hard to get to business value.

So what we did in Fabric has really embrace open source data formats at the heart of Fabric, right? So, anytime you bring data in Fabric, by default, you build a data warehouse. By default, the data is sitting in Apache Parquet and Delta Lake, and now we support Iceberg as well. 

By default, it's open source data formats. And customers really love that because it means that they were being locked into Microsoft. They don't have to worry about shuttling data over and over again just to get it into a particular format for a particular analytics or data engine.

So the second promise we thought of with Fabric is really a lake-centric and open architecture. The third one is really about empowering every business user. So we built all the data in Fabric into every part of the Office experience. So it's built into Power BI, it's built into Teams, it's built into Excel, it's built into PowerPoint, it's built into SharePoint. With all the governance flowing through, all the security permissions flowing through, because you want to put this data in the service of business. And that's something that is really, really exciting for customers. And the fourth promise is all of the AI capabilities that be built into Fabric. 

Every part of the Fabric experience has a built-in Copilot, as you would expect from Microsoft these days. But it also accelerates the entire data journey, but also helps you build these new gen AI applications much more quicker than you otherwise would have. So that's kind of how I think about the areas we're investing in.

Tyler Radke:
Got it. Got it. It certainly seems like a pretty compelling consolidation message for customers. I know that's a big theme that we're hearing from IT executives. I guess I'm wondering how you are positioning Fabric in the context of also some really strong partnerships with ISVs. Out at Microsoft Build, we were out there in Seattle and you highlighted companies like Snowflake, Databricks, MongoDB. How do you sort of think about where to partner versus pushing your own cloud-native services? And how does that work for customers if they're trying to consolidate?

Arun Ulag:
Yeah, it's a really good question. I'd say, hey, first Microsoft is a hyperscaler. And as a hyperscaler, we have to do two things simultaneously. The first is making sure Azure's a great platform for ISVs. So it's awesome to have industry-leading ISVs like Databricks, like Snowflake, like Mongo, make huge bets on Azure because that makes Azure exciting for customers. That means that they can bet on Azure knowing that they have choice of industry-leading ISVs. And as these ISVs bet on Azure, they also make Azure better. It allows us to improve our services, provide more capabilities, et cetera. So that is number one for us.

Number two is that, as a hyperscaler, we also have a great set of first-party offerings that compete with many of these ISV offerings. We are not unique in that other hyperscalers do it too, but we do have really, really compelling offerings in market, and it's great for customers because they have really good choices. And that's what we are doing with Fabric. That's what we're doing with Azure SQL Hyperscale, with Cosmos DB, with all of our first-party services. The third thing is that regardless of whether it's third-party or first-party, we owe it to our customers to make all of this stuff work together. That's why we owe it to our customers to make all of this stuff work together. That's why at Build, I had Christian Kleinerman from Snowflake on stage with me talking about how they're making a bet on Fabric as a native data store for Snowflake. We had Ali Ghodzi from Databricks on stage with me in November talking about the partnership we have with Databricks and how it's integrated into Fabric. So we really do think about all three things. Azure is a great platform for ISVs, making sure we have great first-party offerings, and we have strong interoperability between Azure services and the third-party services.

Tyler Radke:
Right. And I think with Fabric, it's been about a year and a half since the announcement out at Build, in May last year. What's the customer feedback and reception been? Any adoption statistics you can share with us?

Arun Ulag:
The customer reception to Fabric has really been absolutely incredible. Satya announced our last earnings call that at this point we had more than 14,000 customers, paying organizations, pretty much from industry leaders in pretty much every geography. Companies like Accenture or Kroger or Rockwell Automation or Zeiss, they're pretty widespread. So we've seen adoption everywhere. We also had our first Fabric conference in March, which at that point, Fabric had been generally available for four months, and we were surprised when 4,500 people showed up. We didn't expect that kind of reception.

Tyler Radke:
We were one of them actually.

Arun Ulag:
Thank you. So we were pleasantly surprised and we also talked to a lot of customers, but why they're so excited about Fabric, and there's lots of reasons, but three reasons show up. The first is just time to value. Instead of putting all of these complicated things together, Fabric gives you all of the capabilities end-to-end so you can build solutions much more quickly than you could ever do before. A great example is One New Zealand. One New Zealand is the largest telco in New Zealand, and they were able to build a solution end-to-end and get it in production in just three weeks with Fabric. This thing would've taken quarters or semesters or much longer in the past. So first thing we're hearing is just time to value, really matters to customers.

The second thing we are hearing is costs. Now, let me go a little bit deeper here because I think it's worth understanding. If you look at the data and AI infrastructure, you string multiple of these PaaS services or platform service together to create a solution, each of them have different compute meters, so you're forced to create lots of pools of isolated compute and they're not all running all the time. So, there's a lot of wastage in the data and AI infrastructure. Now, what we are doing with Fabric is all of the compute in Fabric, whether it's data engineering or data warehousing or PowerBI or whatever the compute is, all compute is virtualized and serverless. So you just buy one thing, Fabric compute. So the same compute overnight could do a lot of data integration, maybe some data engineering, maybe some AI, and in the morning as your people walk into the office, the compute flows to PowerBI for business users and to SQL, right? This means that customers can consolidate a lot of wasted compute into Fabric and get much higher utilization.

One example, a large consumer company in the UK, they were spending about, publicly traded, they were spending about $165 million in their data infrastructure over five years, most of it running in competitive clouds and competitive products. And they were able to move their entire stack from what they had right now into Fabric. And their spend goes from $165 million over five years to $45 million. So they're able to put $120 million back into the business. So, really massive savings for customers and obviously huge opportunity for Microsoft because our spend went up substantially as a result of the customer saving money. So number two I would say is cost savings.

Number three is really Gen AI, and that comes in two parts. One is because Fabric has Copilot built in end-to-end, so it really accelerates time to value. It's not just Copilot for a single link in the chain. It's Copilot across the data journey, whether it's data factory or data warehousing or BI, Fabric helps accelerate the entire time to solution using Copilot and that customers really love. The second part of it is really getting data ready for Gen AI applications. Because Fabric on OneLake is built into Azure AI, Azure AI studio. So you're building these Gen AI applications and you need to get the data estate ready, Fabric makes it possible for you, and it's just built into the AI stack as well. These are the things that we are hearing from customers about why they're so excited.

Tyler Radke:
And as you think about the cost savings, I mean those are some pretty impressive numbers. Is that primarily cost savings from other hyperscalers and other competitive products? Maybe some of those which you partner with? Or how do you sort of think about where that budget for Fabric is coming from?

Arun Ulag:
I'd say, again, it varies customer by customer and customers experience different levels of savings. So what I shared was one example. In that particular case, the customer was on a competitive cloud using a whole bunch of competitive products, some of those products available in Azure as well. And for them, they had a change. They had a new chief data officer come in and he looked at this and said, "Wait a minute, we're spending all this money on a data infrastructure."

The second is not just the money they're spending on licensing, it's also the heavy investment in engineering to make all these different products work together. A significant chunk of its capacity was just on wiring things together, configuring things, monitoring things, making sure one product worked with another, et cetera, which doesn't accrue to business value.

And the third thing that they heard from the CFO is that, "Look, if you want to make all of these AI or BI investments, well, you're not going to get a much bigger check. So you go to free up funds to be able to invest in these areas." And for him, he found out about Fabric at the right time, which helped to make the choice. So that's what happened in that particular case. But we generally see cost pressures exist in customers. They want to get more value, they want to accelerate time to value. They don't want to always spend more, and we have some really compelling options for them.

Tyler Radke:
Yeah, it sounds like great scale for product that's only about year and a half old in some mindsets.

Arun Ulag:
That is true. And I would say that most of the components of Fabric are not new. We've been in data warehousing for decades. We have been in real-time intelligence for a long time. We have been in business intelligence for a long time. So as much as Fabric is new, it's built on a robust set of technologies that have wide market adoption, that have matured over a long period of time that are used at scale.

Tyler Radke:
I'd love to hear from you just the significance of the engineering organization that you have working on Fabric and then also what you're most excited about, maybe what customers are most excited about in terms of what's coming on the roadmap.

Arun Ulag:
Yeah, it's a very big investment for Microsoft, so it's a very big bet. You hear Satya talking about, you hear Scott talking about it. So Fabric and our data stack is a big bet for us, and it's not new. We've been investing in the data space for decades now. So Microsoft has always been a big player starting from when SQL Server launched, I guess 30 years ago, right? So it's a very big bet.

Now, when you asked about some of the innovation that I'm most excited about, and I wanted to call out two things. One is OneLake, which is part of Fabric. And if you look at most customer architectures, the data lake is a core part of a customer's architecture. It's the easiest place to store your data. But data lakes are pretty messy and complicated today. If you look at what a data lake is, it's nothing more than a bunch of storage accounts provisioned by developers, which means customers have to write a lot of code, a lot of infrastructure to make data lakes usable, not just for IT, but for business.

And what we saw as an opportunity to simplify the entire data lake infrastructure. And you use an analogy if you use office for example, you just let OneDrive deal with your documents. You don't have to worry about which storage accounts where it lives. OneDrive just takes care of it. So that's why we introduced OneLake. In fact, we picked the name so that the analogy to OneDrive will be clear, but OneLake basically makes data lakes very, very easy to work. It not only provides storage out of the box, but it also allows you to virtualize storage and connect to storage data, whatever it lives. You might have data living in other parts of Azure. You might have data living in on-premises systems. You might have data sitting in AWS or GCP. OneLake allows you to simply shortcut the data wherever it lives and provide business value.

And customers really love that because we don't begin every customer conversation with migrate everything to whatever my platform is. First, we talk about delivering business value with leaving the data where it is. So not only provides storage out of the box, but it also virtualizes storage and allows you to get to business value very, very quickly. So that's been a huge innovation for customers. Customers are really excited about it.

The second area which we launched a public preview, it's not yet generally available, it will be in a few months, is what we refer to as real-time intelligence. Now, as the world has gotten increasingly digitized, there's a lot of data out there that is coming out in real time. It might be trucks sending telemetry. It might be NFC sensors in your supply chain. It might be applications providing telemetry logs getting written. And generally real-time data is very hard to work with.

It comes in very large volumes. It's semi-structured, the schemas drift over time. So as a result of it being very hard to work with people don't use a lot of real-time data today. When you look around and work with businesses, you'll find that most of them are working with data that is in batch mode. You'll be lucky if it's from yesterday, often it's a week old, it's a month old, it's a quarter old. And back to my car analogy, it's like driving, working with batch data is driving by looking at the rear-view mirror.

But all this data is out there. So with real-time intelligence and Fabric, we make it drop-dead simple. You don't have to do complicated things like spin up Kafka clusters or Rights Park streaming jobs. Fabric takes care of all of that for you. So you're really focused on business value. And just like OneLake, we can work with events from everywhere, IOT events from your sensors, events from Azure, but events from AWS and GCP as well. We make it really, really simple to work with it. And I see huge opportunity to help customers work with data in-real time, and it also substantially increases the value for customers and the time that we address.

Tyler Radke:
Great. Great. I'd love to zoom out and just sort of get your perspective since you've been in the space a long time where we are in this data modernization and GenAI journey, right? You talked about how obviously you need good data to flow into LLMs and build copilots and everything. If we use the analogy of a baseball game, I know that's overused, but where are we in terms of that maturity curve of that data modernization? And then conversely, as you start to think about GenAI use cases, POCs and everything, where do you think we are in that stage of adoption?

Arun Ulag:
Yeah, I think on the data modernization side, I think we're well on our way. A fair bit of migrations have already happened, but customers still have a substantial part of their data as they still sitting on-prem. So we still see a lot of opportunity ahead to help customers migrate and AI and GenAI is now providing more incentive for customers to accelerate their migrations to the cloud.

If I look at... In addition to migrations, we also see some additional opportunities. The first is a lot of customers are just interested... If they're not ready to migrate today, they still want to connect their data estate to Azure, to the cloud. So for example, we have Data Factory in Azure Fabric. It allows customers to connect their on-prem estate into Fabric, into Azure, and get value even before they do their migration. We have hundreds of thousands of these gateways already deployed by customers.

The other thing that we're seeing is a lot of interest in Azure Arc. Now Azure Arc is our multi-cloud on-prem management solution where you can get Azure value, where your bits already run on-premises or multi-cloud before you migrate to Azure. I think Satya announced on our last earnings call that we have over 36,000 customers using Azure Arc, which grew 90% year over year. So we are really seeing a lot of interest in customers connecting to Azure even before the migration.

The last thing I'd say is that, hey, these GenAI projects, there's a lot of them going on. While I would say a year ago there was a lot of tinkering and doing something with it just to learn. Now customers are becoming a little bit more thoughtful about where the ROI is, what is it time to value, how does it change their business process? And some of these things matter, and this is where I would say out-of-the-box solutions like GitHub Copilot or M365 Copilot, you can say, "Hey, you can get to business value without doing a lot of work."

So those things are attractive for customers and they're being a little bit more thoughtful about prioritizing the AI investments based upon business value than maybe a year ago where there was a lot of experimentation going on.

Tyler Radke:
Right, right. That's helpful, helpful color, and obviously GitHub Copilot is kind of off in those races for you, big success story. I'd love your perspective, just as you think about some of Microsoft's traditional data products, be it on the data warehouse side with Synapse, maybe it's called Fabric now. I don't want to-

Arun Ulag:
It's Fabric.

Tyler Radke:
But just as you think about the role of, say, a traditional data warehouse or a transactional SQL-based databases, as we start thinking about emerging GenAI architecture, LLMs, a lot of JSON documents, vector databases, what role do those play? I mean, do you still think there's a huge growth curve ahead for data warehouses and traditional databases, or do you think we're sort of entering this massive tectonic shift?

Arun Ulag:
Yeah, it's a good question. When I look at the application patterns, when I think about transactional operational databases or data warehouses, I kind of feel like they're evolving more quickly today, Tyler than they ever were evolving before. And the reason is that very quickly, pretty much every application is becoming an AI application. And guess what? They're using operational databases or data warehouses or other parts of the data stack. So they're evolving more quickly today than they ever were before.

I see four areas in which the evolution is happening. The first is not new, it's just reliability, security, transactional performance. Those things still matter because these applications have to be reliable, they have to be secure, and Microsoft has a bit of an advantage there. If you look at SQL, it has a lot of security capabilities. We have customers using very large transactional volumes with very strong asset guarantees. If you look at Cosmos DB, it provides single millisecond performance. It's used by ChatGPT, the fastest growing consumer app in history. So I do think there's a lot of value that we continue to deliver in terms of just security, reliability, the core. So that's number one.

Number two, when you think about these AI applications, we see a huge opportunity to bring the AI capabilities into the database itself. So you'll see... You talked about vector databases, it's required for LLMs, the RAG pattern, the retrieval augmented generation is how people often build AI applications. Well, vector databases are now available as part of the database itself. It's built into Cosmos. It's built into Postgres, right? So you don't have to take the data out. It works with the database. It makes it easier to build these applications. In Fabric, we launched something called AI Skills that allow you to interrogate your data lake or your data warehouse with just natural language and get those results in an application. So we really see the AI capabilities now being infused into the data stack, which is again, a huge leap forward for customers.

The third thing we are seeing is really the fact that developers are getting more and more impatient. They want quick time to value.

Tyler Radke:
Have they ever been that patient?

Arun Ulag:
They're less patient today than they were, let's say... Because they don't want to waste their time. They don't want to spin up clusters, they don't worry about infrastructure, they don't worry about networking storage. These things should just work. So we are seeing a lot of interest in SaaS-based platform software as a service. If you look at Power BI, we've been SaaS from day one, when we started, launched nine years ago. We have 350,000 organizations on the planet that use Power BI, by far the world's leading BI service. If you look at Fabric, it's all SaaS. So we are seeing a lot more receptivity for developers for SaaS-based platforms because it accelerates time to value, it helps them get to those business outcomes much more quickly.

And the last thing I'd say is really the integrated data estate. Because if you look at an enterprise customer, they're not happy with all these silos of data, all these proprietary data formats, all these walls that exist between different applications, different data warehouse, different data lakes. They want all of this thing to come together. They want all of this to provide business value regardless of which cloud it lives on. And that's why we've been thinking about OneLake and really embracing multi-cloud and helping customers accelerate a business value.

So to your question, we see databases and data warehouse evolving much more quickly. These four areas are perhaps the biggest areas where we're seeing a lot of innovation.

Tyler Radke:
Right, right. So we talked a lot about how... A lot of positive receptivity to Fabric and we're well along this data modernization journey. I'm curious on sort of the constraints. What are the biggest roadblocks that you see for customers in terms of not being able to go down this data modernization journey? And then also on the GenAI front, we talked a little bit about prioritization, but would love your perspective on those constraints.

Arun Ulag:
Yeah, I mean, customers are doing this extensively. And if I think about constraints, I'd probably call out three areas.

The first is just complexity. Building GenAI applications is not easy. These are new application patterns. Not a lot of developers are familiar with them. Lots of services to string together, learning how these things work. Lots of work on that front. So complexity is something that customers are wrestling with.

The second thing is really cost. And we talked about that a little bit before, but these things have to... There's not massive new budgets for overall IT spend to go invest in all of these projects. If this thing goes up a lot, something else has to adjust, right? So customers are looking for cost savings and making sure they can fund these initiatives.

And the third thing we see is really responsible AI. Because these LLMs are new, they behave in different ways, often unexpected, but you want to make sure that the LLM that's providing customer service for your customers is respecting your brand promise, is safe, is not hallucinating, is not... Avoiding output that offends your customer. And that's where we are making a lot of investments on the responsible AI side to do this in a way that helps customers.

So these are the biggest areas where I find that it does create friction for customers to overcome, to be able to go on their AI and GenAI journey.

Tyler Radke:
Got it. That makes sense. I'm curious, as we sort of connect all the dots together, we talked a lot about Fabric and the whole Azure data platform, which I think is really unique versus anyone out there. How does this all add up to Microsoft's overall GenAI strategy in your competitive position? Can you bring it all together and just talk about how this ties in with the goals around GenAI?

Arun Ulag:
Yeah. I think overall, I think Microsoft in a very, very strong leadership position. And when I think about our competitive advantage, I'd probably call it four areas, some of which we've talked about before, but I'll just recap it for you.

The first is that we have a very complete data and AI stack. And the data and AI stack that we have is built in-house. It's not an acquired collection of pieces that somehow don't work together, right? Because they're built in-house over a period of time, they've had a chance to mature, they're engineered to work together, and we are bringing it all together with Fabric. So a really complete data stack that we're bringing together with Fabric.

The second is really a GenAI leadership, AI and GenAI leadership. And it's very extensive because we have a comprehensive set of GenAI models, everything from the leading frontier LLM to small language models to thousands of models from third parties all being available in Azure with responsible AI. All of those things are very an extensive set of assets that customers really, really appreciate. But it's not just about the models we offer. We also have very strong first-party services that use these models. Things like GitHub Copilot or M365 Copilot or Dynamics Copilot, which gives us an opportunity to add value to customers, but it also gives us an opportunity to learn, right? And inform what kind of tooling we need to provide for others to do the same thing. So I do think that we have very significant strengths on the AI and the GenAI side. 

The third thing is really our advantages with developers and developer tools, right? The most popular tools on the planet are the ones that Microsoft runs, whether it's GitHub or VS Code or Visual Studio. 

We have well over a hundred million developers building on the Microsoft tools. And many of them are fans. They love the tools that they get to work with. And we have a really big opportunity to connect this tooling to Azure infrastructure, make it easier for them to discover these Azure services and consume them, leverage the Copilot experiences to guide them appropriately. So lots of advantages with developers. 

And the last one is really advantage with business users. Because eventually, as we talked about, all of this data is in the service of business. And most of the business users on planet earth are using Excel, they're using Teams, they're using Office, they're using PowerPoint, they're using SharePoint, they're using Power BI, and we have the opportunity to use all of this data to inform all of these business users. So these, I would think about our sustainable competitive advantages as the world is transitioning to the era of AI.

Tyler Radke:
Right. And as we think about that positioning is one of the best position hyperscaler for the world of AI, certainly the numbers from Microsoft have been very impressive with Azure Growth, north of 30% in commercial bookings up in the high teens last quarter. One of the things we've been hearing is just how the AI positioning or GenAI positioning is actually just contributing to more share gains within the core sets of services. I'm curious, is that that something you're seeing and how significant is the Azure data platform is part of these commercial booking strengths that we've seen?

Arun Ulag:
Yeah, you're absolutely right. As people build these GenAI applications, they're not just using the LLM in isolation, right? They're using Cosmos DB, for example, to store the chat history, right? They might use Azure AI search to be able to provide back to search on top of the database. They might unify their data in OneLake across clouds to be able to feed it to the LLM, right? So we are seeing a lot of growth associated with the AI workloads because it's not just about the AI workload. I think we shared in our last earnings call that we have over 60,000 customers using the Azure AI services. And we said there, we also shared that about half of those... And the growth of Azure data services among the customers using our AI services grew 50% year over year. So we do see substantial opportunity as customers are building these AI capabilities to not just provide the LLM, but provide all of the services that help the application get business value.

Tyler Radke:
One of the things you mentioned earlier is honing in on that developer focus, and obviously developers are even less patient these days in terms of things they demand. As you sort of think about making sure that you have relevance with that next generation of developers, I know that's always been a focus for Microsoft. But what are some of the things that you're doing and your organization to make sure that you don't lose that momentum?

Arun Ulag:
When I think about the developers, especially in the data and AI space, it's just such an exciting time. There's so much innovation, there's so much energy in this. It does feel like very energizing. When I look forward into the biggest opportunities where we invest, I probably look at it in maybe three areas, okay. 

The first is really AI powered development. This is about GitHub Copilot. It's about the Copilot experience at Fabric, the Copilot experience built in the power platform. You can really dramatically accelerate time to value. You can train legions of new developers. You can help them write code, build solutions, document it, have the AI guide the developer every step of the way. Have the AI guide, the debugging experience, a documentation experience. So we see tons and tons of opportunity just in terms of the AI powered development. 

The second area that I would say I'm really excited about, especially my team is investing quite a bit, is really driving an AI powered data estate, right? We talked about OneLake and how it's abstracting the storage systems. But why wouldn't we bring a lot of the AI capabilities into OneLake itself, right? Why wouldn't we bring that into the storage system and help developers just say, it's just built in. There's nothing to string together. There's nothing to connect. It just works. It's a core feature of the data stack... Of the storage system itself. So we do think there's a lot of opportunity here to AI empower the data estate and accelerate time to value for developers. 

The third thing I really think about is less about developers and more about business users. And that I think about the opportunity to provide AI powered insights. If you look at most of the business users on the planet, very few of us can afford to have a business analyst who can analyze all your data and tell you what your data means.

Most of us cannot, right? But here's where AI can step in. So it can look at the data, it can analyze it, it can find those insights. It can coach the business users to making better decisions and better outcomes, right? And I see huge opportunity for us to add business value for all the business users. And there's hundreds of millions and billions of these people out there that can make better decisions based on AI. So those are the three that I'm most excited about. AI powered development, AI empowering the data estate and AI empowering the business user.

Tyler Radke:
Yeah. So bigger picture question. Obviously Gen.AI has bursted onto the scene over the last couple of years. It's been pretty transformative to watch. As you think about the next five years, what are some of the things that you're excited about? What are some of the things that maybe you think the market is not talking about, whether we're too distracted with Gen.AI or anything else? What are you most looking forward to?

Arun Ulag:
I think, just I would say the biggest thing that I am really looking forward to is really democratizing access. The world is very large. We have lots of people in different countries, in different organizations with different economic situations, lots of companies with different abilities to invest, and we need to bring everybody along. This cannot be just technology for the top of the top of the pyramid. So I do think that Microsoft, with our mission, with our scale, with our ability to think about democratizing actions, driving down costs, getting these capabilities into production, empowering business users has a really unique opportunity to really lift the whole planet up. So for me, that's the part that I feel is the most exciting on the journey that we're all on together.

Tyler Radke:
Yeah. Great. Well, I know we got a couple of minutes left, but I did want to turn it back to you if there was anything that you wanted to cover that we didn't address. And maybe just leave the audience, the main takeaways and what the focus is from your end.

Arun Ulag:
No, I think you covered a lot of ground here, Tyler. I don't know if I have a lot more to share. But I just want to reiterate, it's just such an exciting time. There's just so much innovation happening, so much opportunity with customers, and I'm really, really excited about the opportunity ahead. So thank you.

Tyler Radke:
All right. Thank you very much.

Arun Ulag:
Thank you.