Direct Routing PSTN calls to Teams Auto Attendant does not forward to Shared Voicemail
Hi all, I’m running into a strange issue with a Teams Auto Attendant and I’m hoping someone here has seen it before. We have a Direct Routing number where business hours calls go to a Call Queue, which works, and after hours calls should go to Shared Voicemail for a Microsoft 365 Group. If I call the Auto Attendant from inside our Teams tenant, the after-hours Shared Voicemail works correctly. I can leave a message and the voicemail is delivered to the group inbox as expected. If I call the same number from the PSTN over Direct Routing, I hear the after-hours greeting, so the schedule and call flow are clearly being hit, but once the greeting finishes I get: “Sorry, we cannot connect your call at the moment, please try again later.” I have already verified that the resource account has the correct Teams Phone Resource Account license, Enterprise Voice is enabled, the LineURI is assigned, the Online Voice Routing Policy is assigned, the Direct Routing route and SBC look healthy, the Auto Attendant is associated with the correct resource account, the after-hours call flow points to the correct Microsoft 365 Group, and the group mailbox exists and is healthy. What makes this more confusing is that redirects to internal or tenant-side destinations work, but redirect to Shared Voicemail from a PSTN-originated call does not work. I also tested redirect to an external PSTN number, and that fails with the same error as well. Because the after-hours greeting plays correctly, and because internal Teams calls can successfully leave voicemail in the shared mailbox, I do not think the issue is with the Auto Attendant configuration itself or with the Microsoft 365 Group mailbox. At this point it looks more like the handoff or redirect path for PSTN-originated calls over Direct Routing is where things break. Has anyone run into this with a Teams Auto Attendant, Shared Voicemail, and inbound PSTN over Direct Routing? I’m trying to figure out whether this is a known limitation, a bug, or if there is some specific setting related to PSTN-originated redirects that I am missing. Thanks!
Office 365 issues
We have an end user that started with us approximately a year ago. Shortly after he started he began noticing that his status would go away on a fairly regular basis on MS Teams. We tried uninstall/reinstall, resetting, repairing and the problem persisted. Since he was a relatively new hire we were thinking it was something with his laptop so we replaced and the issue returned. Turned in a ticket with our Office 365 vendor who in turn opened a ticket with Microsoft. After some initial testing they sent a Teams install file that seemed to fix the issue. Since that time he has regularly had issues with Teams disconnecting, Outlook just stop receiving emails, while showing connected. Typically the only fix was a restart and on some occasions that did not work. Sometimes a reset or repair might fix this issue. Throughout this we did clear credential manager, caches, etc...This got a point yesterday where I created a new user profile for him, basically like a new laptop and it temporarily fixed the Teams and Outlook issue, however when attempting to sign into MS Edge it would just spin and had to use task manager to close the app. Tried a repair on the app as you cannot uninstall and same result it would hang up and have to forcibly closed. Just wondering if someone else has encountered something like this and possible fixes. ThanksTeams Private Channels: Group-Based Compliance Model & Purview eDiscovery Considerations
Microsoft Teams Private Channels are undergoing an architectural change that will affect how your organisations uses Microsoft Purview eDiscovery to hold and discovery these messages going forward. In essence, copies of private channel messages will now be stored in the M365 Group mailbox, aligning their storage with how standard and shared channels work today. This shift, due to roll out from early October 2025 to December 2025, brings new benefits (like greatly expanded channel limits and meeting support) and has the potential to impact your Purview eDiscovery searches and legal holds workflows. In this blog post, we’ll break down what’s changing, what remains the same, and provide you with the information you need to review your own eDiscovery processes when working with private channel messages. What’s Changing? Private channel conversation history is moving to a group-based model. Historically, when users posted in a private channel, copies of those messages were stored in each member of the private channel’s Exchange Online mailbox (in a hidden folder). This meant that Microsoft Purview eDiscovery search and hold actions for private channel content had to be scoped to the member’s mailbox, which added complexity. Under the new model rolling out in late 2025, each private channel will get its own dedicated channel mailbox linked to the parent Teams’ M365 group mailbox. In other words, private channel messages will be stored similarly to shared channel messages; where the parent Teams’ M365 group mailbox is targeted in eDiscovery searches and holds, instead of targeting the mailboxes of all members of the private channel. Targeting the parent Teams’ M365 Group mailbox in a search or a hold will extend to all dedicated channel mailboxes for shared and private channels within the team as well as including any standard channels. After the transition, any new messages in a private channel will see the message copy being stored in the channel’s group mailbox, not in users’ mailboxes. Why the change? This aligns the retention and collection of private channel messages to standard and shared channel messages. Instead of having to include separate data sources depending on the type of Teams channel, eDiscovery practitioners can simply target the Team’s M365 Group mailbox and cover all its channel, no matter it’s type. This update will introduce major improvements to private channels themselves. This includes raising the limits on private channels and members, and enabling features that were previously missing: Maximum private channels per team: increasing from 30 to 1000. Maximum members in a private channel: increasing from 250 to 5000. Meeting scheduling in private channels: previously not supported, now allowed under the new model. The table below summarizes the old vs new model for Teams private channel messages: Aspect Before (User Mailbox Model) After (Group Mailbox Model) Message Storage Messages copied into each private channel member’s Exchange Online mailbox. Messages are stored in a channel mailbox associated with the parent Teams’ M365 group mailbox. eDiscovery Search Had to search private channel member’s mailboxes to find channel messages. Search the parent M365 group mailbox for new private channel messages and user mailboxes for any messages that were not migrated to the group mailbox. Legal Hold Placement Apply hold on private channel member’s mailbox to preserve messages. Apply hold on the parent M365 group mailbox. Existing holds may need to include both the M365 group mailbox and members mailboxes to cover new messages and messages that were not migrated to the group mailbox. Things to know about the changes During the migration of Teams private channel messages to the new group-based model, the process will transfer the latest version of each message from the private channel member’s mailbox to the private channel’s dedicated channel mailbox. However, it’s important to note that this process does not include the migration of held message versions; specifically, any messages that were edited or deleted prior to the migration. These held messages, due to a legal hold or retention policy, will remain in the individual user mailboxes where they were originally stored. As such, eDiscovery practitioners should consider, based on their need, including the user mailboxes in their search and hold scopes. Legal Holds for Private Channel Content Before the migration, if you needed to preserve a private channel’s messages, you placed a hold on the mailboxes of each member of the private channel. This ensured each user’s copy of the channel messages was held by the hold. Often, eDiscovery practitioners would also place a hold on the M365 group mailbox to also hold the messages from standard and shared channels After the migration, this workflow changes: you will instead place a hold on the parent Team’s M365 group mailbox that corresponds to the private channel. Before migration: It is recommended to update any existing hold that are intended to preserve private channel messages so that it includes the parent Team’s M365 group mailbox in addition to the private channel members’ mailboxes. This ensures continuity as any new messages (once the channel migrates) will be stored in the group mailbox. After migration: For any new eDiscovery hold involving a private channel, simply add the parent Teams’ M365 group mailbox to the hold. As previously discussed eDiscovery practitioners should consider, based on need, if the hold also needs to include the private channel members mailboxes due to non-migrated content. Any private channel messages currently held in the user mailbox will continue to be preserved by the existing hold, but to hold any future messages sent post migration will require a hold placed on the group mailbox. eDiscovery Search and Collection Performing searches related to private channel messages will change after the migration: Before Migration: To collect private channel messages, you targeted the private channel member’s mailbox as a data source in the search. After migration: The private channel messages will be stored in a channel mailbox associated with the parent Team’s M365 group mailbox. That means you include the Team’s M365 group mailbox as a data source in your search. As previously discussed eDiscovery practitioners should consider, based on need, if the search also needs to include the private channel members mailboxes due to non-migrated content. What Isn’t Changing? It’s important to emphasize that only Teams private channel messages are changing in this rollout. Other content locations in Teams remain as they were, so your existing eDiscovery processes remain unchanged: Standard channel messages: These are been stored in the Teams M365 group mailbox. You will continue to place holds on the Team’s M365 group mailbox for standard channel content and target it in searches to do collections. Shared channel messages: Shared channels messages are stored in a channel mailbox linked to the M365 group mailbox for the Team. You continue to place holds and undertake searches by targeting the M365 group mailbox for the Team that contains the shared channel. Teams chats (1:1 or group chats): Teams chats are stored in each user’s Exchange Online mailbox. For eDiscovery, you will continue to search individual user mailboxes for chats and place holds on user mailboxes to preserve chat content. Files and SharePoint data: Any file shared in teams message or uploaded to a SharePoint site associated with a channel remains as it is today. In conclusion For more information regarding timelines, refer to the to the Microsoft Teams blog post “New enhancements in Private Channels in Microsoft Teams unlock their full potential” as well as checking for updates via the Message Center Post MC1134737.Feature request: "AFK" status whilst on call
We would like to use Microsoft Teams calls as a continuously open call for long periods of time whilst working remotely as a team. However the current inability to visually see on the call screen whether another attendee is at their keyboard, without everyone having their cameras on all the time (which eats a lot of bandwidth) limits our ability to do so. I would like the ability to have an "away from keyboard" status, similar to the "raise hand" status, that can be set by each attendee when they step away from their desk/keyboard to grab a drink or take a comfort break. This could either be implemented by: adding a new group in which "raise hand" is one option, and "step away" is another adding a new option along the tool bar specifically for "step away" The only way to do this currently is to create another meeting (with yourself) and join that meeting so that you appear 'on-hold' within the previous call. This is very tedious to implement for every attendee involved.
Teams Desktop and Microphone
It appears I am flogging a dead horse here. My microphone works everywhere on my laptop except Desktop Teams I have tried every possible solution available in these discussions, and everywhere else on the Internet. Basically, they all take you through the same steps. It is not like I do not know how to solve hardware issues. I will never recover the amount of time I have spent trying to fix this. I have tried Windows troubleshooters (the ones still active). On Windows 11, using the microphone test available in System > Sound > Properties, it works 100%. The microphone works 100% using Teams web It works using onlinemictest.com Testing it in Teams (Make a test call), no sound is played back. . On closing, the microphone and speakers are ticked in green. This is a recent development with the latest Teams. I did not change anything. I'm aware of hidden issues like Teams concurrently running on your phone, etc. I recently reinstalled Windows 11, so it is not a driver issue. It is HUGELY frustrating. P.S. When I tried to publish this, using YOUR built-in editor, I got a notification. Your post contains invalid HTML. I had to go into the code to remove <span> tags!Microsoft Places individual desk booking is not working
Hi, Following the documentation, https://learn.microsoft.com/en-us/microsoft-365/places/configure-desk-booking, I successfully ran the shared command lines without any errors. However, on Microsoft Places, I am unable to see individual desks appear; only desk pools are visible. Has anyone managed to get this to work? Thanks,
Collateral storage and creation of M365 Group
Hi there Can you please answer a few questions for me? Is it true that for each campaign created, a Microsoft Team and SharePoint site is also created? And, I discovered that collateral is saved to the creator's OneDrive, (if above is true) is it also saved in the SharePoint site for the campaign? What is the reason for saving it to the user's OneDrive? .And how are past campaigns affected if that user leaves the organisation and the OneDrive account is deleted? Thank you.
Cross-Tenant Shared Meeting Room Spaces
We have two M365 tenancies under our group. We need to allow users from both tenants to use Meeting room resources (book rooms, use calendars etc..). Is this just about configuring Exchange OR Sharing in EXO or do we need anything beyond that to facilitate Teams meeting room resource sharing? Would we also need to sync these meeting room objects across tenancies to allow users to see them in GAL etc.. ? Thank you!
Viva Engage Notifications
We would like to understand whether Viva Engage supports any of the following capabilities: Automatically enabling email notifications for new members when they join a community. Configuring community members to receive notifications by default and requiring them to opt out rather than opt in. Applying a tenant-wide or community-level policy that enables email notifications for all members of selected communities. Configuring notification settings through Microsoft 365 admin settings, Viva Engage admin settings, PowerShell, Microsoft Graph, or any other administrative mechanism. Identifying whether this functionality is on the Microsoft roadmap if it is not currently available. Our company is currently test piloting Viva Engage with a few different departments, but they are noticing that member engagement is not very high. We are looking for ways to get members more engaged in the product. Thanks, Greg
MacBook Pro TouchBar's not working in meeting with new teams
Hello, I have a MacBook Pro with Touch Bar. With old version of Teams, Touch Bar work in meeting but when I install a new version of teams (business) my Touch Bar not work. I have clear the cache, delete and reinstall Can you help me with a problem? Thank you
