launch-control

Follow Episode 6 of the Launch Control series end-to-end — register a Microsoft 365 Cowork custom plugin that talks to the built-in Dataverse MCP server for the Launch Control environment, paired with a schema-aware Business Skill. Use when the user asks to "do Episode 6", "build the Cowork plugin episode", "wire Cowork to Launch Control via MCP", or "set up the Cowork Dataverse plugin end-to-end".

Programmatically create and upload a Copilot Studio "cliagent" declarative agent (bot + MCP tool components) into a Dataverse environment via the Web API, minting bot-scoped connection references against the connector's authorized connection so nothing is hardcoded. Use when a Launch Control episode needs to stand up a Copilot Studio agent from code (for example Episode 9 Act 4) instead of clicking through the maker portal, or to re-create/version an agent that has been reverse-engineered from a live bot record.

Teaches the Dataverse security model and drives an agent to implement and test a specific slice of it against any Dataverse environment. The model has two independent axes plus a per-agent variant, and the calling prompt names which one to build and its targets. Use whenever the user asks to "explain the Dataverse security model" or to implement a named slice of it ("set up row-level security", "secure a column", "add data masking", "scope an application user / agent"). The prompt passes in the security TYPE to build and its TARGETS (tables, columns, role/profile names, personas or the application user). Supported types: - row-level : security roles + owner-teams + business-unit depth, so the same query returns different row counts per persona. - column-level : secure columns + a field security profile (+ optional (data masking) masking rule), so the same row returns cleartext for one principal and a mask/omission for another. - per-agent : assign a

Follow Episode 5 of the Launch Control series end-to-end — produce a .NET Custom API plugin, a Power Fx Function twin, a REST custom connector, a remote MCP custom connector, and a Power Automate test-harness flow, all programmatically against a Dataverse environment. Use when the user asks to "do Episode 5", "build the custom tools episode", "make the readiness Custom API and Fx twin", "register a REST/MCP custom connector programmatically", or "deploy the Ep 5 test harness flow".

Authoritative LaunchControl business policies — launch readiness, status transitions, escalation, briefings — live as rows in the Dataverse `skill` table (entity set `skills`) in the LaunchControl environment. Before answering any LaunchControl business question, this skill instructs Cowork to load and follow those policies at the start of the session rather than improvise. Trigger phrases: - "is [launch] ready to ship" / "go / no-go on [launch]" - "what's the readiness for [launch]" - "this task is blocked, what do I do" / "escalate [task|milestone]" - "can I move [launch|milestone|task] from [status] to [status]" - "draft a launch briefing for [launch]" - "what's our policy on [topic]" - "what business skills are loaded" / "list LaunchControl policies" Do NOT use for: ad-hoc CRUD over Dataverse rows (use the dataverse-launchcontrol-mcp skill) or schema discovery (use dataverse-launchcontrol-schema).

