Recent Discussions
Feature Request: Custom Status Labels for Calendar Events (e.g., 'In a Training')
Hey Teams Community! đ I have a small but impactful feature idea and would love your votes and feedback. --- đ´ The Problem Right now, every calendar block in Microsoft Teams shows the same status to colleagues: "In a Meeting." Whether you're in a 10-minute standup or a 3-hour mandatory training â it all looks identical. This creates ambiguity, leads to unnecessary interruptions, and doesn't reflect how modern workplaces actually function. --- đĄ The Feature Request Allow users to assign a custom status label to a calendar event when creating it â visible to colleagues who check availability â without exposing private event details. Something as simple as a dropdown when creating an event: â In a Meeting (default) đ In a Training đŻ Focus Time đ In a Workshop The chosen label would appear: â In the chat status indicator â On the calendar availability hover card â When someone tries to @mention or call you --- â Why This Matters - Reduces interruptions during high-focus or learning sessions - Helps colleagues make smarter decisions about whether to wait or escalate - Especially valuable for schools, hospitals, training teams, and L&D departments - Lightweight to implement â no privacy concerns since it doesn't reveal event titles --- đłď¸ If you've ever been interrupted during a training because someone thought you were just "in a meeting" â please upvote and share your experience below! Let's get this on the Teams roadmap. đ Tags: Feature Request, Calendar, Status, Availability, Training, Teams, Microsoft Teams
Mute/unmute hotkey stopped working in main windows during presentation
In recent versions I have been able to press CTRL + SHIFT+ M when I was presenting (sharing) something from my Teams main window. Recently this stopped working and I need to go forth and back from main window to the my call window to mute myself. Could you please restore the old behavior. Thank you! Best regards Tom
Copilot Studio bot in Teams occasionally sends duplicate responses
Iâm using a Copilot Studio bot deployed in Microsoft Teams, and Iâm experiencing an intermittent issue where a single user message occasionally triggers two identical responses. This does not happen consistently, and there is no intentional duplicate logic in my bot design. Iâm not sure whether this is caused by duplicate message delivery from Teams (e.g., retries or at-least-once delivery behavior), or something within Copilot Studio itself. Is this a known behavior for the Teams channel or Copilot Studio? Are there any recommended ways to detect or prevent duplicate responses at the bot level? Any insights or best practices would be appreciated.Update to disabling Teams meeting recording expiration notification emails
Hello, Thank you to everyone who shared their thoughts and feedback regarding the planned Upcoming change: disabling Teams meeting recording expiration notification emails. After carefully reviewing the feedback from this discussion, survey responses, and support channels, we have decided to pause the rollout of this change. The updates originally planned for June 1st will not take effect on that date. What this means for you: - Email notifications for expired Teams meeting recordings will continue as they do today. - No action is required on your part. - Recording expiration and deletion policies remain unchanged. Your input along with ongoing, internal engineering discussions helped shaped this decision. We want to make sure that any changes we make to the notification experience truly work for your organizations, and the feedback we received made it clear that we need more time to get this right. We're still committed to improving the notification experience for Teams meeting recordings and will provide updates here and through the Message Center when we have more to share. In the meantime, please continue to share your thoughts in this discussion. Thank you for your patience and for being part of our community.Microsoft to Retire Together Mode for Teams Meetings
In a somewhat surprising decision, Microsoft announced plans to retire the Together mode feature for Teams meetings in June 2026. Based on personal experience, it didnât seem that many people used Together mode. It seemed like it was something that people tried a couple of times before giving up. Maybe itâs just the meetings I attend, but I havenât seen Together mode used in years. https://office365itpros.com/2026/05/04/together-mode-retirement/Upcoming change: disabling Teams meeting recording expiration notification emails
Hello, We wanted to share an important update regarding email notifications for expired Microsoft Teams meeting recordings. Based on valuable feedback from our community, weâve decided to make a change to how notifications are handled. Whatâs changing: Starting June 1st, we will stop sending email notifications for expired Microsoft Teams meeting recordings. We are making this change due to complaints we received from many customers about the high volume of notifications which they deemed low value. This change allows us to respect your preferences while ensuring critical communications remain accessible. Recording expiration and deletion policies remain unchanged and items that expire will be deleted even when notifications are not being sent. How to keep receiving notifications: For those customers that would like to continue receiving email notifications, we will create a new setting and make it available before June 1st. This will be a per-tenant setting. We will send another message center post once this setting is available and update our documentation in this discussion and on our support page. After June 1st: If you didnât change notification settings before the deadline, you can still re-enable them at any time by running the PowerShell command. Note: Our original message center post incorrectly asked recipients to fill out a survey and failed to include a link to the survey. We are committed to providing options that work for your organization, and we would like to hear from you. If you have questions or additional feedback about this change, please complete this survey and join the discussion: Teams Meeting Recording Notification Changes â Fill out form Thank you for being part of our community.Copilot Studio in Teams sometimes wraps user input with HTML tags (e.g., <div>)
Iâm using Copilot Studio deployed to Microsoft Teams, and I noticed that user messages are occasionally received with HTML tags. For example, when a user sends "get me the onboarding status", sometimes it displays in the dialog box as "<div>get me the onboarding status</div>" This does not happen consistently. Iâm not sure whether this is caused by how Teams renders or sends messages (e.g., HTML vs plain text), or if it is something specific to Copilot Studio. Is this expected behavior for the Teams channel? Any clarification or recommended handling would be appreciated.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?
Set the visibility of allocated shifts only to the person allocated to it and owners?
I am wondering if it is possible to set visibility of allocated shift only to the assigned person and the owner of the schedule/disable the ability to view the entire teams shifts if you are only a "member"? I know there is an option to only send out notifications to the affected people but not actually set visibility for the shifts. //TobiasTransforming Microsoft Teams into a Project Management Hub
If you use Microsoft Teams only for chats and meetings, youâre missing much of what it can actually do. While Microsoft Teams is often seen as a communication tool, it can also function as a central workspace for managing projects - from planning and brainstorming to execution and documentation - all in one place. When combined with tools like Microsoft Planner, SharePoint, and Microsoft Loop, Teams can become a practical project management hub that keeps work organized and reduces the need to switch between systems. This article walks through a clear, practical approach to setting up and using Teams for real-world project delivery. Why Use Microsoft Teams for Project Management? Organizations often hesitate to introduce new tools due to cost, training effort, or resistance to change. Microsoft Teams offers a strong advantage: it is already widely adopted in many organizations as part of Microsoft 365. Using Teams for project management allows you to: Centralize communication and documentation Reduce tool fragmentation Improve team visibility and collaboration Leverage existing infrastructure without additional cost Instead of switching between multiple platforms, teams can manage conversations, files, tasks, and workflows in one place. Structuring Your Project in Teams A well-structured Team is the foundation of successful project management. Create a Dedicated Team Start by creating a Team specifically for your project. Avoid mixing multiple projects in one Team, as it leads to confusion and poor organization. Recommended channels structure: General (announcements and overview) Planning (timelines, scope, requirements) Execution (daily work discussions) Risks and Issues Documentation Onboarding Lessons Learned This structure ensures clarity and separates strategic discussions from operational ones. Managing Tasks with Planner Task management is a critical part of any project. Inside Microsoft Teams, you can add a Planner tab to manage tasks visually within the same workspace where communication and files are stored. How to use Planner effectively: Create buckets (e.g., To Do, In Progress, Completed, or structured by topic) Assign tasks to team members for clear ownership Set due dates and priorities Attach files and add comments directly to tasks Use labels to categorize work (e.g., Design, Frontend, Backend, Testing) for better filtering and tracking Planner also provides multiple views beyond the basic board: Board view (Kanban-style) for workflow tracking Charts view for progress and workload overview Schedule (Calendar) view to track deadlines visually across time This combination allows teams to switch between operational tracking and higher-level planning depending on the need. This visual approach improves accountability, transparency, and makes task tracking easier even for non-technical users. Document Management with SharePoint Every Team in Microsoft Teams is backed by a SharePoint site. This means all files shared in Teams are stored and managed through SharePoint. Using SharePoint effectively allows you to: Structured storage of project documentation through folders and metadata Maintain version control Role-based access management Centralized file organization Control access permissions Enable real-time collaboration Best practices: Create clear folder & metadata structures (e.g., Contracts, Designs, Reports) Avoid duplicate files Use naming conventions Instead of sending documents via email, teams can collaborate directly within Teams, ensuring everyone works on the latest version. SharePoint Lists in Microsoft Teams SharePoint Lists in Microsoft Teams provide a structured way to store, manage, and track information directly within the collaboration workspace. A SharePoint List is essentially a flexible data table, where each item represents a record with defined fields (such as status, owner, due date, priority, or category). They are especially useful for: Project roadmaps and milestone tracking Action item tracking with ownership and status Checklists for delivery and execution steps Simple status registers and progress tracking Unlike free-form messages or documents, SharePoint Lists keep information structured, filterable, and easy to update, which makes them suitable for ongoing tracking and reporting. When used inside Microsoft Teams, Lists help teams move from discussion to execution by turning decisions into trackable items with clear ownership, status, and visibility. Embedding SharePoint Pages in Teams Beyond file storage, Microsoft 365 allows SharePoint pages to be embedded as tabs within Teams, making key project information easily accessible in one place. SharePoint pages can be added as tabs inside Microsoft Teams channels, providing structured and persistent access to key project information without leaving the collaboration space. In practice, organizations often use SharePoint pages for: Project home page with key links and overview Governance page with rules and standards Onboarding page for new team members Documentation hub for core resources Centralized knowledge hubs This helps ensure that essential information is not scattered across chats or files, but is instead organized and always available within the project workspace. SharePoint is better suited for structured, stable, and long-term information. Microsoft Loop for Real-Time Collaboration Microsoft Loop introduces a more dynamic layer of collaboration inside Microsoft Teams, designed for fast, interactive work where content is continuously evolving. Loop components (such as notes, tables, task lists, and meeting agendas) can be embedded directly into Teams conversations and edited in real time by all participants. It is especially useful for: Live meeting notes Quick decision-making and feedback collection (including simple polls or inputs) 1:1 discussions and follow-ups Brainstorming sessions and idea capture Shared task tracking during discussions In practice, teams can collaborate on meeting notes or brainstorming pages during calls, with updates visible instantly to everyone. This removes the need to switch between documents or wait for post-meeting summaries. Unlike structured tools like SharePoint, Loop is designed for fluid, real-time collaboration, where information is shaped and refined as the discussion happens. Automating Workflows with Power Automate Manual processes can slow down project execution. With Power Automate, you can streamline repetitive tasks. Common automation examples: Notify the team when a task is completed Send reminders for upcoming deadlines Automatically save email attachments to SharePoint Trigger approval workflows Example scenario: When a task in Planner is marked as âCompleted,â a notification is sent to the project manager and logged in a tracking list. This reduces manual follow-ups and improves efficiency. Power BI Dashboards Power BI can be integrated into Teams as a tab, allowing teams to access real-time reporting directly within their project workspace. It is commonly used for: Project status dashboards KPI and performance tracking Resource and workload visibility Financial or delivery reporting Instead of switching to a separate reporting tool, teams can monitor progress and insights directly inside Teams, ensuring better visibility and faster decision-making. Microsoft Whiteboard Microsoft Whiteboard provides a visual collaboration space for real-time ideation and planning. It is especially useful for: Brainstorming sessions Process mapping and flow design Workshop facilitation Visual planning during meetings Whiteboard supports freehand drawing, sticky notes, and structured diagrams, making it effective for capturing ideas during live discussions and workshops. Integration with Other Tools (Microsoft & Third-Party) Microsoft Teams can be extended with a wide range of Microsoft 365 services and external applications, allowing it to function as a central hub for project work, reporting, and collaboration. Teams also supports many external tools, allowing organizations to align existing systems without fully replacing them. Common examples include: Jira â agile project and issue tracking Trello â lightweight task and board management ServiceNow â IT service management workflows GitHub â development and repository tracking Salesforce â CRM data and customer-related workflows Communication and Collaboration Effective communication is essential for project success. Microsoft Teams provides multiple ways to facilitate this: Channel Conversations Keep discussions organized by topic instead of using scattered chats. Meetings and Calls Schedule regular check-ins, sprint reviews, or stakeholder updates directly within Teams. Mentions and Tags Use @mentions to notify specific team members and ensure accountability. Practical Use Case Consider a company implementing a new internal intranet. Using Microsoft Teams: A Team is created for the project Planner tracks tasks such as design, content migration, and testing SharePoint stores documents and site assets Power Automate sends reminders for deadlines Teams meetings are used for weekly progress reviews This setup enables the team to manage the entire project lifecycle without introducing additional tools. Best Practices for Success To maximize the effectiveness of Microsoft Teams for project management: Keep your structure simple and consistent Avoid creating too many channels Encourage team members to use channel conversations instead of private chats Regularly review and clean up tasks Use automation where it adds clear value Adoption is just as important as functionality. A well-designed system only works if the team actively uses it. Limitations to Consider While Microsoft Teams is powerful, it has limitations: Not suitable for highly complex project scheduling Limited dependency management compared to dedicated PM tools Reporting capabilities are basic without Power BI For large-scale or highly regulated projects, a dedicated project management tool may still be required. Professional Context and Applied Perspective The approach described in this article reflects practical experience in designing and implementing collaboration environments using Microsoft Teams within real organizational settings. It is based on applied use of integrated Microsoft 365 capabilities, including SharePoint, Microsoft Planner, and Microsoft Loop, to support structured project execution and improve cross-functional collaboration. Rather than relying on isolated tools, this approach focuses on designing a unified digital workspace that aligns communication, task management, documentation, and automation within a single environment. Microsoft Teams is more than just a communication platform. When used strategically, it becomes a practical and efficient tool for managing projects. By combining Teams with Planner, SharePoint, and Power Automate, organizations can create a unified workspace that supports collaboration, task management, and process automation. For teams looking to simplify their toolset while maintaining productivity, Microsoft Teams offers a compelling solution for modern project management.Transforming Microsoft Teams into a Project Management Hub
If you use Microsoft Teams only for chats and meetings, youâre missing much of what it can actually do. While Microsoft Teams is often seen as a communication tool, it can also function as a central workspace for managing projects - from planning and brainstorming to execution and documentation - all in one place. When combined with tools like Microsoft Planner, SharePoint, and Microsoft Loop, Teams can become a practical project management hub that keeps work organized and reduces the need to switch between systems. This article walks through a clear, practical approach to setting up and using Teams for real-world project delivery. Why Use Microsoft Teams for Project Management? Organizations often hesitate to introduce new tools due to cost, training effort, or resistance to change. Microsoft Teams offers a strong advantage: it is already widely adopted in many organizations as part of Microsoft 365. Using Teams for project management allows you to: Centralize communication and documentation Reduce tool fragmentation Improve team visibility and collaboration Leverage existing infrastructure without additional cost Instead of switching between multiple platforms, teams can manage conversations, files, tasks, and workflows in one place. Structuring Your Project in Teams A well-structured Team is the foundation of successful project management. Create a Dedicated Team Start by creating a Team specifically for your project. Avoid mixing multiple projects in one Team, as it leads to confusion and poor organization. Recommended channels structure: General (announcements and overview) Planning (timelines, scope, requirements) Execution (daily work discussions) Risks and Issues Documentation Onboarding Lessons Learned This structure ensures clarity and separates strategic discussions from operational ones.Failure to sign in
First of all, I have TEAMS on my old computer. However, I bought a new computer, and I am unable to gain access to the TEAMS file on my new computer. I gain access to TEAMS, it asks me to sign in again. But the sign-up page does not open. It ends there. I have read the instructions and have spent over an hour trying everything without success. It shouldn't be so difficult.
SharePoint-site as a Teamsapp opens up sitepages in a web browser
Hi, I'm developing a custom Teams app using the Microsoft Teams Developer Portal. The app is configured to display a SharePoint site as a personal tab The initial page loads fine inside the Teams app. However, when users click on internal links (e.g., to other SitePages within the same site the link opens in a new browser window instead of navigating inside the Teams app. The settings looks ok. Both in SharePoint and in the App. The strange thing is that we have an older app / site that works as intended with the same settings. But all new sites /apps does not keep the user in the Teams app. I wonder if MS has changed something backend. I know thay changed the Website-Tab in a Microsoft Teams Team to open in the browser. Might this effect the Custom Teams app and tabs as well? Any ideas?Microsoft Teams PowerShell Module 7.6.0 is broken
Dear Community I have a few Script with Microsoft Teams PowerShell, witch authenticate via Access Token. Everything works fine until latest Microsoft Teams PowerShell Module Update 7.6.0. I got following Error with the Script. Connect-MicrosoftTeams : Could not load file or assembly 'Microsoft.IdentityModel.JsonWebTokens, Version=8.3.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified. If I downgrade my environment from Version 7.6.0 to Version 7.5.0 and rerun my script, the authentication is working as expected. What is wrong here with latest PowerShell Module 7.6.0 and how can I resolve the issue Many thanks for sharing any hint or tip ANDYHow to explicitly state an external org is trusted
We have a B2B relationship with our parent company. They manage their own M365 we manage ours, but we added each others' domains as instructed in Cross-Tenant Access Settings and allowed access to each other's directory and calendar. However, on our Teams, their users pop up with a grey "external" badge stating "This person's org hasn't yet been added to your org's trusted list" even though Team's External Access Settings is set to Allow all External Domains, which means there is no trust list to begin with. Do the trusted domains have to be specified explicitly if so, is there a way to set this external domain as trusted without having to change "Allow all External domains" to "Allow only specific external domains"?
Unable to remove old account sing up form Teams on Mac OS
I cannot remove an old sing account from Teams on Mac OS. I have to delete the keychain, I delete the temp folder, and remove and reinstall Teams, and the old account is still there. I have a case open with the Microsoft team, and they cannot figure it out. Where is the login info store, and why has Microsoft not provided a solution where users can remove accounts as easily as they can add? Please help!
My Point of View on Microsoft 365 E7
1) Introduction: Microsoft 365 E7 is built for organisations ready to move beyond traditional productivity suites and embrace an AIâdriven operating model. It unifies advanced collaboration tools, enterpriseâgrade security, identity management, and AI innovation into a single platform. Its purpose is to transform human intent into automated AI action while ensuring strong governance and control. At the heart of E7 is Microsoft Agent 365, a management layer that enables organisations to deploy, scale, and govern AI agents across the digital workplace. 2) Core components E7 combines existing Microsoft technologies with new AI capabilities: Microsoft 365 E5 Teams for collaboration Outlook and Exchange for communication SharePoint and OneDrive for document management Advanced compliance and security features Enterprise analytics and data protection Microsoft 365 Copilot AI assistant integrated across apps Helps draft content and emails Analyses data in Excel Summarises meetings and documents Automates routine tasks Microsoft Entra Suite Identity and access management Secures identities and applications Manages user access across systems Protects against identityâbased threats Supports secure remote and hybrid work Microsoft Agent 365 Platform for managing AI agents Provides governance and control for automation Enables safe and scalable AI deployment 3) Why Microsoft 365 E7 Matters? E7 signals a shift from traditional digital workflows to environments where AI agents actively assist and automate work. With E7, organisations can: Scale AI capabilities across departments Maintain compliance and governance Safeguard sensitive data and identities Empower employees with intelligent, productivityâenhancing tools For businesses pursuing an AIâfirst strategy, Microsoft 365 E7 offers a unified foundation for innovation, efficiency, and growth. Strategic Perspective : E7 represents a significant evolution in enterprise communications. Traditionally, unified communications focused on integrating voice, video, messaging, and collaboration into a seamless experience. With E7, Microsoft is extending that vision into AIâdriven orchestration, where communication isnât just about connecting people, itâs about enabling agents and automation to act on intent. Key Strengths Deep Integration: By combining Microsoft 365 E5, Copilot, Entra, and Agent 365, E7 creates a single ecosystem where collaboration, identity, and automation are tightly bound. AIâFirst Workflows: Copilot and Agent 365 shift communications from reactive (chat, email, meetings) to proactive, where AI agents can summarise, draft, and even execute tasks. Governance & Security: Entra ensures that identity and access remain central, which is critical as AI agents begin to act on behalf of users. Scalability: Agent 365 provides the control layer to scale AI safely across departments, avoiding the chaos of fragmented automation tools. 4) Why It Matters for Unified Communications? E7 is not just another productivity suite itâs the next operating model for enterprise collaboration. In UC terms, it means: Meetings and messaging become AIâaugmented experiences. Communication channels are contextâaware, with agents that can act during or after interactions. Governance ensures that automation doesnât compromise compliance or trust. 5) My Take Microsoft 365 E7 is essentially Unified Communications 2.0 moving from connecting people to connecting people + AI agents in a governed, secure environment. For organisations, this means less friction in workflows, faster decisionâmaking, and a foundation for scaling AI across the enterprise. Itâs a bold step: UC is no longer just about âhow we talk and collaborate,â but about how intent flows seamlessly into action. 6) Unified Communications (UC) use cases where Microsoft 365 E7 could have the biggest impact a) Meetings & Collaboration AIâSummarised Meetings: Copilot automatically generates minutes, action items, and followâups from Teams meetings. RealâTime Agent Assistance: Agent 365 can deploy meeting assistants that track decisions, schedule tasks, and notify stakeholders instantly. CrossâLanguage Communication: AI agents provide live translation and contextâaware summaries, making global collaboration seamless. b) Contact Centers & Customer Engagement AIâDriven Call Routing: Agent 365 can intelligently assign customer calls to the right agent or bot, reducing wait times. Automated Responses: Copilot drafts responses to customer queries based on knowledge bases, improving speed and consistency. Compliance Monitoring: Entra ensures identity verification and secure access for agents handling sensitive customer data. c) Frontline & Field Communications Task Automation: AI agents can log field reports, update inventory, or trigger workflows directly from mobile Teams chats. Secure Access Anywhere: Entra provides identityâbased security for frontline workers accessing apps remotely. VoiceâtoâAction: Workers can issue voice commands that AI agents convert into automated actions (e.g., âlog equipment issueâ). d) Executive & Leadership Communication AIâCurated Briefings: Copilot summarises enterprise communications, surfacing key insights for leadership. Governed AI Agents: Agent 365 ensures executives can safely delegate routine communication tasks to AI without losing oversight. DataâDriven Decision Support: Integration with analytics tools provides leaders with realâtime dashboards and AIâgenerated recommendations. 7) Key Differences when comparing with E5+ Copilot Comparison table Feature / Factor Microsoft 365 E5 + Copilot Microsoft 365 E7 Core Productivity Includes Teams, Outlook, SharePoint, OneDrive, compliance, analytics Same foundation (E5 included) AI Capabilities Copilot integrated into apps (Word, Excel, Teams, Outlook) Copilot + Copilot Studio + Work IQ + AI agent orchestration Identity & Access Basic Entra features (with E5 security/compliance) Full Microsoft Entra Suite for advanced identity governance AI Agent Management Not included Microsoft Agent 365 â deploy, manage, and govern AI agents Governance & Compliance Strong compliance/security tools Enhanced governance for AI workflows and agent actions Target Audience Organisations experimenting with AI productivity Organisations scaling AI enterpriseâwide with governance Cost (per user/month) E5: ~$57â$65 + Copilot addâon: ~$30 â ~$87â$95 $99 flat pricing (Frontier Suite) Positioning Secure productivity + AI assistant AIâdriven operating model with enterprise governance Key differences: Governance Layer: E7 introduces Agent 365, which ensures AI agents can be deployed safely across departments something E5 + Copilot lacks. Identity Integration: E7 bundles the Entra Suite, giving advanced identity and access management beyond E5âs baseline. Unified Pricing: Instead of stacking E5 and Copilot costs, E7 offers a single license at $99/user/month. Strategic Role: E5 + Copilot is about productivity enhancement; E7 is about enterprise AI transformation. Risks & Tradeâoffs Cost Premium: E7 is ~10â15% more expensive than E5 + Copilot combined. Adoption Readiness: E7 makes sense only if an organisation is ready to scale AI broadly; otherwise, E5 + Copilot may suffice. Complexity: Governance and agent management add layers of responsibility requiring IT maturity. Conclusion: If your organisation is still testing AI productivity gains, E5 + Copilot is costâeffective. But if youâre ready to scale AI across the enterprise with governance, compliance, and identity controls, E7 is the better longâterm foundation.
## 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.â
external calls with call queue or resource account.
Hi. I am setting up a call queue and an auto attendant for my customer service department. I already receive the calls and they are forwarded to my agents as I have configured in the call queue. My problem comes with the outgoing calls, I don´t want the customer service users to call directly. I want them to call through the resource account. I can do this by selecting the resource account in the teams (see image) I need that the default option is always the resource account or a way to make that when they call always do it through the resource account or the same call queue. Is it possible?
Recent Blogs
- 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 withou...May 01, 2026
- 13 MIN READOur team just wrapped up the M365 Community Conference in Orlando, FL, and it was an incredible way to close out April! Our teams were energized by connecting with, listening to, and sharing whatâs n...Apr 30, 2026
