--- title: "Lucy — AI Assistant for Microsoft 365 | Lucid Labs" description: "Lucy is a Microsoft 365 Copilot agent built for chained, multi-step work — across your line-of-business systems, with DLP checks and Copilot usage reporting." url: "https://lucidlabs.com.au/products/lucy" --- SaaS product Available to pilot # Lucy Multi-step work, seen through to the end Lucy takes a whole sequence and sees it through — find the record, build the document from it, file it, update the system, tell the client — inside Microsoft 365 Copilot, as you, with your permissions. She reaches your line-of-business systems too, and surfaces the governance signals worth acting on: Copilot adoption, your agent inventory, and a DLP check before anything leaves the tenant. [Talk to us about a Lucy pilot](https://lucidlabs.com.au/#contact)[All products](https://lucidlabs.com.au/products) ## Built for the whole sequence, not just the next step Microsoft 365 Copilot is very good at the task in front of you: draft the email, create the document, book the meeting. Lucy extends that across a sequence — find the record, pull the right figures out of it, build the document from those, file it where it belongs, update the system, then tell the client — as one instruction. Keeping a long job on track is an engineering problem, and that is where our work has gone. Each step hands the next one a clean, complete result — the record, the figures, the file it belongs with — so nothing has to be guessed at or looked up twice. Lucy is given a tight, well-described set of things she can do, and every answer is kept to a size the assistant can comfortably hold. A job with six steps in it comes back finished rather than trailing off somewhere in the middle. The same design lets a chain reach past Microsoft 365 and into the systems your business runs on — the CRM, the ledger, the timesheet, the partner portal — inside the same request. Lucy reports what she did and what she skipped, anything destructive asks first, and every action runs under your identity, so permissions and audit trails stay exactly where your organisation already keeps them. She surfaces the governance picture in the same place. Copilot adoption and usage reporting, the inventory of agents published to your org, the sensitivity label on the document you are about to attach — all readable on request, and all usable as the trigger for an action rather than a dashboard someone has to remember to open. It is also how you tell whether the seats you are paying for are earning out. That is what makes the automation something you can hand to a whole team. Every outbound action passes a DLP gate first: labels on the attachment and the destination are checked, an escalation asks for confirmation and a business justification, and a manager override is a deliberate, recorded act. ## How it works 1. ### Install her in your tenant Lucy installs as a Microsoft 365 Copilot agent inside your own tenant, with the permissions you approve. No data leaves it, and there is no separate account to manage. 2. ### Find her where you work Copilot chat, Teams, or an IDE. There is no new app to learn and no portal to log into. 3. ### Ask for the outcome, not the draft “Send the signed SOW to the client and file it in their folder.” “Turn this thread into three tasks with owners and dates.” “Book the follow-up and invite the project team.” 4. ### Check her work She reports what she did and what she skipped. Anything that changes or sends something asks first, and outbound content is checked against its sensitivity labels before it leaves the tenant. ## What you get ### She finishes the chain Find the record, build the document from it, file it, update the system, tell the client — one instruction, not six. Each step hands the next one a clean result to work from. ### Threads become tasks Action items extracted from mail, chat, or a meeting and created in Planner with an owner and a due date. The follow-up exists before the conversation is cold. ### Documents written and filed Word documents and decks generated on your branded templates, labelled on creation, and saved to the library they belong in — not left in a downloads folder. ### Calendar handled Meetings booked, moved, declined, and written up, with focus time protected around what is actually on your calendar. Minutes and follow-ups go out without a second ask. ### Records kept current Whatever your team actually tracks — CRM records, projects, approvals, timesheets — updated from the work rather than from memory at the end of the week. ### A DLP gate on every send Sensitivity labels on the attachment and the destination are checked before anything leaves. Escalations ask for confirmation and a written justification, and a manager override is recorded. ### Sized to what the assistant can hold An assistant can only take in so much at once — a few thousand words an answer, and a set number of tools. Lucy is built to those limits, so a long sequence comes back complete, and where there is more room she uses it. ### Copilot spend you can justify Per-user activity and licensed-seat counts over 7 to 180 days, so you can see which seats earn out. Lucy adds no per-seat licence of her own — she runs on the Copilot entitlement you already pay for. ## Built on - Microsoft 365 Copilot - Copilot Cowork - Model Context Protocol - Microsoft 365 Agents Toolkit - Microsoft Agent 365 - Microsoft Entra Agent ID - Microsoft Copilot Studio - Microsoft Graph - Microsoft Work IQ - Microsoft Purview - Microsoft Teams - Azure ## Give Lucy the task you like least Pick the job that eats your week — the one that ends in someone opening a system and typing. We will wire Lucy to it in a pilot and you can judge her on that one thing. [Talk to us about a Lucy pilot](https://lucidlabs.com.au/#contact)