Trust Center

WorkCycle365 is designed to operate within the Microsoft environment you already control.
Lifecycle processing uses customer-selected Microsoft 365 and Power Platform services, customer-owned connections, and standard Microsoft connectors. Your organization retains control of identities, permissions, data, retention, and policy, with no vendor-hosted operational data store, external runtime, telemetry service, or persistent vendor access path.

Customer controlled by design

Your organization keeps control of identities, connections, permissions, destinations, records, retention, and policies.

WorkCycle365 stays inside the Microsoft environment your organization controls.

  • Customer-owned connections provide access to the Microsoft services WorkCycle365 uses.

  • SharePoint stores configuration, requests, and operational records.

  • Teams and Outlook provide configured communication experiences.

  • Microsoft Entra ID supports identity and lifecycle actions.

  • Your existing tenant policies, licensing, access controls, and retention rules remain in effect.

  • WorkCycle365 has no vendor identity, hosted runtime, or persistent access path into your tenant.

Microsoft services and connectors

The current WorkCycle365 topology uses standard built in Microsoft connectors and no custom or premium connectors. Availability remains subject to the customer tenant’s licensing, policies, and configuration.

Where lifecycle records live
black blue and yellow textile
black blue and yellow textile

WorkCycle365 lifecycle records remain in customer-selected Microsoft services.

Core locations include:

SharePoint for configuration, requests, and operational records.

Outlook and Exchange Online for configured email and calendar activity.

Teams for operational communication.

Microsoft Entra ID for identity context and configured lifecycle actions.

Retention, access, and protection remain governed by the customer’s Microsoft environment.

a man riding a skateboard down the side of a ramp
a man riding a skateboard down the side of a ramp
a man riding a skateboard down a street next to tall buildings
a man riding a skateboard down a street next to tall buildings
Limited external surfaces

WorkCycle365 has only limited, intentional, and optional external touchpoints.

Optional recipients:


Configured recipients outside the tenant may receive applicable communications.

External image delivery:
WorkCycle365 branding and an optional customer logo may load from externally reachable HTTPS addresses.

These image requests contain no lifecycle data and are not used for telemetry, analytics, tracking, or runtime processing.

There is no vendor-hosted lifecycle data store or external operational runtime.

WorkCycle365 relies on standard Microsoft connectors across its connected Microsoft 365 services.

Connected services include:

SharePoint Online.

Microsoft Entra ID and Microsoft 365 Users.

Microsoft 365 Groups and Teams.

Outlook, Microsoft Approvals, and Excel Online for Business.

Power Apps and Power Automate support the user experience and workflow orchestration.

Customer DLP policies and connector availability remain in effect.

Standard connector posture

Shared responsibility

WorkCycle365, Microsoft, and your organization each play a defined role in protecting the operating environment.

a man riding a skateboard down the side of a ramp
a man riding a skateboard down the side of a ramp

WorkCycle365 provides the solution logic, documented configuration, and intended operating model.

Microsoft provides the security, availability, and platform controls of Microsoft 365 and Power Platform.

Your organization controls identities, permissions, connections, licensing, policies, retention, and access to its data.

Deployment is validated within the customer tenant before handoff, while ongoing governance remains under customer control.

Operational records may contain employee lifecycle and identity information and should be protected according to your organization’s existing security, privacy, and records-management policies.

What WorkCycle365 does not add

The WorkCycle365 operating boundary is intentionally simple and transparent.

  • No vendor-hosted operational database.

  • No external lifecycle runtime.

  • No telemetry, tracking, or phoning-home service.

  • No vendor identity or persistent support access into customer operational data.

  • No custom connector.

  • No premium connector required by the current solution.

  • No separate vendor data warehouse or lifecycle archive.

  • No vendor-imposed retention schedule.

Customer-selected Microsoft services remain the operating boundary.

Top

See where WorkCycle365 fits

Tell us how your teams coordinate employee transitions today.

[email protected]