# 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 manual), connector and licensing impact, and a fixed implementation quote for each standard workflow. We check Microsoft Entra enterprise-app consent settings where relevant, Power Platform DLP policies, and whether each connection belongs to a named user or a customer-approved service account. The standard scope covers one commercial tenant, one program, and up to five workflows, typically over three working days. Contact us for a quote. Power Automate and third-party licenses are separate customer costs.

Canonical: https://o365hq.com/services/microsoft-365-automation-assessment
Provider: IT Partner LLC — US Microsoft partner since 2006. Book: https://o365hq.com/book

**Price:** Contact us for a quote · Fixed price, pay after approval.

## Overview

We start with the Microsoft 365 automation and business-process competencies already in your environment. For each of up to five workflows in one automation program, we create a written current-state record and recommend Power Automate, Zapier, or leaving the process manual. Power Automate is the default when a suitable connector and required operation are available. Zapier is considered only when no suitable Power Automate connector exists for the required non-Microsoft app, or when the customer already uses Zapier, and only after security and data-handling approval.

The assessment records source and destination, trigger and actions, data categories, owner, available evidence, required licensing, and operating and exception responsibilities. It also checks the tenant's Entra enterprise-app consent settings and applicable grants for Microsoft connections where those integrations use an Entra enterprise application; Power Platform DLP connector classifications and environment policies; and whether each connection is owned by a named user or a customer-approved service account. Authentication varies by connector: we document the actual auth method, permission scope, and token/consent path rather than assuming every connection is an Entra OAuth grant or has mailbox or SharePoint access. We do not grant consent or change production policies during this assessment.

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 security/compliance materials do not list FedRAMP authorization; accordingly, GCC, GCC High, and workloads requiring FedRAMP are excluded. This commercial-only assessment produces the inventory, platform decision, security/licensing impact, and a fixed implementation quote for each recommended standard workflow; it does not change production. The word Zapier is used only as a factual reference to a third-party tool, not as our service or product name.

## Success criteria

- The client receives a written inventory of every in-scope workflow and a Power Automate, Zapier, or manual recommendation for each.
- Each recommendation records connector availability, required operation, license/consumption implications, data flow, and connection ownership.
- The relevant Entra consent and Power Platform DLP checks and actual connector authentication path are documented, including any evidence gaps.
- Each recommended standard implementation has a fixed written quote and defined acceptance criteria; no production changes are performed.

## Deliverables

- Written inventory of up to five current or proposed workflows in one program, identifying the source, destination, trigger, actions, owner, data categories, exception path, and available evidence.
- A written recommendation for every inventoried workflow: Power Automate, Zapier, or leave manual, with the connector/operation evidence and the reason for the choice.
- Per-workflow licensing impact distinguishing Microsoft 365 seeded standard-connector rights from any separately licensed Power Automate Premium or Process/per-flow entitlement, plus customer-paid Zapier and connected-app subscriptions and consumption.
- Security review record covering Entra enterprise-app consent settings and relevant grants where applicable, actual authentication and permission scopes, Power Platform DLP policy/classification, and named-user versus customer-approved service-account connection ownership.
- A fixed implementation quote for each recommended workflow against the stated standard workflow boundary; material exceptions are separately identified and quoted.
- Findings walkthrough, outstanding decisions, and implementation acceptance criteria.

## Licensing and third-party costs

- Many Microsoft 365 subscriptions include Power Automate seeded rights for standard connectors, subject to the exact SKU, use rights, and service limits. This does not mean every connector or workflow is included at no additional charge; we verify the customer's specific plan and required operations.
- Premium Power Automate connectors, including SQL Server, HTTP, Dataverse, and most third-party connectors, require a separately licensed Power Automate Premium plan (currently US list price $15 per user/month) or an eligible Process/per-flow license. Microsoft pricing is regional and may change; verify eligibility and current price before purchase.
- The customer buys Microsoft, Power Automate, Zapier, and connected-app subscriptions directly from their vendors and pays all task, API, and consumption fees. IT Partner does not resell Zapier and receives no revenue from its subscription. Power Platform DLP policies govern Power Platform flows/connectors, not Zapier itself.

## Implementation plan

1. **Confirm scope and evidence** — Agree one commercial tenant, one program, up to five workflows, owners, approved evidence sources, and the data-handling boundary.
2. **Inventory and assess security** — Document each workflow, its connector operations and actual auth path; review relevant Entra app-consent settings and grants, Power Platform DLP policy, and named-user or service-account ownership without granting consent or changing production.
3. **Compare platform and licensing** — Recommend Power Automate, Zapier, or manual per workflow. Choose Zapier only when no suitable Power Automate connector exists for the required non-Microsoft app or the customer already uses Zapier, and only if customer security approves. Verify exact Microsoft, Zapier, and app entitlements and vendor costs.
4. **Quote and hand over** — Deliver the written inventory, licensing/security impact, recommendation, fixed quote per standard workflow, and unresolved-decision list.

