Power Automate unattended RPA add-on — Pricing, Plans & What's Included

The Power Automate unattended RPA add-on provides licensing for unattended robotic process automation in Power Automate, because it is designed to let approved automations run without a person manually driving every step. It is a Commercial add-on subscription option available with monthly or annual commitment choices, subject to current Microsoft licensing and technical requirements.

No, the Power Automate unattended RPA add-on is not a standalone license, because it is sold as an add-on that requires the correct base Power Automate licensing in the customer tenant. Before purchase, confirm the required base license, assignment model, and deployment design with IT Partner or Microsoft licensing guidance.

The Power Automate unattended RPA add-on does not include a standalone Power Automate base license, infrastructure, operating system rights, hosting, remote access, target-application licenses, or automation development services. Those items must be validated separately because unattended RPA depends on the machine setup, application licensing, authentication method, and operating model used for the automation.

The required quantity depends on the unattended RPA deployment design, because Microsoft licensing and technical rules can depend on how and where the unattended work runs. Confirm the number of add-ons needed for your machines, processes, schedules, and runtime approach before ordering, rather than estimating only by the number of users.

Commercial customers can choose a monthly commitment with monthly billing, or an annual commitment paid either upfront or monthly, because the CSP catalog supports those subscription structures for this offer. Annual upfront is typically the lowest total-commitment option in the catalog, annual paid monthly can help cash flow, and monthly commitment is best when the automation need may be temporary.

Choose monthly commitment if the unattended RPA need is uncertain or short-term, because it gives more flexibility at renewal and cancellation points. Choose annual commitment if the bot is part of an ongoing production automation plan, because it better matches long-running deployments and usually provides the more predictable commitment structure.

No, this product should be treated specifically as the unattended RPA add-on, because its purpose is to add unattended RPA licensing to an eligible Power Automate setup. If you also need attended desktop automation, confirm whether your base Power Automate licensing already covers it or whether another current Power Automate plan is more appropriate.

Do not assume that Microsoft 365, Teams, or Power Automate for Teams provides the required base rights, because seeded or limited automation rights generally do not equal full unattended RPA licensing. Confirm the exact base Power Automate license required in the tenant before buying this add-on.

No, Copilot should not be treated as a replacement for the Power Automate unattended RPA add-on, because Copilot capabilities and unattended desktop automation licensing are separate licensing questions. If Copilot helps design or trigger an automation, you still need to confirm that the Power Automate base license, unattended RPA add-on, connectors, and runtime setup are properly licensed.

Yes, unattended RPA is intended for automations that can run without a person manually operating every step, because that is the purpose of the unattended add-on. The process still must be technically suitable for unattended execution, including supported authentication, stable application behavior, compliant credential handling, and any required machine or runtime configuration.

Review Power Platform environment governance, data loss prevention policies, connector usage, credential handling, machine access, logging, and target-application permissions, because unattended RPA can access business systems without a user actively present. The add-on provides licensing, not a guarantee that your automation design meets your organization’s security or compliance requirements.

Credentials for unattended RPA must be designed carefully, because automations may need to sign in to systems without an interactive user approving each step. Confirm whether the target applications support unattended authentication, whether MFA or conditional access will block the flow, and whether your credential storage and account model comply with company policy.

Validate the base Power Automate license, add-on quantity, machine or hosting design, target-application licensing, credentials, process stability, triggers or schedules, monitoring, and support ownership, because licensing alone does not make a process suitable for unattended automation. IT Partner can help document these prerequisites before checkout so the subscription matches the automation you are ready to deploy.

The current CSP catalog entry for this Commercial offer does not show a trial option, because it is listed as a paid add-on subscription. If you need a proof of concept, confirm whether another Microsoft evaluation path or a limited paid pilot is the right approach before purchasing production quantities.

A CSP partner transfer should not require reinstalling Power Automate or moving tenant data, because the Microsoft cloud service remains in the customer tenant while the CSP billing and support relationship changes. Service continuity is normally preserved, but confirm timing, delegated admin permissions, renewal status, and any subscription changes with IT Partner before initiating the transfer.

The underlying Commercial Microsoft offer remains the same catalog product, because a CSP transfer changes the partner relationship rather than the product identity. However, the final billed amount, applicable terms, and checkout total must be confirmed with IT Partner before transfer, because CSP partners present the final customer agreement and billing details.

Cancellation and quantity reduction depend on the CSP subscription term and Microsoft commerce rules, because annual commitments and monthly commitments have different flexibility. In general, annual paid monthly is still an annual commitment, so confirm cancellation windows, renewal settings, and reduction timing before ordering.

Yes, additional licenses can typically be added when more unattended RPA capacity is needed, because CSP subscriptions support quantity changes subject to Microsoft commerce rules. Reductions are more restricted than increases, so size the initial order carefully and confirm any prorated billing or renewal impact at checkout.

No, a Government customer should not assume the Commercial add-on is the right purchase, because GCC, GCC High, and related government cloud environments can have separate availability, residency, compliance, and procurement requirements. Confirm the correct Government offer, tenant cloud, data residency needs, and unattended RPA availability before ordering.

Not automatically, because nonprofit and education customers may have separate eligibility rules, offers, grants, or assignment models that differ from the Commercial catalog. A nonprofit should confirm Charity eligibility and grant context, while an education customer should confirm whether the intended users or automation owners fall under student, faculty, or staff licensing rules before purchasing.