> For the complete documentation index, see [llms.txt](https://help.pump.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.pump.co/how-we-work-with-cloud-providers/how-pump-works-with-azure.md). # How Pump Works with Azure This page is for Azure account managers who want to understand how Pump operates within the Microsoft Azure ecosystem. For customer-facing setup instructions, see [Connecting Your Azure Subscription](https://help.pump.co/~/revisions/5URpT9FFn4Jcsx7LTVRt/azure/connecting-azure). ### Pump's Azure Partner Status | Detail | Value | | ------------ | ---------------------------------- | | Program | Authorized Microsoft Azure Partner | | Distribution | Ingram Micro | ### How the Azure Relationship Works Pump participates in the Microsoft Cloud Solution Provider (CSP) program as an indirect solutions provider through Ingram Micro. When a customer joins Pump on Azure, Pump manages billing and commitment optimization for the customer's Azure subscriptions. The customer's Azure tenant, subscriptions, resource groups, and workloads remain entirely under the customer's control. #### What changes for the customer | Before Pump | After Pump | | ----------------------------------------------------------------- | ------------------------------------------------------------------------------------ | | Customer pays Microsoft directly | Customer receives a consolidated invoice from Pump | | Customer manages their own reservation and savings plan purchases | Pump manages commitment purchases on the customer's behalf (if Autopilot is enabled) | #### What does not change The customer retains full ownership and administrative control of their Azure tenant and subscriptions. The customer's existing Microsoft support plan remains active. The customer's AM relationship is unaffected. ### How Connection Works The customer connection flow uses a service principal (application registration) approach: 1. **Service principal creation.** The customer runs `az ad sp create-for-rbac --name pump` in Azure Cloud Shell to create a service principal for Pump. 2. **Role assignment.** The customer runs Pump-provided `az` CLI commands to assign specific RBAC roles to the service principal at the subscription or management group level. 3. **Credential registration.** The customer provides the tenant ID, application ID, and client secret to Pump. Pump authenticates using OAuth2 client credentials. No ARM templates, Bicep files, or Terraform modules are involved. The setup is done entirely through Azure CLI commands. ### Permissions Pump Receives #### Read-only role (all customers) | Role | Scope | Purpose | | ------------------------- | ---------------- | --------------------------------------------------------- | | Billing Reader (built-in) | Per subscription | Access to cost and usage data for analysis and dashboards | #### Autopilot role (customers who opt into automated commitment management) | Role | Scope | Purpose | | ----------------------------------- | -------------------------- | ------------------------------- | | Pump Autopilot Role (custom) | Management group or tenant | Commitment purchase actions | | Reservations Contributor (built-in) | Management group or tenant | Reservation management | | Reservations Purchaser (built-in) | Management group or tenant | Reservation purchase execution | | Savings Plan Contributor (built-in) | Management group or tenant | Savings plan management | | Savings Plan Purchaser (built-in) | Management group or tenant | Savings plan purchase execution | ### How Commitments Are Managed Pump analyzes the customer's Azure usage patterns and existing reservation and savings plan portfolio using the Cost Management API. It calculates optimal commitment purchases based on usage trends and existing coverage. Commitments purchased by Pump are scoped to the customer's own subscriptions. Pump does not pool commitments across customers. If a customer leaves Pump, their reservations and savings plans remain in their subscriptions and run off on their natural expiration schedule. Customers can choose between two modes: | Mode | Behavior | | --------- | ------------------------------------------------------------------------------------------------------------ | | Autopilot | Pump automatically executes recommended commitment purchases. Customer can block individual recommendations. | | Manual | Pump generates recommendations. Customer reviews and explicitly approves before any purchase is made. | ### Impact on AM Quota Customer spend that flows through Pump still counts toward the Azure AM's quota and attribution. Pump does not take commission from Azure AMs. Pump's solutions provider model is additive to the AM relationship. ### Data Sources Pump Uses | Source | What Pump reads | Purpose | | ------------------------------------------------ | --------------------------------------------- | ----------------------------------------- | | Cost Management API (generateDetailedCostReport) | Detailed cost reports | Cost analysis, dashboards | | Consumption API (usageDetails) | Usage detail records | Commitment planning, utilization analysis | | Billing API | Billing accounts, profiles, invoice sections | Account structure mapping | | Resource Groups API | Resource group listing | Subscription and resource visibility | | Reservations/Savings Plan APIs | Existing commitment inventory and utilization | Commitment portfolio management | #### Data backfill On first connection with read-only access, Pump pulls up to 90 days of historical cost data (chunked into 7-day jobs). Routine refreshes operate on a 7-day rolling window. ### SOC 2 Type II Pump is SOC 2 Type II certified. Audit reports are available on request through . ### Questions? If you have questions about a specific customer's Pump setup or about Pump's Azure partner status, contact . --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://help.pump.co/how-we-work-with-cloud-providers/how-pump-works-with-azure.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.