Automate your D365 implementation workflow

Do I need to connect my Dynamics 365 org?

Not for the Advisor plan — it works from the ticket alone. Connecting is optional and recommended: with a connection, the Advisor plan grounds every step in your environment's real tables, columns and forms, and it only reads your environment — it never writes. Executor, Inspector, and Autopilot connect to your D365 environment via a secure OAuth 2.0 app registration.

How are my D365 credentials stored?

Client secrets are encrypted at rest with AES-256 and scoped to your organization. Every database record is isolated per tenant.

What happens if a configuration step fails?

On the Executor plan and above, a failed step triggers a full run rollback — completed reversible steps are reversed in order. The few operations that can't be undone (for example, publishing) are flagged in the run log for manual review.

Which ticketing systems are supported?

Jira, Azure DevOps, ServiceNow, and Linear. Filter by project, board, sprint, label, assignee, date range, or a custom JQL/OData query, then run the pipeline on a single ticket or a batch.

Data & API Security

Where is my data stored?

All data is stored in the United States on Supabase (PostgreSQL), hosted on AWS us-west-2. Your Dynamics 365 credentials and connection tokens are encrypted at rest using AES-256 and never logged or exposed in plaintext.

How does D365 Agent connect to my Dynamics 365 environment?

We use OAuth 2.0 with delegated permissions scoped to your specific Dynamics 365 environment. We never store your Microsoft account password. The OAuth token is encrypted at rest. It is used to read your environment on every plan, and on the Executor plan and above also to execute the configuration changes you explicitly authorize.

Does D365 Agent store my ticket content (Jira, Azure DevOps, ServiceNow)?

Ticket content is fetched at run time, processed by our AI pipeline, and the relevant summary is stored in your run history for audit purposes. Raw ticket payloads are not permanently stored. You can delete individual runs from Run History at any time.

Is my data used to train AI models?

No. Your data is never used to train any AI model. We send ticket content and configuration context to the Anthropic Claude API solely to generate configuration instructions for your run. Anthropic's API usage policy prohibits using API inputs/outputs for model training without explicit consent.

What API security measures are in place?

All API endpoints are authenticated via Clerk session tokens. Multi-tenant data isolation is enforced at the database level using Row Level Security (RLS) on PostgreSQL — no query can access another organization's data. All traffic is encrypted in transit via TLS 1.2+.

Who can access my organization's data?

Only authenticated members of your Clerk organization can access your data. Erlly Technology staff can access anonymized usage metrics for billing and support purposes only, and only when required to resolve a support issue.

Can I change plans later?

Yes. Upgrade or downgrade at any time from your settings — billing is handled through Stripe and prorated automatically.

Which Dynamics 365 products does D365 Agent support?

D365 Agent is purpose-built for Dynamics 365 Customer Engagement (CE) and the Dataverse platform, covering Sales, Customer Service, Field Service, and Project Operations.

What configuration tasks can the Executor and Autopilot plans automate?

The Executor and Autopilot plans automate Dataverse configuration: tables and columns, choices, relationships, forms and views, security role assignment to teams, and publishing pending customizations. Power Automate flows come back as a precise manual step: live testing showed the platform cannot yet write to the Flow API, so we do not claim to automate them. Anything that can't be automated safely, like plugins and Business Rules, comes back as a precise manual step with the exact path and content.