Forum Widgets
Latest Discussions
Exchange Online Restricts the Number of Dynamic Distribution Groups
Exchange Online is imposing a new tenant-wide limit of 3,000 Dynamic Distribution Groups. Few tenants might be affected, but the question might be asked why Microsoft is limiting DDGs at this point. Is it a cunning plan to prompt people to use dynamic Microsoft 365 groups instead? Or are some tenants abusing DDGs in weird and wonderful ways? Who knows, but the limit applies from early April 2025. https://office365itpros.com/2025/03/10/dynamic-distribution-groups-limit/Why Only Web-Based Outlook Clients Can Recall Encrypted Email
The new message recall facility has been around since 2022. Even after Microsoft revamped the feature in 2023, it’s still only possible to recall protected messages with OWA and the new Outlook. As it turns out, the reason is that a premium license is needed, and Outlook classic might need some new code to check for that license. In other news, Outlook mobile now supports message recall. https://office365itpros.com/2025/03/13/message-recall-protected/Exchange health set unhealthy
Hello everyone! Some healthprobes on our Exchange 2016 Server have been reporting an unhealty state since the middle of February. OAB.Proxy, EWS.Proxy, Outlook.proxy and OutlookMapiHttp.Proxy. We have no mailboxes on the server, so its not critical, but I would still like to figure out what is going on. They all fail with "The remote server returned an error: (401) Unauthorized" and if I try to invoke the probe i see this in the response: It looks like the SSL validation is not happening. Is it normal for the probe to use localhost for this? When I run "Get-WebServicesVirtualDirectory" both internal and external virtual directry is set to our external url. Any insight is greatly appreciated!Time to Remove the Old Report Message Add-Ins
Microsoft says that the Report Button is now available for all Outlook clients and it’s time to remove the old Report Phishing and Report Message add-ins. A note in the documentation says that the old add-ins are unsafe, but Microsoft is probably more concerned about getting rid of COM-based add-ins. In any case, a single button to handle all aspects of reporting suspicious email seems like a good idea. https://office365itpros.com/2025/03/17/report-button-outlook/
Message submission rate - Avoid spam sending
Hello everyone! I am looking for a way to set a limit on the number of messages sent per hour (or per minute) in Exchange 2016/2019. Analyzing the documentation below, I configured the Message rate limit per user, but it had no effect. Ref: Message rate limits and throttling | Microsoft Learn When sending a number of messages greater than the configured limit, we receive the message "4.4.2 Message submission rate for this client has exceeded the configured limit," but all the messages are sent normally. I would like to know if there is any way to limit the number of messages per account in order to prevent spam from being sent through our environment. Any suggestions? Tks!
Issues after Exchange 2019 CU15 install
Hello, We have some issues with our Exchange server. After CU15 install we have high(er) CPU usage at the server and slow(er) Outlook (online no cache mode enabled) connection at the client. MAPI over HTTP and Exchange Extended Protection is enabled. Have anybody else who have the same issues?Expose ResourceDelegates in OWA Settings > Calendar > Resource Scheduling
Expose ResourceDelegates in OWA Settings > Calendar > Resource Scheduling · Community I'm posting this here in hopes of getting votes over at the feedback site. What I'm after as a solution is this: 1.) Room "Owners" be granted FullAccess (ideally with AutoMapping disabled). 2.) Room "Owners" open room mailboxes in OWA and manage both Calendar permissions, and Resource Scheduling options (a.k.a., Booking Options), entirely themselves. 3.) Admins are relieved of the burden of having to do all this work for Room "Owners" because some of the settings are hiding in PowerShell only. We're almost there in EXO's OWA options > Calendar > Resource Scheduling. We're just missing ResourceDelegates: I suppose additional checkboxes could also be added to cover off all the other settings available in Get-/Set-CalendarProcessing, but for me ResourceDelegates is the most vitally important one. In large orgs, the ability to truly hand off responsibility of these settings to a room owner will be a huge administrative overhead relief.
