[New Mission] Operative NextGen: Publish, share, and complete the course

[aprildunnam]

[New Mission] Operative NextGen: Publish, share, and complete the course

Summary

Author the Operative NextGen completion mission. Learners establish the release version, publish the Hiring and Interview Prep agents, make the Hiring Agent available in Microsoft 365 Copilot, share it with a controlled audience, run the full hiring scenario, and claim the Operative badge.

This uses the modern publish and share experience and turns course completion into a release-readiness check rather than a badge-only page. Duplicate checks found no issue proposing this complete Operative NextGen mission.

Proposed mission

Field	Value
Section	Operative NextGen
Folder	docs/operative-v2/10-course-completion/
Title	Mission 10: Publish, Share, and Complete the Course
Operation codename	OPERATION FINAL APPROACH
Difficulty	2
Time	45 minutes

Scenario

The hiring solution has passed its evaluation gate and is ready for a controlled release. The learner records the release version, publishes all dependent components in the correct order, shares the Hiring Agent through Microsoft 365 Copilot, validates the complete workflow as an end user, and claims the Operative credential.

Use a release-gate analogy: every dependency, permission, test, and owner must be checked before the solution leaves the training environment.

Mission objectives

• Establish a traceable course release version.
• Publish dependent agents and workflows in the correct order.
• Configure Microsoft 365 Copilot availability and sharing.
• Run and document an end-to-end acceptance test.
• Complete the Operative badge claim.

Prerequisites to state in the mission

• Completion of Missions 01–09.
• Passing critical safety and end-to-end evaluation cases.
• Publishing access configured in the tenant.
• Microsoft 365 Copilot access and a controlled test user or group.
• Required workflow and MCP connections owned by an appropriate account.

Proposed lab outline

Prepare the release

Record solution, agent, skill, workflow, test-set, and mission content versions. Review unresolved issues, owners, connections, permissions, evaluation results, and known limitations.

Publish dependencies

Publish Workflows and the Interview Prep Agent before the Hiring Agent. Verify connected-agent references, Dataverse MCP, Work IQ Calendar, feedback settings, and the release’s published timestamp.

Configure availability and sharing

Use the current publish and channel flow to make the Hiring Agent available in Microsoft 365 Copilot. Share it with a limited test group and explain direct sharing versus organizational catalog submission.

Run final acceptance

As a test user, upload a fictitious resume, extract and match, confirm application creation, generate interview prep, exercise the email/Teams workflow as appropriate, find and confirm a meeting time, submit a reaction, and verify Monitor evidence.

Claim the badge

Present the Operative badge requirements and official claim form, verify the current URL and required identity, submit the claim, and set expectations for issuance.

Acceptance criteria

• Define a release version that covers the complete solution, not invented per-agent semantic versions unsupported by the product.
• Document and follow dependency publication order.
• Publish both agents and all required workflows successfully.
• Configure Microsoft 365 Copilot availability without implying tenant-wide approval is automatic.
• Share only with a controlled test audience and document required licenses and permissions.
• Run the full scenario with fictitious data and verify every expected side effect.
• Record final evaluation results, Monitor evidence, known limitations, and cleanup actions.
• Verify badge image, requirements, claim URL, and issuance instructions before publication.
• Do not require learners to star a repository or create unrelated accounts unless the official badge process currently requires it.
• Preserve <mission-meta /> and <analytics-tag section="operative" mission="10-course-completion" />.
• Follow WRITING_STYLE.md; run validation, Markdown linting, and npm run docs:build.
• Inspect the rendered mission and deployed Microsoft 365 Copilot experience.

Out of scope

• Organization-wide production deployment.
• Managed-solution pipelines and CI/CD.
• Public web or custom application channels.
• Production support and service-level agreements.

Risks

• Channel availability and sharing depend on tenant policy and licensing.
• End-user permissions can differ from maker permissions.
• MCP and workflow connections can break when owned by an individual maker.
• The badge claim process and URL can change.
• End-to-end tests create real messages, events, and test records that require cleanup.

References

• Current Operative badge mission
• Publish an agent
• Connect to Teams and Microsoft 365 Copilot
• Share an agent