Azure Infrastructure Costs (Managed SaaS Deployment)

1. Overview

When you deploy Centrify 360 as a Managed SaaS solution via the Azure Marketplace, Azure provisions several resources in your subscription:

  • Azure Database for PostgreSQL flexible server

  • Azure Container Apps (ETL orchestrator)

  • Azure Storage (file shares)

  • Azure Monitor / Log Analytics

The Centrify 360 plan price on Azure Marketplace covers the management fee (software and managed service). All Azure infrastructure resources are billed directly by Microsoft to your Azure subscription according to standard Azure pricing.

This document explains:

  • Which Azure resources are created per plan.

  • How these resources affect your monthly Azure bill.

  • Example order-of-magnitude cost estimates for each plan (Starter, Professional, Advanced).

All prices in this document are illustrative only. Azure prices vary by region, currency, discounts, and reservations.
Always validate cost estimates in the official Azure Pricing Calculator before making commercial commitments.

2. Cost Components

The Centrify 360 managed application provisions the following main components:

  • Azure Database for PostgreSQL flexible server (Burstable tier)
    Starter → Standard_B2ms (2 vCores, 8 GiB)
    Professional → Standard_B4ms (4 vCores, 16 GiB)
    Advanced → Standard_B8ms (8 vCores, 32 GiB)
    Storage size scales by plan (32/64/128 GiB in the default template).

  • Azure Container Apps (Consumption)
    Runs the Centrify 360 ETL orchestrator. Billed by vCPU-seconds, GiB-seconds, and HTTP requests, with a generous free grant per subscription each month.

  • Azure Storage (File shares)
    A single file share (default 100 GiB quota) for configuration and ETL artifacts.

  • Azure Monitor / Log Analytics workspace
    Billed primarily by data ingestion (GB/month) and retention beyond the first month.

These costs are in addition to the Centrify 360 management fee and any other resources in your subscription.

3. Plan Sizing Assumptions

The managed application ARM template uses the following mapping between Centrify 360 plans and Azure resources:

Plan ID PostgreSQL SKU vCores / Memory Provisioned storage Sync window

starter-scheduled

Standard_B2ms

2 vCores / 8 GiB

32 GiB

Scheduled (DB start/stop)

starter-alwayson

Standard_B2ms

2 vCores / 8 GiB

32 GiB

Always-on

professional-scheduled

Standard_B4ms

4 vCores / 16 GiB

64 GiB

Scheduled (DB start/stop)

professional-alwayson

Standard_B4ms

4 vCores / 16 GiB

64 GiB

Always-on

advanced-scheduled

Standard_B8ms

8 vCores / 32 GiB

128 GiB

Scheduled (DB start/stop)

advanced-alwayson

Standard_B8ms

8 vCores / 32 GiB

128 GiB

Always-on

Container Apps, Storage, and Log Analytics components are largely the same across plans; the main driver of cost difference between plans is the PostgreSQL compute and storage tier.

4. PostgreSQL Cost per Plan (Illustrative)

Public examples for Azure Database for PostgreSQL Flexible Server (Burstable) show approximate monthly prices (pay-as-you-go) for common SKUs such as:

  • B2ms (2 vCores, 8 GiB) ≈ $99/month.

  • B4ms (4 vCores, 16 GiB) ≈ $198/month.

  • B8ms (8 vCores, 32 GiB) ≈ $397/month.

These figures are indicative and based on example regions as of 2025–2026; they will differ for your region and contract. Storage is billed separately per GiB/month and IOPS; a 32–128 GiB disk is typically a small portion of the total cost.

Given your template’s mapping, you can think of the database compute cost per plan approximately as:

Plan PostgreSQL SKU Typical pay-as-you-go DB compute (always-on)

Starter

Burstable B2ms (2 vCores, 8 GiB)

≈ $100/month

Professional

Burstable B4ms (4 vCores, 16 GiB)

≈ $200/month

Advanced

Burstable B8ms (8 vCores, 32 GiB)

≈ $400/month

For scheduled plans (where the Logic Apps start/stop PostgreSQL daily), compute charges apply only while the server is running; when stopped, you pay just for storage and backups.
If you run Postgres 2 hours/day instead of 24/7, your monthly compute cost is roughly divided by 12, while storage cost remains constant.

5. Container Apps, Storage, and Logs (Illustrative)