## Prerequisites

- One commercial Microsoft 365 tenant, one automation program, a named process owner, and an administrator/technical contact.
- Up to five candidate workflows, existing automation inventory, process documentation, and sanitized sample data.
- The tenant's Microsoft 365 license SKUs, relevant Power Automate environments and DLP policies, Entra enterprise-app consent settings, and relevant connection-owner information, provided through approved read-only evidence or a client-led demonstration.
- The client's approval of evidence handling and whether any workflow data may leave Microsoft 365.
- Confirmation that no in-scope tenant or data requires GCC, GCC High, or FedRAMP authorization.
- Standard scope is one tenant, one program, and up to five workflows. Additional candidates or tenants require separate written scope.

## Responsibilities

**IT Partner:**

- Deliver only the approved, commercially scoped work described in the statement of work.
- Verify connector, license, security, and access assumptions against the client's actual environment.
- Obtain client authorization before consent, production changes, grant removal, replay, or work beyond the approved cap.
- Document evidence, test outcomes, limitations, and the customer handover.

**Client:**

- Provide accurate workflow, licensing, data-handling, access, and connection-owner information.
- Buy and maintain Microsoft, Zapier, and connected-app licenses directly from their vendors.
- Approve consent, DLP, data movement, access, production changes, acceptance, and any change to the commercial cap.
- Name the workflow operator and retain post-handover responsibility for subscriptions, connections, and ongoing operation.

## Not included

- Commercial Microsoft 365 tenants only. GCC and GCC High tenants, and workloads requiring FedRAMP authorization, are out of scope for all three services.
- Microsoft, Power Automate, Zapier, and connected-app subscriptions, premium connector licenses, API fees, and task or other consumption charges are paid separately by the customer directly to the vendors. IT Partner does not resell Zapier and receives no revenue from its subscription.
- Azure Functions, Logic Apps, custom connectors, custom Zapier apps, code steps, bespoke middleware, and custom APIs are not part of the standard offer. Any such development requires a separately approved and priced engagement.
- Production workflow creation, connection authorization, application configuration changes, or remediation.
- Historical data migration, bulk cleanup, bidirectional synchronization design, or enterprise-wide process reengineering.
- Continuous monitoring, managed operations, ongoing maintenance, guaranteed savings, or a delivery schedule for a later implementation.

## Limitations & technical notes

- Power Automate seeded rights and connector tiers depend on the exact customer SKU, use rights, region, and current vendor terms; verify these before quoting.
- Authentication and permissions vary by connector. Entra enterprise-app consent review applies only where the actual Microsoft integration uses that consent path; do not infer mailbox or SharePoint access.
- Zapier is not used as a fallback for GCC, GCC High, or FedRAMP-required workloads. The customer must approve third-party data movement.
- The name Zapier is used descriptively to identify a third-party product only; no endorsement, partnership, certification, or resale is claimed.

## FAQ

### What does the Microsoft 365 Automation Assessment deliver?

A written inventory of up to five workflows, a Power Automate, Zapier, or manual recommendation for each, licensing and security findings, and a fixed implementation quote for each recommended standard workflow.

### How do you choose between Power Automate and Zapier?

Power Automate is first choice when a suitable connector supports the needed operation. Zapier is considered only when no suitable Power Automate connector exists for the required non-Microsoft app or the customer already uses Zapier, and only after customer security approval.

### What is the assessment scope and how much does it cost?

The standard scope covers one commercial tenant, one program, and up to five workflows, typically over three working days. Contact us for a quote; the final price is confirmed in the statement of work.

### Are licenses included?

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.

### What security checks are included?

We review applicable Entra enterprise-app consent settings and grants, Power Platform DLP policies and connector classifications, and connection ownership. We record each connector's actual authentication and permission model rather than assume every connection is an Entra OAuth grant or accesses mailboxes or SharePoint.

### Can you assess GCC, GCC High, or FedRAMP workloads?

No. These are commercial-tenant services. GCC, GCC High, and workloads requiring FedRAMP authorization are out of scope because Zapier's published compliance materials do not list FedRAMP authorization.

### Will the assessment change our production tenant?

No. The assessment uses approved evidence or demonstrations and does not create connections, grant consent, change DLP policy, or enable production workflows.

### Does the Zapier name mean an official partnership?

No. Zapier is referenced only as a third-party tool option. IT Partner does not claim endorsement, certification, or official partner status.

---

Fixed-price engagement by IT Partner LLC. To scope it for your tenant, book a call with Mike (https://o365hq.com/book) or request a quote via the site's /api (see https://o365hq.com/openapi.json).