 Hello and welcome to the role of customer partner and vendor collaboration in enterprise open source strategy. My name is Jose Miguel Parrella. I'm with the open source ecosystem team at Microsoft. Over the next half an hour, I'd like to share with you how Microsoft's approach to collaboration and partnerships has transformed with open source and some of our learnings are on the way. Hoping that it can help you and your program engage with your value chain and the open source community at large. I have been working with open source at Microsoft for over a decade and had the opportunity to contribute to many of the milestones that you see here. Some of these are product related. Some of these were announcements that signal more strategic investments. Some were contributions to third party projects and others involved releasing of Microsoft's IP as open source. But these are all representative of Microsoft's open source transformation where today over 30,000 employees use GitHub for work and over 150,000 open source components are used to deliver value to customers and people around the globe in millions of different ways. But something that particularly struck me when I joined Microsoft was the power of partnerships. It was clear to me that partners were going to play a critical role in Microsoft's open source journey that Microsoft wasn't going to do this alone and was willing to stand on the shoulders of giants. Now this meant changing many things. How we engage with partners and even who we engage with. One of the most important examples of this today remains how we work with open source foundations and other governance bodies. This represents a shift from work that used to focus mostly on standards and it requires developing a mindset, a skill set and a cultural affinity that spans the large and growing numbers of organizations that influence several aspects of Microsoft business today. Now this is important work that we continue doing. You can visit open source at Microsoft.com if you want to learn more. But I thought I'd describe some specific collaboration models that we're seeing more of today. For example, cross industry collaboration where we see a group of somehow unlikely partners are increasingly happening powered by open source. Examples range from tackling problems like separation of concerns in cloud native application model. What we do with Alibaba and others in open app model or concerns like confidential computing consortium that brings together from hardware vendors to cloud providers and end users as well. Now this cross industry collaboration is also seen at a more granular level in certain technology ecosystems. I could mention perhaps on its runtime in the machine learning space or yarn in the Fatchist upper foundation analytics space or our partnership with OpenAI. The reality is that the harder the problem and the more impact it has in both society and people that more often it seems like open source is helping bring participants together across industries. Two examples of here include differential privacy, OpenDP in particular, OpenData. True not only this OpenData initiative but also several other work that Microsoft has been doing around licensing for data sets through open source licenses that are on GitHub. There's also healthcare environmental sustainability and we participate in several of this directly as Microsoft as well as through GitHub. If I had to pick one such challenge from the top of my head, I would say that be our joint responsibility to security open source software supply chain. It's something that no single company, no single provider, no single Linux distro, a single foundation or project can tackle alone. And when it comes to identifying threats, rethinking disclosure and developing security, tooling and best practices, the open source security foundation reflects this cross industry collaboration with participants that include JP Morgan Chase for example. Now, in addition to actively participating in governance forms like Linux foundation or the cloud native computing foundation, and signing with industry peers in certain contribution spaces like Yarn and engaging in cross industry collaboration for broad impact problems like differential privacy. I'd like to talk a little bit more about our work with commercial partners because it best reflects the open source transformation with Microsoft. I like this different mindset that this type of partnership requires. Now, Sonic stands for software for open networking in the cloud. It's an open source project released by Microsoft in 2015. It comprises code base as well as specs. It was originally assigned to help with flood service provider software defined networking needs in the cloud. Every packet that comes in or out of a Microsoft data center today goes through a top of rack switch running Sonic. And it has a modularity that allows different partners to plug their hardware offerings. As a result, there are about a hundred supported platforms in Sonic from a dozen different vendors. And some of the things that we've been doing with Sonic include the fact that get-have-issues and pull requests are the place where the development of the project happens in the open with contributions from many people that are not at Microsoft employees. Also something else that we've done with Sonic give everyone the chance to grow the Sonic brand by establishing a quality bar, both in technical as well as in general and user experience standpoint on what really makes a great Sonic derivative or a Sonic distribution a great customer experience. So as you can see this type of collaboration this partner industry collaboration not only creates opportunities for a lot of the hardware vendors that can use Sonic to go to market. And today there are Sonic distributions there as commercial offerings from several of these partners but also requires a different approach a different mindset, a different thinking about governance and it's still a long-term investment that still requires every single bit of help and time and resource investment as any other kind of project but it has an interesting commercial implication that again is a reflection on the transformation on how this type of collaborations are happening. Now one other collaboration I'd like to highlight is how we work with partners to build solutions in Azure to build things in our platform is not about keeping an arms length from a lot of these different collaboration forums but in many cases like with the commercial open source companies that you see here is that joint engineering, joint operations and joint support that materializes in different ways depending on the nature of the service but results in an integrated experience for customers with integrated identity integrated security and integrated billing is what we really call jointly built. These are solutions you can buy from the Microsoft price list this are joint SKUs, joint solutions join go to market, join services. In the case for example of Azure Red Hat OpenShift not only has Red Hat Proctax OpenShift which is an open source project but Microsoft and Red Hat have open source the control plane of the service which is the Azure Red Hat OpenShift research provided or RORP open source don't get have today. And these are all great examples of how we can partner that cultural affinity between Microsoft and the commercial partners commercial open source partners can translate the benefits for the open source ecosystem because all of these companies handle communities handle their project and that they understand upstream and downstream project and product and whether it's innovation or simply fixing experience patching security issues or whatnot where one more participant that knows and is in the long term to bring all of this learnings from going into production and going into market back to the open source projects. Now, one more example I'd like to provide on a particular type of community industry collaboration comes from our Postgres team. There is a significant Postgres investment at Microsoft. We have several core contributors to the Postgres project working at Microsoft and we offer a managed Postgres service. It is every extension and every contribution we've made is open source and we continue innovating in this space with things like PJ Kron which basically helps with scaling background workers in Postgres scenarios in a more idiomatic or better integrated way. In the case with PJ Kron which again is an open source collaboration is that it was not just the brainchild of Microsoft it was actually the collaboration between Microsoft. Amazon, a competitor that offers also offers a managed Postgres service and Salando, a retailer, a customer that uses Postgres and it's this type of collaboration that we also see in some of the scenarios that I described like Onyx Runtime or in the cloud native computing foundation space where more and more we coincide with others oftentimes competitors, other industry participants, industry peers and customers that are doing this contribution in the open which is quite amazing and again another example of the type of collaborative flavors of collaboration that we are often finding. Again, a lot of this is not only commercial it's not only about creating opportunities which we still do is not just about being an active participant and the governance bodies of things that influence the business interests of Microsoft or of your company but it's also tackling big problems and coming together to offer solutions that customers and the community at large really want like in this case, this particular Postgres extension. If I had to paint a little bit of a framework I would say that working together in open source starts with collaborating with the industry starts with being present in all the governance bodies it involves the building of our platform with others oftentimes that means bringing publishers into our marketplace, establishing partner relationships partner programs, partner channels but also going above and beyond and building with partners which is something that we uniquely do through this joint engineering, joint operations, joint support and the integrated experience and that long-term commitment to go through the upstream open source communities through and with our partners. There are two customer related examples here that I have at the bottom and I'd like to talk about one of these two a little bit in depth. Of course, Microsoft does have like many software companies a consulting function. This is what I'm calling here coding for customers. In this consulting function because we work with enterprise companies these of course, there's a lot of open source usage whether it's office dynamics of front end solutions around ASP.NET, .NET Core itself being open source helper solutions around SQL Server running on Linux containerized solutions. These are all spaces where our traditional consulting customers keep asking for more and more open source but I wanted to focus on coding with customers which is something that Microsoft that we do through our commercial software engineering organization and it's in this coding with customers where we see some reflection of the motivations around the broader collaboration both with commercial and non-commercial entities. In this code with engagements we're seeing a ubiquitous open source usage that includes languages like Python and Go, solutions like Kafka, oftentimes all of those running in Linux containers pulling the OCI stack pulling the Linux operating system. In this engagements we use a standard legal framework that describes jointly owned IP which focus on reusability and respect for the open source licensing of anything that's brought into the engagement just the result of joint decisions and joint discussions with our customers and like I said, it's something that we see very often. We find that we might be improving on a particular way of doing something and that results in joint upstream contributions as well and a whole motivation behind this is the ability for Microsoft to understand how open source is being used in different industries. Commercial software engineering engages in industry friending from healthcare to public sector. Some of the customers we engage with include Alliance, AXA, UBS, HSBC. So that is critical for us and we see the same thing that you see in terms of open source and they're pinning a lot of trends around digital transformation as well as entire categories of technology in particularly or basically defined by open source. Now, one of the big learnings here is that long-term sustainability is as much as a concern in this type of code with engagements of vendor, this case cloud service provider and user as it is for any industry peers or any cross industry collaboration. No one really wants to be in the business of rolling out code no matter how good the code is no matter how helpful we think it might be for someone else and then failing to create a community or failing to care about its long-term sustainability. So this is an aspect we've learned from particularly in the early stages of our work here with some Kubernetes and cloud-native related projects around best practice frameworks for example where it's always hard to start this engagement thinking how do I decouple this? How do I design this in a way that others can naturally come that naturally attracts contributors and future maintainers that requires understanding you having some product understanding what's gonna be the value proposition who's gonna be the audience of this project of this repo that I'm gonna be standing up and of course much more than that what's the governance of this what infrastructure is gonna be necessary and oftentimes also requires recruiting some critical base do we wanna talk to others in our same industry in the case for example, let's say banks are there other banks or there are other peers I can talk to and see if there's any across sorry industry peer collaboration we can put together around this project. Now interestingly some of this comes from perhaps underestimating non-code artifacts. When we focus mostly on code and this concern is almost brings everything to a stall it's a real blocker. When we consider non-code artifacts like specs like architectures and other deliverables then things get a little bit interesting because we can make meaningful open source contributions even though it's not necessarily a software framework or something that resembles a software product. So this is an area we want to explore more on. In fact, I would say that the internal training at Microsoft that we have for all of this organization that performs the code with engagements internally we call this open hack this is actually open source. So the entire training materials for all of this type of engagements are open source already as you know at Microsoft like it's a normal and in the cloud all documentation SDKs client libraries et cetera are also open source. But there are so many artifacts that don't require necessarily that cognitive aspect of you need to bind to this framework or this particular piece of technology which can be a little bit of a limiting factor when considering adoption of a lot of this. So this is an interesting finding for us that how even in this type of engagements which are these are non billable type of engagements non prescriptive type of engagements we find many of the same motivations and challenges that drive this cross industry collaboration of which we have many examples that I've talked about today. We find that long-term sustainability remains a big topic. We find that cross talking to industry peers is an aspect that could potentially help here that that matchmaking across industries is also another aspect that could help here. And certainly there are forums like this forum where we can talk about several of this problems in client coming around. And this is something we truly believe there's more investment and more that we can be doing in this space. In fact, I am very interested in your learnings working with others in open source particularly working with others in your value chain and particularly working with the ecosystem and the community at large. We are seeing again an increase like you are here today we're seeing an increase of end user participation in several of those governance bodies and trying to understand what else can we do as trusted advisors and cloud service providers and software companies to ensure the maximum impact and the maximum value for the open source community at large. To summarize here are five of the models that I've talked about today in terms of collaboration with others in open source that collaboration with industry and active participation in governance the development of the basic partner ecosystems to build our platform but also going with commercial open source software companies building with VAM services in our platform that then allow us to deliver more value to the open source ecosystem. And obviously working with customers including that coding with motion for us that has yielded some interesting learnings into reusability and what things must be considered beyond just licenses and other technical factors and the code itself to ensure that these are successful and impactful contributions for everyone else as well. Like I said, I'm really interested for input and more than happy to get in touch via open source at microsoft.com. We'll also open it up for a few questions in just a minute. If you'd like to learn more about how we do open source at Microsoft and the kind of things we do with open source at Microsoft you can visit opensource.microsoft.com I'm particularly interested in any follow up conversations you wanna have with your team with others in your industry I'd be delighted to share a little bit more details about some of this engagements but for now let's open it up for a few questions. And again, thank you for making the time and enjoy the rest of the forum.