Carry prior board commitments into the next curriculum-and-budget agenda
The scenario revisits past meeting discussions, proposes an agenda, captures current decisions, and organizes recap communications and follow-up documentation.
Tool
Teams use cases: 17 examples
Source-linked workflows that name Teams. Part of the AI agent use cases on UsecaseBoard, or browse all use cases.
Organize university-policy feedback into a source-backed draft and revision process
The example combines stakeholder meetings and approved research with a Word policy draft, then supports circulation and revision before adoption.
Align accessible course materials with explicit learning objectives
The scenario gathers curriculum resources and support requirements, maps content to objectives, and involves accessibility specialists in creating multiple ways to engage with the material.
Prepare a semester curriculum update from faculty and student communication
Microsoft's higher-education example gathers relevant messages, drafts a curriculum-status update, and supports course and research-outline preparation.
Prepare a business-review agenda from scattered requests and performance data
The scenario assembles agenda requests, analyzes the period's business data, builds a presentation, and distributes prework before capturing follow-up actions.
Draft a supplier RFP from prior requests and current requirements
Microsoft's workflow summarizes earlier RFPs, retrieves current requirements, develops questions, and refines the document after a team review.
Build a change-adoption plan from stakeholder impacts and workshop ideas
The scenario combines meeting insights, an Excel impact assessment, Whiteboard brainstorming, and an executive presentation to organize a change-management effort.
Carry negotiation-meeting evidence into a reviewed licensing term sheet
The example combines Teams notes, relevant agreement research, and Word analysis to prepare negotiation materials for legal-team review.
Turn a policy revision into translated change notes, FAQs, and an adoption plan
The Microsoft workflow compares old and new policies, drafts employee questions and answers, and prepares training and communication materials for review.
Prepare a cash-flow discussion from rolling-period variance evidence
The example standardizes invoice and payment data, analyzes a 12-month cash-flow comparison, and combines the findings with prior team questions for a meeting brief.
Create a self-service training pack for a newly introduced finance tool
The scenario turns a tool demo and existing documentation into an onboarding guide, draft FAQs, a training presentation, and a request for pilot-user feedback.
Prepare a supplier negotiation using contract deliverables and payment variances
The example combines finance data, supplier meetings, and contract records to build an evidence-backed supplier comparison and updated procurement documentation.
Update an RFx document using stakeholder decisions and revised cost assumptions
The scenario links meeting recap, document retrieval, Excel cost checks, and Word revisions before requesting stakeholder feedback.
Clarify workplace idioms and separate meeting-chat discussion from spoken decisions
Microsoft's example combines context-sensitive phrase explanations, Teams interpretation, and separate summaries of meeting speech and chat for multilingual collaboration.
Prepare customer follow-up from a meeting recap with fewer manual steps
The accessibility scenario combines cross-source account search, Teams recap, and an Outlook follow-up draft to reduce repetitive typing during customer work.
Group cross-border email by country and carry commitments into a work plan
Microsoft's accessibility example combines Outlook summaries, translation, meeting recaps, and document retrieval to reduce the effort of coordinating international work.
Copilot Studio: agent accounts, process memory, GitHub Copilot harness triggers
Microsoft Copilot Studio adds org-owned managed agents with their own Microsoft 365 credentials (@mention in Teams/Outlook/Office comments), business process memory that carries preferences across cycles, and GitHub Copilot harness triggers so agents start on email or a cadence without a new prompt—rolling out via Frontier.