Technical details and readiness
Looking for what this does?
Try a fictional sales example. This page is for administrators and technical reviewers, not the starting point for sellers.
Readiness snapshot: October 16, 2026. Owner testing passed as reported. Final-name import/display and recipient access remain unverified; optional packages still need host testing. Copilot Studio is deferred. Website examples do not run an agent.
Current release—not the earlier seven-package layout
| Package | Role | Definitions |
|---|---|---|
| Seller Workflows | Primary | 56 |
| Account & Deals | Primary | 56 |
| V-Team Service | Optional | 11 |
| Admin Support | Optional | 14 |
All 137 definitions are retained across four packages. The seven older packages are the source layout, not extra releases to install. Final 2.1.3 keeps the consolidation IDs and short names. Do not enable overlapping layouts together. Browse the complete catalog.
Open only the detail you need
Architecture and Copilot Studio status
Workflow instructions guide clarification, evidence review, drafts, and handoffs. Approved tools supply live evidence under a verified identity. Instructions grant neither access nor execution authority.
The GitHub Copilot harness is behind the managed Copilot Studio agent, not another seller application. The full agent has a recorded optional Work IQ connection-reference initialization blocker. The narrower Dataverse proof does not establish full-agent readiness or per-user isolation.
Dataverse core first: reconcile the release and prove record matching, citations, denied access, missing data, unavailable tools, effective caller permissions, no-effect behavior, usage, and rollback. Import and publish success are not conversation proof.
What local validation proves—and does not
The 2.1.3 packages passed 59 Toolkit rules each and 28 targeted tests. Forty selected local Sales and Account Intelligence unit tests passed on October 16. These cover overlapping components, not forty additional host scenarios.
The final-name revision passed four consolidation tests and 59 Toolkit rules per package (236 total). All 137 workflow files, icons, IDs, version and permissions match the earlier 2.1.3 archives; only full manifest names/descriptions and ZIP filenames changed. New hashes identify these bytes.
The owner reported all test cases passed before that cleanup; exact tested version and detailed scope were not supplied. This is owner attestation, not independent execution evidence. Final import/display verification, optional-package host tests and each recipient's own permissions remain open. A definition count is not a live-capability count.
Later enhancements: Work IQ and Salesforce
Work IQ is deferred unless a measured core gap requires it. Business skills are governed natural-language instructions, not executable code or directly interchangeable Cowork entries. The Dataverse semantic model is not a Power BI semantic model; the referenced preview guidance notes no new-model creation and no model ALM support. Tenant availability and current limits require revalidation before use.
Salesforce: planned, not qualified. A Dataverse test does not establish Salesforce support. Salesforce-target pilots require separately authorized sandbox, identity, mapping, source-link, no-effect, and rollback tests.
Microsoft: customize and share · Microsoft: admin deployment · Microsoft: sales in cowork · Microsoft: sales agent versus cowork · Microsoft: business applications · Microsoft: business skills · Microsoft: semantic model
Data access, effects, and pilot expansion
Notes-only tasks need no CRM connection. Live tasks need exact account/record scope, approved sources, verified identity, and source dates. Unknown or denied evidence stays unknown; no cross-account fallback.
Sending, saving, scheduling, assignment, CRM changes, authentication, deployment, and publication require their own supported path and explicit approval. Natural-language instructions are not security controls.
Qualify the internal pilot first. Reuse its versioned artifacts and tests with customers only after customer-specific access and scenario approval. A maker-owned connection does not prove another person's isolation.