JML360 is a governed joiner, mover and leaver service layer for MSPs delivering Microsoft Entra services. It helps structure requests, approvals, evidence, access-change history, and customer visibility.

Does JML360 replace Microsoft Entra?

No. JML360 is not a replacement for Microsoft Entra. It is a service layer for MSPs managing joiner, mover and leaver work around Microsoft Entra tenants.

What problem does JML360 solve for MSPs?

JML360 helps MSPs move from fragmented or purely automated JML execution into a controlled service model with clear requests, business approvals, evidence trails, and repeatable customer reporting.

JML360

Employee lifecycle assurance for MSPs

Know whether every employee technology change was actually completed.

Q: Does JML360 replace Rewst, CIPP, PSA workflows, Power Automate, or internal scripts?

No. JML360 is designed to sit around existing automation and service tools. Those tools can execute work; JML360 focuses on the governed request, approval, evidence, and service record.

JML360 is the control layer between client decisions and MSP delivery. It keeps authority with the customer, works with the selected delivery path and checks the result against what was approved.

Discuss a controlled proof See how assurance works

Start with leaver completion assurance, then extend the same governed model across joiners and movers.

JML360 client approval and assurance dashboard showing approval outcomes, users, licences, devices and deployed applications — Client decisions, lifecycle status and technology visibility in one workspace.

Defined outcomeWhat must be achieved

Client authorityThe customer decides

Existing deliveryThe MSP keeps its tools

Evidence-backed resultCompletion is checked

The assurance gap

A closed ticket does not prove the employee lifecycle is complete.

Work can be marked done while access, licences, devices or applications remain unresolved.

Each system reports its part. Without one control layer, no one owns or proves the complete business outcome.

Fragmented ownership

Different teams and tools each complete only part of the lifecycle change.

False closure

A successful task or ticket can hide an incomplete overall outcome.

Weak evidence

The customer cannot easily see what happened or what remains unresolved.

Lifecycle control layer

Govern the outcome without replacing the tools that deliver it.

JML360 connects the business decision, the approved work, the selected delivery path and the resulting evidence.

Define the outcome

Make clear what the employee lifecycle change must achieve.

Protect authority

Request and approval remain with authorised client users.

Coordinate delivery

Use JML360 or the MSP’s configured delivery path.

Verify reality

Compare the resulting state with the approved outcome.

Clear authority

The client decides. The MSP delivers. JML360 verifies.

The customer sees the decision it owns, while approved work follows the selected delivery path and returns for outcome checking.

JML360 workflow selection for a joiner, mover or leaver request — A clear client journey without exposing delivery complexity.

Assurance context

See the people, access and technology behind each lifecycle decision.

JML360 turns read-only observations of users, licences, devices and deployed applications into business-readable context while preserving source and freshness.

JML360 application assurance view mapping deployed applications to associated users — Understand deployed applications and who they affect without replacing the source system.

Fits existing service delivery

Keep your PSA, automation and Microsoft tooling.

JML360 can perform approved work or route it to one MSP-configured delivery path, then receive and check the result. Delivery never becomes client decision authority.

StageAuthorityJML360 control

RequestClientStructured and recorded

ApprovalClient approverBound to the intended outcome

ExecutionSelected providerOnly after approval

ResultJML360 assuranceChecked against the request

JML360 client reports for users, licences, devices and application distribution with CSV export — Business-readable reporting with governed CSV export.

Evidence, not activity

Show what was approved, what happened and what still needs attention.

Clients can review lifecycle outcomes alongside visible users, licences, devices and application distribution, then export the governed view.

Commercial starting point

Start with leaver completion assurance. Prove value before expanding.

Begin with one customer and one repeatable process. Make incomplete outcomes visible, create defensible evidence and expand from demonstrated value.

Discuss a controlled proof

Low-friction start

Qualify one customer and one lifecycle process without replacing the MSP stack.

Visible value

Expose completion gaps and produce evidence the customer can understand.

Repeatable service

Extend the proven model across customers while CooperBox maintains the platform.

Buyer questions

Clear answers for MSPs assessing lifecycle assurance.

JML360 is designed for MSPs that need to govern and prove the complete employee technology outcome across client decisions and fragmented delivery systems.

What is JML360?

JML360 is an employee lifecycle assurance control layer. It connects client authority, MSP delivery, observed outcomes and evidence in one governed journey.

Does JML360 replace Rewst, CIPP, PSA workflows, Power Automate, or internal scripts?

No. Those tools can still deliver approved work. JML360 governs the intended outcome, client authority, hand-off, result checking and evidence around them.

Can JML360 deliver the work directly?

Yes. A client can use a JML360-managed path or its MSP’s configured external automation path. Only one approved execution owner is selected for the client.

Who is JML360 for?

Microsoft-focused MSPs and clients that need to know whether employee technology changes were fully completed, not merely marked done.

Controlled proof

See where your current leaver process loses assurance.

Start with one client and one process. Keep the delivery tools that work and make completion visible.

Discuss a controlled proof