Is There Any Cost for Production Environment Without Dataverse and Azure Pay-as-you-go?

Question

I have access to create a Production environment, where I see options to enable or disable “Add a Dataverse data store?” and “Pay-as-you-go with Azure?”.

I would like to understand whether a Production environment is free to use if I only work with Solutions, Power Automate flows, SharePoint lists, and Canvas apps, without enabling Dataverse or Pay-as-you-go.

Could you please clarify if there are any licensing or cost implications in this scenario?

Answer 1

Hi @Ashokan, Immanuel Sanjai Kumar, 

Good day, and I appreciate the clear explanation of your concern. 

Regarding your concerns, a production environment is not a separately billed item. Instead, any potential costs are driven by the specific tools you use inside that environment and whether you choose to link it to an Azure billing plan.

If you set Add a Dataverse data store? to "No" and Pay-as-you-go with Azure? to "No" you are not enabling automated billing. Pay-as-you-go charges only apply if the environment is manually connected to an Azure subscription.

Below I would like to clarify the relationship between solutions and dataverse

While you can run apps without it, the platform requires a Dataverse store to be enabled if you want to use the Solutions feature. Even if you use SharePoint for your actual data, the system uses a small amount of internal storage to manage the Solution files (metadata) themselves. If you choose "No" for Dataverse, the Solutions tab will not be available in that environment.

Since you plan to use SharePoint, canvas apps, and flows, your current setup is very efficient:

• Standard Connectors: Tools like SharePoint and Excel are considered standard. Most office-based license plans (such as E3 or E5) already include the rights to use these at no extra cost.
• Premium Features: Costs only enter the picture if you use premium connectors (like SQL or Jira) or if you enable Managed Environments in the settings. Keeping those features disabled ensures you stay within your existing entitlements.

These are some important factors you should consider for your production environment:

• Azure Billing: If someone links an Azure subscription later, usage would then be billed through meters.
• User Access: If an app is built using premium features, every person who opens it will need a premium entitlement.
• Tenant Capacity: Creating a new environment usually requires at least 1 GB of available database capacity in your organization’s overall pool.

Because every organization has a unique setup, the most reliable way to confirm your specific situation is through official support channels:

1. For environment billing: Ask your internal admin to open a support request through the Power Platform admin center.
2. For subscription questions: Contact your billing department or the partner who manages your licenses.

Below are official articles you can refer to for more details:

• Environment Management: Create and manage environments in the admin center
• Pay-as-you-go Overview: How billing plans work
• Billing Meters

I hope this information helps you move forward with your project with more confidence. If you have any other questions as you begin setting up your apps and flows, please feel free to reach out.

---

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Answer 2

A production environment itself isn’t a billed item; costs come from the licenses and meters used by what runs inside it.

From the provided information:

• Pay-as-you-go billing only applies when the environment is explicitly linked to an Azure subscription via a billing plan. If “Pay-as-you-go with Azure?” is not enabled (no billing plan / no Azure subscription linked), then Azure pay-as-you-go meters will not be charged for that environment.
• When an environment is linked to Azure via a billing plan, it becomes a pay-as-you-go environment and usage of Power Apps, Power Automate, Dataverse, and Microsoft Power Platform requests that exceed included amounts are billed to the Azure subscription. Removing the environment from the billing plan stops Azure billing for that environment.
• Pay-as-you-go can only be set up at the environment level, not per individual app or flow. All apps in a pay-as-you-go environment are billed against the associated Azure subscription unless explicitly excluded (in which case users need appropriate per-user licenses).
• Production and sandbox environments are eligible for pay-as-you-go, but simply being a production environment does not automatically mean pay-as-you-go billing is active.

What this means for the described scenario, based only on the context:

• If Dataverse is not enabled and “Pay-as-you-go with Azure?” is disabled (no billing plan, no Azure subscription linked), then there are no Azure pay-as-you-go charges for that environment.
• Any costs or licensing requirements for using Solutions, Power Automate flows, SharePoint lists, and Canvas apps in that environment depend on the users’ existing Power Apps/Power Automate/Microsoft 365 entitlements, which are outside the pay-as-you-go mechanism described here.

So, from the pay-as-you-go and Dataverse perspective in the context, a production environment with Dataverse disabled and no Azure pay-as-you-go configured does not incur Azure metered charges; it behaves as a “regular environment,” and usage is not billed to Azure.

---

References:

• Pay-as-you-go plan
• Known issues and frequently asked questions
• Power Platform licensing FAQs