Help your customers get answers and support with Teams Phone Agent
Now generally available, Teams Phone Agent is an AI-powered calling receptionist that helps organizations serve their customers. It answers incoming calls to help customers with common requests, such as answering questions and booking appointments. It also intelligently transfers callers to an employee or department with context notes when additional assistance is needed.Serve customers with Queues app's collaborative calling for Microsoft Teams
Queues app for Microsoft Teams turns an existing call queue into a collaborative workspace where calling representatives and supervisors work the same set of customer conversations together in Teams. Eligible organizations can try it with a 90-day Teams Premium trial and discount opportunity. Terms and conditions apply.
Error office 365 e3 developer license will be deleted on XXXXX. Currently disabled
My Office 365 E3 Developer has been marked for deletion and disabled today. No earlier comms from Micrsoft or any sort of messages.It just locked our my E3 Developer license has there a not supporting it any more. I wanted to try and backup/export my mail box and no luck - the option is greyed out. My SharePoint admin center has been blocked also can't backup any of my files. I'm just helpless.What a shame Microsoft What other plans can i move to and what should i do now since Teams and mail is not working. Can I at least get a a grace period. Any resources or advice would be appreciated
Not receiving any notifications in my Samsung S26 Ultra
Hello, Since I moved to Samsung S26 Ultra, I am not getting any notifications. Following are my settings. Please help to fix the issue. Following are settings in Samsung phone Following are settings in my Teams app in deskop Following is the settings set for all my channels ThanksThe new Planner in Microsoft Teams is now available to customers in GCC High
We’re excited to announce that the new Planner app in Microsoft Teams (web and desktop) is now available to customers in the Government Community Cloud (GCC) High environment! There’s no migration required—your existing tasks, basic plans, and premium plans are already in the new Planner. In August, we introduced the modern Planner experience on the web for GCC High. Now, that same experience comes to Microsoft Teams—the hub for teamwork in Microsoft 365—so your teams can plan, track, and collaborate on work right alongside their chats, meetings, and files. Add the Planner app in Teams and start managing all your work in one place You can learn more about the new Planner in our previous announcement. Your feedback helps us prioritize what to build! Share it with us via the Planner Feedback Portal. Getting started Open Planner in Teams. You can also find the Planner app in the Apps browser. Start by selecting the View more apps “…” menu in the navigation bar. Then, select the Planner icon. Once you’ve added Planner, you can pin the app (select Pin) to the left side of Teams for easy access. Differences for customers in GCC High It’s important to note that a few features are not available to customers in GCC High. These include: Copilot in Planner. Tasks assigned to you in premium plans will not appear in the My Tasks view. The ability to convert a basic plan to a premium plan. Task history in premium plans. Project Manager agent. Frequently asked questions Does the rollout include the Planner app in Teams mobile? No. The rollout to GCC High delivers the new Planner App in the Teams web and Desktop clients. Is there anything I need to migrate? No. Existing personal tasks, basic plans, and premium plans appear in the new Planner automatically. Will I see the same features as the Microsoft commercial cloud? Core planning features are consistent, but certain capabilities are not yet available in GCC High. We’ll share updates as these become available. Share your feedback We encourage you to share any feature requests by adding your ideas to the Planner Feedback Portal. Your feedback helps inform our feature updates, and we look forward to hearing from you as you try Planner’s new and existing capabilities! Resources Learn more about Planner at the Planner adoption page. Sign up to receive future communication about Planner. Check out the Microsoft 365 roadmap for feature descriptions and estimated release dates for Planner. Watch Planner demos for inspiration on how to get the most out of Planner in Teams. Visit the Planner help page to learn more about the new Planner.
Teams Retains Stale App Metadata After Removing and Re-uploading a Sideloaded App
After the app is removed and subsequently re-uploaded, Microsoft Teams appears to retain stale application metadata or session information from the previous installation. This may include the previous app identity, bot or static tab references, and WebView session state. As a result, Teams may display errors such as "This app can't be found" or prevent navigation to the Messages/Chat section, even though the application configuration and React routing are functioning correctly. The issue appears to occur particularly when the application is re-uploaded using the same manifest version. Completely quitting and restarting Teams may temporarily resolve the problem. Expected Behavior After removing a sideloaded app and uploading it again, Teams should load the latest application configuration and should not retain stale metadata or session state from the previous installation. Actual Behavior Teams may continue using stale app metadata or session state after the app has been removed and re-uploaded, resulting in navigation failures or "This app can't be found" errors.Static Tab and Chat Tab Order Is Not Persisting in Microsoft Teams
manifest file: "staticTabs": [ { "entityId": "schedule", "name": "Schedule", "contentUrl": "...", "websiteUrl": "...", "scopes": ["personal"] }, { "entityId": "conversations", "scopes": ["personal"] } ] the Schedule tab is intentionally place before conversations: it initially appears correctly, but after navigating away from the app and returning, Teams places Chat/Conversations before Shcedule. I'm using schema version 1.12. The tabs are configured in the specified order in the manifest file, and the expected tab order is displayed correctly when the app is initially opened. However, when I navigate to the Chat section, the tab order changes and does not persist as defined in the manifest file.
Cannot deploy Custom backgrounds for Teams in VDI environment
We have detected (or so we think) a malfunction in Teams on VDI when attempting to deploy Teams backgrounds that should be available to users for their video calls. The only article that documents how to do this is the following: https://learn.microsoft.com/en-us/microsoftteams/custom-meeting-backgrounds It clearly states that the path where custom Teams backgrounds are stored is in the user profile, specifically in the folder: %LOCALAPPDATA%\Packages\MSTeams_8wekyb3d8bbwe\LocalCache\Microsoft\MSTeams\Backgrounds\Uploads Expected Process The process is not direct, but it is straightforward. Using a script, a UUID is generated, which is used to create two image files (JPG, BMP, or PNG format, depending on the original image). For example, if the original is a JPG: UUID.JPG UUID_thumb.JPG These two files are copied to the path above, and on the next Teams session startup they should be available to the user. ✅ This works correctly in physical (non-VDI) environments. Tested many times without issues. What We Have Observed in VDI Even when the file pair is copied to the correct path within the user's FSLogix profile, the image does not become available in the Teams client — even after restarting Teams multiple times or even the VDI session itself. After each restart, the files are confirmed to be persistent and located at the correct profile path.[ %LOCALAPPDATA%\Packages\MSTeams_8wekyb3d8bbwe\LocalCache\Microsoft\MSTeams\Backgrounds\Uploads folder contents] When a background image is added manually through the Teams UI, a folder is created in OneDrive called "Microsoft Teams User Custom Video Backgrounds". If additional images are manually added to that OneDrive folder, they do not appear as available in Teams. This leads us to believe that the upload process performs additional operations in the registry or other configuration locations beyond simply copying the file. A ProcMon capture was performed, but after an initial superficial inspection, it was not possible to determine exactly what is happening under the hood.
