Forum Widgets
Latest Discussions
How to Find Active EWS-Based Apps in a Microsoft 365 Tenant
Microsoft will retire Exchange Web Services (EWS) from Exchange Online on October 1, 2026. A new usage report helps tenants understand what apps use EWS. Many of the apps are likely to be first-party (Microsoft) apps, but some might be third-party apps developed externally or internally. Those apps need to be retired or upgraded to use Graph APIs. Time is slipping away to do the work. https://office365itpros.com/2025/04/29/exchange-web-services-apps/149Views0likes6CommentsWindows Handle error when using Connect-Exchange Onlinew Module version 3.7.
The following error is received when trying to connect to exchange online. Windows 11 Exchange Online Management 3.7.1 PowerShell 5.1 Error attached. On another Windows 11 Laptop, the 3.6 version of the module works without error. I am having the user downgrade to 3.6 and see if it fixes the error. I have upgraded this to 3.7.1 and now get the same error. Any help woudl be much appreciated. I can't past the error. Won't let me post.DFOTAMay 23, 2025Copper Contributor2.2KViews0likes6CommentsExg 2019 CU15 Error: OWA not login
After installation of CU15 upgrade, OWA/ECP virtual directory got misconfigured or corrupted. Task i have tried: Remove Virtual Directory and created new. --- Not resolved. Trying with Upgrade from ISO Exchange setup -- Not resolved. I found article of copymissing.dll script and tried --- Not resolved. I found "C:\Program Files\Microsoft\Exchange Server\V15\Bin\Microsoft.Exchange.HttpProxy.dll" this dll file missing in my path. What shall i check or do to resolve this issue?binodmaharjan_2020May 23, 2025Copper Contributor6Views0likes0CommentsMissing emails
Got a weird one here and hoping someone else has seen this before. Scenario: Internal user sends an email to about 15 other internal users. I see the sent item in message trace, delivering successfully for all recipients. Days later, the sender and recipients can not locate the item in their mailboxes. I spot check one of the recipients and perform as thorough of a search on their mailbox as I can and am unable to locate it. All recipients claim to have not permanently deleted the item. What I've done: I did multiple content searches with scopes of varying depth, none of them have found the item. I checked audit logs for 'move to deleted' and 'delete from deleted', nothing. I checked Defender to see if the item had any post delivery processing performed, nothing. The trace shows successful delivery, Explorer in Defender portal shows the same, yet the item is undetectable. I don't know what I'm missing as far as what system could have snagged that item out of the mailboxes, which I'm assuming happened since the content searches are coming up empty. For the affected users, there are no commonalities regarding delegate access. There are 3 administrative users for the environment - none recall performing any purge for this item. There are no logs of a purge of this item that I can find.CharlieDeltaMay 23, 2025Copper Contributor74Views0likes2CommentsExchange Mailbox Migration Errors - Corrupted items
Howdy Folks! I'm getting a lot of errors in one of the last mailboxes we're migrating to 365 from Exchange 2019 Hybrid. Has anyone managed to remediate these type of errors? I've remediated abandoned users from permissions but nothing has worked. The errors still popping up even after creating a new batch. Subject Kind Scoring Classification Folder Name FolderACL CorruptFolderACL FolderACL, SourcePrincipalError Tasks FolderACL CorruptFolderACL FolderACL, SourcePrincipalError Tasks FolderACL CorruptFolderACL FolderACL, SourcePrincipalError Notes FolderACL CorruptFolderACL FolderACL, SourcePrincipalError Notes FolderACL CorruptFolderACL Inbox, FolderACL, SourcePrincipalError Inbox FolderACL CorruptFolderACL Inbox, FolderACL, SourcePrincipalError Inbox FolderACL CorruptFolderACL FolderACL, SourcePrincipalError Investments FolderACL CorruptFolderACL FolderACL, SourcePrincipalError Investments FolderACL CorruptFolderACL FolderACL, SourcePrincipalError Health FolderACL CorruptFolderACL FolderACL, SourcePrincipalError Health FolderACL CorruptFolderACL FolderACL, SourcePrincipalError Eleanor FolderACL CorruptFolderACL FolderACL, SourcePrincipalError Eleanor FolderACL CorruptFolderACL FolderACL, SourcePrincipalError Clover FolderACL CorruptFolderACL FolderACL, SourcePrincipalError Clover FolderACL CorruptFolderACL FolderACL, SourcePrincipalError ACL ASIC FolderACL CorruptFolderACL FolderACL, SourcePrincipalError ACL ASIC FolderACL CorruptFolderACL FolderACL, SourcePrincipalError __Pre 2011 FolderACL CorruptFolderACL FolderACL, SourcePrincipalError __Pre 2011 FolderACL CorruptFolderACL FolderACL, TargetPrincipalError __Pre 2011 FolderACL CorruptFolderACL FolderACL, SourcePrincipalError __2011-2012 FolderACL CorruptFolderACL FolderACL, SourcePrincipalError __2011-2012 FolderACL CorruptFolderACL FolderACL, TargetPrincipalError __2011-2012 FolderACL CorruptFolderACL FolderACL, SourcePrincipalError Contacts FolderACL CorruptFolderACL FolderACL, SourcePrincipalError Contacts FolderACL CorruptFolderACL FolderACL, SourcePrincipalError Recipient Cache FolderACL CorruptFolderACL FolderACL, SourcePrincipalError Recipient Cache FolderACL CorruptFolderACL FolderACL, SourcePrincipalError Recipient Cache FolderACL CorruptFolderACL FolderACL, SourcePrincipalError Recipient Cache FolderACL CorruptFolderACL FolderACL, SourcePrincipalError PeopleCentricConversation Buddies FolderACL CorruptFolderACL FolderACL, SourcePrincipalError PeopleCentricConversation Buddies FolderACL CorruptFolderACL FolderACL, SourcePrincipalError PeopleCentricConversation Buddies FolderACL CorruptFolderACL FolderACL, SourcePrincipalError PeopleCentricConversation Buddies FolderACL CorruptFolderACL FolderACL, SourcePrincipalError Organizational Contacts FolderACL CorruptFolderACL FolderACL, SourcePrincipalError Organizational Contacts FolderACL CorruptFolderACL FolderACL, SourcePrincipalError Organizational Contacts FolderACL CorruptFolderACL FolderACL, SourcePrincipalError Organizational Contacts FolderACL CorruptFolderACL FolderACL, SourcePrincipalError GAL Contacts FolderACL CorruptFolderACL FolderACL, SourcePrincipalError GAL Contacts FolderACL CorruptFolderACL FolderACL, SourcePrincipalError GAL Contacts FolderACL CorruptFolderACL FolderACL, SourcePrincipalError GAL Contacts FolderACL CorruptFolderACL FolderACL, SourcePrincipalError Companies FolderACL CorruptFolderACL FolderACL, SourcePrincipalError Companies FolderACL CorruptFolderACL FolderACL, SourcePrincipalError Companies FolderACL CorruptFolderACL FolderACL, SourcePrincipalError Companies FolderACL CorruptFolderACL FolderACL, SourcePrincipalError {A9E2BC46-B3A0-4243-B315-60D991004455} FolderACL CorruptFolderACL FolderACL, SourcePrincipalError {A9E2BC46-B3A0-4243-B315-60D991004455} FolderACL CorruptFolderACL FolderACL, SourcePrincipalError {06967759-274D-40B2-A3EB-D7F9E73727D7} FolderACL CorruptFolderACL FolderACL, SourcePrincipalError {06967759-274D-40B2-A3EB-D7F9E73727D7} FolderACL CorruptFolderACL FolderACL, SourcePrincipalError Calendar FolderACL CorruptFolderACL FolderACL, SourcePrincipalError Calendar FolderACL CorruptFolderACL FolderACL, SourcePrincipalError Calendar FolderACL CorruptFolderACL FolderACL, SourcePrincipalError Calendar FolderACL CorruptFolderACL FolderACL, SourcePrincipalError Calendar FolderACL CorruptFolderACL FolderACL, SourcePrincipalError Calendar FolderFreeBusyACL CorruptFolderACL FolderACL, SourcePrincipalError Calendar FolderFreeBusyACL CorruptFolderACL FolderACL, SourcePrincipalError Calendar FolderFreeBusyACL CorruptFolderACL FolderACL, SourcePrincipalError Calendar FolderFreeBusyACL CorruptFolderACL FolderACL, SourcePrincipalError Calendar FolderFreeBusyACL CorruptFolderACL FolderACL, SourcePrincipalError Calendar FolderFreeBusyACL CorruptFolderACL FolderACL, SourcePrincipalError Calendar FolderFreeBusyACL CorruptFolderACL FolderACL, SourcePrincipalError Calendar FolderACL CorruptFolderACL FolderACL, SourcePrincipalError Calendar_JFK3F8.ics FolderACL CorruptFolderACL FolderACL, SourcePrincipalError Calendar_JFK3F8.ics FolderACL CorruptFolderACL FolderACL, SourcePrincipalError Calendar_JFK3F8.ics FolderACL CorruptFolderACL FolderACL, SourcePrincipalError Calendar_JFK3F8.ics FolderACL CorruptFolderACL FolderACL, SourcePrincipalError Calendar_JFK3F8.ics FolderACL CorruptFolderACL FolderACL, SourcePrincipalError Calendar_JFK3F8.ics FolderACL CorruptFolderACL FolderACL, SourcePrincipalError Calendar_JFK3F8.ics FolderACL CorruptFolderACL FolderACL, SourcePrincipalError Calendar_JFK3F8.ics FolderACL CorruptFolderACL FolderACL, SourcePrincipalError Calendar_JFK3F8.ics FolderACL CorruptFolderACL FolderACL, TargetPrincipalError Calendar_JFK3F8.ics FolderACL CorruptFolderACL FolderACL, SourcePrincipalError Freebusy Data Model walkthrough with NT CorruptItem Calendar, Item, StartMustExistCalendarCorruption Calendar81Views0likes2CommentsExchange Online User Unable to use Aliases on Mobile
Hi Exchange Brain Trust, We have a user recently moved to EXO and he has 3 aliases on his mailbox. He's trying to reply to a mail from one of the aliases, it gets send to himself. Anyone seen/worked around this behaviour? Thank you!31Views0likes2CommentsSMTP relay without on-prem Exchange server
Hi Exchange Experts, One of my Customer has following Requirement: They have already migrated all their user mailboxes to Exchange Online. They still have 2 Exchange on prem servers functioning as SMTP relay for their applications and printers. They want to decommission the 2 Exch servers and directly use Exchange online (yourdomain-com.mail.protection.outlook.com) as SMTP relay. Their applications and printers do not have a public ip address. They don't want to use any on-prem mail relay servers. They don't want to use azure Communication Services. Their devices and applications do not support TLS 1.3 or TLS 1.2 What would be the best solution ? Thanks and Best Regards, Vijay.57Views0likes2CommentsPowerShell EXO: Get-MessageTrace still only 10 days back?
Hi, For some time now, we can use the GUI to get realtime data for older than 10 days. I think we can now go 3 months back but only with a timeframe of 10 days. Why doesn't this work with PowerShell? I've read the following news: Extended Query Range: Admins can query up to 90 days of historical data, but each query is limited to a 10-day range. Initially, only 30 days of historical data will be available for near real time queries, gradually increasing to the full 90-day range. But everytime I try to get Get-MessageTrace going with, for example, Get-MessageTrace -StartDate 04/22/2025 -EndDate 04/28/2025 -RecipientAddress email address removed for privacy reasons -Status DELIVERED -Sender $sender.PrimarySMTPAddress I get the message "The StartDate can't be older than 10 days from today...." Why? It was so much easier with OnPrem environments. Now I have to start a historical search if I want to do some simple tracing and send a report with PowerShell? Not to mention that I don't even know if a generated report from Start-HistoricalSearch can be downloaded and sent with PowerShell. What am I missing?Mister_XMay 22, 2025Copper Contributor26Views0likes2CommentsApplicationAccessPolicy vs Azure Automation Account
Hi all. I have an Azure Automation Account (AAA) with enabled system managed identity. I added Graph API permission Mail.Send (application) to this identity and in script I'm able to send behalf of any email mailboxes. It works correctly. I want to restrict this AAA to specific mailboxes. So, I followed the Limiting application permissions to specific Exchange Online mailboxes - Microsoft Graph | Microsoft Learn. I created Service Principal for AAA by "New-ServicePrincipal" command and created new Application Access Policy. When I test it via Test-ApplicationAccessPolicy command I see correct result. But AAA is still able to send an email behalf of an email mailbox. Do you have the same experience?SolvedJanRezabMay 22, 2025Brass Contributor37Views0likes2CommentsHybrid Configuration Wizard Fails – MRSProxy Unauthorized
Issue: HCW8078 - Migration Endpoint could not be created Details: MRSProxy connection to https://mail.domain.ca/EWS/mrsproxy.svc failed. Error: The HTTP request is unauthorized with client authentication scheme 'Negotiate'. The authentication header received from the server was 'Basic realm="mail.domain.ca"'. We’ve confirmed: MRSProxy is enabled Basic Auth is enabled Virtual directories (EWS, Autodiscover, RPC) have correct auth settings Outlook clients began prompting unexpectedly after configuration changes Looking for advice on resolving this auth issue during Hybrid Configuration Wizard setup.nflnetwork291May 22, 2025Copper Contributor61Views1like3Comments
Resources
Tags
- exchange online2,499 Topics
- Exchange Server2,270 Topics
- office 3651,222 Topics
- hybrid859 Topics
- outlook747 Topics
- 2016735 Topics
- admin656 Topics
- 2013277 Topics
- 2010159 Topics
- 201979 Topics