You already pay for Microsoft 365 Copilot. Your renewal emails get drafted there. Your follow-up notes get summarized there. The one thing missing is the part the email is actually about: the account, the open opportunities, the recent cases. Henoyo registers as a Copilot agent so that piece lands in the same pane, from the same Prompt your team already uses on voice.
Coming next quarter · MCP-based agent registration. Join the early-access list.
It’s 2:30pm. You’re drafting a renewal email to Lisa Cho, Acme’s champion, $1.8M renewal closing in August. The Outlook draft is open. Copilot is in the side pane. You ask:
Sarah types in Outlook:“Draft a renewal email to Lisa for Acme’s August renewal. Use the Henoyo Account 360.”
Copilot returns about twenty seconds later:
Henoyo through Copilot:Acme is your $1.8M renewal closing August 18. Lisa Cho is the champion. Last QBR went well, no escalations open. Net new ARR is up 12% year over year. One small flag: three open support tickets aged over 21 days that Marcus owns. The draft below anchors on the renewal date, names the YOY growth, and invites a 30-minute call to align on the year ahead. It does not raise the ticket aging. That conversation belongs on the call.
The draft is in the email, ready to edit. You change two sentences and send it. The ten minutes you used to spend tabbing to your CRM, copying the deal context, pasting it into the email, formatting it: gone.
Three things, mostly.
Renewal emails, follow-up emails, deal-status updates. Copilot drafts them with the actual Account 360 readout in context. The reps stop alt-tabbing to the CRM tab to copy a few facts. The drafts come out tighter the first time.
The Account 360 you author once shows up in voice in the browser, on MCP for Claude or Cursor, on REST for your team’s automations, and now in Copilot. You don’t rebuild it as a Copilot Studio agent. You don’t maintain four versions. Same Prompt, same governance, same audit trail.
Henoyo doesn’t replace Microsoft 365 Copilot. It extends it. The Microsoft skills you already use (summarize this email thread, find that file in OneDrive, set up that meeting) keep working exactly the way they do today. Henoyo skills sit beside them, invoked the same way.
Microsoft’s Copilot Studio is the official path for building Copilot agents. It’s a strong native option if your CRM is Dynamics, your data is in the M365 graph, and you’re comfortable rebuilding your prompt library inside Microsoft’s tools.
The customers we hear from aren’t there. They’re on Salesforce, or NetSuite, or a multi-vendor stack. They’ve already authored prompts in Henoyo for voice and MCP. They don’t want to rebuild those prompts a second time as Copilot Studio agents, and maintain two versions whenever the data context changes.
The Henoyo Copilot channel is the bridge: register your existing Henoyo Prompts as a Copilot agent through MCP. Your reps see them in the Copilot pane next to Microsoft’s native skills. You keep authoring in one place. Your IT team approves one registered agent in Entra, on the controls they already use for every other Copilot agent.
Three example invocations: the user types in the Copilot pane the same way they ask Copilot anything else. The response renders inline, the read lands in your audit log.
Henoyo, give me the Account 360 on Acme.
Inline pane response with the same Account 360 readout your team gets on voice: open opps, recent activity, last touch, the recommended-next-step paragraph.
Read logged in the Henoyo audit trail in your AWS or Azure account.
Henoyo, draft a renewal brief for the Lisa Cho meeting Friday.
Renewal 360 readout rendered next to the calendar invite: risks, expansion paths, the three things to land in the meeting, draft talking points.
Read logged in your Henoyo audit trail; calendar event itself untouched.
Henoyo, what’s stuck this week?
Monday-morning Stuck Deals summary in the Outlook Copilot pane: three deals over $50k with no movement in 14 days, with Salesforce links and last-touch timestamps.
Read logged in your Henoyo audit trail. Microsoft Purview captures the pane interaction separately.
Same Prompts, every surface.
Three answers, in case you’re forwarding this page to your M365 admin.
In your Azure subscription (or AWS account), separate from your Microsoft 365 tenant. The Copilot agent that shows up in your users’ Copilot pane is registered through Microsoft’s MCP-based agent surface against the Henoyo container running in your cloud. Your CRM tokens stay in your Azure Key Vault or AWS Secrets Manager. Henoyo’s servers see none of this.
The Copilot agent is registered in your Microsoft Entra ID tenant like any other Copilot agent. Disabling it goes through the same Entra admin path your team already uses for every other registered application. The Henoyo container can also be torn down independently from your Azure or AWS console. Two independent levers, each in your control.
The Copilot pane sees the rendered response and the user’s prompt text. The reads against your CRM, ERP, and warehouse happen inside your Henoyo install in your cloud and are logged there. Microsoft Purview audit covers what flows through the Copilot pane; Henoyo’s audit covers what was read to produce the answer. Your CRM tokens never traverse Microsoft’s tenant.
Yes. The Henoyo agent extends Copilot. It doesn’t replace it. Your users need M365 Copilot licenses; Henoyo skills are invoked through that surface alongside Microsoft’s own Copilot capabilities.
Copilot Studio is Microsoft’s native authoring layer for building agents inside the M365 boundary. Henoyo is a separate consumption layer running in your cloud. The agent it registers in Copilot is one of several places (voice, MCP, REST) where your governed Prompts can be invoked, against Salesforce or Dynamics or NetSuite or all of them at once. If your CRM is Dynamics and your stack is fully Microsoft, Copilot Studio is a strong native option. If your reality is Salesforce + Microsoft, or multi-CRM, Henoyo is the layer that makes them all answerable from the same Prompts.
In your AWS or Azure account, just like every other channel. Copilot routes the user’s request to the registered Henoyo agent; Henoyo executes the Prompt against your CRM and ERP using tokens in your secrets store; the response renders in the Copilot pane. Customer data never leaves your boundary.
Yes. Per-Prompt deployment toggles let your admin decide which Prompts and Skills are exposed on which channels. A Prompt deployed to voice and MCP isn’t automatically available in Copilot; you opt it in.
Two weeks if you pick the right starting Prompt. The Account 360 in Copilot is usually the fastest first win. Your reps drafting renewal or follow-up emails save ten minutes per email, several times a day. The math justifies itself by the second week.
Get on the early-access list. We’ll walk through the Copilot agent registration in your Entra tenant, with your IT lead in the meeting if you want, show how the same Prompts you author once light up across voice, MCP, REST, and Copilot, and answer the questions your M365 admin is going to ask.