The only automated Azure rate optimization solution

Calculating your optimal point-in-time commitment portfolio requires deep analysis, and making changes quickly is error-prone. Doing this work continuously is only possible with sophisticated automation. Offload the grunt work to ProsperOps, so you can focus on higher-level FinOps initiatives.

Virtual Machines, App Service, AKS, Dedicated Host, Container Apps, Container Instances, Virtual Desktop, Spring Apps, Azure Databricks, Functions, and database services (Azure SQL Database, Azure SQL Elastic Pools, Azure SQL Managed Instance, Azure Database for MySQL, Azure Database for PostgreSQL) are supported.

Azure Reservations and Savings Plans for Compute.

Yes. When ProsperOps is enabled, it will discover existing commitments and assume management of them.

Yes. ProsperOps takes your negotiated rates into account when managing your commitments.

Each cloud provider has their own rules and discount mediums. The rules and attributes of commitments provided on Microsoft Azure are functionally different from that of AWS and Google Cloud. ADM for Azure uses its own Adaptive Laddering and other rate optimization techniques to maximize savings and flexibility, while adhering to Microsoft’s terms and conditions. 

Autonomous Discount Management is priced based on a small percentage of the total savings achieved with ProsperOps. See pricing page.

We require limited IAM permissions for your Azure billing scope(s). ProsperOps requires the following Azure roles:

• Enrollment Reader on the billing account (for Enterprise Agreements) or Billing Profile Reader on the billing profile (for Microsoft Customer Agreements)
  • Enable billing exports
  • Read aggregated compute service cost and usage history
• Billing Reader on the root management group
  • Read hourly subscription cost and usage data
• Owner on a dedicated ProsperOps billing export storage account
  • Configure and read billing export data

See help article for Azure Savings Analysis.

Roles must be added to the App Registration deployed in your billing scope(s) before the Savings Analysis was conducted. See permissions below.

Enterprise Agreements

• EA Purchaser on the billing account
• Reservations Purchaser on the root management group
• Savings Plan Purchaser on the root management group
• Quota Request Operator on the root management group

Microsoft Customer Agreements

• Billing Profile Contributor on the billing profile
• Reservations Purchaser on the root management group
• Savings Plan Purchaser on the root management group
• Quota Request Operator on the root management group

For more information, see help article on ADM for Microsoft Azure permissions.

We place a high priority on security, such that we only access and store information required for us to deliver our discount optimization services, which includes metadata about the types of instances you are running and the existing commitments present in your account. See help article on general security information and how we handle in-console data storage.

As for compliance, ProsperOps is SOC 2 Type II compliant. We run our systems on cloud provider environments, which provide robust security. See our Trust Center for more information.