D365 Power Automate

You are a Dynamics 365 and Power Automate automation specialist. The user wants to create Power Automate flows that automate business processes in Dynamics 365, including triggering actions based on events, updating records, and managing approvals.

What to check first

• Verify you have access to a Dynamics 365 environment and Power Automate (https://make.powerautomate.com)
• Confirm you have the correct security role and permissions to create flows in your D365 tenant
• Check that your D365 connector version is current in Power Automate (look under Data > Connections)

Steps

1. Log into Power Automate and select Create → Cloud flow → Automated cloud flow to trigger on D365 events
2. Name your flow (e.g., "Update Lead Status on D365 Contact Create") and choose When a record is created as the trigger from Dynamics 365 connector
3. Select your Environment and Table (e.g., "Contacts", "Accounts", "Leads") — this defines what D365 entity fires the flow
4. Add an Action step using Dynamics 365 – Update a record to modify the triggered record or a related record
5. Map dynamic content from the trigger output (record ID, fields) into the action step using the Add dynamic content picker
6. Add Condition logic if needed: use If statements to check field values before performing actions
7. Include Apply to each for bulk operations when working with multiple D365 records
8. Test the flow by manually triggering the event in D365, then check flow run history and D365 audit logs for success

Code

{
  "triggers": [
    {
      "name": "When_a_record_is_created",
      "type": "Dynamics365",
      "inputs": {
        "host": {
          "connectionName": "shared_dynamicscrmonline",
          "operationId": "CreateTrigger"
        },
        "parameters": {
          "environment": "00000000-0000-0000-0000-000000000000",
          "table": "contacts",
          "scope": "Organization"
        }
      }
    }
  ],
  "actions": [
    {
      "name": "Update_Contact_Record",
      "type": "Dynamics365",
      "inputs": {
        "host": {
          "connectionName": "shared_dynamicscrmonline",
          "operationId": "UpdateRecord"
        },
        "parameters": {
          "entityName": "contacts",
          "recordId": "@triggerOutputs()['body/contactid']",
          "item": {
            "statuscode": 2,
            "description": "Auto-updated by Power Automate flow"
          }
        }
      }
    },
    {
      "name": "Condition_Check_Email",
      "type": "

Note: this example was truncated in the source. See the GitHub repo for the latest full version.

Common Pitfalls

• Treating this skill as a one-shot solution — most workflows need iteration and verification
• Skipping the verification steps — you don't know it worked until you measure
• Applying this skill without understanding the underlying problem — read the related docs first

When NOT to Use This Skill

• When a simpler manual approach would take less than 10 minutes
• On critical production systems without testing in staging first
• When you don't have permission or authorization to make these changes

How to Verify It Worked

• Run the verification steps documented above
• Compare the output against your expected baseline
• Check logs for any warnings or errors — silent failures are the worst kind

Production Considerations

• Test in staging before deploying to production
• Have a rollback plan — every change should be reversible
• Monitor the affected systems for at least 24 hours after the change