Microsoft 365 × AI

AI agents for Microsoft 365: approvals in Teams and Outlook.

voluro Nexus runs business processes in SAP, Salesforce and other systems. Microsoft 365 is where your team takes part in the decisions: exceptions arrive as a card in Teams or a message in Outlook, with all the data on the case.

  • Microsoft
  • SAP
  • Salesforce
Book a process checkWhat the approver sees

Today, approvals run on forwarded emails.

Today

  • An order with a special discount is forwarded to the sales lead by email.
  • The approver pulls customer data, terms and credit limit together from SAP or the CRM.
  • Who agreed and when sits in a mailbox or a chat thread.
  • After the “looks fine”, someone keys the case into the target system by hand.

With Nexus

  • The approval arrives as a card in Teams or a message in Outlook.
  • Case, rule and reason are part of the request.
  • Once approved, Nexus executes exactly the approved version in the target system.
  • The decision is recorded in the audit trail with role and timestamp.

How an approval in Teams works.

Using a sales order with a special discount as the example. The thresholds are sample values; you set your own.

  1. Prepare the case

    The agent reads the order, checks customer, prices and availability in SAP and prepares the sales order.

    SAP · Salesforce

  2. A rule applies

    The discount is 12%. Your rule says a special discount above 10% needs the sales manager’s approval.

    Guarded Autonomy

  3. Card in Teams

    Nexus sends the request to the responsible person in Teams. People who prefer their inbox get it in Outlook.

    Teams · Outlook

  4. Decide

    The sales manager approves, rejects or sends the case back with a comment.

    Human

  5. Execute and record

    Nexus creates exactly the approved version in SAP and logs who approved it and when.

    Audit trail

What the approver sees in the request.

Every request contains what the decision needs. The approver doesn’t have to open SAP or the CRM to make it.

Contents of an approval request

  • The data: the prepared case with customer, line items, amount and terms, plus context from the systems involved
  • The rule: which rule triggered the approval, such as “special discount above 10% → sales manager approval”
  • The reason: why the agent won’t close the case alone, for example a 12% discount against a 10% limit
  • The options: approve, reject or send back with a comment
  • Multi-step approvals, such as finance and sales for large orders
Approval in Microsoft Teams · View from the demo environment

Three ways to approve.

Approvals in Microsoft 365 are ready for production use. You decide per rule which channel applies to which role.

  • Teams

    Teams card

    The request appears as a card in the responsible person’s Teams chat, with data, rule and buttons for the decision.

  • Outlook

    Outlook

    The same request as an email, for approvers who run their day from the inbox.

  • Nexus

    Inbox in Nexus

    Open approvals also appear in the Nexus inbox, where you see every case waiting for a decision.

Copilot, ChatGPT or Claude use Nexus agents.

Many companies already use an AI assistant. Nexus provides an MCP server for exactly that. Through the Model Context Protocol, Microsoft Copilot, ChatGPT or Claude can call Nexus agents as a tool. An employee asks the assistant for the status of an order or starts a case, and Nexus carries it out through its tools.

These calls are subject to the same rules, approvals and audit trail as any other Nexus agent. An order with a special discount still goes to approval when someone starts it from Copilot. Agentforce and Joule stay in use inside their platforms, and Nexus adds the execution across system boundaries.

How SAP and Salesforce fit in.

In Nexus, Microsoft 365 is where decisions and confirmations happen. The transactions themselves are created in your business systems, connected as controlled agent tools.

  • SAP S/4HANA and ECC

    Sales orders, prices, availability and blocks through released interfaces. Nexus reaches systems behind your firewall through a relay service, outbound only.

  • Salesforce

    Opportunities, cases, flows and Apex actions become agent tools. Order number and status go back to the CRM after execution.

  • Microsoft 365

    Teams and Outlook for approvals and order confirmations. Users come from Microsoft Entra ID.

Limits.

Nexus controls the actions executed through Nexus tools. Whatever Copilot or another assistant does outside of them is still governed by its own permissions and your Microsoft 365 tenant settings.

Workflows that stay inside Microsoft 365, such as filing documents, sending a notification or a simple leave request, are usually well served by Power Automate. You don’t need an AI agent for those. Nexus pays off when a case has to be assessed and executed in SAP, Salesforce or other systems.

We agree with your IT upfront which permissions the Teams and Outlook connection needs in your tenant.

Frequently asked questions about AI agents in Microsoft 365

Do we need Microsoft Copilot to use approvals in Teams?

No. Nexus sends approvals to Teams and Outlook itself. Copilot, ChatGPT or Claude only come in if employees should call Nexus agents from an AI assistant.

What happens if the case changes after approval?

Nexus executes exactly the version that was approved. The audit trail therefore shows unambiguously which version someone approved.

Where is it recorded who approved?

In the Nexus audit trail. For every action it holds the data read, the rule applied and its version, the approver with role and timestamp, and the target system’s response.

Can an agent bypass the approval rules via Copilot?

No. Nexus checks the rules outside the language model before any tool runs. Where the call comes from makes no difference.

Read on

Start with one process.

30 minutes · free · with a senior architect. You get a verbal initial assessment and concrete next steps.

Book a process check Discuss a proof of value