WorkCycle365 Requirements
WC365 is intentionally lightweight. The platform runs entirely inside Microsoft 365 using native services, so the licensing and infrastructure footprint is minimal. Most organizations already meet the baseline requirements without needing to purchase anything new.
Service Account Requirements
WorkCycle365 is designed to run on the lowest practical Microsoft 365 licensing tier. It uses only standard connectors and seeded Power Automate capacity, and it does not require Dataverse, custom connectors, external databases, or additional infrastructure. The licensing tiers below reflect real-world throughput and Microsoft’s identity architecture.
The service account performs lifecycle orchestration and must be able to read, write, and update identity and SharePoint data.
User Administrator (required)
SharePoint Site Owner for the WC365 configuration site
Entra ID P1 (required)
Teams access if using Teams‑based notifications
Power Apps import permissions for solution deployment
No Global Admin permissions are required.
Licensing Requirements
WorkCycle365 is designed to run on the lowest practical Microsoft 365 licensing tier. It uses only standard connectors and seeded Power Automate capacity, and it does not require Dataverse, custom connectors, external databases, or additional infrastructure. The licensing tiers below reflect real-world throughput and Microsoft’s identity architecture.
Microsoft 365 Business Basic + Entra ID P1
This is the lightest configuration that still supports modern identity automation. Entra ID P1 enables dynamic groups and group-based licensing, which are foundational to WorkCycle365’s architecture.
Best for:
Small organizations
Low-volume lifecycle activity
Environments with only a few hires per week
Tenants prioritizing minimal licensing cost
What to expect:
Supports roughly 10 lifecycle events per day
Fully compatible with all WorkCycle365 flows
Uses only seeded Power Automate capacity
This tier is intentionally lean and cost-efficient. Many organizations start here.
Microsoft 365 E3
Many organizations already license their workforce on E3 for reasons unrelated to WorkCycle365. When E3 is already in place, the service account can inherit the same licensing model for consistency.
Best for:
Organizations already standardized on E3
Tenants with steady lifecycle activity
Environments that benefit from higher seeded limits
What to expect:
Supports roughly 15 lifecycle events per day
Higher daily action limits than Business Basic
More predictable throughput during busy periods
E3 is not required for WorkCycle365.
WorkCycle365 does not require Power Automate Premium. Some organizations choose to license the service account with Premium to increase throughput during high-volume periods.
Best for:
High-churn environments
Large organizations with frequent hires
Tenants with complex provisioning scenarios
What to expect:
Significantly higher daily action capacity
Faster execution during peak activity
No impact on end-user licensing
Premium is a scaling choice made by the organization not a requirement of WorkCycle365.
Power Automate Premium
Environment Requirements
WorkCycle365 is designed to run on the lowest practical Microsoft 365 licensing tier. It uses only standard connectors and seeded Power Automate capacity, and it does not require Dataverse, custom connectors, external databases, or additional infrastructure. The licensing tiers below reflect real-world throughput and Microsoft’s identity architecture.
WC365 can run in any standard Microsoft 365 environment.
A SharePoint‑backed Team is recommended for visibility and collaboration
A standalone SharePoint site is also supported for organizations that prefer a non‑Teams footprint
No external systems, servers, or databases are needed
No custom hosting or infrastructure to maintain
WC365 is fully tenant‑native and portable across environments.
What You Don't Need
WC365 removes the overhead common in lifecycle platforms and is a turnkey solution. There’s no infrastructure to deploy, no external systems to maintain, and no premium stack required to get started.
No servers
No Azure Functions
No SQL databases
No Dataverse
No custom APIs
No external identity systems
No premium automation unless you choose it
No need for months of consulting
WC365 runs entirely inside Microsoft 365 using the tools your organization already has. The platform stays lightweight, easy to adopt, and simple to maintain—whether you support ten lifecycle events a month or hundreds.