As more and more companies adopt Microsoft Azure as their public cloud, the need to control Azure costs becomes ever more important. As IT, Development and Operations grow their usage of Azure cloud assets, Finance is catching up. Your CFO has seen the bill, and says, “I thought cloud was supposed to be cheaper. So why is this so high?”
Azure Spend Growing
It’s no secret that overall Azure spend is rising rapidly. Azure is the fastest-growing cloud provider, both from adoption by new customers, and growth within accounts of existing customers. Many users of other clouds, such as AWS, are also adopting Azure as a secondary option for diversity.
Here’s the thing: as this spend grows, so too does wasted spend. And customers know this. But as one ParkMyCloud user told us, “As we started to dive into it, we found that a large part of our spend is simply on waste. We didn’t have visibility and policies in place. Our developers aren’t properly cleaning up after themselves, and resources aren’t being tracked, so it’s easy for them to be left running. It’s something we want to change, but it takes time and energy to do that.”
So it’s no wonder that IT, Development, and Operations teams are being tapped by CFOs left and right to reduce costs, as the Azure bill becomes a growing line item in the budget.
Control Azure Costs Before Your CFO Makes You
There are a few things you can do to be proactive and control Azure costs before your CFO comes bursting through your office door. Here are some starting points:
Control your view – the first step toward change is awareness, so use an Azure dashboard to view all of your resources in one, consolidated place. We’ve heard from ParkMyCloud users, upon getting a single view of all of their resources in the ParkMyCloud dashboard, that they found VMs they didn’t even know were running.
Control your processes – talk with your team and set clear guidelines around provisioning appropriately sized VMs, stopping non-production VMs when they are not needed, and governing existing VMs (for example, whose responsibility is it to make sure each team is only running the resources they actually need?)
Control Azure costs – there are a few simple actions you can take to get your actual Azure costs in control. Here are some starting points:
“Right size” your VMs – make sure you aren’t choosing larger capacity/memory/CPU than you need
Set automatic schedules so your non-production VMs don’t run when you don’t need them (free with ParkMyCloud’s core version – try it out)
Set a spending limit on your Azure account. You can do a hard cutoff that will turn off your VMs once you hit the limit, or simply sign up to receive email alerts when you approach or hit the spending limit.
So, automate your operations today and make your CFO happy. Bring your Azure spend down before it becomes a problem!
If you read any cloud or tech blogs, you’ve probably seen the latest financials that show that Microsoft Azure is growing – and that it’s currently the fastest-growing cloud provider. However, this growth means an ever-increasing amount of wasted spend on Microsoft Azure resources.
Overall, Azure’s growth is exciting for customers who have bought into the Microsoft stack — more momentum means quickly evolving product lines, balanced prices, and improving cloud services.
However, dominant competitor Amazon Web Services (AWS) has had more time to feel and subsequently address growing pains. That means that AWS users have more options available to them to address certain concerns that come with using public cloud. For example, managing costs.
Managing Costs: a Major Concern Among Cloud Users
How much are Azure users worrying about managing their cloud costs? According to RightScale’s 2017 State of the Cloud report, managing costs is a huge, top-of-mind challenge. While it’s a top-3 concern for all cloud users, for mature cloud users, managing costs is the number one concern.
The primary goal of cost management efforts is to optimize costs – in other words, to eliminate wasted spend. Most cloud customers would agree that they have some amount of spend wasted, whether that’s from leaving resources on when not needed, oversized resources, orphaned storage volumes, etc. However, estimating the amount of wasted spend is a problem.
RightScale found that customers consistently underestimate how much they are wasting:
So when we’re looking at Microsoft Azure specifically – how much spend is wasted?
Wasted Spend on Microsoft Azure
We’ve talked about overall cloud waste before. So let’s apply those numbers to Azure specifically.
Non-production resources are only needed for an average of 24% of the work week, which means up to $900,000,000 of this spend is completely wasted
And that’s only a portion of the waste – it doesn’t even address oversized resources, orphaned volume storage, etc. Many of these problems are well-addressed in AWS, but the Azure support market is still catching up.
The good news is, this $0.9 billion portion of wasted spend is easy enough to solve. All Microsoft Azure users need to do is schedule the “lights to turn off” when they’re not home – in other words, schedule non-production resources to turn off when no one is using them. Try it now with ParkMyCloud!
Last week, we held a web session introducing ParkMyCloud for Microsoft Azure. We’re excited to open up the ParkMyCloud platform to Azure customers, so you can get the same savings that AWS customers have been enjoying for the past year and a half.
Watch the video here, and use the guide below to skip ahead to the parts of the session that interest you:
00:28What is ParkMyCloud?
WHAT: Simple, single-purpose SaaS tool.
HOW: Automatically schedule on/off times for idle servers.
WHY: Optimize cloud services spending.
ROI: Save 60% or more; 6 week payback.
01:13How ParkMyCloud Works
•Discover & Manage cloud computing resources
•Analyze & Recommend resources to ‘Park’
•Policies automatically schedule resources for off/on
01:48ParkMyCloud vs. AWS cost savings options
02:15How much has ParkMyCloud saved our customers?
02:39The Azure World
Your Azure Account (Active Directory Tenant ID)
Your Azure Subscription (Subscription ID)
Your Application (Application ID)
Service Principal for Your Application
Limited Active Directory Role for Service Principal
Your Azure Cloud Resource Groups and Resources
Azure limited access role credential is analogous to an AWS IAM Role + policies
Requires a lot more information:
Subscription ID ~ analogous to an AWS account
Tenant ID ~ the ID of our Azure AD instance
App ID ~ the ID of the ParkMyCloud App in AD
Password (a.k.a., Client Secret) ~ You set this
04:39Four Azure CLI Approaches to creating Azure credentials
Windows Powershell – manual or scripted
Unix azure-cli – manual or scripted
05:42 ParkMyCloud Demo
05:51 PMC Dashboard
06:05 Adding an Azure credential to ParkMyCloud
07:29 Walkthrough of the ParkMyCloud dashboard
08:27 How to attach a schedule to an instance
09:18 How to create a custom schedule
10:51 Your savings projections in ParkMyCloud
11:51 How to see information about your individual instances
12:34 Teams and Roles in ParkMyCloud – containers for organizing users and resources with role-based access control (RBAC)
14:22 Logical Groups – the ParkMyCloud construct for organizing resources for group scheduling and sequencing
16:51 Policy engine – apply schedules in an automated fashion
17:02 Never Park policy – protect production instances from parking
17:26 Creating a new policy for scheduling
19:44 Always Off Schedule – use to park for the maximum amount of time. Useful when users are across time zones.
22:09 Audience Question – using the policy engine for sorting to teams, “snooze only” for schedule enforcement, and others.
23:37 Actual Savings number
24:04 Quick filters for viewing the dashboard
24:32 Recommendations – how to edit and add recommendations, and parking resources that are recommended to park.
25:00 How to download reports in ParkMyCloud
25:12 Audit Log
25:33 Pricing – by instance count
26:45 Is there any functionality for AWS that doesn’t translate to Azure?
28:59 Do you plan to support other clouds besides AWS and Azure?
29:42 How are the projected savings and actual savings numbers calculated?
We are excited to share that ParkMyCloud now supports Microsoft Azure scheduling!
For the past 18 months since our launch, Amazon Web Services (AWS) customers have been using ParkMyCloud to manage their compute resources by turning them off when not needed (called “instance scheduling”) – saving a total of $1,749,279.06 so far – and counting!
Now, that same “Nest for the Cloud” capability is available to Microsoft Azure customers.
Plus, if you use both AWS and Azure, you can manage and govern your accounts together in a single ParkMyCloud dashboard.
Why We’re Excited
Being able to control costs with Microsoft Azure scheduling is our most frequently-requested capability – so we’re excited to share this with our customers and new users.
The size of cloud waste is enormous, with up to $5.6 billion wasted every year on computing time that no one is using. While much of this wasted spend is on AWS resources, Azure is certainly the second-biggest player in the public cloud market. We look forward to helping Azure customers eliminate wasted spend. Learn more in our official press release.
How Does ParkMyCloud Work on Azure?
Just like AWS, it’s simple:
Discover: Connect with Azure to discover your virtual machines (VMs)
Schedule: Schedule on/off times for the desired VMs
Smile: Reduce your costs by up to 60%
If you’re new to ParkMyCloud, check out these additional resources:
Zero-Touch Parking – how to use the ParkMyCloud policy engine to create rules for schedules to be automatically applied
As we launch into 2017, we’re looking to bring our public cloud users even more ways to save on their cloud spend. Here’s a preview of some of the more impactful features and functionality we’ll be releasing throughout the year.
New Cloud Service Providers
Thus far, ParkMyCloud has supported customers of Amazon Web Services (AWS) alone. (No small fries here; about 30% of public cloud infrastructure is in AWS). However, in two weeks, we’re expanding by releasing support for Microsoft Azure.You will be able to manage AWS and Azure resources side-by-side in a single dashboard.
In the following months, Google Compute Engine support will follow.
New Ways to Save
In addition to the new cloud service providers, we’re also adding support for additional services and new ways to save on your cloud infrastructure.
We’ll start the expansion from compute services by parking databases (Amazon RDS and others). We will also offer resource rightsizing, so you can ensure that you’re not wasting money on resources that are larger than you need them to be.
Adding to the ParkMyCloud Experience
We’ll also be enhancing the ParkMyCloud experience with surrounding features, starting with single sign-on (SSO) using SAML 2.0 coming in February.
Following that, we’ll add external notifications leveraging AWS SNS. And for the quants out there we’ll be adding a data analytics layer. We’re also excited to share that we’ll have native mobile support for iOS and Androidby the summer.
Of course, as a small and agile company, this list is not complete! We’re happy to hear your thoughts and suggestions about what you’d like to see in ParkMyCloud this year – so what’s at the top of your list?
We were recently asked about our vision for cloud applications in 2017: are we still seeing ported versions of legacy on-premises Software-as-a-Service (SaaS) applications? Or are most applications – even outside of pure-play startups – being built and hosted in the cloud? In other words, how long until full cloud takes over?
Actually, it already has.
Native cloud applications like ours – an 18-month-old startup – that have been built, tested, and run in the cloud are no longer the fringe innovators, but the norm. In fact, outside of a printer, we have no infrastructure at all – we are BYOD, and every application we use for development, marketing, sales and finance is a SaaS-based, cloud-hosted solution that we either use for free or rent and pay month-to-month or year-to-year.
This reliance on 100% cloud solutions has allowed us to rapidly scale our entire business – the cloud, and cloud-based SaaS solutions, have provided ParkMyCloud with the agility, speed, and cost control needed to manage to an OpEx model rather than a CapEx model.
We were able to rapidly prototype our technology, test it, iterate, and leverage “beta” communities in the cloud in a matter of months. We even outsource our development efforts, and seamlessly run agile remotely using the cloud and cloud-based tools. For a peek into the process, here’s a sampling of software development tools we use in a cloud-shrouded nutshell:
Amazon Web Service (AWS) for development, test, QA and production
VersionOne for agile management
Skype for scrum and video communication
GitHub for version control
Zoho for customer support
LogEntries for log integration
Confluence for documentation
Swagger for API management
And I could repeat the same for our Marketing, Sales, and Finance process and tools – the cloud has truly taken over.
We don’t know if these applications are built and run in the public cloud or the private cloud – that’s irrelevant to us, what’s important is they solve a problem, are easily accessible, and meet our price point. We do know that these are all cloud-based SaaS offerings – we don’t use any on premise, traditional software.
The net net is that many companies are just like ParkMyCloud. The question is no longer about how us newbies will enter the world – the question is, how fast will legacy enterprises migrate ALL their applications to cloud? And where will they strike the balance between public and private cloud?