RhinoAgents + Microsoft Dynamics 365

RhinoAgents × Microsoft Dynamics 365

Connect AI Employees directly to Dynamics 365 Business Central, Finance & Operations (F&O), Sales, and Customer Service via Microsoft Entra ID OAuth 2.0, Dataverse Web API v9.2, and OData v4—with least-privilege RBAC, immutable audit logs, and human-in-the-loop approvals.

Entra ID OAuth 2.0 Dataverse Web API v9.2 Business Central OData v4 Azure Service Bus Events
Zero
Direct SQL / DB Exposure
40+
Typed Dynamics API Tools
OAuth 2.0
Entra ID Service Principal
100%
Action Audit & HITL Ready
01 / INTEGRATION ARCHITECTURE

How RhinoAgents Connects Safely to Dynamics 365

AI Employees never connect directly to underlying SQL tables. All reads and writes go through Microsoft's official Dataverse Web API, Business Central OData v4, or F&O Data Entities under a scoped Application User.

// Dynamics 365 Enterprise Execution Flow
DYNAMICS 365
BC • F&O • Dataverse
Invoices, POs, Leads, Cases
OData v4 / OAuth
RHINOAGENTS RUNTIME
AI Employee + Guardrails
RBAC, Tool Registry, Audit Log
HITL Gate
SIGN-OFF
Teams / Slack
1-Click Approval

Pattern A — On-Demand API Agent

Triggered by an email, chat request, or CRM form. The AI Employee queries Dynamics 365 via OData/Dataverse and returns validated answers or creates drafts.

Email → AI Employee → Dataverse API → Reply

Pattern B — Event-Driven Agent

Dataverse Webhooks or Azure Service Bus events (new PO, invoice variance, opportunity stage change) automatically trigger multi-step reconciliation workflows.

BC Event → Service Bus → Agent → Sync

Pattern C — HITL Approval Agent

Before posting a high-value vendor invoice or journal entry in Dynamics, the AI Employee sends an Adaptive Card to Teams/Slack for manager sign-off.

Agent Draft → Teams Approval → Post ERP
02 / HOW TO CONFIGURE

Step-by-Step Entra ID OAuth 2.0 Setup

Configure a dedicated Service Principal in Microsoft Entra ID so RhinoAgents authenticates via OAuth 2.0 Client Credentials with automatic token rotation.

STEP 01 • AZURE PORTAL

Create Entra ID App Registration

  1. Open Azure Portal → Microsoft Entra ID → App registrations → New registration.
  2. Name it RhinoAgents-Dynamics-Connector (Single Tenant).
  3. Copy the Application (client) ID and Directory (tenant) ID from Overview.
  4. Go to Certificates & secrets → New client secret and copy the secret value.
STEP 02 • API PERMISSIONS

Grant Dynamics API Scopes

  1. Navigate to API permissions → Add a permission.
  2. For Dataverse / Sales / Customer Service / F&O: select Dynamics CRM → user_impersonation.
  3. For Business Central: select Dynamics 365 Business Central → API.ReadWrite.All (Application).
  4. Click Grant admin consent for your organization.
STEP 03 • POWER PLATFORM / BC

Map Application User & Security Role

  1. In Power Platform Admin Center → Environments → Settings → Application users, click New app user.
  2. Select your Entra ID app and assign a custom least-privilege Security Role scoped only to required tables.
  3. In Business Central, search Microsoft Entra Applications, add the Client ID, and assign scoped Permission Sets.
STEP 04 • RHINOAGENTS

Verify Live Connection & Guardrails

  1. In RhinoAgents, open Integrations → Microsoft Dynamics 365 → Connect.
  2. Enter tenant_id, client_id, client_secret, and environment_url.
  3. Click Verify Connection (checks /api/data/v9.2/WhoAmI or BC /companies).
  4. Enable spend limits and Teams/Slack approval gates on write actions.
