LitigationHold Delayholdapplied and Managed Folder Assistant
Hello All, I have a set of mailboxes with LitigationHoldEnabled = True, and I need to remove Litigation Hold from them. My understanding is that after I remove Litigation Hold from an Exchange Online mailbox, the next time the Managed Folder Assistant (MFA) processes the mailbox, it will detect the hold removal and then set DelayHoldApplied = True. This begins the 30-day delay hold period. My question is: Will any retention policies delete data in the time window between removing Litigation Hold and the moment MFA processes the mailbox and sets DelayHoldApplied = True My understanding is "Even though DelayHoldApplied is not yet visible (or True) before MFA processes it, Exchange Online automatically protects the mailbox from deletions immediately after hold removal, before MFA applies Delay Hold" I want to ensure that no data is deleted during this transitional period. Kindly advice with supporting article if possible. Regards Afsar
Email sent from Shared Mailbox gets stuck in Outbox
Hello, I am working with a client who has a primary and shared mailbox in Outlook. They are using the newest version of classic Outlook desktop app and they have full permissions to the shared mailbox, including "send as" permissions. They can send email from their primary mailbox without issue. However, when they send email as the shared mailbox, it gets stuck in the Outbox and never sends. I have tried the following: 1. Removing the profiles re-adding 2. Deleting the Outlook data files 3. Reducing cache to as low as 3 months 4. Turning off cache but when I do the shared mailbox gets an error that it cannot connect to the Exchange server 5. Turning on auto-archive to shrink the data files 6. Switching to "New Outlook". This does seem to work but the company uses a plug-in for a program called "Mail Manager" and they don't fully support New Outlook yet Sometimes these solutions will fix the issue for a few days to a week but then it begins happening again. This issue does not happen when they are using the mobile or web clients. To me this sounds like a corrupted data file but I can't pinpoint what exactly is causing the corruption. Any suggestions? Thanks, MikeSynchronization issue in New Outlook for Mac – ״Failed to refresh subscriptions.״
Hello, I am using Microsoft 365 (Exchange Online) on Mac, running macOS 26.1 (Tahoe). My Outlook client is: Outlook for Mac Version 16.103.3 (25113013), with a Microsoft 365 Subscription license. Since yesterday morning, in the New Outlook interface, my inbox has suddenly appeared empty, and I constantly receive the following error message: “Failed to refresh subscriptions.” It’s important to note: In Legacy Outlook, everything works perfectly. The web version and the Outlook app on my mobile phone also work well. The issue persists regardless of the network I am on (home, office, cellular, etc.). Troubleshooting steps I already tried: • Updating Outlook to the latest version • Removing and re‑adding the account • Clearing cache and preferences • Formatting my Mac and reinstalling everything from scratch Unfortunately, none of these steps has resolved the issue. Is this a known bug, and is there a recommended workaround or an upcoming fix? Appreciate assistance on that issue.
Outlook broke after Office 365 update to 16.0.19328.20158 – cannot open emails Windows Server 2016
Hello everyone, posting to report that after the latest automatic update to Microsoft Office 365 version 16.0.19328.20158, we are experiencing a critical issue on multiple company machines running Windows Server 2016: The Outlook desktop application launches normally, but when trying to open any email, the following error appears: “There was a problem opening this item... The text formatting command is not available... Reinstall Microsoft Outlook.” Launching Outlook in safe mode (Outlook /safe) does not help. Creating the FORMS2 folder (suggested workaround) does not fix it. Attempting a downgrade via OfficeC2RClient.exe fails with error 30183-27 (400). Quick/online repair from Control Panel also has no effect. In our environment, this issue appeared simultaneously on many workstations and servers, right after the Office update today. Temporary solution: We are instructing users to access their mail via Outlook Web App (OWA), which is not affected by this bug. We would like to know: If others have experienced this bug with this build, including on Windows Server 2016 If any working workaround exists, or an official fix timeframe from Microsoft Thanks to anyone who can share their experience or updates!Replying to emails from M365 Outlook group
A problem I am stumped with, so I am reaching out for some help/guidance. One group wants to not have the emails going into their own inbox but manage and reply only from the group inbox itself (so they know the email has been processed by deleting it once replied). It worked OK to begin with and then some users couldn't reply, then more. Some still can. I have tried reindexing local copy, using browser instead of app & changing the send on behalf of permissions. Owner or member of group doesn't seem to make a difference. Error messages include "This message can't be sent because it no longer exists. It can only be discarded. Make sure you copy the contents of the message before you discard if you want to use them later." and "Couldn't send this message". Please see screenshots attached. My questions: 1: Is Outlook on M365 designed to allow users to reply from the group either as the "group" or as themselves? Information I found isn't clear. 2: If it is / can be - what can I do to make it work for all users? Thanks!
