| name | list-my-accounts |
| description | List and look up rows in the standard Dataverse `account` table for the
connected environment (https://org77c9659c.crm.dynamics.com/api/mcp) through
the native Dataverse MCP server. Read-only: this sample reads accounts, it
does not create, update, or delete.
Trigger phrases:
- "list my accounts"
- "show me my accounts"
- "how many accounts do I own"
- "look up the account [name]"
- "find accounts in [city]"
- "show the most recently created accounts"
- "what accounts can I see"
Scope: the single connected Dataverse environment ONLY, and the `account`
table specifically. Do NOT use for other tables, other Dataverse
environments, SharePoint lists, Excel files, or Power BI artifacts.
|
| license | MIT |
| metadata | {"author":"Launch Control","version":"1.0"} |
List My Accounts — Dataverse (Cowork sample)
Connects Microsoft 365 Copilot Cowork to one Dataverse environment through the
native Dataverse MCP server and answers questions about the standard account
table. Authentication flows through Cowork's OAuthPluginVault: the user signs in
once with their own Dataverse identity, and Dataverse security roles decide
which account rows come back.
This is a deliberately small sample skill. It covers one table and read-only
questions. For anything else, defer or decline rather than improvising.
When NOT to Use
- Other Dataverse tables (contact, opportunity, lead, case): out of scope for
this sample; say so.
- Other Dataverse environments: install a separate env-scoped plugin.
- Creating, updating, or deleting accounts: this sample is read-only.
- SharePoint lists, Excel / CSV, or Power BI: use the matching native tool.
The account table
| Property | Value |
|---|
| Logical name | account |
| OData entity set | accounts |
| Primary key | accountid (GUID) |
| Primary name column | name |
| Owner lookup | ownerid (lookup to systemuser / team); on the wire it is _ownerid_value |
Commonly useful columns (select these by logical name; do not request *):
name, accountnumber, emailaddress1, telephone1, address1_city,
address1_stateorprovince, address1_country, primarycontactid,
createdon, modifiedon, statecode, ownerid.
When a column name is uncertain, discover it first (use the MCP server's
schema / describe capability against the account table) rather than guessing.
"My" accounts
"My accounts" means accounts owned by the signed-in user. Two ways to do
this, in order of preference:
- If the MCP server exposes a built-in "current user" or "assigned to me"
filter, use it.
- Otherwise resolve the signed-in user id first (a
WhoAmI-style call returns
the caller's UserId), then read accounts filtered by owner:
_ownerid_value eq <UserId>.
Never assume an owner GUID. If the signed-in user id cannot be resolved, ask the
user to clarify whose accounts they mean instead of returning everyone's.
Query patterns
| User asks | Plan |
|---|
| "List my accounts" | Read accounts filtered by owner = signed-in user, $select=name,accountnumber,address1_city,emailaddress1,telephone1, $orderby=name asc, $top=25. |
| "How many accounts do I own" | Same owner filter, return the count. Prefer a server-side count over fetching all rows. |
| "Look up the account Contoso" | Read accounts filtered name contains/equals the term, $top=10. If multiple match, list them and ask which one. |
| "Find accounts in Seattle" | Filter address1_city eq 'Seattle', $select=name,address1_city,emailaddress1, $top=25. |
| "Most recently created accounts" | $orderby=createdon desc, $top=10, $select=name,createdon,ownerid. |
Always pass a bounded $top (default 25, max a few hundred). Prefer a tight
server-side $filter over fetching everything and filtering in the answer.
Output format
- List queries: a compact table with 4 to 6 columns. Lead with
name.
- Single lookup: a short key/value summary of the most useful columns plus
the row's id.
- Counts: a single sentence with the number.
For choice columns such as statecode, prefer the formatted display value the
MCP server returns over the raw integer.
Hard rules
- Respect Dataverse security. A successful Cowork sign-in does not elevate
the user. If the read returns no rows, the user cannot see those rows. Never
fabricate accounts, owners, or contact details.
- Stay on the
account table. If asked about contacts, opportunities,
budgets, or other tables, say this sample only covers accounts.
- Read-only. Do not attempt create / update / delete from this skill, even
if asked. Point the user to a full Dataverse plugin instead.
- Use logical names. Select and filter by logical column names; resolve any
uncertain name via the server's schema capability before querying.
Errors
| Error | Likely cause | Fix |
|---|
| 401 / unauthorized | OAuth token expired or scope missing | User reconnects / reconsents to the plugin in Cowork |
| 403 / forbidden | Dataverse security role lacks read on account | Admin grants the role; not a plugin issue |
| 400 / invalid column | Logical vs display name mismatch | Use the logical name from the server's account schema |
| Empty result for "my accounts" | Signed-in user owns no accounts, or owner id not resolved | Confirm the user id, or widen to "all accounts I can see" |