Required Connector Fields in RhinoAgents AES-256 Encrypted Vault
Parameter Example Format Purpose
tenant_id 72f988bf-86f1-41af-91ab-2d7cd011db47 Microsoft Entra ID Directory (tenant) UUID
client_id a1b2c3d4-5678-90ef-1234-567890abcdef App Registration Application (client) ID
client_secret •••••••••••• (Vault Encrypted) Client Secret for OAuth 2.0 token exchange
environment_url https://yourorg.crm.dynamics.com Dataverse / F&O base URL or BC API environment
company_id CRONUS USA, Inc. Optional: Business Central multi-company routing ID
03 / COMPLETE API ACTIONS REGISTRY

40+ Supported Dynamics 365 Tools & Triggers

Every Dynamics 365 operation is exposed as a typed, schema-validated tool with role-based access control and immutable audit logging.

Finance, Invoices & AP
list_vendor_invoices(status, date_range)
get_purchase_invoice(invoice_id)
create_purchase_invoice_draft(payload)
validate_three_way_match(po_id, inv_id)
list_sales_invoices(customer_id)
get_customer_ledger_entries(cust_no)
create_general_journal_line(batch, amt)
get_vendor_payment_status(vendor_id)
Purchasing, Orders & Inventory
get_purchase_order(po_number)
create_purchase_order(vendor, lines)
update_purchase_order_line(po_id, qty)
create_sales_order(customer, items)
get_sales_order_status(order_no)
get_item_inventory(item_no, location)
list_low_stock_items(threshold)
list_vendors(search_query)
Sales, Leads & Accounts (Dataverse)
create_lead(name, email, company)
update_lead(lead_id, fields)
qualify_lead_to_opportunity(lead_id)
get_account(account_id)
search_contacts(email_or_domain)
create_opportunity(account_id, value)
update_opportunity_stage(opp_id, stage)
create_quote(opportunity_id, lines)
Customer Service & Activities
create_case(title, customer_id, priority)
get_case_details(ticket_number)
update_case_status(case_id, status)
add_timeline_note(entity, id, note)
create_task(regarding_id, due_date)
log_email_activity(to, subject, body)
Custom OData v4 & FetchXML
query_odata_entity(entity, filter, top)
execute_fetchxml_query(xml_template)
upsert_custom_table_row(table, key)
call_bound_dataverse_action(name)
list_bc_companies()
download_invoice_pdf_attachment(id)
Real-Time Event Triggers
dataverse.record_created
dataverse.record_updated
bc.purchase_invoice_posted
bc.sales_order_released
sales.opportunity_stage_changed
service.case_escalated
EXAMPLE TOOL EXECUTION • validate_three_way_match() Guardrail + HITL Enforced
{
  "tool": "dynamics365.validate_three_way_match",
  "input": { "po_number": "PO-10482", "invoice_id": "INV-8841", "tolerance_pct": 0.5 },
  "result": {
    "status": "VARIANCE_DETECTED",
    "po_total": 14050.00,
    "invoice_total": 14500.00,
    "variance": 450.00,
    "next_step": "PAUSED_FOR_HUMAN_APPROVAL",
    "approval_channel": "Microsoft Teams #finance-approvals"
  }
}
05 / TECHNICAL FAQ

Microsoft Dynamics 365 Integration FAQ

Which Dynamics 365 editions are supported?

Dynamics 365 Business Central (Cloud & API-enabled On-Premises), Finance & Operations (F&O), Dynamics 365 Sales, Customer Service, and custom Power Platform Dataverse tables.

How are write actions & financial postings protected?

You can restrict the Entra ID Application User to read-only tables, enforce spend-limit guardrails, and require one-click Human-in-the-Loop approval in Microsoft Teams or Slack before posting invoices or journals.

Can RhinoAgents connect to custom Dataverse entities?

Yes. Using query_odata_entity(), execute_fetchxml_query(), and upsert_custom_table_row(), AI Employees work with any custom table in your environment.

Can we test in a Dynamics Sandbox first?

Yes. Connect your Dynamics Sandbox environment URL first, run pre-production evaluation suites on test POs and invoices, and promote to your production environment with zero downtime.

Ready to Connect Dynamics 365?

Build & Test Your Dynamics AI Employee Today.

Start on the RhinoAgents platform with credits, or have our engineering team build, integrate, and manage your Dynamics 365 AI workflows end-to-end.