Cloud governance 101
There’s a lot of talk about how and why to move to the cloud, and a lot of guidance to help you make the leap. But here’s a question less often addressed: What happens after you migrate your tools to the cloud?
How does a move to cloud impact your IT team’s to-do list? What should security teams be paying attention to post-migration? Who’s in charge of financial governance? And what else do you need to plan for not only before you choose cloud, but once you’re in the thick of things?
These questions all fall under the heading of cloud governance—a practice that will make or break the long-term success of your cloud transformation.
Cloud governance vs. on-prem management
A move to the cloud is good news for IT teams, who save significant time (and often money) by trusting vendors with server management, security patches, upgrades, and other tool and systems work.
As Evan Lerer, Director of Engineering at Redfin says, “Frankly, having our engineers or IT professionals manage our systems on-premise is a waste of time and money. If there’s a company that already has amazing products, why not have them do it? That way, we can spend our time working on the things that we're good at...”
But because cloud governance is so different from on-prem management, there’s definitely a learning curve—and if you don’t plan for governance up front, it’s easy for important tasks to fall through the cracks.
Even as you remove server upgrades, load balancer purchases, and security patches from the team’s to-do list, a move to cloud adds new, equally important tasks—like cloud cost optimization and vendor management—to that list.
Visit our Security Center
Up next...
Visit the Atlassian Trust Center
Get the latest information on the security, reliability, privacy, and compliance of Atlassian's products and services.
Learn more about cloud migration
Find all the resources, tools, and support you need to start evaluating if cloud is right for your organization.