Power Automate Process Mining add-on for Government — Pricing, Plans & What's Included

Power Automate Process Mining add-on for Government is a Government-segment add-on subscription for Power Automate Process Mining, because the current catalog lists it with Governmental Community Cloud Pricing. It should be treated as an add-on, not as a standalone core Power Automate license.

No, you should not buy this as your only Power Automate license, because the catalog identifies it as an add-on rather than a core standalone license. Confirm the required base licensing, environment, and tenant prerequisites with IT Partner before ordering.

The Government offer includes a Government-priced Power Automate Process Mining add-on subscription, because that is the product and segment shown in the current catalog. The catalog also shows purchasing options for a monthly commitment, an annual commitment paid upfront, and an annual commitment paid monthly.

This add-on does not include a standalone Power Automate license, automatic prerequisite licensing, or automatic confirmation of capacity, storage, admin-role, or environment requirements, because those details are not provided in the source catalog data. IT Partner should validate the full licensing path before purchase.

No trial SKU is shown for this Government offer in the current catalog, because the listed Government options are paid subscription terms only. If a trial or proof-of-concept path is required, confirm available Microsoft options with IT Partner before committing.

The Government catalog shows monthly commitment, annual commitment paid upfront, and annual commitment paid monthly options, because those term and billing combinations are listed for this offer. Use the live configurator to compare the current ordering options before purchase.

This page confirms Government-segment catalog availability, but it does not by itself prove eligibility for every Government cloud environment, because GCC, GCC High, and other government provisioning paths can differ. Confirm the customer’s exact tenant type and service availability with IT Partner before ordering.

No, this add-on page does not guarantee a specific residency, compliance certification, or agency policy outcome, because the source catalog only confirms the Government-priced add-on offer and available terms. Treat residency, compliance, access, and agency review as separate validations with Microsoft documentation and IT Partner guidance.

No, buying through CSP does not change the underlying Microsoft cloud service controls, because CSP is a licensing and billing channel rather than a separate technical version of the service. Your organization should still validate the exact Government environment, compliance requirements, and admin configuration before deployment.

No, this add-on should not be understood as including Microsoft Teams, because the catalog identifies it specifically as a Power Automate Process Mining add-on. If Teams integration, notifications, or collaboration workflows are needed, confirm the required Microsoft 365 or Teams licensing separately.

No Copilot entitlement is confirmed by this Government add-on listing, because the source catalog does not state that Copilot is included. If the buyer needs Copilot-related functionality, IT Partner should validate the separate Copilot licensing and Government cloud availability before purchase.

Those entitlements are not confirmed by this catalog listing, because the source data only identifies a Process Mining add-on subscription and does not provide capacity, storage, or AI Builder details. Confirm any Dataverse, storage, capacity, and environment requirements before ordering.

Validate tenant eligibility, provisioning path, prerequisite licenses, admin roles, environment requirements, capacity, and storage, because the catalog listing does not confirm those operational details. IT Partner can help check the licensing path before your agency commits.

Start by confirming the correct Government tenant, required base licensing, and administrator access, because the add-on may depend on prerequisites not shown in the catalog listing. After ordering, your Power Platform or Microsoft 365 administrators should provision and configure the service according to Microsoft’s current Government documentation.

Possibly, but migration should be planned rather than assumed, because this catalog entry does not confirm data movement, environment compatibility, or feature parity across tenants or clouds. IT Partner should review the current tenant, destination Government environment, and Microsoft migration guidance before purchase.

A CSP provider change is usually a billing and partner-of-record process rather than a tenant migration, because the Microsoft tenant and service configuration can remain in place when handled correctly. IT Partner should validate whether the current subscription is transferable under Microsoft’s current CSP rules to avoid avoidable service interruption.

The Microsoft catalog price and available terms should be based on the same Microsoft CSP offer, because IT Partner is selling the Government catalog SKU rather than a different product. The final customer billing should still be confirmed in the live configurator, especially if term, billing frequency, taxes, or partner services differ.

Renewal depends on the selected CSP term and billing option, because the catalog supports both monthly and annual commitment paths. Confirm renewal date, auto-renew behavior, cancellation window, and billing frequency with IT Partner before placing the order.

Changes may be limited after the Microsoft CSP commitment is placed, because cancellation and reduction rules depend on the selected term and Microsoft’s current commerce policies. Confirm whether the order is monthly commitment, annual paid upfront, or annual paid monthly before buying if flexibility is important.

Not automatically, because this page is specifically for Government-segment purchasing even though the broader product family may appear in Charity, Education, Commercial, and Government segments. Nonprofits should validate Charity eligibility and grant context, schools should validate Education eligibility such as student versus faculty use, and standard businesses should use the Commercial path rather than the Government offer.