No option to go to message from search without opening side panel
When I search for a term (whether using All or Messages) and click on a result, I intend to go to that message in the chat or direct message with the whole window, just as if I had navigated there manually. I do NOT want to open an awkward side panel with that conversation. There are no right click options on the search results. How can I get rid of the side panel and just [Go to message]?Set clear AI expectations for every assignment with Student AI Guidelines
The challenge: students don't know where they stand with AI Every educator has a different approach to AI in their classroom. Some want students using it freely. Others want AI limited to brainstorming or editing. Some assignments shouldn't involve AI at all. The problem? Students are left guessing. Educators have been piecing together workarounds — writing AI policies into assignment instructions, referencing school handbooks, or adding disclaimers to rubrics. None of these are built into the assignment itself, and students often miss them entirely. Student AI Guidelines in Assignments Student AI Guidelines give educators a structured way to set AI expectations directly inside an assignment in Microsoft Teams. When creating an assignment, educators now see a new option to set a guideline level with suggested text: Full AI use allowed. Students can use Copilot for any part of the assignment. AI for editing only. Students write their own work first, then use Copilot to polish, revise, or check grammar. AI for brainstorming only. Students can use Copilot to generate ideas or explore topics, but the final work should be their own. No AI. The assignment should be completed without AI assistance. Student AI Guidelines are available for all grade levels, on desktop and mobile. All students in the assignment see the same guideline. A note on what these guidelines are — and aren't. Student AI Guidelines are a communication tool, not a lockdown. They set clear expectations that students see in the assignment, but they don't technically block access to AI tools. They work the same way a teacher's verbal instruction does: "Here's what I expect for this assignment." The value is in making that expectation visible, consistent, and built into the assignment itself. These are starting points, not fixed rules. Each level comes with suggested text that educators can edit freely to match their school's policies, terminology, or classroom norms. If your school uses different language around AI use — or has its own framework — update the text to reflect that. The feature adapts to your school, not the other way around. Even if your school hasn't enabled Copilot, Student AI Guidelines give you a structured way to communicate AI expectations to students — whether that's encouraging responsible AI use or formalizing a no-AI policy. What students see When an educator sets a guideline, students see it in their assignment view — no hunting through instructions or attachments. The guideline card shows the educator's expectations and, for levels that allow AI use, a direct button to launch Copilot Chat. The Copilot launch button appears for students aged 13 and older at schools where an IT admin has enabled Copilot. If your school hasn't set up Copilot yet, check out the Copilot setup guide for IT admins to get started. If Copilot isn't enabled, students still see the guideline — just without the launch button. If no guideline is set, nothing changes — the student experience stays exactly as it is today. Save time: set a default and reuse across classes Two features help you avoid repeating setup work: Set as default. Any guideline level — including "No AI" — can be set as the default for all new assignments you create. If your school's policy is that most assignments should restrict AI use, set that as your default and you're covered. You can always override it on individual assignments when you want to allow more (or less) AI use. Import Settings. Once you've configured your Student AI Guidelines in one class, you can apply those same settings to other classes using Import Settings. This copies your guideline levels and custom text across classes so you don't have to re-create them each time. Learn more: Import Settings in Assignments and Grades. Why this matters This feature sits at the intersection of two things educators have been asking for: clarity around AI use, and an easy on-ramp to Copilot. Instead of competing with third-party AI tools through restriction, Student AI Guidelines give educators a way to channel AI use purposefully — on their terms, per assignment, with clear communication to students. Resources Set Student AI Guidelines on and assignment in Microsoft Teams Manage Student AI Guidelines in Assignments
New Planner UI - What problem is actually being resolved?
This new UI is a step backwards. I get that people naturally resist change at first, but Microsoft keeps making interfaces more spaced out and less information-dense, which is frustrating in a business environment where efficiency matters. I can now only see about half of what fit on screen before. Even my Planner board headers are cut off because the font sizes and spacing have been increased unnecessarily. Microsoft has a bad habit of redesigning UIs without solving an actual problem. A lot of these changes feel like they’re being made by people who don’t actively use the tools day to day in real working environments.Help Shape the Future of Microsoft Teams for Small and Medium Businesses
Have you ever wished Microsoft Teams worked just a little better for the way your business operates? Maybe you've thought: “It would be great if Teams could do this…” “This workflow would be so much simpler if…” “Why isn’t there a feature for…?” Now’s your chance to directly influence what comes next. Microsoft is inviting Small and Medium Business (SMB) customers and partners to join our Customer Advisory Board (CAB) and Partner Advisory Council (PAC) for Microsoft Teams SMB. These groups give you a simple, low-effort way to share real-world feedback with the product team — and help guide the Teams roadmap for SMBs. What are CAB and PAC? Our SMB advisory programs bring together a small group of customers and partners who: Use Teams in their day-to-day business operations Work with SMB customers implementing Teams Have insights into the challenges SMBs face when adopting collaboration tools Want to help improve the products they rely on Through monthly virtual sessions, participants get the opportunity to: ✅ Preview upcoming features and improvements ✅ Provide feedback during early stages of product development ✅ Share what’s working well — and what isn’t ✅ Highlight real-world business scenarios that should be better supported ✅ Influence priorities for SMB-focused innovation in Teams This isn’t a sales call or a support channel — it’s a direct line to the Teams product team. What’s the Commitment? We know SMB leaders, IT decision-makers, and partners are busy. That’s why participation is designed to be: Flexible – Virtual meetings combined with async conversation Low effort – No prep required for most sessions Conversational – Small-group discussions, not presentations Most sessions are informal conversations focused on understanding your business needs and how Teams can better support them. Your input helps us build features that actually reflect how SMBs work — not just how software thinks they should. Why Join? Participants often tell us that one of the biggest benefits of joining CAB or PAC is the opportunity to: Get early visibility into what’s coming next Understand where Teams development is headed Provide feedback that directly reaches the team building the product Help shape experiences that impact SMB customers worldwide Whether you're an SMB customer using Teams internally or a partner working with SMB clients, your perspective matters. Interested in Participating? If you'd like to be considered for the Microsoft Teams SMB Customer Advisory Board or Partner Advisory Council, simply fill out this short interest form: 👉 Express your interest to join the Teams SMB Advisory Board Once submitted, our team will review your response and follow up with more information on next steps.Join us May 6: Learn how Microsoft Teams is helping SMBs thrive
Running a small or medium-sized business means wearing every hat at once — sales lead, customer support, IT admin, and marketing team, often before lunch. The tools you rely on need to keep up without getting in the way. That's exactly the conversation we're hosting next week. On Wednesday, May 6, the Microsoft Teams SMB product team is going live for a focused 40-minute session designed specifically for small and medium businesses. What you'll learn Angela Chin, Principal PM Manager on the Teams SMB team, will walk through the latest updates in Microsoft Teams built with smaller businesses in mind: Get going faster — onboarding improvements that take SMBs from sign-up to collaboration in minutes. Deeper customer connections — features that turn Teams into a front door for your customers. Effortless cross-business collaboration — work with vendors, contractors, and partner businesses as naturally as your own team. Bring your questions Connect directly with the Teams SMB product team, ask questions, and share feedback that shapes the roadmap. Who should attend SMB owners and operators, IT pros supporting smaller businesses, partners and consultants, and anyone evaluating Teams. Save your seat Wednesday, May 6, 2026, 8:05–8:45 AM PT. Free to attend. 👉 Register here
Making shifts not visible to all team members
Is there anyway to make shifts private, where only the specific team member that the shift is intended for can see it I can not seem to find a setting to restrict team members to only viewing their own shifts. Short of creating a team for each individual member....is there a way I am missing?
## Advanced Copilot Prompt for High‑Fidelity Teams Meeting Analysis (v1.5)
## Advanced Copilot Prompt for High‑Fidelity Teams Meeting Analysis (v1.5) I’ve been working on a structured Copilot prompt designed to dramatically improve the quality of meeting analysis inside **Microsoft Teams**, especially when the default Intelligent Recap doesn’t capture enough nuance, decisions, or actionable follow‑ups. This prompt produces a detailed, repeatable output that includes: - TL;DR executive summary - Meeting quality assessment - Prioritized action items table - Confirmed vs. tentative decisions - Open questions & risks - Mind‑map style outline - Timeline of key moments - Confidence & source citations - Tech jargon glossary - Planner‑ready task export It’s now at **version 1.5**, and I’m sharing it publicly for anyone who wants deeper meeting insights or more reliable task handoff into Planner. --- ### Why I Built This In many engineering, security, and cross‑functional meetings, clarity is everything. The default recap is helpful, but sometimes too generic. I wanted something that: - Reduces ambiguity - Surfaces decisions clearly - Highlights risks and open questions - Produces actionable, Planner‑ready tasks - Works consistently across different meeting types - Enforces strict inference rules to avoid hallucinations If your team relies heavily on Teams + Copilot, this can significantly improve meeting outcomes. --- ### What’s Included The full prompt includes: - Strict ordering rules - Anti‑hallucination constraints - Fallback rules for missing data - TL;DR section - Speaker‑labeling rules - Timestamp restrictions - Bullet‑length limits - Planner task title constraints - Deduplication rules - Tone consistency - Signal‑to‑noise filtering I’ve included the complete prompt below for anyone who wants to use or adapt it. --- ### How to Use It 1. Open the **Recap** tab of any Teams meeting with transcription enabled. 2. Click **Open Copilot**. 3. Paste the entire prompt into the Copilot compose box. 4. Wait for the structured output (usually 30–120 seconds). 5. Copy the Planner tasks section directly into Planner or Copilot for Planner. --- ### Looking for Feedback If you try this prompt, I’d love to hear: - What worked well - What didn’t - What you’d like added in v1.6 - Any edge cases or meeting types where it struggled I’m planning to maintain this as a community resource, so suggestions are welcome. Thanks to everyone experimenting with Copilot in Teams — the creativity in this community is incredible. --- ### Full Prompt (v1.5) ````markdown ```markdown # ============================================================ # PROMPT NAME: Advanced Teams Meeting Analyst (Copilot Enhancement) # ============================================================ # Version: 1.5 # Author: Scott M # Last Updated: 2026-01-14 # # Goal: # Use Microsoft Copilot in Teams (Recap tab or live meeting) to generate a highly structured, # high-signal meeting analysis that goes far beyond the default Intelligent Recap output. # Produce executive summary with TL;DR, prioritized action items table, confirmed/tentative decisions, # risks/open questions, mind-map outline, timeline, quality assessment, confidence/sources, # tech jargon glossary, and Planner-ready task export—all derived strictly from the transcript, # shared screens, chat, and attachments. # # Why This Is Superior to Default Teams/Copilot Processing: # - Default Recap: Basic chapters, highlights, simple tasks, attendance—often generic and misses nuance. # - This custom prompt: Forces strict inference rules (no hallucinations), adds confidence labeling, # decision status, risks section, mind-map structure, quality flags, source citations, # jargon glossary, and direct Planner integration for seamless task handoff. # Delivers scannable, professional-grade notes + actionable tasks for tech/engineering teams. # # Audience: # Microsoft 365 Copilot users in Teams-heavy environments who want deeper analysis # and direct bridge to Planner for follow-up execution. # # Non-Goals: # - This is NOT a replacement for legal/compliance-grade minutes. # - This is NOT verbatim transcription (use the native transcript for that). # - Relies on Teams transcription quality (enable Intelligent Speakers if available). # # Usage Instructions: # 1. Prerequisites: # - Ensure the meeting had transcription enabled (Meeting options → Record & transcribe → Allow transcription). # - For best speaker attribution: Enable Intelligent Speakers (if your org supports it) or have participants use their names clearly. # - Copilot license required (M365 Copilot or Teams Premium for full Recap features). # # 2. Post-Meeting (Recommended – Recap Tab): # - Go to the Teams meeting chat → Click the Recap tab (appears after meeting ends and processing finishes). # - Click Open Copilot (or the Copilot icon in the top-right of Recap). # - In the Copilot pane compose box, paste this ENTIRE prompt and press Enter/Send. # - Wait 30–120 seconds (longer for 60+ min meetings) for the full structured output. # # 3. During Live Meeting (Quick Catch-Up): # - While the meeting is active → Click the Copilot icon in the meeting controls. # - Paste the prompt (or a shortened version if time-sensitive) and ask for real-time summary/actions so far. # # 4. After Output Appears: # - Review the markdown sections—copy any part (e.g., Action Items table, Planner tasks) directly. # - For Planner handoff: # - Copy the entire "10. Planner Integration" section. # - Open Planner (in Teams app or planner.microsoft.com). # - Option A: Manually create tasks by pasting titles/descriptions. # - Option B: In Planner's Copilot pane (if available): Paste the tasks list and say "Create these tasks in my [plan name] plan". # - Save/export: Copy full output to OneNote, Word, or email for sharing. # # 5. Refinement & Follow-Ups (Highly Recommended): # - In the same Copilot pane, type targeted follow-ups like: # - "Expand the Risks section with mitigation ideas" # - "Draft a professional follow-up email to attendees including the summary and action table" # - "Create these tasks in Planner plan 'Engineering Syncs'" # - "Explain [specific jargon term] in more detail" # - "Prioritize the action items by impact" # - Iterate until satisfied—Copilot remembers context in the session. # # 6. Tips & Troubleshooting: # - If output is incomplete: Re-paste the prompt or say "Regenerate full analysis". # - Short meetings (<15 min): Output may be concise—ask for more detail if needed. # - No Recap tab? Ensure recording/transcription was on; wait 5–10 min post-meeting. # - Sensitive meetings: Redaction is automatic per rules, but double-check output. # # Changelog: # v1.0 - Initial release # v1.1 - Added confidence/sources + follow-up suggestions # v1.2 - Added Tech Jargon Glossary # v1.3 - Added Planner Integration section # v1.4 - Expanded Usage Instructions into detailed, step-by-step guide with prerequisites, live/post options, refinement examples, and troubleshooting # v1.5 - Added strict ordering rules, anti-hallucination constraints, fallback rules for missing data, TL;DR section, speaker-labeling rules, timestamp restrictions, bullet-length limits, Planner title constraints, deduplication rules, tone consistency, and signal-to-noise filtering # # ============================================================ # CRITICAL INSTRUCTIONS (STRICT) # ============================================================ - Do NOT summarize, restate, or comment on this prompt. Produce only the meeting analysis. - Follow the numbered sections in the exact order shown. Do not omit, reorder, merge, or rename sections. - If any section lacks sufficient evidence, include the header and write: **“No reliable data found.”** - Derive ALL content ONLY from the Teams transcript, shared content, chat, and attachments. - NEVER invent details. If unclear, mark as “Unclear” or “TBD.” - Use neutral labels (Speaker A, Speaker B, etc.) if speaker names are not confidently identified. - Assign deterministic speaker labels based on first appearance. - Redact sensitive info as [REDACTED] and flag in Risks. - Include inline citations [Transcript HH:MM, Slide X] where possible. - Keep bullet points ≤ 20 words unless quoting transcript evidence. - Exclude small talk, greetings, jokes, or irrelevant chatter unless they directly impact decisions or tasks. - Only include timestamps if explicitly present in the transcript. Never estimate or invent them. - Deduplicate action items, decisions, and risks before final output. - Maintain a professional, concise, cross-functional technical PM tone. - Planner task titles must be ≤ 10 words and start with a verb. # ============================================================ # OUTPUT FORMAT (USE EXACTLY) # ============================================================ **TL;DR (1–2 sentences)** A concise, high-level summary of why the team met and what was resolved. --- 1. **Meeting Quality Assessment** - Clarity: [Good | Fair | Poor — brief explanation] - Speaker overlap / noise: [Low | Medium | High] - Estimated accuracy: [High | Medium | Low — justification] 2. **Executive Summary** Start with 1–2 sentence overview. Then provide 5–8 bullets covering: - Purpose - Attendees (names or count if unclear) - Key topics - Outcomes - Next steps 3. **Action Items** | Priority | Owner | Task Description | Due Date | Timestamp | Dependencies | Status | Notes | |----------|-------|------------------|----------|-----------|--------------|--------|-------| **Rules:** - Sort by Priority (High → Medium → Low), then Due Date. - Infer owners/dates ONLY if explicitly stated or clearly volunteered. - Default Priority: Medium; Status: Open. - Titles ≤ 10 words, start with a verb. - Deduplicate similar tasks. 4. **Key Decisions** - **DECISION:** [What was decided] - Status: [Confirmed | Tentative | Disputed] - Confidence: [High/Medium/Low — reason] - Rationale: [Why] - Impacted: [Who] - Evidence: [Transcript HH:MM or Slide reference] 5. **Open Questions & Risks** **Open Questions** - [Unresolved or unclear items] **Risks** - [Ambiguity, missing owners, conflicting views, scope creep, technical risks, etc.] 6. **Mind Map Outline (Hierarchical Outline)** - Main Topic 1 - Subtopic A - Action / Decision / Fact - Subtopic B **Rules:** - Max 5 main topics - Max 3 levels deep - ≤ 8 words per node - Prune low-signal branches 7. **Timeline of Key Moments** - HH:MM – [Brief one-line description] - HH:MM – [etc.] *Only include if timestamps exist; otherwise write “No reliable data found.”* 8. **Confidence & Sources Summary** - Overall confidence: XX/100 - Key sources: [Transcript HH:MM, Slide X, Chat message, etc.] 9. **Tech Jargon Glossary** - TERM: Definition (1–2 sentences) *Include only if relevant terms appear.* 10. **Planner Integration: Ready-to-Create Tasks** Numbered list, each formatted as: 1. **Task Title:** [≤10 words, verb-led] - Assigned to: [Owner or TBD] - Due: [Date or TBD] - Priority: [High/Medium/Low] - Description: [Brief details + dependencies/notes] - Labels/Buckets: [Suggested grouping] **Rules:** - Only include items with clear action/owner potential. - Group related tasks under consistent buckets. - Deduplicate tasks. --- **Follow-Up Prompts (suggest 3–5)** - “Create these tasks in Planner plan ‘X’.” - “Expand the Risks section with mitigation strategies.” - “Draft a follow-up email summarizing this meeting.” - “Prioritize action items by impact and urgency.” - “Clarify ambiguous decisions and propose next steps.”
