Steps to Update the Work 365 Workflow Owner

Applies To: Work 365 (Dynamics 365 / Power Platform)
Audience: System Administrators, Technical Teams

Overview

When Work 365 is first installed, background workflows are owned by the installer’s user. For reliability, security, and auditability, reassign these workflows to a dedicated service identity (a non-personal service account or an Application User). If the original owner becomes inactive, scheduled jobs and automations can stall.

Prerequisites

• The target service identity exists and is enabled in the environment.

• Security:

  • System Administrator (recommended), or

  • Sufficient rights plus Work 365 Service (and any other required Work 365 roles).

• (If using an Application User) confirm it has required Work 365 roles.

Steps to Update the Workflow Owner

✅ Step 1: Sign in with the Service Identity

Sign in to Dynamics 365/Dataverse as the account that will own the workflows (service account or Application User).
Tip: Prefer a non-personal identity for long-term stability.

✅ Step 2: Locate Work 365 Workflows

• Go to Settings → Processes (or Advanced Settings → Processes).

• Filter:

  • Category: Workflow

  • Status: Active

  • Process Name contains: Work 365

✅ Step 3: Assign a New Owner

• Select the Work 365 workflows (multi-select is fine).

• Click Assign on the command bar.

• Choose Me (assigns to the currently signed-in service identity) and OK.

• If prompted, Save/Publish.
  Note: If any workflow deactivates on assign, click Activate.

✅ Step 4: Validate Job Ownership & Re-queue

• Navigate to Work 365 → Administration → Work 365 Jobs.

• Use a view that shows Owner and Status Reason.

• For jobs in Waiting/Paused:

  1. Open the job.

  2. Set Scheduled For to a near-future timestamp.

  3. Save to re-queue.

✅ Step 5: Verify Background Services

• Open Settings → System Jobs (or Power Platform Admin Center → Background Processes).

• Confirm Work 365 workflows show Running or Succeeded.

• If any show Paused/Deactivated, re-enable them.

Important Considerations

⚙️ Use a Dedicated Service Account or Application User

• Application User is preferred (license-free background ops).

• Must have required Work 365 roles (e.g., Work 365 Service, and others as needed).

• Avoid linking workflow ownership to personal identities.

? Why This Matters

Post-Change Monitoring

• Watch Work 365 Jobs over the next billing cycles for unexpected Waiting/Paused backlogs.

• Review System Jobs for ownership/privilege errors.

• Spot-check key automations (e.g., invoice post-processing, provisioning).

Troubleshooting

Can’t assign owner (button disabled or error):

• Ensure your user has Assign, Write, Read, Append, Append To on Processes and/or the specific workflows; try with System Administrator.

Jobs won’t progress after reassignment:

• Confirm workflows are Active and owned by the service identity.

• Check that the service identity has Work 365 roles.

• Open a stuck job → set Scheduled For slightly in the future → Save.

• Verify provider/accounting connectivity/consent if jobs call integrations.

Application User choice:

• Ensure the Application User is enabled in the environment and has the Work 365 Service role (plus any module-specific roles).

Best Practices

• Standardize: Own all Work 365 workflows under the same service identity.

• Document: Record the owner, roles, and date of change (runbook).

• Offboarding: Use Users → Reassign Records before disabling a departing user.

• Health checks: After updates or role changes, verify:

  • Access to Work 365 Admin Hub

  • Work 365 Start Job and other core workflows are Active

  • Provider/accounting Verify Connectivity passes

Summary

Reassign Work 365 workflows from the installer’s user to a dedicated service identity, then verify jobs and background processes. This prevents outages when users leave, strengthens governance, and keeps billing and provisioning automation running continuously.