Query and update Microsoft Dataverse rows in the LaunchControl environment (https://org1077ae7c.crm.dynamics.com/api/mcp_preview) via the preview Dataverse MCP endpoint. The endpoint exposes a three-tool surface (search / describe / execute) with a limited SQL subset over standard and custom tables. Use this skill to read, search, create, and update rows on lc_* tables — and to answer launch readiness questions per the hard rule below. Trigger phrases: - "is [launch] ready to ship" / "go / no-go on [launch]" - "what's the readiness for [launch]" - "what's blocking [launch]" - "show me open tasks for [launch|milestone]" - "find the team member [name]" - "create a status update on [launch]" - "update [task] to [status]" - "search Dataverse for [keyword]" Scope: LaunchControl environment ONLY. Do NOT use for other Dataverse environments, SharePoint lists, Excel files, or Power BI artifacts.

Authoritative schema reference for the lc_* tables in the LaunchControl Dataverse environment. Resolves table + column logical names and lists the case-sensitive $expand navigation properties needed to traverse lookups via the OData layer or the preview MCP's describe tool. Two entry points: (1) By lc_* table — return the entity set, schema name, lookup columns, and case-sensitive $expand nav properties. (2) By solution — list every table in a solution and forward to entry point (1) per table. Trigger phrases: "what's the logical name for [table]", "schema for [table]", "describe lc_task", "columns on lc_milestone", "what tables are in the LaunchControl solution", "how do I $expand the owner on lc_task", "what nav property points lc_task at lc_launch". Do NOT use for: querying row data (use dataverse-launchcontrol-mcp), schema modifications (admin task), or other environments (install a separate env-scoped plugin).

List and look up rows in the standard Dataverse `account` table for the connected environment via the PREVIEW Dataverse MCP endpoint (https://org77c9659c.crm.dynamics.com/api/mcp_preview). 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.

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.

Authoritative EPPCDemo1FnO business policies (approvals, valid status transitions, escalation, briefing formats) live as rows in the Dataverse `skill` table (entity set `skills`) in the EPPCDemo1FnO environment. Before answering any EPPCDemo1FnO business or policy question, this skill instructs Cowork to discover and follow those rows rather than improvise. Trigger phrases: - "what is our policy on [topic]" - "can I move [record] from [status] to [status]" - "this [record] is blocked, what do I do" / "escalate [record]" - "draft a [briefing|summary] for [record]" - "what business skills are loaded" / "list EPPCDemo1FnO policies" Do NOT use for: ad-hoc CRUD over rows (use `dataverse-eppcdemo1fno-mcp`), schema discovery (use `dataverse-eppcdemo1fno-schema`), or topics outside EPPCDemo1FnO policy.

Query and update Microsoft Dataverse records in the EPPCDemo1FnO environment (https://eppcdemo1fno.crm.dynamics.com/api/mcp_preview) via the preview Dataverse MCP endpoint. Read, search, create, and update rows in standard Dataverse tables (account, contact, lead, opportunity, incident) and custom tables in this environment. Trigger phrases: - "look up the [record] for [name]" - "show me open [records]" - "find the [record] [name] in Dataverse" - "create a new [record] in Dataverse" - "update the [field] of [record]" - "what [records] are assigned to me" - "search Dataverse for [keyword]" - "list rows in the [table] table" Scope: the EPPCDemo1FnO environment ONLY. Do NOT use for other Dataverse environments, SharePoint lists, Excel files, or Power BI artifacts.

Discover Dataverse logical names for tables and columns in the EPPCDemo1FnO environment (https://eppcdemo1fno.crm.dynamics.com/api/mcp_preview). Two entry points: (1) By table: user gives a display name or partial; returns the table logical name plus column logical names, types, and flags for lookup / choice / primary key. (2) By solution: user gives a solution friendly or unique name; returns every table in that solution and their column logical names. Trigger phrases: "what is the logical name for [table]", "schema for [table]", "describe [table]", "columns on [table]", "what tables are in the [solution] solution", "logical name for [field]". Do NOT use for: querying row data (use dataverse-eppcdemo1fno-mcp), schema modifications (admin task), or other environments (install a separate env-scoped plugin).

Authoritative EppcDemo2FRE business policies (approvals, valid status transitions, escalation, briefing formats) live as rows in the Dataverse `skill` table (entity set `skills`) in the EppcDemo2FRE environment. Before answering any EppcDemo2FRE business or policy question, this skill instructs Cowork to discover and follow those rows rather than improvise. Trigger phrases: - "what is our policy on [topic]" - "can I move [record] from [status] to [status]" - "this [record] is blocked, what do I do" / "escalate [record]" - "draft a [briefing|summary] for [record]" - "what business skills are loaded" / "list EppcDemo2FRE policies" Do NOT use for: ad-hoc CRUD over rows (use `dataverse-eppcdemo2fre-mcp`), schema discovery (use `dataverse-eppcdemo2fre-schema`), or topics outside EppcDemo2FRE policy.

Query and update Microsoft Dataverse records in the EppcDemo2FRE environment (https://eppcdemo2fre.crm.dynamics.com/api/mcp_preview) via the preview Dataverse MCP endpoint. Read, search, create, and update rows in standard Dataverse tables (account, contact, lead, opportunity, incident) and custom tables in this environment. Trigger phrases: - "look up the [record] for [name]" - "show me open [records]" - "find the [record] [name] in Dataverse" - "create a new [record] in Dataverse" - "update the [field] of [record]" - "what [records] are assigned to me" - "search Dataverse for [keyword]" - "list rows in the [table] table" Scope: the EppcDemo2FRE environment ONLY. Do NOT use for other Dataverse environments, SharePoint lists, Excel files, or Power BI artifacts.

Discover Dataverse logical names for tables and columns in the EppcDemo2FRE environment (https://eppcdemo2fre.crm.dynamics.com/api/mcp_preview). Two entry points: (1) By table: user gives a display name or partial; returns the table logical name plus column logical names, types, and flags for lookup / choice / primary key. (2) By solution: user gives a solution friendly or unique name; returns every table in that solution and their column logical names. Trigger phrases: "what is the logical name for [table]", "schema for [table]", "describe [table]", "columns on [table]", "what tables are in the [solution] solution", "logical name for [field]". Do NOT use for: querying row data (use dataverse-eppcdemo2fre-mcp), schema modifications (admin task), or other environments (install a separate env-scoped plugin).