Frontline Agent: An Out-of-the-Box AI Assistant for Every Frontline Teammate
As frontline teams face increasing demands and rapid change, the ability to access the right information at the right moment is more critical than ever. For this reason, we’re excited to introduce Frontline Agent, now available in Public Preview. This purpose-built, persona-tuned AI assistant is designed to help frontline workers across industries like retail, healthcare, manufacturing, and hospitality find information quickly, stay caught up, and coordinate work with confidence. Frontline Agent is available out-of-the-box in Microsoft 365 Copilot, as well as in the Microsoft Teams chat rail. You can ask for what you need just like you would a teammate and the agent delivers clear, concise responses grounded in your organization’s SharePoint and Teams chat and channel data with no configuration or custom prompts required. The agent respects SharePoint site permissions and can be scoped down to a select number of SharePoint sites, balancing accuracy and security. Frontline workers can message the agent in their preferred language, even if the documents and messages are in another language. Get started with Frontline Agent by opening Microsoft 365 Copilot and searching for it under “All agents,” and optionally scope down SharePoint sites or deploy as a Teams chatbot from Microsoft Teams Admin Center by following these instructions. What Frontline Agent can do Frontline Agent helps frontline employees: Search for information across SharePoint and Microsoft Teams chats and channel messages “Share the instructions for how to ___” “Help me learn about ___” “Provide a list of files related to ___” Catch up on Teams chat and channel messages “What did ___ tell me to do yesterday?” “Summarize my unread messages from yesterday.” “What changes did __ mention?” “Draft a shift handover based on discussions in the last 12 hours.” These capabilities reduce routine overhead and allow frontline managers to do more and frontline workers to focus on customers, operations, and service quality. Designed for the realities of frontline work in every industry Although frontline roles vary widely, their needs are consistent: fast and simplified access to information, clarity on what requires action, and tools that match the pace of their work, directly in the flow of their work. Retail Store associates can quickly pull up product details, pricing policies, inventory lookup steps, and return procedures to keep lines moving. Department leads can plan priorities for floor recovery, promos, and price changes before shift start. Store managers can generate daily recap reports covering sales trends, staffing notes, shrink issues, and unresolved operational tasks. Healthcare Nurses can quickly reference care protocols, equipment instructions, or facility policies. Care teams can catch up on shift handovers, critical updates, and open tasks before rounds. Administrators can generate summaries of unit activity to support staffing or patient flow decisions. Manufacturing Operators can pull up machine procedures, safety guidelines, or troubleshooting steps on demand. Supervisors can get summaries of production line updates and quality alerts. Transportation and Logistics Drivers and field teams can retrieve route details, documentation, or exception procedures. Dispatch teams can summarize overnight messages to prioritize next day operations. Managers can generate daily recap reports with delivery progress and unresolved items. Hospitality and Travel Front desk teams can reference policies, service procedures, and guest information instantly. Housekeeping leads can summarize messages to plan room turnover and priority tasks. Energy, Utilities, and Field Services Technicians can find site instructions, safety protocols, or equipment manuals. Field supervisors can catch up on team updates and outstanding work orders before starting their day. Operations teams can generate summaries covering outages, escalations, or environmental conditions. The value of a role aware, out of the box AI agent Most AI solutions are built for office workers. Frontline Agent is different because it is designed specifically for frontline roles, with a focus on simplicity, speed, and relevance. Simplicity: Clear responses that reduce cognitive load. Speed: Fast access to important information during active work. Relevance: Answers grounded in Teams messages and scoped SharePoint sites ensure accuracy and trust. Support for shift workflows: Catch up prompts, action item summaries, and smoother handovers. View the examples below. Get started These capabilities are the very beginning of our upcoming roadmap! Frontline Agent is now available in Public Preview and can be accessed in: Microsoft 365 Copilot by searching in “All agents.” If you want to scope down the SharePoint sites, follow instructions 1 and 2 in Set up Frontline Agent - Microsoft 365 for frontline workers | Microsoft Learn. Microsoft Teams chat rail by following these instructions.
Issue with Teams 'Add a User to Group Chat' API call?
I am getting a very strange error when trying to add a new user to an existing group chat using a GraphQL call. I have looked through the documentation, asked AI, and even contacted Microsoft support and no one can seem to explain why this API call is failing. Below is the API call that I am making. I can find no reason that I should be receiving the error message '#microsoft.graph.aadUserConversationMember' To get the basic questions out of the way.... Yes, the account making the API call DOES have permission to add users to the channel (and can do so using the frontend as normal.) Yes, the thread in question is a group chat, so adding members to that chat should be a valid command. Yes, ALL members in the group chat currently have the type '#microsoft.graph.aadUserConversationMember', so it is definitely a valid type for users in this channel. Yes, I have tried both the beta and stable channel; each gives the same error message. Yes, the invited user is internal to our organization, and is a valid target for the invite (invites work through frontend as well.) No, I cannot use the 'add member to channel' endpoint, because the chat is a group chat, not a channel. I can only assume, at this point, that the error message is a red herring and there's something else wrong with my API call?Why am I receiving this error message when trying to add a member to a pre-existing group chat? Thanks in advance for any assistance. POST to URL: https://graph.microsoft.com/beta/chats/[[THREAD_ID]]@thread.v2/members BODY: { "@odXXX.type": "#microsoft.graph.aadUserConversationMember", "roles": [], "email address removed for privacy reasons": "https://graph.microsoft.com/v1.0/users/[[USER_ID]]" } ERROR MESSAGE: {"error":{"code":"BadRequest","message":"The provided '#microsoft.graph.aadUserConversationMember' for 'odXXX.type' is not valid for this operation.","innerError":{"date":"2026-01-29T18:10:32","request-id":"<PII:moderator removed>","client-request-id":"<PII:moderator removed>"}}}
Block users from creating Public Microsoft Teams groups
Hi Community, Is already know that Teams creation in Microsoft Teams is related to O365 groups, and if you would like to block users from creating teams, you need to block them from creating O365 groups, right? Ok, right. But what if we only want to block the possibility to create public teams, but still allow them to create private ones? Would that be possible? The answer is YES. And the solution is Microsoft Purview. You'll need to create a new Label/Label Policy under Information Protection. We'll configure the Label for the scope "Site, UnifiedGroup", with group settings as "Private" and applying the label automatically. Then we can configure/publish the Label Policy as mandatory for all the users, some of them or, as in my example, to a DL that contains all the users that I would like to block. Once published, depending on your tenant size, it can take up to 24 hours to propagate. In my test environment it was quite immediate. Now, the users added to the DL that I configured in the Label Policy can still create teams, but not Public ones ( and can't change the label ) as that option is greyed out. The answer is YES. And the solution is Microsoft Purview.
Mentioning Team vs Mentioning Channel
Hello guys, since recent change (MC793969) it appears that if you mention the team or the channel in a channel that the user has hidden, he will not be notified... In the past this behaviour was only for mentioning the channel... hence users could control the notification.... i hide the channel and get less notification but if something urgent they will mention me by @team... Questions: 1, how can i reach the whole team if some users might have hid the channel where i post? 2, whats the difference now between mentioning the team and the channel?Retiring Teams live events: The next chapter for events at scale in Microsoft Teams
Today, we’re announcing the retirement of Microsoft Teams live events and the associated Microsoft Graph APIs used to create Teams live events. This change will go into effect June 30, 2026, as part of our ongoing effort to continue to modernize our event experiences and deliver a more powerful and flexible solution for large-scale communications.
Team GIF Search Results Changes
Obviously this is not very important, but has anyone else experienced a change (for the worse, in my opinion) to the GIF search results? I type in "Hi" and I get batman rubbing his chin and then a bunch of High-Five results.. Just wondering if there was an update or change announced by MS. Thanks!Whats the best Practise for on-call duty via teams external calling?
Hey community, I'm a bit in a struggle when setting up our Teams Operator Connect Phone system. We have an Auto attendence which is offering different menus (Press 1..., etc) We're planning on setting up a twentyfour x seven on-call duty where customers can call and are getting redirected to the mobile phones of our technician. I saw the option to forward to one number, but there isn't an option to forward to multiple numbers. How do you guys solve such a scenario, where you have to wake up colleagues mid night? We are changing shifts weekly, always 2 guys, sometimes 3 ppl. on shift. Thank in advance, SchnittlauchNew enhancements in Private Channels in Microsoft Teams unlock their full potential
Private channels have long empowered focused collaboration among a subset of a team’s members. Whether you're managing sensitive projects, driving confidential initiatives, or simply need a space for more targeted discussions, private channels offer the control and privacy your team needs. Now, private channels are evolving to meet the needs of modern teams. In response to customer feedback, we are introducing enhanced flexibility, greater scalability, and streamlined compliance management. Read on to learn about these key enhancements and how to prepare. Why Private Channels Matter Private channels offer a dedicated space for conversations that benefit from added structure, persistence, and control. They’re especially valuable when navigating sensitive topics like budgets, HR discussions, managing project-specific workstreams, or collaborating with clients and vendors who require limited access .While chat are ideal for quick exchanges, private channels help keep discussions organized, make shared files easier to find, and help ensure conversations remain accessible over time, all while giving you more control over who can access. What’s Changing—and Why It Matters To support growing usage and help simplify compliance, private channels will now use a group mailbox (like shared channels) instead of storing messages in individual user mailboxes. This change unlocks several key benefits: 🚀 Expanded Limits Feature Current New Max private channels per team 30 1000 Max members per private channel 250 5000 Meeting scheduling ❌ ✅ Supported Simplified Compliance At a user level Group Helping to Simplify Compliance By aligning private channels with group-based storage, compliance policies (e.g., retention, legal hold, DLP, eDiscovery) can be applied at the team (Microsoft 365 group) level, helping to reduce complexity and driving consistency across channel types. For example, one retention policy can be applied to the team’s group, instead of managing a separate policy for private channels. Organizations with compliance policies (retention, legal hold, DLP, eDiscovery, Optical Character recognition) for private channels must ensure those policies are also applied to the team’s group scope before migration begins. Existing policies for user mailboxes will continue to apply; post-migration, new private channel data will be governed by policies of the group mailbox. What Compliance Admins Need to Do To enable a smooth transition and help maintain compliance coverage, follow the below: Microsoft Purview Hold and eDiscovery Before Migration: In Microsoft Purview compliance portal, update hold policies to include the team’s Microsoft 365 group mailbox in addition to user mailboxes. After Migration: New data will reside in the group mailbox. For full eDiscovery, search both user and group mailboxes. Note: Private channel message history (edits/deletes) in user mailboxes under an existing hold will remain in their preserved user library folder until the hold expires. Microsoft Purview Data Loss Prevention (DLP) Policies Before Migration: In Microsoft Purview compliance portal, update DLP policies to include team’s group. After Migration: Check that the DLP policies are scoped to the group mailbox for private channels. Microsoft Purview Retention Policies Before Migration: In Microsoft Purview compliance portal, go to solutions -> Data Lifecycle Management -> Retention policies Create Teams channel messages policy scoped to Teams having equivalent Retention type and duration similar to existing private channel retention policies. After Migration: Set retention policies for the parent team with all channels in the team in mind, including private channels. Microsoft policies for Optical Character Recognition Optical character recognition (OCR) is managed via Data Loss Prevention (DLP) policy. Before migration, modify the corresponding DLP policy that needs be applied for OCR to private channels and change locations to all users and groups. What’s Next This update helps make private channels more scalable, manageable, and compliant. It’s a big step forward for organizations that rely on Teams for secure, structured collaboration. Migration is scheduled to begin in early October 2025 and is expected to be completed by the end of December 2025 for the worldwide cloud. During this period, private channel data will gradually move from user mailboxes to the team’s group mailbox. Private channels can be used throughout the migration. Special cloud migration will happen in early 2026. Migration can start or end at different times for each tenant during the rollout period. To track progress, a new PowerShell command will be available for tenants to check whether their migration has started or is completed. The command will be - Get-TenantPrivateChannelMigrationStatus -TenantId <tenantId> We’ll be updating public documentation soon and will share links here.
Walkie Talkie not working on iPhone in background or when locked
I'm having an issue with Teams Walkie Talkie not working when the app is in the background or the phone is locked. This issue is occurring on an iPhone 11 Pro Max, iOS 16.2. I'm connected to a channel, and the app functions as expected when Teams is open on screen. However, when Teams is running in the background or the iPhone is locked, audio communications from other people/devices do not come through. Teams has full access to notifications, background app refresh, cellular data, etc. Volume settings are correct. No other walkie talkie apps are installed that may be conflicting. Other users continue to see this device as connected to the channel when it is locked or running in the background. I appreciate any thoughts or suggestions on this issue.
