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

Power Automate unattended RPA add-on for Nonprofits is an add-on license for eligible charity tenants that need robotic process automation to run without an actively signed-in user driving the desktop session. It is useful for back-office nonprofit processes, legacy application automation, and scheduled administrative work, because unattended RPA is designed for automations that run independently rather than as a user-assisted desktop task.

No, Power Automate unattended RPA add-on is not a standalone Power Automate plan, because the source offer identifies it as an add-on. A charity buyer should confirm the required base Power Automate licensing before purchase, because Microsoft prerequisite SKUs and assignment rules must be validated for the intended automation design.

The Charity version includes nonprofit-priced purchasing access to the Power Automate unattended RPA add-on for eligible nonprofit organizations. It includes listed subscription choices for monthly commitment, annual commitment paid upfront, and annual commitment paid monthly, because the Charity offer is available in those commitment and billing structures.

Power Automate unattended RPA add-on does not include a full standalone Power Automate base plan, nonprofit eligibility approval, Windows or VM infrastructure, third-party application licenses, or a confirmed bot architecture. Those items are separate, because the add-on only addresses unattended RPA add-on licensing and does not automatically license every component used by the automation.

No, a nonprofit should not buy the unattended RPA add-on only for attended automation, because attended automation is run with active user interaction and may require a different Power Automate licensing approach. The add-on is appropriate when the automation must run unattended, such as scheduled back-office processing or legacy application tasks without a user at the keyboard.

No, the unattended RPA add-on should not be assumed to include the machine, VM, Windows rights, hosted desktop, or infrastructure needed to run the bot. Those requirements depend on the deployment architecture, because unattended RPA typically needs a properly licensed and managed Windows environment, application access, and operational controls.

The exact assignment, capacity, bot, machine, and concurrency model should be confirmed against current Microsoft licensing terms before sizing. This is important because the source identifies the offer as an unattended RPA add-on but does not specify the machine, session, or concurrency rules needed to design a compliant deployment.

No, Power Automate unattended RPA add-on does not include Microsoft Teams, Microsoft 365 apps, Teams Phone, or user collaboration licensing. Those products are licensed separately, because this add-on is specifically for unattended RPA scenarios in Power Automate and not for broader productivity workloads.

No, Copilot, AI Builder capacity, and hosted RPA should not be assumed to be included with this unattended RPA add-on. They may require separate licensing or a different Power Automate offer, because the listed Charity product is specifically the unattended RPA add-on and not a bundled AI or hosted infrastructure package.

A nonprofit must first qualify under Microsoft nonprofit eligibility rules, because Non-Profit Pricing is intended only for eligible nonprofit organizations. Whether grant benefits apply to this specific add-on should be confirmed before purchase, because nonprofit eligibility and grant entitlement are related but not always the same thing.

For Charity customers, the unattended RPA add-on is available as a month-to-month commitment with monthly billing, an annual commitment paid upfront, or an annual commitment paid monthly. Annual upfront has the lowest listed annualized rate posture among the listed options, while month-to-month is more flexible and annual paid monthly balances commitment with cash-flow flexibility.

No, the source offer does not list a trial for the Charity unattended RPA add-on. A nonprofit should validate the automation design before purchase, because testing the process, prerequisites, machine access, and application permissions reduces the risk of buying the wrong licensing model.

A nonprofit should plan least-privilege identities, controlled credentials, environment-level governance, data loss prevention policies, logging, and bot run monitoring, because unattended automations can access systems without a user present. The add-on licenses the unattended RPA capability, but it does not replace secure configuration, application permissions, or operational oversight.

No, the unattended RPA add-on by itself does not determine data residency, regulatory compliance, or whether every connected system is compliant. Compliance depends on the Microsoft cloud environment, Power Platform configuration, connectors, data sources, machine location, and the nonprofit’s own controls, so regulated nonprofits should confirm the design before deployment.

A charity should not assume the Charity commercial-cloud offer satisfies government cloud or controlled data requirements, because GCC and GCC High are separate government cloud environments with different eligibility and compliance considerations. If the nonprofit handles government-regulated workloads, ITAR-like requirements, or agency-mandated residency controls, it should confirm whether Government, GCC, or GCC High licensing is required before buying.

A nonprofit should start by documenting the process to automate, the target applications, whether it truly needs unattended execution, the required machine or VM design, and the prerequisite Power Automate licensing. This sequence matters because unattended RPA licensing cannot be sized correctly until the organization understands service accounts, application access, concurrency, and whether a hosted RPA option would be more appropriate.

Yes, a nonprofit can often redesign an attended desktop automation or manual process for unattended RPA, but the licensing and architecture should be reassessed first. The change matters because unattended execution may require different identity handling, machine availability, application permissions, scheduling, monitoring, and add-on licensing than an attended user-run flow.

A CSP move to IT Partner is normally an administrative and subscription-provider change rather than a tenant migration, because the Microsoft tenant, Power Platform environments, flows, and bot assets can remain in place. IT Partner should still review the current provider, term dates, and subscription rules, because some changes may need to be scheduled at renewal or handled through a replacement subscription plan.

Moving to IT Partner should not change the nonprofit’s Microsoft tenant data, because the tenant and Power Platform environment are separate from the CSP billing relationship. The underlying Microsoft nonprofit offer family can remain the same where available, but invoicing, taxes, currency, partner terms, and timing should be confirmed before transfer.

Renewal and cancellation rules depend on the selected commitment term, because month-to-month subscriptions are generally more flexible while annual commitments usually lock in the term after Microsoft’s limited cancellation window. Quantity increases are typically easier than reductions during a committed term, so a nonprofit should size cautiously and confirm CSP change rules before purchasing or renewing.