Governed managed JML service for MSPs

Turn hidden JML work into a managed service customers can approve and trust.

JML360 helps MSPs take the joiner, mover and leaver work already happening in tickets, emails, scripts, PSA notes, and technician memory, then package it as a repeatable customer-facing service with requests, approvals, evidence, and service history across Microsoft Entra tenants.

Works alongside Rewst, CIPP, PSA workflows, Power Automate, and internal scripts.
Hidden workMade visible and sellable
Request intakeStandard customer path
Approval evidenceBusiness context attached
Service recordCustomer-visible delivery

The real MSP pain

MSPs are already doing JML work. Too much of it is hidden inside support.

The work already exists.
The commercial service model is usually missing.

Joiners, movers and leavers often arrive as tickets, emails, quick scripts, PSA notes, and technician memory. That work consumes skilled time, carries access risk, and is hard to explain to customers as a named managed service.

Hidden labour

Skilled technicians keep handling predictable JML work that should be packaged and standardised.

Hidden approvals

Business approval is often buried in tickets, email threads, or side conversations.

Hidden evidence

The customer cannot easily see what changed, when, why, and who approved it.

Product definition

A governed service layer for the JML work your team already delivers.

JML360 gives MSPs a standard operating layer for customer JML requests, approvals, access changes, evidence, and service records. It is designed to sit around the automation and service tools you already use, not replace them.

01

Request intake

Capture joiner, mover and leaver details in a consistent format before execution starts.

02

Approval evidence

Keep business approval tied to the access change, not buried in tickets or email threads.

03

Access-change record

Track what was changed in Microsoft Entra, when it changed, and why.

04

Service history

Give MSP teams and customers a repeatable record of JML delivery across tenants.

What customers see

Give customers a JML service they can buy, approve, and understand.

JML360 makes the managed service visible to the customer without exposing internal MSP tooling.

Customer request view

A clean way for customer contacts to submit joiner, mover, and leaver requests.

Approval trail

A visible record of who approved the access change and when.

Evidence report

A repeatable service record showing what changed, what was completed, and what needs review.

Automation stack

Keep your automation stack. Add the governed managed-service layer.

Already using Rewst, CIPP, PSA workflows, Power Automate, or internal scripts? Good. Your automation stack can execute the work. JML360 helps standardise the request, approval, evidence, customer visibility, and commercial service model.

LayerExisting stackJML360
Task executionBuilds and runs workflowsUses execution outputs
Customer request modelUsually designed by the MSPPackaged service path
Approval evidenceCan be builtCore workflow
Access-change historyOften fragmentedCentral service record
Customer visibilityVaries by MSPBuilt into service model
Commercial packagingIndirectPrimary purpose

JML maturity

Where most MSPs get stuck.

Level 1

Manual tickets

Slow, inconsistent, technician-heavy.

Level 2

Scripts and PSA workflows

Faster, but fragmented.

Level 3

Automation platforms

Powerful execution, but service design still sits with the MSP.

Level 4

Governed JML service

Requests, approvals, execution, evidence, and customer visibility.

Level 5

Commercialised JML offer

A repeatable service customers can buy and trust.

JML360 helps MSPs move from Level 3 execution into Level 4 and 5 service maturity.

Trust and control

Built for controlled identity operations.

Microsoft Entra focused

Designed around Microsoft Entra joiner, mover, and leaver service delivery.

Approval-first workflow

Access changes stay connected to business approval and request context.

Evidence by design

Service records are kept as part of the workflow, not treated as an afterthought.

MSP multi-tenant model

Built for MSPs managing repeated JML delivery across customer environments.

Hosted and maintained

CooperBox hosts and maintains the JML360 platform for partners.

Data minimisation

Capture what is needed to evidence and manage the JML service.

Partner model

Package JML as a managed service your customers can buy and trust.

JML360 gives partners a governed JML service model they can take to MSPs or use inside their own MSP operation. CooperBox hosts and maintains the platform, while partners focus on turning existing JML demand into a clearer commercial service.

Discuss JML360 partner model

Sellable service model

Turn JML from internal process work into a clear customer-facing offer.

Repeatable delivery

Use one service pattern across multiple customers and Entra tenants.

Hosted by CooperBox

CooperBox maintains the platform, roadmap, and service foundation.

Buyer questions

Clear answers for MSPs assessing JML360.

JML360 is designed for MSPs that already deliver Microsoft Entra joiner, mover and leaver work, but want to turn hidden operational effort into a controlled managed service with requests, approvals, evidence, and customer visibility.

What is JML360?

JML360 is a governed joiner, mover and leaver service layer for MSPs delivering Microsoft Entra services. It helps turn existing JML work into a structured managed service with requests, approvals, evidence, access-change history, and customer-visible service records.

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

No. Those tools can still execute the work. JML360 sits around the automation stack to standardise the request path, approval evidence, Entra change context, and repeatable service history.

Does JML360 replace Microsoft Entra?

No. JML360 is not a replacement for Microsoft Entra. It is a service layer for MSPs managing JML work around Microsoft Entra tenants.

Who is JML360 for?

JML360 is for MSPs and partners that want to turn identity operations into a clearer customer-facing managed service, especially where JML requests, approvals, and evidence are currently fragmented across tickets, email, scripts, automation tools, and manual notes.

What problem does JML360 solve for MSPs?

It helps MSPs move from hidden or fragmented JML execution into a governed service model with clear requests, business approvals, evidence trails, and repeatable customer reporting.

Is JML360 legal, compliance, or security certification?

No. JML360 information is for service evaluation and partner discussion. It is not legal advice, compliance certification, a security audit, or a guarantee of Microsoft Entra configuration or customer access outcomes.

Partner discussion

Build a JML service customers can buy and trust.

If your MSP already handles JML work but needs a cleaner customer-facing managed service model, JML360 is designed to sit around the work you already do.

Discuss partner model