Skip to main content
Dynamics 365 integration enables powerful automation for customer relationship management, enterprise resource planning, and business process automation across Microsoft’s business applications platform. This guide covers setup, operations, and common enterprise patterns.

Capabilities

Dynamics 365 Sales:
  • Lead and opportunity management
  • Contact and account operations
  • Sales pipeline automation
  • Quote and order processing
  • Activity tracking
Dynamics 365 Customer Service:
  • Case management
  • Knowledge base integration
  • Service level agreements (SLAs)
  • Customer support workflows
  • Omnichannel routing
Dynamics 365 Field Service:
  • Work order management
  • Resource scheduling
  • Inventory management
  • Service agreements
Dynamics 365 Finance & Operations:
  • Financial management
  • Supply chain operations
  • Project management
  • Asset management

Setup

Step 1: Register Application in Azure AD

  1. Go to Azure Portal → Azure Active Directory → App registrations
  2. Click New registration
  3. Configure:
    • Name: Noxus Integration
    • Supported account types: Accounts in this organizational directory only
    • Redirect URI: Web - https://app.noxus.ai/integrations/dynamics365/callback
  4. Click Register
  5. Note Application (client) ID and Directory (tenant) ID

Step 2: Create Client Secret

  1. In your app registration, go to Certificates & secrets
  2. Click New client secret
  3. Add description: “Noxus Integration”
  4. Set expiration (e.g., 24 months)
  5. Click Add
  6. Copy Value (secret) immediately

Step 3: Configure API Permissions

  1. Go to API permissions
  2. Click Add a permission
  3. Select Dynamics CRM
  4. Select Delegated permissions:
    • user_impersonation
  5. Click Add permissions
  6. Click Grant admin consent (if you have admin rights)

Step 4: Add to Noxus

  1. Open Connections in the sidebar and click Add connection
  2. Find Dynamics 365
  3. Enter:
    • Environment URL: https://your-org.crm.dynamics.com
    • Client ID: Application (client) ID
    • Client Secret: Secret value
    • Tenant ID: Directory (tenant) ID
  4. Click Connect
  5. Authorize access

Step 5: Verify Connection

Test by querying Account or Contact records.

Nodes Available

Dynamics 365: Query Records
  • Execute FetchXML or OData queries
  • Filter and sort results
  • Returns list of records
Dynamics 365: Get Record
  • Retrieve single record by ID
  • Returns full record data
Dynamics 365: Create Record
  • Create new record (Lead, Contact, Account, etc.)
  • Set attributes
  • Returns record ID
Dynamics 365: Update Record
  • Update existing record
  • Modify attributes
  • Returns success status
Dynamics 365: Upsert Record
  • Create or update based on alternate key
  • Prevents duplicates
  • Returns record ID
Dynamics 365: Delete Record
  • Delete record by ID
  • Returns success status
Dynamics 365: Associate Records
  • Create relationship between records
  • Link related records
Dynamics 365: Execute Action
  • Execute custom action
  • Run business logic
  • Returns action result

Triggers

A flow can start on a Dynamics 365 event. In the flow editor, open Triggers, then the trigger library, and search for “Dynamics”.

OData Query Syntax

Basic Query Structure

Common Queries

Leads:
Opportunities:
Accounts:
Cases:

Advanced Queries

Expand (Include Related Data):
Filtering with Lookup Fields:
Option Set Values:

Common Patterns

Pattern 1: Lead Scoring and Routing

Pattern 2: Opportunity Stage Automation

Pattern 3: Case Management and Auto-Routing

Pattern 4: Quote Generation and Approval

Pattern 5: Account Data Enrichment

Pattern 6: SLA Monitoring and Escalation

Pattern 7: Marketing Campaign Response Tracking

Custom Entities and Fields

Work with custom entities just like standard entities:

Batch Operations

For multiple operations, use batch requests:

Rate Limits

Service Protection Limits:
  • 6,000 API requests per 5 minutes per user
  • 52,000 API requests per 24 hours per user
  • Concurrent request limit: 52 per user
Best Practices:
  • Use batch operations
  • Implement exponential backoff (429 retry-after header)
  • Cache reference data
  • Monitor API usage

Webhooks

Configure webhooks via Power Automate or Plugin Registration: Common Triggers:
  • Record created
  • Record updated
  • Record deleted
  • Field changed
  • Status changed

Troubleshooting

”401 Unauthorized”

Problem: Authentication failed Solutions:
  1. Verify Azure AD app credentials
  2. Check token expiration
  3. Regenerate client secret
  4. Verify API permissions

”403 Forbidden”

Problem: Insufficient privileges Solutions:
  1. Check security roles
  2. Verify record-level permissions
  3. Check field-level security
  4. Grant necessary privileges

”404 Not Found”

Problem: Entity or record not found Solutions:
  1. Verify entity name (use plural)
  2. Check record ID format (GUID)
  3. Verify record exists
  4. Check environment URL

”429 Too Many Requests”

Problem: Rate limit exceeded Solutions:
  1. Implement retry with exponential backoff
  2. Use batch operations
  3. Reduce request frequency
  4. Contact Microsoft for limit increase

Best Practices

Use Alternate Keys: Define alternate keys for upsert operations Security Roles: Assign appropriate security roles to integration user Batch Operations: Batch multiple operations to reduce API calls Error Handling: Implement comprehensive error handling with retries Audit Trail: Enable auditing for critical entities Testing: Always test in sandbox environment first Change Management: Use solutions for deployment Performance: Cache lookup data and use selective queries Documentation: Document all customizations and integration points Monitoring: Track integration health and API usage
Dynamics 365 integration enables enterprise-grade CRM and ERP automation, streamlining business processes across Microsoft’s business applications platform.

Integration Authentication

Setup Azure AD OAuth

Data Transformations

Transform Dynamics 365 data

Human-in-the-Loop

Build approval workflows

Text Generation

AI-powered CRM operations