5.1. Azure Container Apps (ETL Orchestrator)

Azure Container Apps Consumption tier bills per vCPU-second, GiB-second, and request, with free grants per subscription each month (first 180,000 vCPU-seconds, 360,000 GiB-seconds, and 2 million requests).

For a typical Centrify 360 deployment with:

  • 1 replica, light-to-moderate ETL workload.

  • A few million requests per month (BC push + internal health checks).

you will often see single-digit to low double-digit USD per month for the Container App, especially when the free grant is taken into account. Heavy or 24/7 ETL workloads, or many parallel environments, can increase this cost.

5.2. Storage Account and File Share

The managed application creates:

  • A Storage account (Standard_LRS).

  • A file share (default quota 100 GiB).

Azure Files and Blob storage are typically billed per GiB/month. For tens of GiB, the monthly cost is usually in the low single-digit USD range, unless you store many large artifacts or backups.

5.3. Log Analytics

Azure Monitor / Log Analytics is billed primarily by data ingestion volume and retention beyond the first month.

As a rough guideline:

  • Ingestion is around a few USD per GB ingested per month in the default Pay-As-You-Go tier.

  • For Centrify 360, if you keep logging moderate (e.g. a few GB per month per environment), Log Analytics typically stays in the single- to low double-digit USD per month.

  • Verbose logging or multiple large environments can increase this significantly.

6. Putting It Together: Example Monthly Ranges

The table below gives a very rough consolidation of Azure infrastructure costs per plan for a single environment in a typical region, assuming:

  • Pay-as-you-go pricing.

  • 24x7 database uptime for always-on plans.

  • Approximately 2 hours/day uptime for scheduled plans.

  • Light-to-moderate usage for Container Apps, Storage, and Log Analytics.

Plan DB compute (estimate) Other infra (Container Apps, Storage, Logs) Illustrative total range

Starter-scheduled

≈ $10–20/month (B2ms, 2h/day)

≈ $5–20/month

≈ $15–40/month

Starter-alwayson

≈ $90–110/month (B2ms, 24x7)

≈ $10–30/month

≈ $100–140/month

Professional-scheduled

≈ $20–40/month (B4ms, 2h/day)

≈ $10–30/month

≈ $30–70/month

Professional-alwayson

≈ $180–220/month (B4ms, 24x7)

≈ $10–40/month

≈ $190–260/month

Advanced-scheduled

≈ $40–70/month (B8ms, 2h/day)

≈ $15–40/month

≈ $55–110/month

Advanced-alwayson

≈ $360–440/month (B8ms, 24x7)

≈ $20–50/month

≈ $380–490/month

These ranges are illustrative only, based on public example prices for Azure Database for PostgreSQL Flexible Server burstable SKUs (B2ms/B4ms/B8ms) and typical small-to-medium workloads.
Your actual costs will differ depending on:
* Azure region and currency.
* Discounts (reserved capacity, savings plans, EA).
* Actual database uptime (scheduled vs always-on).
* Real ETL load, logging volume, and storage usage.
Always validate using the Azure Pricing Calculator.

7. How to Refine the Estimate in Azure

To get a precise estimate for your environment:

  1. Open the Azure Pricing Calculator.

  2. Add the following services:

    • Azure Database for PostgreSQL Flexible Server (Burstable tier, B2ms/B4ms/B8ms).

    • Azure Container Apps.

    • Storage account (File storage).

    • Azure Monitor / Log Analytics.

  3. Set:

    • Region where you will deploy Centrify 360.

    • vCores and memory mapping according to your chosen plan.

    • Expected database uptime hours per month (24x7 or scheduled).

    • Estimated log volume (GB/month) for Log Analytics.

  4. Save the estimate and revisit it regularly as usage and requirements change.

8. Cost Optimization Tips

  • Use scheduled plans where possible
    Scheduled Centrify 360 plans start/stop PostgreSQL to align with data refresh hours, reducing compute cost while keeping storage and configuration intact.

  • Leverage reservations / savings plans
    For stable, long-term workloads, consider Azure database reservations or savings plans for PostgreSQL to reduce compute cost.

  • Consolidate environments where appropriate
    Where governance allows, running multiple companies/environments on the same Centrify 360 instance can improve resource utilization, but always balance this against isolation requirements.

For questions about how plan sizing maps to your specific workload, or for a tailored cost review, please contact the Centrify 360 team.