Start small, then expand with evidence
Release to your team.
Start with the two sales plugins and a named internal pilot group. Give people one task to try—not the whole catalog to learn.
A website download, a shared Cowork plugin, and an administrator deployment are different release steps. None grants CRM access.
1. Confirm the exact release
- Start with Seller Workflows and Account & Deals only. Keep optional V-Team Service and Admin Support out of the general seller launch.
- The owner reports successful testing. Record the tested version/scope and check final V2.1.3 import, displayed names and one notes-only rehearsal after the metadata cleanup.
- Keep a pilot owner, exact ZIP hashes, supported source scope, known limitations, minimal test evidence and rollback route in approved internal storage.
- Agree the named participants, permitted sharing channel and support contact before sharing. Stop if policy, entitlement or effective data access is missing.
Download final package checksums · Run or repeat the acceptance tests.
2. Share inside your organization
- Open Cowork → Customize → Plugins. Open the detail page for each of the two plugins you uploaded. First verify the version and displayed name.
- Select Share. Choose Specific users in your organization; add only the approved participants by name or email. Check the recipients, then select Apply.
- Copy each plugin link from the Share dialog. These are the recipient-use links. Do not send a local Downloads path or assume the website installs anything.
- Send both links through the approved internal channel. Include the getting-started page, a notes-only prompt, pilot owner/support contact and the request below. Sending is a separate decision from sharing.
- Test as a recipient. They check the shared plugin detail/Add controls available to them, enable it in Sources & Skills, and start a fresh task. They run the four synthetic sales scenarios before separately authorized live-data tests. Record T11 using their own identity.
If Share is missing or blocked: stop and ask the tenant administrator. If approved, participants may instead upload the exact ZIPs themselves following the personal install guide. Do not bypass policy or share credentials.
When changing an already shared plugin, Microsoft documents Re-share to send the latest version to its recipients. Review the changed bytes and recipient list first; do not assume a renamed ZIP updates installed copies.
3. Give the pilot one clear job
Suggested internal invitation—fill in the links and support contact before sending:
Try Sales Extension Suite for Copilot in Cowork. It adds reusable team routines for account briefs, meeting follow-up, deal coaching and handoffs alongside Microsoft’s standard Sales plugin.
Start with these two shared plugins: [Seller Workflows link] and [Account & Deals link]. Follow [getting-started link], then try one fictional example. Please tell us whether the answer is useful, what you corrected and anything that blocked you. Review drafts before acting; do not use live customer data until your access and scope are approved. Support: [pilot owner/contact].
This is a draft, not a sent message. Do not include private customer evidence in public feedback. Record usefulness, corrections and time observed; no ROI claim is established yet.
4. Expand only after recipient success
Administrator-managed rollout to a larger internal group
Ask the tenant/Copilot administrator to review the plugin through the organization’s supported custom-app submission process. Uploading privately or sharing with named people is not organization-wide approval.
Once the plugin is available to the administrator, Microsoft documents Microsoft 365 admin center → Agents → All agents or Tools → select the plugin → Installed for → Specific users/groups → Next/install. Begin with an approved pilot group, not All users. Exact availability depends on tenant policy and rollout.
Org-wide publication requests need administrator approval. Managed deployments cannot be removed by recipients; they can disable them for conversations. The administrator owns deployment rollback, blocking and audience changes. Blocking takes effect for new conversations; already-running conversations may continue.
Customer reuse is a separate release
Same-organization sharing does not establish cross-tenant distribution. A customer needs its own approved package-delivery route, tenant availability, licenses, administrator review, effective identities, data scope, scenarios, support owner and rollback. Do not copy internal evidence or offer these ZIPs as proof of universal CRM compatibility. Keep customer-specific content out of a public download site.
Rollback and support
For a personal pilot, disable only the suite plugins involved, restore recorded prior enabled states and start a fresh task. Preserve original packages and connections. For named sharing or managed deployment, have the owner/administrator review the audience and supported revoke/block controls. Do not promise immediate revocation of existing conversations.
Send the pilot owner the package version/hash, host/build, minimal error and expected versus observed result through an approved internal channel. Never paste tokens or raw customer records into a public issue.
Website publication is not plugin deployment
A public website makes the overview and download ZIPs available on the internet. It does not install plugins, share them in Cowork, approve tenant access or send an invitation. Those actions need their own approved audience and supported process.
Use the approved internal distribution route for private evaluation. A local preview link works only on the author’s computer; a public download is not a recipient’s Cowork plugin link.
Microsoft instructions checked October 16, 2026: Customize, upload and share · Administrator deployment and governance.