# North Maple Systems — Microsoft 365 Operations Assistant
## Everyday requests. Clear approvals. Controlled changes.

**Customer overview · Product in development · Proposed pilot**

Employee arrivals, departures and access requests can involve several administrators, applications and approval steps. North Maple Systems proposes an authenticated conversational assistant that turns a request into a consistent plan, routes it to the right owner and reports what was completed or still needs attention.

The intended audience is small and medium businesses already using Microsoft 365, with defined administrative ownership and repeatable employee/access procedures. The purpose is easier request handling and more consistent execution; time savings must be measured in a pilot.

## Intended use cases

| Request | Proposed workflow | Required control |
| --- | --- | --- |
| Onboard an employee | Select an approved job profile; prepare identity, license, groups and access tasks | Manager/IT approval and license availability |
| Offboard an employee | Schedule access removal, session revocation and agreed data handover tasks | Verified HR/IT authorization and retention policy |
| Grant SharePoint access | Resolve the exact resource, recipient and role; review current access | Resource-owner approval and sharing policy |
| Report access | Show available direct/group/link-based permissions with evidence and coverage limits | Authorized report reader; group/inheritance checks |
| Report usage | Present available activity for a defined period and source | Approved audit/report access and data-availability checks |

All workflows are planned, not implemented. Folder-level changes and complete access enumeration require technical feasibility review; coverage must be disclosed rather than assumed.

## A simple experience

An authorized requester could say: “Prepare onboarding for Alex, starting Monday, using the Sales profile.” The assistant would resolve the exact start date and identity details, show the approved profile version and list proposed tasks. It would identify missing information before submission.

The designated approver would see the exact employee, license, groups, resources and execution time. After an approved workflow runs, the requester would receive a receipt distinguishing verified changes, failures, skipped tasks and manual follow-up. A chat acknowledgement alone would not authorize a change.

This example is illustrative. No account, license or permission is currently created by the product.

## First pilot

Start with **one onboarding profile and plan/approval only**. Use synthetic employee records in a lab to validate identity resolution, profile rules, rejection paths and approval records. No production changes are included in this first stage.

Later, separately approve a limited lab execution path and validate it before a customer rollout. Offboarding, external sharing, privileged roles and destructive actions remain outside the first pilot.

## Customer control

The proposed assistant would require organizational sign-in and enforce authorization independently of the conversational model. Approved job profiles determine permitted tasks. Resource owners approve access; IT controls execution identities and permissions. Sensitive HR details, credentials and tenant exports do not belong in public documentation.

Offboarding must account for data preservation and active business ownership. Removing an account is not equivalent to safely completing departure tasks, and reversibility differs between operations.

## Reporting that explains its limits

An access report answers who can access a resource and through what visible mechanism. A usage report answers what recorded activity is available during the selected period. These are different datasets. A missing activity record does not prove that a person never accessed a file; retention, collection, reporting delays and permissions limit visibility.

## Platform and commercial prerequisites

The proposed foundation is Copilot Studio with authenticated agent tools, Power Automate approval/workflow components and suitable Microsoft 365 APIs. It is not a claim that enabling Microsoft 365 Copilot alone delivers these automations.

Customer licenses, connector availability, consumption costs, environment configuration and endpoint permissions must be checked during discovery. Pricing, duration, hosting and support obligations will be agreed after reviewing the workflow. No Microsoft partnership or certification is implied.

**Next step:** select one job profile, identify its administrator and approver, and agree a synthetic onboarding pilot.

Version baseline: 2026-10-13. Documentation only; no connected agent or supported production service exists.