Microsoft 365 Automation Assessment
The Microsoft 365 Automation Assessment gives you a written inventory of up to five current or proposed workflows, a recommendation for each (Power Automate, Zapier, or leave…
We implement one agreed workflow in one commercial Microsoft 365 environment: one trigger and up to five connector actions on one straight-through path, with a client-approved test and written sign-off. Power Automate is used when a suitable connector supports the required operation. Zapier is considered only when no suitable Power Automate connector exists for the required non-Microsoft app or the customer already uses Zapier, subject to security approval. The standard unit covers one workflow and typically takes up to five working days. Contact us for a quote. Platform licenses and vendor usage are separate customer costs.
This is a fixed-scope implementation for one workflow in one commercial tenant. A workflow is one event trigger plus up to five connector actions on one straight-through path; the trigger does not count as an action. Branches, loops, additional environments, and additional workflows are separately scoped. The client signs off the agreed acceptance test before handover. Power Automate is the default when a suitable connector supports the required operation. Zapier is considered only if no suitable Power Automate connector exists for the required non-Microsoft app or the customer already uses Zapier. A Zapier path requires customer approval of data movement, the connector's auth/permissions, Entra consent where applicable, and Power Platform DLP implications. We do not assert that every Zapier connection uses Entra OAuth or has access to mailboxes or SharePoint. The customer owns the accounts and connections; we do not retain credentials. Many Microsoft 365 plans include seeded Power Automate rights for standard connectors, subject to the exact SKU, use rights, and service limits. Do not assume every Microsoft 365 subscription or scenario is covered. Premium connectors, including SQL Server, HTTP, Dataverse, and some third-party connectors, require separately licensed Power Automate Premium (currently listed at US $15 per user/month) or an eligible Process/per-flow license. The customer buys Microsoft licenses directly; regional prices and eligibility must be confirmed against current Microsoft terms. Zapier and connected-app subscriptions are separately paid by the customer directly to their vendors; IT Partner does not resell Zapier and receives no revenue from its subscription. Zapier's published compliance materials do not list FedRAMP authorization, so GCC, GCC High, and FedRAMP-required workloads are excluded. Custom-code or connector work is out of this standard service unless separately scoped and priced. Zapier is only a descriptive reference to a third-party platform, not the name of the service.
Approve one commercial environment, one trigger, up to five actions on one path, connectors, field mappings, acceptance tests, and fixed per-workflow fee.
Confirm the exact connector tier and Microsoft 365 use rights; obtain separate premium licensing when needed. Review data movement, actual authentication and permissions, relevant Entra consent, DLP policy, and customer-owned connection accounts.
Build with Power Automate first where a suitable connector exists. Use Zapier only under the stated exception rule and customer approval. Test the agreed normal and exception paths; document unsupported requirements.
Obtain written process-owner acceptance, enable only the approved production workflow, and provide operator handover. New work requires another fixed per-workflow scope or a written change.
One trigger and up to five connector actions on one straight-through path in one commercial environment. The trigger does not count as an action. Branches, loops, additional environments, or additional workflows require a separate quote.
Contact us for a quote for the standard unit: one commercial environment, one trigger, up to five connector actions on one straight-through path. The final price and any exclusions are confirmed in the statement of work.
Power Automate is first choice when a suitable connector supports the operation. Zapier may be used only when no suitable Power Automate connector exists for the required non-Microsoft app or the customer already uses Zapier, after customer security approval.
Many Microsoft 365 plans include seeded Power Automate rights for standard connectors, subject to the exact SKU, use rights, and service limits. Do not assume every Microsoft 365 subscription or scenario is covered. Premium connectors, including SQL Server, HTTP, Dataverse, and some third-party connectors, require separately licensed Power Automate Premium (currently listed at US $15 per user/month) or an eligible Process/per-flow license. The customer buys Microsoft licenses directly; regional prices and eligibility must be confirmed against current Microsoft terms. Zapier and connected-app subscriptions are separately paid by the customer directly to their vendors; IT Partner does not resell Zapier and receives no revenue from its subscription.
The client approves one representative acceptance test and agreed exception cases before build. The process owner signs off results before production enablement. Replays or production writes outside this plan require separate approval.
No. These are commercial-tenant services; GCC, GCC High, and workloads requiring FedRAMP authorization are excluded.
No. Custom code, Azure Functions, Logic Apps, custom connectors, and bespoke APIs are excluded from the standard unit and can only be separately scoped and priced.
No. The customer pays Zapier and connected-app vendors directly. IT Partner does not resell Zapier or earn subscription revenue.