How do you actually unlock growth from Microsoft Teams Marketplace?
Hey folks đ Looking for some real-world advice from people whoâve been through this. Context: Weâve been listed as a Microsoft Teams app for several years now. The app is stable, actively used, and well-maintained - but for a long time, Teams Marketplace wasnât a meaningful acquisition channel for us. Things changed a bit last year. We started seeing organic growth without running any dedicated campaigns, plus more mid-market and enterprise teams installing the app, running trials, and even using it in production. That was encouraging - but it also raised a bigger question. How do you actually systematize this and get real, repeatable benefits from the Teams Marketplace? I know there are Microsoft Partner programs, co-sell motions, marketplace benefits, etc. - but honestly, itâs been very hard to figure out: - where exactly to start - what applies to ISVs building Teams apps - how to apply correctly - and what actually moves the needle vs. whatâs just ânice to haveâ On top of that, itâs unclear how (or if) you can interact directly with the Teams/Marketplace team. From our perspective, this should be a win-win: we invest heavily into the platform, build for Teams users, and want to make that experience better. Questions to the community: If youâre a Teams app developer: what actually worked for you in terms of marketplace growth? Which Partner programs or motions are worth the effort, and which can be safely ignored early on? Is there a realistic way to engage with the Teams Marketplace team (feedback loops, programs, office hours, etc.)? How do you go from âorganic installs happenâ to a structured channel? Would really appreciate any practical advice, lessons learned, or even âwhat not to doâ stories đ Thanks in advance!
The issue with channel sites (private and shared channels in Teams)
Hi, I'd like to know of your opinions, experiences, practices, decisions you've made concerning private and shared channels in teams. In my company, we are progressively migrating to Teams from Webex. Users have started creating private and shared channels. My own practice and recommendation to users has been to get a new team created when a different list of users need private access to conversations or documents, instead of a private or shared channel. My reasons are as follow: Rigidity: The SharePoint channel site created cannot follow its own direction if needs arise. It is locked with the parent site. Say we want to reorganize teams and work units, and we want to join a SharePoint channel site with a another hub â we can't, at least not easily. And now the rigidity of subsites is brought back! And anyway, the conversations are also locked with the parent team! It can't be made independent. Lack of control: Control is removed once again from us, the admins â Microsoft loves to allow users to do everything they want and foster chaotic environments. We have disabled group creation and sites creation for all but a few in order to manage the information environment, try to restrict the scattering of important documents, and make things clearer for users. But with private and shared channels, end users can now create new SharePoint sites. As the documents management specialist, I can't easily see where documents end up. And when I export the list of sites to Excel, the channel sites don't appear! So I can't really see which sites take a lot of storage space. Lack of features: Let's say the management team of a department created a private channel for management topics in the department team, and after several months of active use, they now decide they'd like to manage tasks in Planner â tasks that should be private to the management team. They can't, should have created a M365 group for that! Once again, it is rigid. Troubles for the admin: I want to apply a change to all SharePoint sites â so IâŻtype a PowerShell command that will apply to all sites. But it won't apply to all sites: not the channel sites. Also, ShareGate can't seem to get the access matrix of channel sites â it returns errors for them. However, when I turn to the Web for advice with this issue, I only find appreciation for private and shared channels, and none of my concerns addressed. Apparently, they allow to avoid the multiplication of teams. However, I'm not sure how multiplying channels is better than multiplying teams. With both teams and channels, users can hide or show them, and as a team always have a channel, they can disable notifications. Maybe IâŻshould just deal with and accept the rigidity, lack of M365 features and troubles for the admin. Maybe I should approach the control of the information architecture and documents differently. What is your view on that? Did you have any issues with channel sites, and if yes, how do you deal with them? Did you discourage or prevent the creation of private and shared channels? Have you reconsidered your decision? Do you see private and shared channels as a very useful feature, and if so, why? I'm interested in all experiences on this topic and I'm thankful for all answers.
Teams calendar for exchange on prem users not working
Hello I am having issues to make Exchange On prem users use Calendar on teams. Initially Client autodiscover was blocked externally but they added a cname and open flows but I am still having issues to makecalendar on teams work HCW as passed and new hybrid dedicated app was used any help is welcome
Teams meeting email invites do not display "Add to Calendar" header when there's an attachment.
Trying to solve an issue when someone sends out Teams meeting invites that include attachments. The header that typically appears directly above the body of the email showing the time and date of the meeting and the option to add the meeting to your calendar does not appear, this issue is consistent across outlook and gmail inboxes of the recipients. The attachment takes over the space that the 'Add to Calendar' would appear, I have been able to replicate this issue consistently. Removing attachments rectifies the issue but is not really satisfactory as they want to include relevant files to the meeting in the invitations that are sent out. Thanks, L
## 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.âAmericas & EMEA Fabric Engineering Connection
đ Excited to announce the upcoming Fabric Engineering Connection call for Microsoft partners! Join us on Wednesday, December 10, from 8â9 am PT (Americas & EMEA) and Thursday, December 11, from 1â2 am UTC (APAC) for an insightful session featuring Erin Stellato and Mark Brown. This weekâs focus: đŻ GitHub Copilot in SSMS with Fabric SQL đŻ User-Data Function Integration with Cosmos DB in Fabric Donât miss the opportunity to learn directly from the experts and discover the latest innovations in Microsoft Fabric. To participate, make sure youâre a member of the Fabric Partner Community Teams Channel. Join here: https://lnkd.in/g_PRdfjt Letâs connect, learn, and shape the future of data together! đĄ
