What's New in Microsoft Teams | August - September 2026
A quick note before we get into it: What's New in Teams is shifting from a monthly to a quarterly rhythm. You'll hear from us next in December, March, and June, and each edition will round up everything announced and released over the full quarter. One post, one fuller view of what's new. Two investments shape where Teams is heading, and you'll see both in this quarter's releases: AI transforming teamwork with agents as part of the team, and a simpler, smarter, more secure foundation underneath it all. AI in Teams is showing up in the flow of your work. Teams Phone Agent brings that to your phone line, helping callers with common requests in more than 60 languages and routing them with context attached, so a missed call turns into a next step instead of a lost one. Context carries forward, too. Video recap turns a meeting you missed into a short, narrated highlight reel, so what a meeting decided outlasts the conversation itself. And protection for everyday collaboration is always top of mind. The new Security Detection Report brings detections such as impersonation and malicious URLs into one view in the Teams admin center, so admins see the whole picture in one place. Read on for all the latest updates! Feature categories: (All features listed are generally available unless otherwise noted) Chat and Collaboration Meetings Teams Phone Workplace Teams Events Fundamentals and Security Teams Platform Certified devices Chat and Collaboration Ask Copilot in Teams conversations Stay in the flow of work and get help from Copilot directly within your conversations. Open Copilot from a message or selected text in a Teams conversation, with the relevant context already included, making it easier to gain insights, explore questions, and move work forward without needing to re-explain information. Find agents and apps faster through Teams search Discover the tools you need with agents and apps surfaced directly in Teams search results. As you type in the search bar, matching agents and apps appear alongside other relevant results, helping you spend less time searching and more time getting things done. Find and share files faster in Teams Locate the files you need while sharing content in Teams. Search for cloud-based files directly from the attachment experience, making it easier to find and share the right content without interrupting the flow of collaboration. Emoji shortcuts on iOS and Android Express yourself with emoji shortcuts. Desktop emoji shortcuts now work on iOS and Android. Insert emojis directly in the compose box by typing a word between colons, so :smile: becomes đ. Autocomplete suggestions help speed up entry, and custom emojis are also supported. Clearer text highlighting in dark mode and high contrast mode Make highlighted text easier to read while composing messages in Teams. Improvements to text highlighting in dark mode and high contrast mode provide a more consistent and accessible editing experience, helping content stand out more clearly. Meetings Video recap in Teams Meeting recap now delivers a bite-sized video recap of with key highlights from your Teams meeting. It combines AI-generated voiceover summaries with video snippets, spotlighting the most important moments while preserving the original tone and flow, so you can catch up on key topics in a few minutes. Video recaps now support meetings in 23 languages across 31 regional variants, learn more. Translation button to change the language for intelligent meeting recaps After an intelligent meeting recap is generated, you can change the recap language at any time using a translation button, even if a different language was selected during the meeting. Multilingual teams get more flexibility to read meeting insights, action items, and discussion summaries in the language that is most comfortable for them. Teams Phone Teams Phone Agent Teams Phone Agent is an AI-powered receptionist for your businessâs phone line, so callers can get help with common requests even after hours. For customer-facing organizations and departments using Teams Phone, such as bank branches or IT help desks, it takes repetitive calls off employees' plates so they can focus on the conversations that truly need a human touch. With support for over 60 languages and locales, Teams Phone Agent handles common requests such as answering routine questions or booking appointments. , And it can route a caller to the right department or employee with an AI-generated summary of the conversation, so customers do not have to navigate phone menus or repeat themselves. Custom voice agents are available for specialized workflows. Teams Phone Agent is now generally available, learn more. If the player doesnât load, open the video in a new window: Open video Intelligent call recap in Queues app Intelligent call recaps in Queues app help you catch up on recorded or transcribed queue calls with AI-generated summary notes covering key discussion points and follow-up actions. To open a recap, find the call record in the Queues app call history and select Recap. Copilot in Queues appâs shared call history for post-call insights Quickly catch up on a call queue call and uncover key details with the ability to use Copilot in the shared call history in Queues app. After a recorded call is completed, users with Copilot can now open the call record in the shared call history, access the Copilot Chat sidecar from the Recap tab, and ask questions about the call. Automatic recording and transcription for call queues Capture customer interactions without requiring your organizationâs calling representatives to manually start recording. Admins can enable automatic recording and transcription for individual Teams call queues and control access to recordings. Recordings are stored in SharePoint and accessible through call recaps in the shared call history in Queues app. View and manage auto attendant shared voicemails in Queues app Help your team stay on top of customer messages by managing auto attendant shared voicemails directly in Queues app. Calls routed from an auto attendant to voicemail will appear in Queues app, giving collaborative calling teams a centralized place to track, triage, and respond to messages. Customize recording and transcription notifications for Teams calls Give your organization greater control over how recording and transcription are communicated during Teams calls. IT admins can customize select user notification strings for recording and transcription in the Teams admin center, helping tailor the experience for participants in Teams VoIP calls. Enhance control of delegated calls with call lock and delegate join alerts Call delegation in Teams gains real controls: a delegator can lock an active call and see when a delegate joins. Locking prevents delegates from joining or resuming the call, and optional warning tones notify participants when a delegate joins or resumes. Workplace Interpreter agent support in Teams Rooms on Android The Interpreter agent acts as a translator in Microsoft Teams meetings, letting participants listen in their chosen language with real-time translation. It is now available in Teams Rooms on Android licensed for Teams Rooms Pro. Zero-touch provisioning on Teams MDEP-based Android devices IT teams can deploy MDEP-based Android devices at scale with automated, hands-off provisioning, cutting manual setup and applying security policies from first boot, similar to Autopilot for Windows. Deployment is managed from the Teams Rooms Pro Management portal. New room optimization mode in Teams desktop Room optimization mode makes it easier to use your laptop for meetings and collaboration in spaces such as focus or huddle rooms that do not yet have a Teams Rooms system. It replaces shared display mode, has a new location, and enables or disables room-specific features. When room peripherals are connected, Teams can automatically select audio and video devices, enable speaker recognition and shared display, and disable voice isolation. Meeting room join time comparison analytics in the Pro Management portal Admins can now compare meeting join times between Teams Rooms and bring-your-own-device rooms. These analytics help monitor the experience and plan workspaces, and the portal uses the comparison metrics to recommend actions proactively. Available with Teams Rooms Pro and Teams Shared Space licenses. Enhanced bookable desk experience with Teams panel-based desk hub devices The Teams panel app now enables devices to enhance bookable desk experiences, indicating at-a-glance availability and letting visitors book directly on the device, so people have better experiences in flexible work environments. Each device requires a Teams Shared Space license. Modernized Gallery view in Teams Rooms on Android The updated Gallery view in Teams Rooms on Android prioritizes video on the meeting stage, arranges participants in consistent aspect ratios, and minimizes movement of participant tiles on stage. You can hide the room self-preview video and choose to see audio and video participants equally on stage instead of prioritizing video participants. Admins can set the default behavior using local device settings and the Pro Management portal. Teams Events Breakout rooms in Teams Meetings & Events Breakout rooms are now supported in Teams Meetings & Teams Events with up to 1,000 participants across 100 rooms, increased from the previous limit of 300 participants across 50 rooms. Organizers can use breakout rooms to create smaller focused sessions within an event for more interaction and collaboration. Specify who has control of production tools in Teams Events Organizers can designate who controls production tools, granting chosen people access to Manage what attendees see and the green room so event production stays with the right crew. The setting is a new meeting option applied when the event is set up. Expanding presenter visibility in âManage what attendees seeâ Producers can resize and expand the presenter panel in Manage what attendees see, making it easier to view, manage, and switch between presenters while a live event is running. New layout when sharing content for Teams events Organizers and presenters who have access to production tools now see updated layout options when sharing content in the âManage what attendees seeâ experience for Teams events. The available layouts are speaker focused, content focused, and content only. The new speaker focused layout prioritizes presenter video alongside shared content for greater visibility. Available for Teams events organizers on Teams for Windows desktop and Mac desktop. Fundamentals and Security Enhanced real-time alerting rule management in Teams admin center Administrators can now duplicate an existing alerting rule to create a similar configuration without rebuilding it, bulk upload users when creating or editing a rule, and delete rules directly from the management experience. These capabilities are available for in-progress meetings and calls rule types, and organizations can configure monitoring for up to 500 users across their real-time alerting rules. Security Detection Report in Teams admin center A new Security Detection Report in the Teams admin center gives admins a unified view of messaging security detections across signals such as impersonation, malicious URLs, and weaponizable file types. Admins can review detection activity in one place and export detailed data for further investigation, improving visibility into threats in Teams. Single pane for monitoring and troubleshooting meetings and calls (Windows) Administrators can monitor meeting and call health across the organization from one place, identifying recurring issues, uncovering trends, and proactively troubleshooting problems affecting people in both live and past meetings and calls. Meeting participant detail audit records in all participating tenants Admins can now access participant-level audit records for their own users in cross-tenant meetings, helping investigate incidents even when another organization hosted the meeting. Teams audit logging now shares meeting participant detail records with all participating tenants, not just the organizer tenant, and each record includes organizer information so admins can tell whether a meeting was organized inside or outside their tenant. Teams optimization for VDI now supports Teams Events (Windows) Attendees joining Teams Events from virtualized Windows desktops can offload audio and video to their local device, supporting high definition playback while easing load on the virtual desktop. Optimization works on Windows endpoints connecting to Azure Virtual Desktop, Windows 365, Citrix, Omnissa, or Amazon. Captions, DVR, reactions, streaming chat, and Q&A are all supported, as are first-party and third-party eCDNs. Teams Platform Unified agent and app installation management across Microsoft 365 and Teams admin center (Windows) Administrators using the Microsoft 365 admin center and Teams admin center can apply app and agent installation changes once and have them enforced consistently across Teams, Outlook, and Microsoft 365 Copilot. Previously, installation changes made in the Microsoft 365 admin center applied only to Outlook and Microsoft 365, and changes made in the Teams admin center applied only to Teams. Identify custom Teams apps that need updates for private and shared channels Admins can view a list in Teams admin center of custom apps in their tenant that need updates to work in private and shared channels. The list helps admins identify impacted apps, understand which ones require developer action, and coordinate updates so people can keep using custom apps across all supported channel types. Prominent search for app and agent discovery in the Store Search now sits in the middle of the Store page, with improved type-ahead suggestions, a more informative results page, and natural language processing to surface the most relevant apps and agents. Add multiple steps when building a workflow from scratch When building a workflow from scratch, you can add several steps at once, so you can assemble multi-step automation without returning to edit it step by step, reducing repetitive setup work and simplifying the creation of more advanced automations. Collect information with List Form in Workflows A workflow can open with a form that gathers the details it needs up front, so automation runs on structured input rather than chasing information midway. Single-character keyboard shortcuts for focused message actions (Windows) Single-character shortcuts let you quickly take common messaging actions such as edit, delete, reply, forward, pin, save, mark unread, quote reply, and react when a message has keyboard focus. The shortcuts are a predefined messaging set, and they are discoverable and customizable in the keyboard shortcuts dialog. Certified devices EPOS IMPACT 1000 MS UC ANC WL USB-C+A On-ear BluetoothÂŽ headset. Supplied with a BTD 900c dongle, a USBâC to USBâA adapter, and a USBâC charging cable. Features ANC, EPOS BrainAdapt⢠technologies, and EPOS AIâ˘âpowered voice pickup and noise cancellation, ensuring your voice sounds natural and clear in any environment. EPOS IMPACT 1000 MS UC ANC WL USB-C+A Stand On-ear BluetoothÂŽ headset. Supplied with a table stand for wireless charging, a BTD 900c dongle, a USBâC to USBâA adapter, and a USBâC charging cable. Features ANC, EPOS BrainAdapt⢠technologies, and EPOS AIâ˘âpowered voice pickup and noise cancellation, ensuring your voice sounds natural and clear in any environment. EPOS IMPACT 1000 MS UC Mono WL / ANC WL Dongle-free BluetoothÂŽ headsets available in monaural and binaural on-ear configurations. Supplied with a USB-C charging cable and a USB-C to USB-A adapter. Features EPOS BrainAdapt⢠technologies and EPOS AIâ˘-powered voice pickup and noise cancellation for clear, natural-sounding communication in any environment. The binaural ANC WL model also includes Active Noise Cancellation (ANC) to help reduce background distractions. EPOS IMPACT 1000 MS UC ANC WL Stand On-ear, dongle-free BluetoothÂŽ headset. Supplied with a table stand for wireless charging, a USBâC charging cable, and a USBâC to USBâA adapter. Features ANC, EPOS BrainAdapt⢠technologies, and EPOS AIâ˘âpowered voice pickup and noise cancellation, ensuring your voice sounds natural and clear in any environment. Q-SYS RoomSuite Collaboration Bar + Controller The Q-SYS RoomSuite Collaboration Bar and expansion devices provide a scalable AV solution for standard small-to-large meeting spaces. This Windows-based solution features built-in audio, video, and supports Microsoft Teams Rooms and bring-your-own-meeting conferencing. Includes a touch panel for control and allows for optional table microphones for extended audio coverage. Q-SYS RoomSuite Collaboration Bar + Controller + Expansion Mic The Q-SYS RoomSuite Collaboration Bar and expansion devices provide a scalable AV solution for standard small-to-large meeting spaces. This Windows-based solution features built-in audio, video, and supports Microsoft Teams Rooms and bring-your-own-meeting conferencing. Includes a touch panel for control and allows for optional table microphones for extended audio coverage. The Q-SYS RoomSuite Collaboration Bar can support up to 4 expansion mics. Shure IntelliMix Room Kit 30 | 50 | 70 | 80 Microsoft Teams Rooms-certified solutions for small, medium, and large meeting spaces. Shure IntelliMix Room Kits include a Windows-based Teams Rooms compute with Shureâs premium audio signal processing, an intuitive touch panel, an all-in-one ceiling array microphone and loudspeaker, and intelligent high-resolution video. Designed for streamlined deployment with zero-touch or low-touch setup, the kits provide high-quality audio and video experiences across a range of room sizes. Simply connect devices, power on, and sign in to get started. Shure IntelliMix⢠Bar Pro Kit (Black) Clearly capture precise audio and video for AI-powered meetings in medium to large collaboration spaces with this powerful all-in-one Android based video conference bar. Enterprise ready with auto-setup and simple global management, IT managers can create meeting experiences focused on participants with reliable transcription for enhanced AI tools. Yealink MP66W Powered by the Microsoft Device Ecosystem Platform (MDEP) and Android 15, the Yealink MP66W offers accelerated performance and enterprise-level security. With an IP67 rating for water and dust resistance, 1.8-meter drop protection, and an antibacterial, chemical-cleaning-resistant housing, the MP66W is built for mobile workers in healthcare, manufacturing, retail, and warehouse environments. Armed with Yealink's Optima HD Audio and AI Noise Cancellation Technology, MP66W delivers distraction-free, natural-sounding calls even in loud environments. Moreover, MP66W keeps mobile teams connected thanks to its support for Wi-Fi 6E, Bluetooth 5.3, and up to 8 hours of talk time on a single charge. Neat Pad Generation 2 Neat Pad Generation 2 keeps Microsoft Teams meetings moving. As a meeting room controller or scheduling display, it gives teams instant, familiar control and IT a simple, scalable way to standardize rooms across every space. A built-in microphone extends audio pickup in the room, helping conversations sound clearer without extra hardware. Built-in sensors monitor temperature, humidity, and air quality for a healthier workspace. Mount it on a wall, table, or mullion and power it with a single PoE cable â plug in and go. Manage every device remotely with Neat Pulse, and count on Neat's next-generation P2 platform for lasting performance as your needs evolve. Compact, reliable, and easy to deploy, it delivers a consistent experience so every room just works. Barco ClickShare Hub Pro, HuddlyÂŽ L1⢠and Shure for Teams Rooms on Android This ClickShare Hub Pro, HuddlyÂŽ L1⢠and Shure bundle is a certified Microsoft Teams Rooms solution for medium meeting rooms. ClickShare Hub Pro enables one-click, wireless conferencing and 4K content sharing, with two next-gen ClickShare Buttons (featuring Wi-Fi 6E and USB-C DisplayPortâ˘) and dual screen support. Built on the Microsoft Device Ecosystem Platform (MDEP), itâs designed for a secure meeting experience. HuddlyÂŽ L1⢠delivers engaging video collaboration with an on-device AI director, exceptional image quality, and software-defined longevity. The Shure MXA902 ceiling array microphone and loudspeaker with the ANIUSB-MATRIX USB audio network interface provide top-quality audio. Shure MXA925 Ceiling Array Microphone + MXP-6 Pendant Passive Loudspeaker + MXN-AMP PoE + IntelliMix P300 This Microsoft Teamsâcertified bundle combines the MXA925 ceiling array microphone, IntelliMixÂŽ P300 DSP, MXNâAMP PoE+ multichannel amplifier, and MXPâ6 pendant loudspeakers to deliver a fully validated, endâtoâend room audio solution for medium to large spaces. Designed to meet Microsoftâs performance and reliability requirements, it provides automatic, precise speech capture, enterpriseâgrade echo cancellation, and evenly distributed sound reinforcement while simplifying deployment through networked audio, PoE+ power, and a singleâvendor ecosystem. Shure MXA925 Ceiling Array Microphone + MXP-5 Ceiling-Mount Passive Loudspeaker + MXN-AMP PoE + IntelliMix P300 This Microsoft Teamsâcertified bundle delivers a complete, scalable room audio solution by combining the MXA925 ceiling array microphone with IntelliMix P300 DSP, the MXNâAMP PoE+ multichannel amplifier, and MXPâ5 ceiling speakers for clear speech capture and consistent sound coverage in medium to large meeting spaces. The MXA925 uses Automatic Coverage⢠and advanced IntelliMix DSP to capture natural, intelligible speech without complex setup, while the P300 provides powerful echo cancellation, noise reduction, and USB connectivity to Teams Rooms systems. The MXNâAMP and MXPâ5 speakers simplify installation with networked audio and PoE+ power, delivering balanced, roomâfilling audio for both inâroom and remote participants. Shure MXA320 Table Array Microphone+MXN5-C Networked Loudspeaker + Intellimix P300 Audio Conferencing Processor The Shure MXA320 Table Array Microphone, MXN5âC Networked Loudspeaker System, and IntelliMix P300 Conferencing Processor form a fully certified Microsoft Teams Rooms audio bundle designed for Medium meeting spaces. This integrated solution delivers clear, consistent, and intelligible audio through advanced DSP, Steerable Coverage⢠technology, and optimized networked loudspeaker performance. The MXA320 captures voices with precision while minimizing ambient noise, the P300 enhances audio quality with powerful IntelliMixÂŽ processing, and the MXN5âC ensures natural, roomâfilling sound playback. Together, they provide a seamless, scalable, and easyâtoâdeploy conferencing experience that meets Microsoftâs stringent certification requirements for performance, reliability, and user experience. Shure MXA902 Ceiling Microphone & Loudspeaker + ANIUSB-MATRIX Audio Conferencing Ki High-quality, reliable meeting room audio is now easier than ever. Certified for Microsoft Teams, the Shure MXA902 Integrated Ceiling Array Microphone + Loudspeaker, paired with the ANIUSB-MATRIX Audio Network Interface, delivers a complete, easy to install, ready to use audio solution. Designed for small and medium sized spaces, it provides premium sound, full room coverage, and seamless connectivity. Shure MXW neXt 4&8 Wireless Microphone Systems with boundary microphone configuration + MXN5W-C Networked Loudspeaker This Microsoft Teams-certified solution combines MXW neXt wireless microphones, IntelliMixÂŽ DSP, and the MXN5W-C networked ceiling loudspeaker to deliver consistent speech capture and clear room audio for hybrid learning and collaboration spaces. With flexible wireless deployment, integrated signal processing, and cloud-based management, the solution simplifies installation while providing reliable audio performance for both in-room and remote participants. Shure MXW neXt 2 Wireless Microphone System with Boundary Microphone Configuration and MXN5W-C This Microsoft Teams certified bundle combines the MXW neXt 2 wireless microphone system with boundary microphones and the MXN5W-C networked ceiling loudspeaker to deliver clear speech capture and consistent room audio for classrooms and collaboration spaces. Easy to deploy and cloud enabled for remote management, the solution simplifies installation while providing reliable wireless performance for both in-room and remote participants. Barco ClickShare Hub Pro and Huddly ÂŽC1⢠Crew for Teams Rooms on Android The ClickShare Hub Pro, Huddly C1 Crew bundle is a certified Microsoft Teams Rooms solution for small-to-medium meeting rooms. ClickShare Hub Pro enables one-click, wireless conferencing and 4K content sharing, with two next-gen ClickShare Buttons (featuring Wi-Fi 6E and USB-C DisplayPortâ˘) and dual screen support. Built on the Microsoft Device Ecosystem Platform (MDEP), itâs designed for a secure meeting experience. Huddly C1 Crew adds AI-driven multi-camera video with integrated audio. Its on-device AI director frames people naturally for inclusive meetings, with clear image and sound throughout the room. For meeting participants, this bundle ensures intuitive, engaging meetings. For IT managers, it provides modular flexibility, enterprise-grade security, compliance, and standardized integration. Logitech Zone Vibe Pro for Business Zone Vibe Pro for Business is certified for Microsoft Teams and offers the over-ear design that people love â purpose-built for open offices and wide deployment. Our AI-powered voice isolation uses machine learning to capture your voice clearly. Adaptive hybrid ANC minimizes distractions, while custom 40 mm drivers deliver vivid, true-to-life audio.
"View all communities" button does not show all communities
If you're in Viva Engage, and you go to "Communities," and you click "View all communities" to see all the communities, it doesn't show you all of the communities - it shows you the recommended communities. If you want to see all of them all at once, you have to click the arrow next to "Recommended" and select "Alphabetical" or "Community size." Is there any way to make the default view "Alphabetical"? Most users will a) expect a view all communities option to show all communities, b) not think to use a drop-down filter and choose 'alphabetical' or 'size' as options to show 'missing' communities. This is a direct consequence of the behaviour of the button not matching the button labelling and as a result this is impacting the visibility and discovery of communities in our network.
News to Know â Volume 3, Edition 10, September 2026
September brings practical updates that help you support survey participants, simplify administration, and keep up with changes across Viva Glint. This edition covers new Copilot experiences and survey improvements available this month, along with an early look at reporting and administration capabilities planned for upcoming releases. New on your Viva Glint platform This section highlights new capabilities now available on your Viva Glint platform this month. Handling data for deleted users. Starting October 1, 2026, we restarted the live processing of user delete signals received via Microsoft Entra as well as the processing of the delete signals that were generated since the beginning of the related planned maintenance window in June 2025. Users who were deleted from Microsoft Entra since June 2025 will be processed in Viva Glint and their data will be retained or deleted based on the user data configurations for your Viva Glint instance. Admins can now choose to retain a user's email address and employee ID after that user is removed from Glint, preserving historical reporting accuracy. Delete user data from Viva Glint | Microsoft Learn Copilot in Viva Glint: Admin Assistant. The first phase of the Viva Glint Admin Assistant is now generally available for commercial customers. Grounded in Microsoft Learn content and best practices, it provides contextual, step-by-step guidance for configuration tasks so you can complete common setup work without switching between the product and documentation. Coaching and action-taking capabilities are planned for future phases, and availability for government cloud environments is planned for future release. Survey administration: Multiple-choice list questions. You can now upload option lists from a CSV file when creating multiple-choice questions, with support for multilingual lists and up to 500 options. Survey participants can search and filter longer lists before selecting one or more responses, making complex questions easier to configure and complete. For more information see Multi-choice list questions. Product updates: In-product announcement access. Service administrators can now use a new announcement icon in the Viva Glint header to reach existing product updates, newsletters, and community posts. This gives you a more direct way to find information about recently released capabilities without first locating the relevant update channel. Stay updated with the Viva Glint newsletter | Microsoft Learn. Copilot in Viva Glint: Support for survey comments. Rolling out at the end of September for survey types other than 360s, authenticated survey participants can use Copilot to rewrite all or part of an open-text response when the experience is enabled by their organization. It can help people refine their wording and reduce recognizable writing patterns, supporting more confident and candid feedback while preserving the participant's intended meaning. Access to the feature is controlled by the new âCopilot in Viva Glint Survey Takingâ VFAM control which is defaulted to an âOFFâ state. Rewrite Comments with Copilot in Viva Glint | Microsoft Learn. Survey experience: Clearer navigation and automatic comment saving. Survey comments now save automatically as participants type, reducing the risk of lost feedback if a session is interrupted. A single Next button replaces separate Skip and Done actions, and updated scrolling keeps participants at the question they are editing instead of moving them unexpectedly to the end of the survey. These changes apply automatically, including surveys already in progress, and require no configuration or admin action. Improvements for Glint integration with Microsoft 365 Organizational Data Service: Clearer oversight of imports and configuration changes (Public Preview). You can now trace organizational-data imports with a consistent ingestion ID across activity logs, downloaded advisory and summary files, email notifications, and the validation experience. Audit events for imports data management enhanced to provide greater visibility into integration configuration changes, including downloadable details where available. Coming soon to Viva Glint The following section offers an early look at capabilities coming to Glint in upcoming releases. Continuous Engagement administration | Private preview in October. Private preview customers will be able to map survey questions to eligible workplace metrics directly in a simplified administration flow. A guided setup experience and summary page will reduce manual coordination and give administrators more control over which contextual metrics managers can review alongside survey results. Multi-attribute report exports | Private preview in October. We are extending Viva Glint's multi-attribute export beyond admins to managers, leaders, analysts, and HRBPs, so they can export filtered, grouped, cross-dimensional data (e.g., department + location + tenure) outside the app for flexible, personalized analysis. This will be available for Private Preview in October. Express interest to join preview here: Viva Glint Multi-Attribute Export â Private Preview Sign-Up form Program setup: Required-field indicators | Generally available in October. Visual indicators will identify required fields throughout program setup, with clearer treatment when a required value is missing. The update will help you understand what each step requires before moving forward, without changing which fields are required or optional. Glint integration with Microsoft 365 Organizational Data Service | Generally available in October. This capability will be available for all customers including GCC-M and customers with multiple instances of Viva Glint. GA release will enhance the capability with upload email notification management and enhanced user experience. Sign Up for Survey Owners Can View Survey Results by 2nd Oct | Private Preview. Survey Owners will automatically get access to the results of the surveys they own, without gaining broader access to other surveys in the tenant. Today, this access is largely role-based, often requiring survey creators to get special roles or admin help just to view their own results. With this feature, ownership moves to the survey level: owners can be assigned individually or by group, and access is scoped only to the surveys they own, with no extra administrative privileges. Private Preview is open now to participate use the link here. Action taking analysis report | Private Preview. A long-requested capability for listening program leaders will provide a report showing which leaders and managers have accessed their survey results and whether they've gone on to take action, such as holding team conversations. Instead of guessing whether results are landing, program owners will be able to see engagement directly and target support where follow-through is lagging. Private Preview is open now to a limited group of customers, with the opportunity to give feedback ahead of Public Preview. Express your interest here. See our public roadmap for more feature updates. Events and learning opportunities Recent EECC Customer Engagement Sessions: September 24th â Viva Glint Multi-Attribute and Comments Report Exports: Current Capabilities and Improvements on the Roadmap Target Audience: Viva Glint admins, HRBPs, analysts, managers, and leaders We invited EECC customers to discuss how Viva Glint's Multi-Attribute Report and Comments Report exports work today, along with a preview of where we're taking both. The session drew 45 live attendees representing 24 customer organizations, spanning healthcare, financial services, manufacturing, retail and logistics, and professional services. The conversation opened with a candid look at how customers use exports today, then moved into a live demo of upcoming Multi-Attribute Report changes and a design-stage preview of Comments export enhancements. Customers weighed in throughout on confidentiality safeguards, missing data dimensions, and gaps in in-app reporting. Key takeaways: Today's Multi-Attribute Report Export is admin-only and limited to three attributes and 12,000 value combinations. Several customers said the current output is difficult to read and interpret, leading many to rely on raw data exports and custom scripts instead. The planned update will open export access to non-admin roles under admin-controlled permissions, remove the three-attribute cap, raise the row ceiling to roughly one million, and add question-level filtering. A private preview is targeted for mid to late October. Customers were especially eager for in-app heat map and cross-tab views, such as comparing engagement scores by location and gender, rather than exporting and manually recombining data. Presenters flagged this as valuable input for future roadmap consideration. For Comments export, customers requested additional attribution dimensions, including worker type and region, while preserving group-level confidentiality suppression. Feedback was mixed on how broadly to open attribute-level access, with some customers preferring it remain limited to HR and analyst roles rather than extending to all managers. Connect with us⯠Stay engaged with the Viva Glint & Pulse community through the Employee Experience Customer Connection (EECC) program.⯠TheâŻEmployee Experience Customer Connection (EECC)âŻprogramâŻoffers our customers an opportunity to be part of a feedbackâŻcommunity as employee experiences continue to evolve withâŻVivaâŻandâŻMicrosoft 365 Copilot.⯠What the program provides:⯠Product team engagement for Employee Experiences powered by Viva and M365Copilot⯠Forums for you to influence product direction & unlock value for your organization⯠Early insight into product roadmap⯠Private preview engagement opportunities⯠Connection with other enterprise customers⯠If⯠youâreâŻinterested in joining, please fill outâŻthis formâŻso we can guide you through the enrollment process and help you get started.⯠We look forward to partnering with you to build better products together.âŻBring Your Azure DevOps Repos to Azure SRE Agent Plugins
Plugins package the skills, agents, and connector settings your team wants every SRE Agent to have. A plugin marketplace is a Git repository that lists those plugins so any agent can install them. Until now, that repository had to be on GitHub. If your team keeps its runbooks and tooling in Azure DevOps, you had to mirror them somewhere else. Now you can point your agent at the Azure DevOps repository directly. Your team keeps authoring plugins in the repository it already uses. The agent reads from that repository and installs the plugins you choose, and a pinned version stays put until you change it. Connect a marketplace Azure DevOps marketplaces are rolling out now. You can use them today by turning on the preview feature. Open the Plugins page on your agent and select Connect marketplace . Paste the repository URL, for example https://dev.azure.com/<organization>/<project>/_git/<repository> . Sign in to Azure DevOps if the agent is not connected to that organization yet. Choose your account, a managed identity, or a personal access token. The marketplace is added as soon as the credential is saved. If the organization is already connected under Code access, the dialog uses that connection and skips the sign-in. When the repository finishes cloning, its plugins appear on the Plugins page. Select a plugin to review its skills and install it. The docs below cover each step, including managed identity setup. Use a personal access token or managed identity limited to the repositories you need rather than your own account. Try it Put one procedure your on-call team repeats into a plugin, push it to an Azure DevOps repository, and connect that repository to a test agent. If the skill runs as expected, connect the same marketplace to your other agents. Create or open your Azure SRE Agent to get started. Product documentation: Plugin marketplace overview Add a private marketplace, which now covers Azure DevOps Install a plugin from a marketplace Create a skill if you are not using a marketplace. You can build a custom skill directly in the agent, with no repository involved.Comparing Three Approaches to AI Agent Evaluation and Observability
Why evaluation and observability belong together Agent evaluation and observability answer two related questions: Is the agent producing the right result? What happened from the initial request through every model and tool call? Evaluation measures quality with repeatable scores (is our system working), such as task completion, tool-call accuracy, groundedness, or safety. Observability captures the end-to-end execution flow, including prompts, model responses, tool calls, latency, token usage, and errors. You need both. A score can tell you that an agent failed, while a trace helps you understand why. Microsoft provides several ways to host and monitor agents. You can use a Microsoft Foundry hosted agent with integrated tracing and evaluation, or run the agent independently on a service such as Azure Container Apps and connect it to Azure Monitor. Open-source platforms such as Langfuse provide another option and can be self-hosted in Azure. We built three proofs of concept (POCs) to compare these approaches: Self-hosted Langfuse A Microsoft Foundry hosted agent A standalone agent on Azure Container Apps The best choice depends on more than features. Authentication, networking, security boundaries, operational ownership, and the existing Azure architecture all affect the decision. Note These findings come from one controlled comparison, not a general performance benchmark. We used the same agent image, model deployment, prompt, tools, and synthetic test data in all three POCs. The common test The test agent summarized a synthetic portfolio. It had to call three deterministic tools in a fixed order: Load the dataset Validate its schema Compute the summary The expected answer was known in advance, which allowed us to evaluate both the final result and the tool trajectory. We also created a deterministic tool-call-accuracy score so we could compare how each platform stored and displayed the same custom metric. POC 1: Self-hosted Langfuse For the Langfuse POC, one private Azure virtual machine ran the agent and the Langfuse stack with Docker Compose. The deployment included Langfuse web and worker services, PostgreSQL, ClickHouse, Redis, MinIO, and an OpenTelemetry Collector. Azure Bastion provided private administrative access, and a managed identity retrieved secrets from Azure Key Vault. The main advantage was the integrated experience. Traces, scores, datasets, experiments, annotations, latency, token usage, and cost appeared in one application. We could move from the original prompt to each tool call, the final response, and the evaluation score without building a separate dashboard. That capability comes with operational responsibility. A production self-hosted deployment requires patching, scaling, backup, recovery, data retention, access control, and monitoring for the Langfuse services and their data stores. Choose this approach when a unified, open-source AI engineering platform and deployment control are higher priorities than minimizing platform operations. POC 2: Microsoft Foundry hosted agent For the Foundry POC, Microsoft Foundry hosted the agent from a pinned container image. Application Insights and Log Analytics stored the telemetry. We used Foundry's Traces experience for agent trajectories and added an Azure Workbook for custom evaluation metrics. Foundry provided the strongest Azure-native developer experience. Its trace view displayed model and tool activity as an agent trajectory, and its evaluation capabilities included built-in and custom evaluators. The underlying traces still flowed to Application Insights, where they could be queried and used in Azure Monitor visualizations. The tradeoff is architectural alignment. The application must fit the customer's Foundry account, identity, networking, and deployment model. Custom business metrics can also require additional emission and visualization work beyond the native evaluation experience. Choose this approach when managed agent hosting, Foundry-native tracing, and Azure-native evaluation are the priorities. POC 3: Standalone agent on Azure Container Apps For the third POC, we removed Foundry from the hosting path. The same image ran as an Azure Container App and used a managed identity to pull from Azure Container Registry and call Azure OpenAI. OpenTelemetry sent agent activity to Application Insights and Log Analytics. This POC demonstrated that the Azure Monitor foundation is not limited to Foundry-hosted agents. Application Insights still provided an end-to-end transaction waterfall showing model calls, tool executions, latency, and errors, along with agent-level monitoring views. The difference was the amount of assembly required. The team owns application instrumentation, the evaluation runner, custom metric emission, dashboards, and CI integration. The result offers more control over hosting, authentication, ingress, and network placement, but it requires more engineering than the Foundry-native experience. Choose this approach when the agent must fit an existing container platform or custom security architecture and the team is prepared to build the evaluation workflow around it. Side-by-side comparison Decision area Langfuse Foundry hosted agent Azure Container Apps Agent hosting Customer-operated in this POC Microsoft-managed hosted agent Customer-managed container app Primary trace experience Native Langfuse tracing Foundry Traces plus Application Insights Application Insights Evaluation Native scores, evaluators, datasets, and experiments Foundry built-in and custom evaluators Custom runner or separate evaluation service Custom metrics Native scores and dashboards Emit to Azure Monitor and visualize as needed Emit to Azure Monitor and visualize as needed Infrastructure ownership Highest Lowest for agent hosting Moderate Architecture flexibility High, but the platform must be operated Aligned to Foundry architecture Highest for the application hosting layer Best fit Integrated open-source AI engineering platform Managed Azure-native agent experience Existing container and security architecture What we learned All three approaches can support meaningful evaluation and observability. The real difference is where the capabilities live and how much the customer must assemble and operate. Langfuse provided the most integrated tracing and evaluation experience in this comparison, but we owned the platform infrastructure. Foundry reduced hosting operations and provided a purpose-built agent trace and evaluation experience. Azure Container Apps provided the greatest hosting flexibility while preserving Azure Monitor observability, but required us to supply the evaluation and custom visualization layers. Because all three POCs used the same model, prompt, and tool sequence, the LLM token cost for an equivalent run was effectively the same. Platform and infrastructure costs were not equivalent and require a separate estimate based on scale, retention, networking, support, and operational requirements. The decision should start with the customer's constraints: Does the agent fit the Foundry hosting and identity model? Does the organization want to operate an open-source observability platform? Does the agent need to run inside an existing container and network architecture? Which evaluation capabilities must be available before deployment and in production? Who will own instrumentation, dashboards, storage, upgrades, and incident response? There is no single correct platform for every agent. The right choice is the one that provides the required evidence about quality and behavior while fitting the customer's security, architecture, and operating model. Learn more Set up tracing for agents in Microsoft Foundry Monitor AI agents with Application Insights Review Microsoft Foundry agent evaluators Collect OpenTelemetry data in Azure Container Apps Explore Langfuse observability Explore Langfuse evaluation Deploy Langfuse on AzureSending Email from an AKS Pod Without a Single Secret
The problem You have a workload running in AKS that occasionally needs to send an email â a notification, an alert, a report. The obvious options all come with baggage: An SMTP relay means yet another credential to store, rotate, and eventually leak. A shared "app password" mailbox account means an identity nobody really owns, that can authenticate as itself forever. Granting Mail.Send as a Microsoft Graph application permission is tempting â until you realize it lets your app send email as any mailbox in the entire tenant, not just the one you intended. This post walks through a pattern that avoids all three: Azure Workload Identity for the pod, Microsoft Graph for sending, and Exchange Online RBAC for Applications to scope the identity down to exactly one authorized mailbox. No secrets stored anywhere in the cluster, and no tenant-wide send permission. Architecture Pod (AKS) -- federated OIDC token --> Workload Identity Workload Identity -- client_credentials + client_assertion--> Microsoft Entra ID Entra ID -- access token (aud=Graph) --> Pod Pod -- POST /v1.0/users/{sender}/sendMail (Bearer token)--> Microsoft Graph --> Exchange Online The pod never handles a password or a client secret. It reads a federated identity token that Azure Workload Identity's webhook mounts automatically, exchanges it with Entra ID for a Graph access token, and calls sendMail directly. The only thing that determines which mailbox it's allowed to send as is a role assignment on the Exchange Online side â not anything configured in Kubernetes. Step 1 â Get a Workload Identity bound to your namespace This is a platform-team request, not something you self-service from inside the cluster: you need a Managed Identity (or App Registration) with a Federated Identity Credential issued for your specific Kubernetes namespace and ServiceAccount subject. Give your platform/identity team: The target namespace (e.g. my-namespace) The target ServiceAccount name (e.g. my-mail-service-account) The intended use case (application email via Microsoft Graph) They hand you back a Client ID â that's all your manifest needs. One important thing to not ask for: don't request the Graph Mail.Send application permission on this identity. That permission, if granted directly in Entra ID, is unscoped â it lets the identity send as anyone. The actual sending restriction is going to live in Exchange, not in Entra ID (see Step 2). Step 2 â Restrict sending to one mailbox with Exchange Online RBAC for Applications Microsoft's currently recommended way to scope application email-sending rights is RBAC for Applications in Exchange Online â the modern replacement for the deprecated Application Access Policies. The short version: The Managed Identity gets no unscoped Graph Mail.Send grant in Entra ID. (Entra ID and Exchange RBAC authorizations are additive â if you leave an unscoped grant in place, it defeats the whole point.) Exchange Online registers a pointer to the Managed Identity's service principal (New-ServicePrincipal), then assigns it the Application Mail.Send role, scoped to a Management Scope that resolves to exactly one mailbox (or one security group of mailboxes). The identity can now call /users/{authorized-mailbox}/sendMail and get a 202. Any other mailbox returns 403. This part is usually owned by whoever administers your Exchange Online tenant, not by the application team â it's a five-minute PowerShell runbook for them (New-ManagementScope, New-ServicePrincipal, New-ManagementRoleAssignment), fully documented in Microsoft's RBAC for Applications docs. For reference, here's the actual runbook: # 0. Make sure no unscoped Graph Mail.Send grant exists on the identity first $mi = Get-EntraServicePrincipal -ServicePrincipalId $MiObjectId $graphSp = Get-EntraServicePrincipal -Filter "appId eq '00000003-0000-0000-c000-000000000000'" $mailSendRole = $graphSp.AppRoles | Where-Object { $_.Value -eq "Mail.Send" -and $_.AllowedMemberTypes -contains "Application" } Get-EntraServicePrincipalAppRoleAssignment -ServicePrincipalId $mi.Id | Where-Object { $_.ResourceId -eq $graphSp.Id -and $_.AppRoleId -eq $mailSendRole.Id } | ForEach-Object { Remove-EntraServicePrincipalAppRoleAssignment -ServicePrincipalId $mi.Id -AppRoleAssignmentId $_.Id } # 1. Connect to Exchange Online Connect-ExchangeOnline # 2. Scope to exactly one mailbox (filter on ExternalDirectoryObjectId, not SMTP address) $mbx = Get-EXORecipient -Identity $AllowedMailbox -Properties ExternalDirectoryObjectId New-ManagementScope -Name $ScopeName ` -RecipientRestrictionFilter "ExternalDirectoryObjectId -eq '$($mbx.ExternalDirectoryObjectId)'" # 3. Register the service principal pointer (this is NOT a new identity, just a reference) $exoSp = New-ServicePrincipal -AppId $MiAppId -ObjectId $MiObjectId -DisplayName $MiDisplayName # 4. Assign exclusively Application Mail.Send, scoped New-ManagementRoleAssignment -Name $AssignmentName ` -App $exoSp.ObjectId -Role "Application Mail.Send" -CustomResourceScope $ScopeName # 5. Validate both directions Test-ServicePrincipalAuthorization -Identity $exoSp.ObjectId -Resource $AllowedMailbox # expect InScope = True Test-ServicePrincipalAuthorization -Identity $exoSp.ObjectId -Resource $BlockedMailbox # expect InScope = False Two things that trip people up here: -App in step 3/4 expects the Object ID of the Enterprise application / service principal, not the App Registration object â and never fall back to Application Mail Full Access or an exclusive management scope, since Microsoft explicitly notes exclusive scopes don't restrict application access. Worth calling out explicitly: this RBAC scope restricts the sender only. It has no concept of a recipient allowlist. Once your identity is authorized to send as a mailbox, it can send to anyone, inside or outside your tenant. If you need recipient-side restrictions, that has to be application logic â Exchange RBAC won't do it for you. Step 3 â The Kubernetes manifest Three resources: a ServiceAccount annotated with the Client ID from Step 1, a ConfigMap holding the send script, and a Deployment that mounts it. Here's the complete manifest: --- apiVersion: v1 kind: ServiceAccount metadata: annotations: azure.workload.identity/client-id: <CLIENT-ID-FROM-YOUR-IDENTITY-TEAM> name: my-mail-service-account namespace: my-namespace --- apiVersion: v1 kind: ConfigMap metadata: name: send-email namespace: my-namespace data: send-email.sh: | #!/bin/bash set -euo pipefail if [ $# -lt 2 ]; then echo "Usage: $0 <sender-email> <recipient-email> [recipient-email...]" exit 1 fi SENDER_EMAIL="$1" shift RECIPIENTS=("$@") TENANT_ID="${AZURE_TENANT_ID:-}" CLIENT_ID="${AZURE_CLIENT_ID:-}" FEDERATED_TOKEN_FILE="${AZURE_FEDERATED_TOKEN_FILE:-}" if [ -z "$TENANT_ID" ] || [ -z "$CLIENT_ID" ] || [ -z "$FEDERATED_TOKEN_FILE" ]; then echo "ERROR: Workload Identity variables not set" exit 1 fi FEDERATED_TOKEN=$(cat "$FEDERATED_TOKEN_FILE") TOKEN_RESPONSE=$(curl -s -X POST \ "https://login.microsoftonline.com/${TENANT_ID}/oauth2/v2.0/token" \ -H "Content-Type: application/x-www-form-urlencoded" \ -d "client_id=${CLIENT_ID}" \ -d "scope=https://graph.microsoft.com/.default" \ -d "client_assertion_type=urn:ietf:params:oauth:client-assertion-type:jwt-bearer" \ -d "client_assertion=${FEDERATED_TOKEN}" \ -d "grant_type=client_credentials") ACCESS_TOKEN=$(echo "$TOKEN_RESPONSE" | grep -o '"access_token":"[^"]*' | cut -d'"' -f4) if [ -z "$ACCESS_TOKEN" ]; then echo "ERROR: Failed to get token" echo "$TOKEN_RESPONSE" exit 1 fi RECIPIENTS_JSON="" for r in "${RECIPIENTS[@]}"; do if [ -n "$RECIPIENTS_JSON" ]; then RECIPIENTS_JSON="${RECIPIENTS_JSON}," fi RECIPIENTS_JSON="${RECIPIENTS_JSON}{\"emailAddress\":{\"address\":\"${r}\"}}" done cat > /tmp/email.json <<EOF { "message": { "subject": "Test from AKS", "body": { "contentType": "Text", "content": "Test email from Workload Identity" }, "toRecipients": [${RECIPIENTS_JSON}] }, "saveToSentItems": "true" } EOF HTTP_CODE=$(curl -s -w "%{http_code}" -o /tmp/response.json \ -X POST "https://graph.microsoft.com/v1.0/users/${SENDER_EMAIL}/sendMail" \ -H "Authorization: Bearer ${ACCESS_TOKEN}" \ -H "Content-Type: application/json" \ -d @/tmp/email.json) if [ "$HTTP_CODE" -eq 202 ]; then echo "Email sent successfully" else echo "ERROR: HTTP ${HTTP_CODE}" cat /tmp/response.json exit 1 fi --- apiVersion: apps/v1 kind: Deployment metadata: name: debug-deployment namespace: my-namespace labels: app: debug azure.workload.identity/use: "true" # Required. Only pods with this label can use workload identity. spec: replicas: 1 selector: matchLabels: app: debug template: metadata: labels: app: debug azure.workload.identity/use: "true" # Required. Only pods with this label can use workload identity. spec: serviceAccount: my-mail-service-account serviceAccountName: my-mail-service-account containers: - name: debug image: <your-registry>/az-init:0.1 command: ["sleep", "3600"] readinessProbe: exec: command: ["ls"] livenessProbe: exec: command: ["ls"] resources: requests: memory: "256Mi" cpu: "250m" limits: memory: "512Mi" cpu: "500m" volumeMounts: - name: script mountPath: "/script" volumes: - name: script configMap: name: send-email defaultMode: 0555 Two details that will bite you if you skip them: /me/sendMail doesn't work here. In a client_credentials flow (app-only, no signed-in user), /me returns 400 BadRequest: /me request is only valid with delegated authentication flow. You must call /users/{sender}/sendMail and name the sender explicitly. configMap.defaultMode matters. 0500 only grants execute to the file's owner (root); if your container runs as non-root, you'll get a Permission denied on exec. Use 0555. Step 4 â Test it kubectl apply -f email-pod.yaml kubectl exec -n my-namespace -it deploy/debug-deployment -- \ /script/send-email.sh authorized-sender@yourcompany.com \ recipient1@yourcompany.com recipient2@yourcompany.com A 202 and Email sent successfully means it worked. Try it again with a sender mailbox that isn't in your RBAC scope â you should get a clean 403. If you don't, go back and check that no unscoped Graph Mail.Send grant is still sitting on the identity in Entra ID; that's the most common way this containment silently fails. Conclusion This solution addresses an application email-sending need without introducing static credentials into the cluster or broadening permissions beyond what is strictly necessary. Full cloud, with no on-premises dependency or manually managed secret: No password, API key, or certificate is stored in Kubernetes (Secret, ConfigMap, or anywhere else). Authentication relies entirely on OIDC federation between the Kubernetes ServiceAccount and Microsoft Entra ID (Workload Identity) â the federated token is issued and mounted automatically by the webhook, never manually generated or distributed. The entire authentication and sending chain (Entra ID, Microsoft Graph, Exchange Online) goes through Microsoft-managed HTTPS endpoints; no on-premises component is involved in the application path (section A.3 covers a pitfall related to Exchange hybrid setups on the target mailbox side, not the authentication path itself). Provisioning the sender mailbox and the RBAC configuration are themselves managed natively within Microsoft 365 / Exchange Online, with no extra script or infrastructure to maintain on the client side. Secure by design (least privilege): The OIDC federated token is short-lived (limited lifetime, automatically renewed by the webhook) and scoped to the my-mail-service-account ServiceAccount in the my-namespace namespace â it cannot be reused outside this specific context. No tenant-wide Microsoft Graph Mail.Send permission is granted to the identity: without this precaution, the identity could send as any mailbox in the tenant. Exchange Online RBAC for Applications carries the real authorization, strictly scoped to the mailboxes that are members of the dedicated Exchange group. The containment is verified both positively and negatively before going to production â not only tested on the case that must succeed. Known and documented limitation: this RBAC model restricts only the sender, never the recipient â application-side control is still required if recipient restriction is ever needed. See You in the Cloud JamesdldNEW Teams Feature: Test Your Mic & Speaker BEFORE Joining a Meeting!
đď¸ No more "Can you hear me?" moments in Microsoft Teams! Microsoft just rolled out a small but genuinely useful feature: you can now test your microphone and speaker directly from the Teams pre-join screen â before you even enter the meeting. â Test your speaker with a quick tone â Record and play back your mic â Get a green checkmark confirming you're ready to join No more digging through Settings > Devices > Make a test call every time. Have you tried it yet? Let me know in the comments if this feature has saved you from an awkward audio moment in a meeting đ #MicrosoftTeams #Microsoft365 #TeamsUpdate #Productivity #RemoteWork #M365Insider
'External guests' able to join community?
Hi, We have merged two companies, and until we have one tenant, we are having to add one organisation as guests to one tenant instance of Viva Engage. This means creating a new 'All Company' community for them - everyone will be added. We are also looking at more optional communities (ie an AI community) - is there a way that the 'external guests' can choose to join this community? What would be the best way instead of adding everyone into it?
Viva Engage Topics
Hi all, The org I work for is looking into creating a Values in Action employee recognition program in Viva Engage. From searching I have not been able to find clear answers on our requirements. The requirements are: One dedicated Viva Engage community Recognition-only posts (no general discussion) 5 organizational values Users must select one value when recognizing a colleague We would prefer to use Praise posts Reporting Can Viva Engage be configured to: Restrict users to only 5 approved Topics? Prevent users from creating additional Topics? Require a Topic/Value to be selected before posting? Require or default to Praise posts? If not natively supported, what governance or configuration approach is recommended?
Is Teams especially the class notebook being very slow?
Has anyone else noticed Teams being slower this last two weeks? What about class notebooks? Ours are taking more than an hour to distribute a simple page. Is that just us, or is anyone else experiencing that? What can you suggest to make it faster, how it was previously? Thank you.
