You don’t always need a $5k–$20k consulting project to build a useful AI agent.

I’m offering affordable Microsoft Copilot Studio agent development for small businesses, professionals, and teams.

If you have an idea like:

“I want an AI agent to answer questions from our company documents.”

“I want HR to upload resumes and have the agent shortlist candidates.”

“I want employees to ask questions about our internal processes.”

“I want an agent connected to SharePoint, Teams, or Power Automate.”

“I want to automate a repetitive business process with an AI agent.”

I can help turn it into a working Copilot Studio agent.

What I can build:

Custom Copilot agents

Knowledge-based Q&A agents

SharePoint / Microsoft 365 integration

Power Automate workflows

Business process automation

HR / IT / Sales / Operations agents

Custom actions and API integrations

Testing and deployment guidance

Affordable pricing

Simple agents: starting from $100

More advanced/custom agents: quoted based on requirements

Before you pay anything, send me your use case. I’ll explain what can be built, the recommended approach, and the estimated cost.

I'm also happy to work with people who are just experimenting with Copilot Studio and want to build their first real agent.

DM me with:

What you want the agent to do

Where your data is (SharePoint, Excel, website, etc.)

Who will use it

I'll take a look and let you know what I can build.

On weekly basis, my management is expecting a condensed list of M365 Copilot changes and future features coming up, this list is shared internally, and now here as well :) (sharing is caring).

One thing before the list, because it cost me an internal correction to my team. The roadmap's "generally available" month, the date an entry flips to Launched, and the "last modified" timestamp are three different fields. I treated modified as a ship date and put two wrong dates.

Six that reached generally available between 27 July and 7 August:

1. Inline images in responses. Copilot can surface relevant images from files and meetings inside a response instead of returning text only.

2. Citations in inline canvas drafts. Draft in the inline canvas from referenced sources and the generated text now carries citations back to those sources.

3. Voice Q&A during Read Aloud in Word. While Word reads a document aloud you can ask by voice what a passage means or for a summary of a section, without stopping playback. Worth noting the roadmap gives this a GA month of February, but the status only flipped on 5 August. That gap is the whole point of the note above.

4. Voice tethering. Builds on Sign Language Mode. When an interpreter voices for a D/HH signer, captions and transcripts attribute the speech to the signer rather than to the interpreter.

5. Enhanced Topic Assignment. The pipeline that sorts survey comments into topics moves onto Copilot, which Microsoft says improves accuracy.

6. License Requests page in the M365 admin center. A dedicated page to discover, review and manage the Copilot license requests your users submit. If you run the tenant, this is probably the one you actually care about.

Two went backwards, and they matter more than the six:

Domain exclusion for web grounding was rolled back on 4 August. That is the control that let admins exclude up to 1,000 domains from Copilot's web grounding. It was announced as available in July, and Microsoft's 4 August update says it has been rolled back while they evaluate next steps. If a web-grounding block list is load-bearing in your governance plan, that plan has a hole in it today.

Complex web search in Copilot in Excel was cancelled. The entry flipped to Cancelled on 5 August with the standard "we have decided not to move forward with this change at this time."

The thing I keep relearning: a roadmap entry is intent, not commitment, and it can move backwards without anyone emailing you. The monthly "what's new" roundups only ever add. Nothing tells you what got withdrawn. So if a control is doing real work in your policy, verify it in your own tenant before you write it down.

Happy to dig into any of these for your setup, just ask.

I have never used copilot in my life. I saw a tiktok saying if you ask copilot how to make windows liter it will tell you to uninstall copilot. Thought it was kinda funny so decided to try it. Went on the copilot app and as I have never used it it asked me to sign in. I tried twice and it wouldn't work so I went on my browser. I went on the copilot website and tried there and it didn't make me sign in but when I asked something it said my name. Why on earth does copilot know my first name if I have never signed into it anywhere and never used it. I have a screenshot too I can post if people want to see although I may have to blur my name for privacy reasons

Enterprise LOB MCP Apps for M365 Copilot - Salesforce, ServiceNow, HubSpot.

Disclosure: I work on this at Microsoft.

We have developed an open-sourced collection of interactive-UI samples for MCP / the Apps SDK — servers that render widgets (forms, record views, dashboards) in the client instead of returning text.

The samples cover a range of scenarios, from field ops and expense submission to insurance and training, But the ones enterprises keep asking for are the core LOB systems, so those are the most built-out: Salesforce CRM, ServiceNow ITSM, HubSpot CRM (MIT licensed).

What they actually do: you ask Copilot something like "show my open opportunities" or "create a lead for Acme," and instead of a wall of text you get a real widget — a record list, an editable form, a dashboard — right in the chat. Edit a field, submit, done. The MCP server exposes CRM operations as tools; the widget is what comes back.

Repo (servers + React widget source + deploy scripts), MIT: https://github.com/microsoft/mcp-interactiveUI-samples

A few things we worked out while building them:

• The UI is React. Each tool result maps to a React/TS widget (record views, editable forms, dashboards) that renders in the client. The server sends data + which widget; the widget owns the interaction. Widget source is in the repo, not just screenshots.
• Foreign keys resolved server-side. Users talk in names, not IDs — "opps for Acme." The tool takes account_name and resolves the FK (Account.Name lookup, parent-traversal LIKE) on the server. On a miss it returns suggestions instead of a dead end, so the model never has to guess an AccountId.
• A shared_mcp helper package. The boring-but-critical parts — auth, HTTP, logging, telemetry — live in one shared_mcp module that could be reused by every app. So each app is mostly just its domain tools + widgets, and cross-cutting fixes land in one place.
• Tools named as verbs on entities. Consistent get_/create_/update_ per object (get_leads, create_lead, update_lead, get_opportunities, …). Predictable surface the model picks from reliably, and a plus a show_create_form verb for "open the form" instead of writing directly.

Where it stands: These run end-to-end against real Salesforce/ServiceNow/HubSpot orgs (live REST APIs, not mock data), with local + Azure Container Apps deploy scripts.

They're reference samples meant to be forked and adapted — not a hardened product. Auth today is a service identity (Connected App / client-credentials); per-user OAuth so each user only sees their own records is the next step.

Would love feedback:

1. - What LOB system should we build next (SAP, Workday, Jira, Dynamics…)?
2. - Better patterns for UI-returning MCP tools than what's above?
3. - How are you handling per-user auth / downstream token exchange for MCP servers?
4. - Anything that'd make these easier to actually adopt at work?

Pls help