Oktane19: Accelerating Your Integration and M&A Strategy
Crystal: So, my name is Crystal. I'm from Okta Product Marketing. You guys have been here maybe two, three days already. Hopefully, you guys have had a chance to see how Okta is able to help integrate apps and people. In this session, we're going to be talking about a very special type of integration; the integration of organizations in mergers and acquisitions. I'm going to give a brief overview of how Okta can help with that. I'm sure you guys know how we can integrate some of these applications, but I just want to put a perspective for mergers and acquisitions on top of that. And then we'll also be hearing from our customers at Moody's on how Okta has helped with their M&A activities. So, let's go ahead and get started.
Crystal: First a word from our legal department. As Nicole mentioned, the TLDR here is "things can change". So, to get started for real. Every year Deloitte does this study, one of our partners on mergers and acquisitions, it's called "The state of the deal", and in this study, they basically survey a bunch of companies both private and public. I believe it's over 1000 corporations in the U.S, and they study the M&A trends. And for this year, 2019, they realize that there were three top strategic goals across all of these organizations for mergers and acquisitions. They are acquiring technology, diversifying and expanding your product area, and then finally, and this is the biggest one this year, expanding your customer base.
Crystal: Now through all these different acquisitions and mergers that they looked at, there was a single theme that they realized the executives were saying was the most important for the success of an M&A. Any guesses to what that was?
Speaker 2: Speed?
Crystal: Speed? Good guess, not quite. I wish it was identity, but it's not either. It's effective integration. Now there's a lot that goes into integration. There's a lot of different challenges. There's a lot of different people and different stakeholders. And it's not always just about tools and technology, 'cause you're really also trying to bring together different people from different organizations and also trying to combine that culture, right? Of course tools and technology can help, but take a look at the different challenges.
Crystal: First, we thought your business challenges, right? A lot of the primary goals here are "how do we get that return on investment faster?" To do that, we have to make sure that we can effectively collaborate between the acquiring company and the acquired company. Next, we have to look at the IT teams. They have a huge job to fulfill. There are different disparate tools and technology between the two different companies. There might be some on premise things. There might be things in the Cloud. These tools and technologies may not even talk to each other natively, so how do we integrate these things so that they are able to talk to each other, how do we reduce complexity, really, how do we streamline the IT processes?
Crystal: Next, there's security, right? These folks also have a big role to fill, and it's a bit of a nail biter in M&As, because you don't really know what you're going to get until you start digging in and doing that security due diligence. They're looking at how to close security gaps. What types of risk are we inheriting as the acquiring company? Deals fall through because of this, right? So what they're ultimately trying to figure out is how do we provide the right access to the right people for the right applications for them to do their jobs. Now, that's all going to be internal to the workforce, right?
Crystal: So, we have one more group that cares a lot about the M&A, but they're not part of either the acquired company or the acquiring company. That's going to be the customer, right? They're sitting over there to the side wondering "How is this going to affect me? As a consumer, supposedly you guys did this deal to benefit me, I want to make sure my experience is going to be just as good. I don't want anything to change, but wait, you guys have to make it better at the same time, 'cause I want access to all the new resources the parent company have."
Crystal: So how does identity help in this, and how can Okta help? Well, when we talk about identity in M&A cases, our primary goal here is to streamline and secure access. In terms of that, what are we talking about? Let's take the best of cloud apps from both the parent company and subsidiary. I'm going to use parent and subsidiary 'cause it fit on my presentation better, and it's easier to say. Let's make sure both users from both companies can have centralized and streamlined access to that through single sign-on. And then let's also do that to our on-premise applications. And at the same time, while we're talking about those on-premise applications, let's see if there's any redundancies or things we can move on to the Cloud, and gets rid of some of that more costly on-premise infrastructure.
Crystal: Next, let's take those directories from the parent and subsidiary, and let' make IT's job a little easier by giving them a single pane of glass. And this is also going to provide visibility for the security teams to make sure that they can see who has access to what and be able to control that access for the tools.
Crystal: Finally, let's start automating some of the routine processes; Onboarding and the off boarding, when we bring in users; whether they're internal or contractors, or your partners or whether they're even customers. Let's start creating processes so that we can do this automatically.
Crystal: So how can Okta do this? What are some of the benefits? First, we support that flexible architecture, every M&A is going to be a little bit different, and we provide that flexibility for our customers. This may seem like the most simple set up, we have one big happy family, everybody's merged together, there's the parent. We have access to all our apps and then we have one big global AD. But a lot of organizations don't want that. You guys heard this morning from Albertsons. They're a national company, but they still want to connect to their local communities. So whether it's for geographical reasons or sometimes it's compliance reasons, if it's a global company, we do want maintain some autonomy. So we also support hub-and-spoke architectures, where the subsidiaries can have access, and their own tenants, they have access to their own applications, and they have access to their local directories, tenant apps, ADs, what have you, but then they can also get access to the resources the parent company provides. And the parent company can also see the different users and workers in these subsidiaries.
Crystal: So that's one side. The other side is going to be the customer. So an idea to enhance the customer experience starting with the first touch, which is typically the long on-experience on your website. So here, let's do things like IDP discovery, where we can route customers on the back-end, depending on their device, where they're coming from, and also domain, or location, and route them to the correct identity provider, 'cause some of your subsidiaries may not be using the same IDP as your parent company. And let's also enable social opt for them, so that they have easier ways to log in, and they're using something they might already have a password for, for example. And of course, you can also do this for your workforce customers as well.
Crystal: So, that way you're also able to provide them the same experience they were used to as a customer of subsidiary, but then at the same time they have really easy access to the new products, the new experiences that the parent company can also provide. That's because on the back-end, we're able to help import these users and import these customers, and we also have flexible ways to do that. Of course, we can do bulk imports, we can also do staged imports. If you were at the UD, what's it called...the UD session yesterday, you learned about some of the enhancement we're planning, the advanced features, so that we can say the Hadoop users who may be customers of both. And so again, we're also providing that flexibility. We can do Just-In-Time imports, and leave it kind of up to the customer on when they want to be migrated into the database.
Crystal: In summary, Okta can provide that day one access needs in an M&A, for things like consolidating AD, or might I say, eliminating AD, adding single sign-on and making sure everybody has access to the apps that they need on day one. But because M&As don't always take a single day, most of the time they don't, we can also help you achieve the future goals by continuing to streamline, continuing to set up processes to help automate onboarding and off boarding, and manage your external identities, including partner identities and customer identities.
Crystal: So that's it for my spiel. I want to, so all of that will help fit in and serve your goals of effective integration, and hopefully a successful M&A. And with that, I want to welcome Keith Berry and Garinder Bath from Moody's onto the stage.
Speaker 2: Oktay, thank you, and thanks for turning up at the end of the second day. My name's Keith Berry. I am Executive Director of Moody's Analytics, part of the executive team. A long time ago, I had technology background, and now I'm very much kind of on the business side of things.
Speaker 2: So Moody's really has two core components. We have the rating agency, which is what most people know us for, but then we also have a company called Moody's Analytics which is a data analytics and software company. And we've been growing rapidly over the last 10 years, since we came into being, and our goal is to help our customers which tend to be financial institutions, banks, asset managers, insurance companies, make better, faster decisions using technology, using software, using data and analytics.
Speaker 2: Over the last 10 years, I joined the company where the red flag is, we've grown substantially, about 12 1/2 percent a year, from $4-500 million dollars in revenue, to now $1.7 billion. But this chart really shows all the acquisitions we've done along the way. So, every year, two years, we add one or two acquisitions and if anything we've been speeding up. You can see the number of employees has grown from 849 to more than 7,000 now and the number of officers from 16 to more than 72, so this is kinda becoming part of our day to day as acquiring companies, about 50% of our growth comes through organics, so new things we build ourself, and 50% through acquisition. And when we do acquire companies, it's for many of the reasons Crystal said, new customers, new data. As a data and analytics company, we're often acquiring new data sets and putting them together with the data sets we've got. And that really means that our teams have to work together and the quicker we can hit the ground running after an acquisition and get people working together, really changes the dynamics of the whole acquisition.
Speaker 2: So the last acquisition we did in 2017, Bureau Van Dirk, was actually our biggest to date, more than $3 billion acquisition, more than 30 locations, and when we actually did, up until this point, very much approached acquisitions that Garinder's going to talk about in more detail, was to basically put everyone on to the same network, and then basically gradually grant them access to various services. So, 19 months into the BVD acquisition, was the time that people could actually really start collaborating and working together. And what we're going to talk to you a bit more about is how we did that differently right now with the Reich acquisition, which happened at the end of 2018, and some of the results we've seen.
Speaker 2: But as an executive team after the BVD acquisition happened, we kinda sat down with our colleagues in the technology and info-sect teams, and said "Look, how do we change this? We're going to do more acquisitions. It's not going to slow down, so how do we set ourselves up to when we do them, and it's probably going to be one or two a year, we can get people working together operationally, in like three months." And I literally remember being sat in that room and people just rolling their eyes saying, "It's impossible. There's no way we can do that." And so I think 18 months later, we've proven that we can do that.
Speaker 2: Collaboration around our business is getting more and more complex, as the number of locations increases, the number of people increases, collaboration across the business lines has been very key. How do we work with external partners? So, we're doing acquisitions, but we're also working more and more with partner organizations. So we were trying to find this set of solutions that will help us do that. And then we're really a technology company, and more and more developers, keeping that kind of development teams happy, and we have some pretty demanding people doing quantified ads, machine learning, big data, and analytics has been really important. And then we put people on the road a lot, when we go and implement our software at a bank, people often sat in the customer's site and maybe using a hotspot for a whole period of time, and kinda struggling with the VPN. So that's been another goal of what we're trying to do.
Speaker 2: Of course, the Moody's brand is pretty key to us, and kind of keeping our data and our customer's data safe is very key to all of that. So we kinda sat down with the team and said, "How do we do all of this, but at the same time, make sure we keep our data safe?" I'm going to pass it off to Garinder, who's going to talk a bit about how we've achieved all that.
Garinder: Thanks Keith. Thanks Keith. Hi folks. So, now that Keith has outlined the asks from the business, I want to talk about how we were able to solution those using Okta, and also how our integration strategy has transformed with Okta playing a key role. All right? So let's get started.
Garinder: We proceeded the first map ask that Keith first referenced into tangible deliverables from the technology perspective that we felt comfortable implementing. So we essentially broke this down into three work streams, those being acquisitions, development, and sales and support. And if you look at this, this essentially represents a business process pipeline of acquiring a company, working with them to build a product or solution, and then pushing that out to the hands of your sales teams, to your customers, and into the market. All right?
Garinder: Going deeper into each of these work streams, we can see that from acquisition perspective, we want to be able to achieve rapid integrations and quick enablements. For collaboration, allowing lines of businesses to collaborate with each other, allowing them to collaborate with external parties and also give our users and developers and open network to operate out of. And finally from a product and service perspective, giving our sales teams the ability to use a modern platform while providing our users a first class consumer experience. And keep in mind, all this has to be under the guise of proper controls, right, so that from a security perspective, we're assured, along with our customers in the security of the solutions that we're building and delivering.
Garinder: And how's Okta helping us with that? So look at it from an acquisition perspective, by leveraging Okta's capability to centrally manage and integrate user identities, we're eliminating the need or reducing the need to have that network integration. From a collaboration perspective, again, reducing the dependency on our network resources and perimeterizing our applications, we're able to do those quick enablements, such as collaboration applications. And finally, providing modern authentication solutions, such as SSO and MFA to our sales and support teams, not only equip them with modern tools, but also help us stand out to our customers.
Garinder: So now I want to talk about basically how Okta was able to be a key component in all these enablement, but equally important is the fact that during each of these phases, we had the proper controls and the granular security ability to be put into place here. So whether that's dictating access based off of security or network topologies, or implementing step up authentication with Okta Verify, based off of user behavior analysis, Okta was essential in helping us deliver the solutions that Keith first referenced in his ask and his objectives.
Garinder: So, let talk about integrations specifically, right? And I want to highlight the differences between how a legacy integration, a traditional integration was, and how we've transformed that process. So from a legacy perspective, an integration at Moody's was typically consisting of four distinct phases, and an implementation time could be up to 18 months. Now, the four phases are base enablements, network preparation, network integration, and a full integration.
Garinder: Now some of you guys might be wondering about this inverted pyramid, but basically what this shows is that from a feature perspective, a capabilities perspective, we're building in capabilities as we're going up in time, so it's getting bigger in terms of the capability of the feature sets as you go up the timeline. Looking at the details of each of these phases, from a base enablement perspective, we're performing network and security assessments, right? So depending on the complexity of the networks, depending on how big in size of that is, that's doing the, not only the security assessment, then that's followed by risk mitigation and remediation actions. And that again, can be a three month effort depending on the complexity of the network before we're able to move into the network preparation phase.
Garinder: And the network preparation phase is actually where we're doing the actual groundwork of deploying equipment to provide the end to end connectivity between the acquisition and the Moody's network. So whether that's procurement of circuits or configuration and putting in hardware equipment like the firewalls and routers and such. This is actually connecting the wires that establish the physical link.
Garinder: So now you can see, we're at six months of pre-work before we're able to provide the network integration, app integration phase. And that's essentially what the user cares about right? That's what's impacting the user is giving the user access to resources and applications which we don't get to until six months down the line.
Garinder: And what the last leg of this integration obviously is the hardware refresh and eventually the sun setting, and de-comming of the original acquisition network. So how does that compare with the modern framework, right? For one, the pyramid is right side up, but additionally, what we're doing is we've shrunken down the stages from four to three, so now we have base enablements, core integration and post integration and mapped out a lot of deliverables that we did in the legacy framework into the modern framework. Along with that, we've drastically reduced the integration time to where we're looking to have a full service and feature capabilities forwarded to our end users within six months timeframe.
Garinder: A key take-away from this is that, a key characteristic of this framework is the fact that the network preparation phase has been completely eliminated. So, not only does this represent the fact that we can move into the next phase six months sooner, but more importantly, what it's done is allow us to strategize how we approach our base enablements in a totally different way, right? So when we're beginning integrations, we're no longer waiting on network connectivity and deployment of equipment to get started. In fact, when we're doing in base enablements, we're doing network security assessments, in parallel, we can kick off the quick enablements of the setting up of applications that can provide immediate value to the acquisition, so they can get up and collaborate with the Moody's lines of businesses.
Garinder: This shows us how a legacy integration framework has transformed into a modern one, and I want to walk you guys through an actual workflow, a visual workflow to show you how this looks, right? So here we have , we have two entities. We have a new acquisition, let's call it NewCo, and Moody's. So on day zero, new acquisition is independently operating on the left here, and you have Moody's Universe on the right, consisting of size enabled applications, fronted for access enablement through Okta, lifecycle management activities, HR activities, and modern workplace capabilities. So what happens on day one, when we kick off this integration?
Garinder: First thing we can do is we can connect the acquisition network to Okta, to be able to start syncing their user store, and bring in that user data for future access enablements. Same time during phase one, we can do what I like to call is "light touch integrations", so these are integrations where there's not much complexity required around application enablement, because the application that we're enabling can provide immediate value to the business, but the same time don't have dependencies on back-end systems. Along the same line, during phase one, we're doing the activities of creating user IDs on our domain for the acquisition network.
Garinder: Now let's look at phase two. Phase two, we're continuing the enablement for a lot of our SAS catalog offerings, but here we're doing it for more, I guess, complicated applications, applications that might have, again, dependencies on downstream systems like back office applications or HR systems or require data manipulation or attribute mapping. That might essentially take a little bit more time to integrate. Also at the same time, this is a huge win for us, where we're able to provide access to non-Moody's accounts to our on-premise Moody's network resources. So if you think about that, what happens is for services and resources that are not internet exposed, we're able to give those and grant access to those to our non-Moody's users. So things like new-hire orientation material or employee handbooks or maybe file shares, that might not be hosted on SAS portal somewhere, again, with the ability of integration through Okta, give that capability to the new users who are non-Moody's users and have them consume that resource.
Garinder: So the frameworks and methodologies help us sort of understand what the technical implementation looks like, but how does that translate to the business, right, because from a metrics perspective, what can we measure in terms of how much impact this had to the business? Well, we can measure time. That's what we want to look at here real quick.
Garinder: Again visiting different phases that we talked about earlier, we can see the differences between pre Okta and post Okta implementations. So from a base enablement perspective, what we normally took three months to deliver, we can do so in about a month, and so that's a two months in savings. From a network preparation perspective, again, a six month effort has been totally eliminated, and like I said, the result of that is not only the ability to start the next phase sooner, but also be able to do a lot of the work in the base enablement phase in terms of the quick enablement accesses. And finally, the network and app integration, which was a seven to eighteen month effort, has been reduced down to six months which is a twelve months savings, along with the capital expenditure, because again, what we're doing is we're not forcing the acquisition to adjust to the Moody's hardware stack during the time of integration. Instead what we can say is, "Hey, you guys can consume applications and services the way we're provisioning through Okta, but as you go through your normal hardware refresh cycle, which is typically a three year cycle, when it's time to refresh your hardware, you come onto the Moody's stack, and you get the Moody's laptop and hardwares.
Garinder: So looking at this here, this was a recent use case that Keith spoke about. Last year, we acquired Reich, which is a real estate firm, and we signed the paperwork and started the official integration mid-October. Within about a week, we were able to connect Reich to Okta to be able to essentially sync up their user store for the enablement and access, right? In a couple of weeks later, we had Reich users in their own independent workspace on our collaborating with Moody's users, with Moody's lines of business among themselves. And in about a month, that's an AWS icon...In about a month, we were able to set up an AWS account on our AWS tenant, and have the Reich users and their developers have access so they can start building out their Cloud infrastructure. And finally, by the end of the year, so we're look at at two and a half months here, from the start of this integration work, that we were able to give them access to our HR system, so they could start doing things like time sheet management, payroll, and vacation tracking and so and so forth.
Garinder: So before I hand it off back to Keith, I want to say that we were able to achieve a lot of valuable things in a particularly short amount of time, relatively speaking. But I want to emphasize what enabled all of this was Moody's commitment to becoming less reliant on our on-premise infrastructure and taking a Cloud first approach to applications and services, right. By embracing technologies, like Office 365, AWS, and collaboration apps, we're able to leverage the technology like Okta which is a Cloud platform itself to deliver solutions much quicker. As we're continuing to go down the path of new challenges and new initiatives, with respect to integrations, Okta not only continues to play an integral part of our [sic] based access strategy, but it's vital to our integration philosophy. Ultimately, bringing people and processes together in an efficient manner is what's continued to distinguish the Moody's brand.
Speaker 2: Thanks Garinder.
Speaker 2: I would just add a couple things. Really on this slide...So the acquisition literally closed on the 15th of October, and two weeks later, we had people collaborating on slack, and this was a data and analytics company, so really a big part of what we were buying was their data set. And in two weeks, we had a slack channel up and running with people passing data sets, sample data sets backwards and forwards, collaborating, asking questions, across the organization and prior acquisitions that has been an incredibly painful process.
Speaker 2: The second thing that really had a hard dollar benefit to us was the business was, the HR payroll enablement, right, Reich is a U.S. company, and basically putting them onto our payroll and HR systems but he end of the year, we'd manage to totally turn off their benefits, their payroll, their 401K system, and basically bring them all into our preferred providers, which actually gave the employees a real benefit. We're a much bigger company, so for the employees of the acquired company, they got immediate access to our much better healthcare, much better 401K plan, but actually saved hundreds of thousands of dollars as well by being able to do that in two and a half months. Something we've never been able to do before.
Speaker 2: The third thing I would add is, this is the first time we've tried it this way, so what's really exciting to us, is literally on October the 15th, we didn't know if Garinder and his team were going to be able to make that HR system work, right? We were kind of adventuring into an unknown area where they were saying "Well, we think we can make it work, but if it doesn't, we're going to have to have a fall back plan." Now, those tools are Okta enabled, so the next acquisition this year, probably this year, maybe next year, we'll just be able to turn these things on, and actually do it even faster. So that's what's really exciting us on the business side about, about what we've done here, and I think it definitely is the most fundamental changes to the way we operate that's happened in the last few years. So thank you.
Speaker 4: So my question was that I think I can see the benefit of using Okta when we, the customers were heavily using Cloud application. I am just trying to make sure that I understand this correctly. If I have good percentage of the on-premise application, maybe your knowledge may not be 100% correct.
Garinder: So you're partially right in that, right? There's still dependency for on-premise infrastructure and to consume lot of those directly, but again, the fact, that we're enabling and embracing a lot of the Cloud capabilities will give us some capabilities integrate back. So like one of the things that was referenced was Amazon workplaces, right? Amazon workplaces allows you to be able to basically have a VDI on the Moody's network. So a consumer, who is not on the Moody's network, doesn't have the Moody's domain credentials, can still be able to leverage a tool like that to consume applications and resources on-prem.
Speaker 2: I would say that it's kinda really turned everybody's, opened everyone's eyes on the business side about part of a benefit of moving to the Cloud, right? So we were already kind of along that path. It's really kind of really reinforced people.
Speaker 2: Yep.
Speaker 5: So, you know, the initial integration piece where I guess, the integration target is still using the HR system, but you're connecting them through active directory, that's pretty exciting because I see that cuts months off of an integration to initially start with some connectivity. My question is when you get the integration target, when they're shifting from their HR system to your HR system, how do you work through the complexity of continuing to maintain that connectivity to those applications? I would assume there would have to be a shift to some degree and how you would manage that. Does that make sense?
Speaker 2: Yeah, it does. I think because of the size, they were a 300 person company, they weren't as tightly integrated in many of those respects, right? So they didn't have an awful lot of their internal systems hanging off the back of their HR system, and often, that's the sort of acquisition we're doing, where they're kind of less down the road.
Speaker 5: So not thousands of users,
Speaker 2: Correct.
Speaker 5: More like hundreds of users,
Speaker 2: Right. In this case, we had 300 users, but you know.
Speaker 6: So you talked about unifying the active directory together. One of the challenges we've had is we've done mergers and acquisitions is having the universal directory so that people know who to contact and how to contact people via phone, email, etc. Are you using Okta to push data back and forth, or how are you handling that to move forward with your integrating with these companies?
Garinder: So right now, active directory is still our source of truth, same as for the acquisition. We're leaving that independently. Right now, the enablement we've done directly has been for SAS consumption of the services. I think it's a bigger effort to align active directories, obviously because they're deeply entrenched in the different capabilities they all have, so that's definitely going to be a challenge that we have. One of the things that can eliminate the challenge is if we end up just saying, "Hey, we're just gonna bring you over into ours", then you don't have the problem of trying to integrate.
Speaker 2: I think the other thing we seen is people at Reich, the company that we acquired, actually use the HR system to look up other people in the organization, find out their contact details, so our active directory syncs with our HR system. And they're using the all chat features, and kinda trying to understand who is it that they're talking to, what, where they sit in the organization, so that's been very beneficial.
Speaker 7: From a branding perspective, hi, are you having the people's whose company was acquired, maintain their previous email addresses, for their domain, for that previous brand? Are you working to provide aliases so they have both the old and the new, and how are you integrating that with Okta?
Speaker 2: It varies on acquisition by acquisition basis. I think the interesting thing about the way we've approached it here, is it actually makes it much more of a business decision, right, how are we going to deal with those things, whereas in the past, it was almost IT driven thing. When could we, you know, in 18 months, 18 months is the soonest we could have put everyone on the same email address. Now it's only a couple months in, we can make a real business decision about how do we want to approach it, and that's actually been kind of one of the most surprising and it changes the whole conversation. Do we want to keep both brands? Do we want to turn one off sooner, and we didn't use to be able to do that. It used to be very much driven by the time of the integration.
Speaker 7: So in that scenario, where you want to have that alias and yeah, I'm going a little deeper, are you using a secondary email address in the provisioning, into UD or into the [sic]? How are you accomplishing that, so if you want to have both, right?
Speaker 2: I believe, I'm not the right person, but I believe we're alias in the email addresses, so both, everything they send will come from their Moody's email address going forward, but any email sent to Reis.com will come through to their email and then transition people.
Speaker 7: Yeah, it's just forwarding. Yeah.
Garinder: And just to add to what Keith says, I think that's one of the beauties of Okta, right, is I think a lot of you guys who have it and who do these implementation, you can see hey from a technical perspective what attributes and what authentication scheme I want to pass to the application, so if the application says, "Hey, I need your native whatever was on your acquisition company, you choose to pass that attribute, whether that's a acquisition's email address, but again, front the user object with their branded email. So that's a great functionality and capability that Okta provides.
Speaker 7: Have you integrated with companies that don't have AD at all, 'cause we're seeing some of that, that are so small, that they're not even running AD.
Garinder: Not with Okta, no. Everything we've done so far has been AD driven, but I think at the end of the day, what Okta cares about is their user store, whether that's AD, LDAP, or anything else. It's just a database that it's pulling from and then it's going to manage that store and identities.
Speaker 7: Oktay, great. Thank you.
Speaker 8: Have you guys integrated with, or merged, or acquired another company that was also running Okta, and if you have, can you explain how you consolidated to single Okta tenant? We're currently going through that right now. We're leveraging org to org, but in the near future, we're gonna have to consolidate to a single tenant, so just curious if you've gone through that yet.
Garinder: I think we should speak to you then, because we haven't really encountered that yet, but I'm sure that, because Okta obviously is transformed a lot of businesses, so we'll end up encountering a case where we have to do an Okta to Okta integration, and probably org to org as well what we'll look at beginning.
Crystal: Well, if there are no other questions, thank you again so much, and please give a final round of applause to Keith and Garinder.
Learn how Okta can help organizations rapidly achieve their M&A goals, and join Moody’s as they dive into their goals, challenges, and ultimate success in quickly bringing on board newly acquired employees to collaborative platforms. They’ll also share their blueprint on how they plan to approach future acquisitions and enable core service integrations in a short amount of time.