Hi Fred, Mike here. Yes. Look, I think that’s an extremely good question. Strategically, I would say we are very pro integration. Let me explain why that is. We’ve talked a bit before about what we call Cambrian SaaS. So there is an explosion of SaaS tools happening out there at the moment. It’s a very verdant period for new solutions for customers, new applications, niche one, big ones, small ones. This is a fantastically interesting period to be in SaaS. We focus on what’s best for our customers. And when you’re doing so, it takes a lot of practicality, pragmatism, a little dose of humility to realize that those customers are going to use a lot of applications that come from other companies for all sorts of reasons. The best thing we can do is be deeply integrated in all of those places. We believe that’s best for the customers. It is then our job to automate workflows to coordinate data. And to do that as best we can across all of those different applications. And that leads to the best outcome for the customer, which leads them to, as you mentioned, be retained or enjoy their Atlassian experience so stay, it also leads them to have an increasingly integrated, which becomes sticky and more valuable to them. Offering set among the different products and applications that we have. One of our biggest competitive advantages is developer ecosystem and our extensibility of products. You see that and as Cambrian SaaS continues to throw up new evolutions of products and variants in different directions. That allows us to flow into those directions through integrations, through acquisitions, through extensibility, automation in lots of different manners as we navigate that that continually evolving world. And so, yes, I think strategically, it’s extremely important that it’s been part of our open philosophy for customers for a long time now. It’s part of Open DevOps, as you saw, as you mentioned, and we know that that resonates with customers, both philosophically in terms of they like that they think it’s a good position for Atlassian to stand, we’ve never been a vendor that said, hey, all your stuff is with us. And you don’t need anybody else. No, we don’t, we don’t believe that. That’s not what we tell customers. That’s not what we talk to them about. So philosophically, that resonates with them. We know from their usage from their satisfaction, that we are then a better vendor for them. So, we see that in the numbers in lots of different places be that analytically usage based or customer satisfaction report based. And then we believe that results in better economics for Atlassian, which is then shows why those integrations are important for shareholders, and the long term future of Atlassian. That’s a philosophy we’ve had for a long time. In fact, we can really show that philosophy in ways that we couldn’t, beforehand because it really becomes apparent. Thinking through my own after the path that I want to also stress, the data integration piece is really important. So, we continue to evolve our data platform as a part of our cloud platform to connect objects – to connect elements across the Atlassian and third party spaces, so that we can give smarter and better answers to customers. And we saw that show up a little bit in the insights features we shipped in Jira Software, that don’t just leverage Jira Software data, they can leverage data from cloud providers, CICD providers, lots of other parts of the DevOps ecosystem, to give you the best answers in Atlassian products and outside Atlassian products. I think that’s a long term strategic piece here as well, is to be able to coordinate and understand data across multiple vendors gives you those automation capabilities, but also gives you insights and unique places that we can get answers to customers.