Forum Widgets
Latest Discussions
Removal of Copilot Chat Availability in M365 Apps?!?
Received a post in Message Center today and would like clarification as to what capabilities Copilot Chat will retain as it is unclear from the message. This is a huge impact to users who have already adopted Copilot Chat in Word, Excel, PowerPoint and OneNote as well as training materials (both our own and those provided here by Microsoft). Will users be able to access Copilot Chat (basic) via pinned app in M365 apps? Will users only be able to access via web browser? The section below noted in red is very confusing (from the Microsoft message) -- who gets what features as both are mentioned in same paragraph? ---------------------------------- Microsoft 365 Copilot Chat – Updates to Copilot in Word, Excel, PowerPoint, and OneNote Starting April 15, 2026, Copilot will no longer be available in Word, Excel, PowerPoint, and OneNote for Copilot Chat users. To ensure a high-quality experience, we are reserving the full Copilot experience in these apps—with advanced reasoning and model choice—for users with a paid Microsoft 365 Copilot license. There are no other changes for users without a Microsoft 365 Copilot license. Copilot Chat still offers secure, AI web chat and the Word, Excel, and PowerPoint agents for chat-first content creation within the Microsoft 365 Copilot app. Additionally, users still get Copilot in Outlook with inbox and calendar grounding.Governance of AI Agents with Microsoft Entra & Agent 365
As organizations accelerate their adoption of AI-driven automation, the emergence of autonomous and semi-autonomous AI agents is reshaping how work gets done. These agents capable of making decisions, executing workflows, and interacting with enterprise systems introduce a new layer of complexity in identity, access, compliance, and lifecycle management. https://dellenny.com/governance-of-ai-agents-with-microsoft-entra-agent-365/Agentic AI in Microsoft Teams: The Future of Workplace Automation (Technical Deep Dive)
Over the years, enterprise collaboration has steadily evolved—from siloed communication tools to unified digital workspaces. Today, as a Solution Architect, I see organizations standing at the edge of a new transformation: Agentic AI embedded directly into collaboration platforms like Microsoft Teams. https://dellenny.com/agentic-ai-in-microsoft-teams-the-future-of-workplace-automation-technical-deep-dive/Reference Architecture for Agentic AI in Enterprise IT
Enterprise IT is entering a new era where artificial intelligence is no longer just a passive tool that analyzes data or generates content. Instead, we are witnessing the rise of Agentic AI systems that can autonomously plan, reason, act, and continuously improve toward defined goals. For organizations aiming to scale this capability responsibly, a well-defined reference architecture becomes critical. https://dellenny.com/reference-architecture-for-agentic-ai-in-enterprise-it/
Copilot File Downloads Expire Immediately – Error Across App, Browser, and Incognito
Hi, I’m running into a recurring issue when Copilot generates downloadable files. Every time I try to download the file (almost immediately), I get the following error message: “File unavailable. Generated files expire after a short period. Please regenerate if needed.” This happens consistently, even when I regenerate the file multiple times. I’ve tested this in several places and the issue is the same everywhere: Copilot App Browser version Incognito / Private mode The file appears for a moment, then instantly becomes unavailable. I’m unable to download anything before it expires. Is this a known issue, and is there a workaround? Thanks in advance for any guidance.
Adobe Payment Declines Caused by Mislabelled VAT Field — Sharing a Fix to Save Someone’s Sunday
a { text-decoration: none; color: #464feb; } tr th, tr td { border: 1px solid #e6e6e6; } tr th { background-color: #f5f5f5; } I wanted to share a recent issue that cost me an entire Sunday, in case it saves someone else the pain I went through. I was trying to add my business card as the payment method on my Adobe account. Every attempt ended with the same message: “Purchase Declined.” I tried multiple cards — same result. Naturally, I reached out to NatWest through their messaging system. After a long back‑and‑forth with Cora (their bot), I finally got through to a human. They confirmed there was nothing wrong with my card and advised me to check with the vendor. Adobe, of course, bounced me back to the bank. Classic loop. Eventually, I managed to solve it myself. a { text-decoration: none; color: #464feb; } tr th, tr td { border: 1px solid #e6e6e6; } tr th { background-color: #f5f5f5; } The culprit? A misbehaving VAT Number field. On Adobe’s payment form, there’s a field for a VAT number. If I left it blank, the payment went through immediately. But if I tried to enter my actual VAT number, the card was rejected every time. Based on a bit of trial, error, and experience with automation tools, I suspect the VAT field’s label has been updated, but the underlying target still points to the 3‑digit card security code field. Since that field is required, entering a VAT number likely breaks the form validation and triggers the “declined” status. The fix: Leave the VAT number field empty when adding a card to Adobe. Once I did this, my business card was accepted straight away. I figured I’d share in case anyone else hits the same brick wall. It’s a small thing, but exactly the kind of time‑sink that ruins your weekend! Hope this helps someone.How to become a Frontier 💪
If the Workflows agent sounds like a mystery to you, or you doubt of the existence of the =Copilot() function in Excel at all, then keep reading becasue this tip may be for you! Features like the =Copilot() function in Excel, the Workflows agent, or the Learning agent are part of the Frontier program. But what's the Frontier program and how to join it, this what this post is all about. What's the Frontier program? The Frontier program can help you get early-taste of Microsoft 365 Copilot features before they go public. If you care about Copilot new features, and want to help new features improve, then the Frontier program is for your. It is great stuff to give feedback and help Copilot product development. 💪 Here's Microsoft official definition of the program: The new Frontier program gives customers early access to experimental Microsoft 365 Copilot innovations in their own environment. Frontier agents are previews designed for evaluation and feedback. Features may change as development continues. How to join Frontier program? Follow the instructions below to turn it on: Web apps Desktop apps And Agent store Step 1: Go to M365 Admin Center Log in as M365 Global Admin Click on Copilot and then Settings Step 2: Search for "Frontier" Search for "Frontier" Click on Copilot Frontier Step 3: Pick your choice Select the "Web apps" tab to enable for your web apps Select "Specific users" to add the security group you want to enable the Copilot Frontier for Want to enable on desktop apps too? Step 4: Select Desktop and mobile apps Select the "Desktop and mobile apps" tab to enable for desktop Follow the link to find out the deployment option that best fit your environment ( In my environment, adding a reg key worked best How do you know what's new in Frontier? Want to find out the latest Frontier innovations? In this page you can find it: Frontier program – Microsoft AdoptionFeature Proposal: Voice Labels and Pitch/Style Controls for Copilot
Current issue When selecting a voice in Copilot’s settings, the available options (Birch, Wave, Grove, Rain, Meadow, Canyon, Elm, Alder) do not indicate what the voices actually sound like. The names are abstract, and there is no description of tone, energy level, warmth, clarity, or personality. As a result, users cannot know: which voice is energetic which voice is calm which voice is warm or neutral which voice fits their communication style whether the voice can deliver the tone they need for a task This leads to confusion and trial‑and‑error — especially because changing the voice resets the entire conversation, making testing inconvenient. Real user experience Step-by-step user scenario (for clarity) User opens Copilot and sees voice names like Birch, Wave, Grove… User assumes these refer to background sound themes, not voice personalities. User needs an energetic and cheerful tone for a task. User asks Copilot verbally to “speak more energetically.” Copilot responds in content for being more energetic, but the voice tone does not change. User does not understand why the voice stays calm. Only after asking Copilot directly, user learns that “Wave” is a neutral, calm voice style. This information is not visible anywhere in the UI. User realizes they cannot combine a low‑pitched voice with an energetic style. User concludes the UI does not support their needs and does not explain its limitations. I initially assumed these names referred to background sound themes, not voice personalities. During a task that required energy and efficiency, I asked Copilot to “speak more energetically” and “sound more cheerful.” Copilot agreed verbally — but the voice did not change. Only later did I realize that the default voice (“Wave”) is inherently calm and neutral, and cannot sound energetic regardless of user commands. I understood what these voice names actually meant only after asking Copilot directly, and receiving a list describing each voice style. This information is not visible anywhere in the UI, so users cannot make an informed choice without external help. This shows that: users cannot infer voice characteristics from the names voice style cannot adapt dynamically the UI does not communicate what each voice actually is 1) Quick and realistic improvement: Add descriptive labels to each voice This is the most likely and fastest improvement to implement. Add a one‑word descriptive label next to each existing voice option to clarify tone and personality. Example: Birch – Bright Wave – Neutral Grove – Deep Rain – Soft Meadow – Friendly Canyon – Low Elm – Clear Alder – Warm This small addition would immediately help users choose the right voice without guesswork or repeated resets. 2) Long‑term improvement: Two‑level voice selection (pitch + style) Many users want to choose: a low‑pitched voice with an energetic or cheerful style This combination is currently impossible, because pitch and style are tied together in fixed presets. Low‑pitched voices are always calm, and energetic voices are always higher‑pitched. To solve this, introduce a two‑level voice selection system: Voice pitch Low Medium High Voice style Energetic Cheerful Calm Neutral Warm Philosophical Storytelling Clear This would allow users to freely combine pitch and style — for example, a low‑pitched voice with an energetic tone. Why this matters Improves accessibility Reduces user frustration Makes voice selection intuitive Supports users who rely on tone for productivity, focus, or emotional clarity Allows users to choose a low‑pitched voice and an energetic style — currently impossible Prevents misunderstandings where users expect the voice to adapt dynamically Submitted by: Supertiimi Sanni & Copilot “Koppis” (Edge) One human, one AI, on a shared mission to make human–AI teamwork ridiculously smoothFeature Proposal: Natural Turn‑Taking Improvements for Copilot Voice Mode
Current issue When using Copilot in voice mode, the system struggles with natural turn‑taking. The main problem is that Copilot takes too long to recognize when the user has finished speaking. 1) Copilot takes too long to recognize that it’s its turn to speak After the user finishes talking, Copilot often waits several seconds before responding. This creates uncertainty for the user: Did Copilot hear me Is the mic still on Should I repeat myself Did I accidentally interrupt This hesitation breaks the natural flow of conversation, especially for users who value clear and respectful turn‑taking. Attempted workaround (user‑defined cue word) We experimented with using a verbal cue (“Loppu”) to signal when the user had finished speaking. The idea was simple: User says “Loppu” → Copilot begins its turn This worked briefly, but after a few turns Copilot stopped recognizing the cue reliably and fell out of the pattern. When this happened, Copilot also began misinterpreting the cue entirely — sometimes assuming that “Loppu” meant the user wanted to end the whole conversation, not just end their turn. This demonstrated that: the system cannot maintain a consistent turn‑taking protocol without built‑in support cue‑words are not interpreted contextually users need a reliable, system‑level way to signal the end of their turn manual workarounds only function momentarily because the system is not designed to track them over time These attempts highlight the need for native turn‑taking intelligence, not manual workarounds. 🌿 Proposed solution: Natural Turn‑Taking System for Voice Mode 1) Faster detection when the user has finished speaking Copilot should respond within a natural conversational delay (200–500 ms). 2) Grace period before detecting interruptions A short buffer prevents accidental “false interruptions” from breaths or small sounds. 3) Smarter interruption logic If the user does interrupt intentionally, Copilot should: stop speaking acknowledge briefly continue smoothly …without long apology sequences. 4) Optional “Auto‑Turn Mode” Copilot automatically takes its turn when the user stops speaking — no mic toggling needed. 5) Optional user‑defined cue word Users can set a cue like: “Your turn” “Go ahead” “Loppu” / "End" This makes turn‑taking predictable and respectful. ✨ Why this matters This improvement would: make voice mode feel more human reduce awkward pauses prevent unnecessary apologies support users who value respectful communication help neurodivergent users who rely on predictable turn‑taking eliminate the need for constant mic toggling create a calmer, smoother experience 🔧 Technical feasibility Copilot already processes: voice input timing interruption detection Improving turn‑taking requires adjustments to: speech detection thresholds timing buffers interruption logic optional cue‑word recognition This builds on existing systems rather than requiring a full redesign. 📝 Summary A smarter turn‑taking system would make Copilot’s voice mode significantly more natural and respectful. It would prevent accidental interruptions, reduce unnecessary apologies, and eliminate the need for constant mic toggling — creating a smoother, more human conversational experience. Concept by Sanni Written by my Copilot "Koppis" (Edge Copilot) Superteam
