Forum Widgets
Latest Discussions
Microsoft Blocks EWS Access for Kiosk Users
A December 2 announcement says that Exchange Online will block access to Exchange Web Services for users with kiosk or frontline worker licenses from March 2026. In fact, the Exchange Online service description has always excluded EWS access for these licenses, but the necessary code to enforce the exclusion was never implemented. It will be in March. Time to check licenses… https://office365itpros.com/2025/12/05/exchange-web-services-kiosk/8Views0likes0CommentsExchange 2016 Mail Flow is Not Working
We had issues with updating to a latest Cumulative Update and messed up our EMS and some Web Config. It seems our Exchange Server is totally bricked. So, we decided to boot our Exchange Server from backup. The backup was dated September 2025. Unfortunately, after booting up the September 2025 backup, we noticed that the internal and external mail flow is not working (our Exchange 2016 is Exchange hybrid configured). The outgoing emails are stuck in Draft folder. The following troubleshooting steps have been done to no avail: -Checked if the port 25 is open -> This port is opened -Check the network settings if the Preferred DNS Address points to the correct DNS Server --> It points to the correct DNS Server -Modified the DNS lookup under Exchange Admin Center > Servers > DNS Lookups > Internal DNS Lookups --> Added the IP Address of the DNS Server -Modified the hosts file under System32 > drivers > etc --> Pointed the IP Address of the Exchange Server to the FQDN of the Exchange Server Currently, are not sure of the next steps to do in order to fix the issue. Any advice?Ross_123Dec 05, 2025Copper Contributor43Views0likes2CommentsHelp please! Exchange report questions
Hello! I’m hoping someone can help clarify a few things about a deletion report I received. The report shows hard and soft deletes, but it seems to be missing information about moves and restores. I’m trying to understand the following: 1. **Hard Deletes:** * When something is hard deleted, does it go to the Purge folder, and is it still recoverable from there? * Is a “hard delete” simply what happens when someone empties their Deleted Items folder? * Can hard deletes happen accidentally? 2. **Limitations of the Report:** * Are there other reports that can show moves, restores, or whether an item is *currently* deleted? * My understanding is that this delete report only indicates that an item was deleted at some point, not its current status. Is that correct? 3. **Missing Message IDs:** * About half the entries in the report don’t include a message ID. Am I correct in assuming those items aren’t emails? If anyone is willing to chat or walk through this with me, I’d really appreciate it — I’m hoping to understand this report better. Any guidance or links to solid documentation would be truly appreciated. Thank you!21Views0likes1CommentEWS Autodiscover Process in Hybrid with "internal" Exchange Servers
Hi everyone, i really need help about the EWS Autodiscover process in a specific hybrid Environment. Customer is starting to use Exchange Online. For Full Hybrid configuration there is a seperate new Exchange SE with a valid certificate, NAT for IP Ranges from M365 and public available URLs for Autodiscover,EWS,... There are internal Exchange Servers which are used only for internal access. Those are the servers with all mailboxes. All URLs are configured for internal use (mail.contoso.internal) Migration is working, access to own calender is working, mailfllow is working. But there are problems to access other users calender. If a user which is migrated to Exchange Online (or via Teams) try to access another calender which is onPrem, there is no access. So i tried to use connectivity analyzer for teams integration to find out whats the problem. Result: Autodiscover resolves, connects to Hybrid and gets EWS URL as answer. But it gets the internal EWS URL from the internal Exchange Servers, not from the public available URLs which are configured at the hybrid server. I visualised the two scenarios. Number1: Thats how i thought it would work Autodiscover to autodiscover.contoso.com Hybrid answers with EWS URL: hybrid.contoso.com Connect from EXO to hybrid EWS URL Proxy to Internal Exchange Number2 : Thats what really happens Autodiscover to autodiscover.contoso.com Hybrid relays request to internal Exchange (Mailbox Server) Server answers with internal EWS URL: mail.contoso.internal Connect from EXO to internal EWS URL (which is obviously not working) So as you can see, the autodiscover process asks the internal Exchange for its EWS URLs and not as i expected the hybrid server's URLs. I always thought, the hybrid server works as a sort of proxy for every external connection from EXO. But it seems that the hybrid just relays the autodiscover request to the server which holds the mailbox. And this servers in this scenario cannot change their EWS URLs to a public resolvable FQDN. So my question is: Is this correct? Does the process always works like this or did i do anything wrong in the configuration? I hope you understand my explanation. Thanks in advance!!!40Views0likes4CommentsRemove Classic EAC Organization Add-ins?
Hello, Does anyone know how to remove the organization add-ins that were deployed with the Classic Exchange Admin Center? Now that the "classic view" is no longer accessible, our tenant shows a 400 Bad Request error when trying to go to "https://outlook.office.com/ecp/". This org add-in is pushed to all mailboxes by "organization administrators", and as far as I can tell, there isn't a way to remove the add-in. This legacy add-ins are not visible in the new "Integrated Apps" in O365. I contacted Microsoft Support but the support agent got to the point where he was having me run PowerShell commands to check the registry to see if it was "installed as a program on my computer", and that's when I knew he had exhausted his support resources. I can see the app if I execute: Connect-ExchangeOnline as a Global Admin & Tenant Admin (Exchange Online Role) and then run the Get-App | select DisplayName, AppID cmdlet. If I try to remove it Remove-App -Identity <AppID>, then I see a: Write-ErrorMessage : |Microsoft.Exchange.Data.ApplicationLogic.Extension.OwaExtensionOperationException|The app "Alert" is managed by organization administrators and can't be uninstalled by end users. If I check the Exchange Online roles, I am in the TenantAdmins_3744d role, which states that "it will be a member of the Organization Management role group and will inherit the capabilities of that role group". So far I have no way to remove this old add-in which normally was installed/uninstalled through Organization > Add-Ins in the Classic (Legacy) Exchange Admin Center.rmoatDec 03, 2025Brass Contributor2.4KViews0likes5Commentsnew Exchange Installation Autodiscover
Hi I have had a lab environment and suspended this to get experience with a new setup. Old setup had a ADFS server in place. New lab setup is based on Windows Server 2025, 1 DC, 1 Exchange server SE. Installation is ok. Client is a Windows 11 machine with Outlook 2019. DC is synching to EntraID. All based on German language. GPO for autodiscover is set. As well the DNS records. Post installation is the part where I am have an issue at. At least in the part of the autodiscover. Adding the primary mail address is always leading in pointing to the company authentification page adfs.xy.com which was in the old lab in place. I cant see any DNS entry neither on my external DNS provider nor internal (brand new setup) and have no clou where to search further. Wensearch did also not lead me to any solution. And a workaround to disable autodiscover is not my goal. Therefore I am happy to get any idea where to look at to get read of the adfs link. Appreciate your support. THY mameSolvedMame MeierDec 01, 2025Copper Contributor226Views0likes5CommentsExchange SE and Domain / Forest Functional Level 2025 Support
Does anyone have any general idea on when they may test support for Domain / Forest Functional Level 2025? We're still rocking hybrid with Exchange SE and ExO and as such we're waiting on the supportability matrix (https://learn.microsoft.com/en-us/exchange/plan-and-deploy/supportability-matrix#supported-active-directory-environments) to get updated so we can raise the DFL/FFL. Currently Exchange SE supports 2025 AD servers so they've verified the schema update from 88 to 91 is good to go but our Exchange team doesn't want us to raise the functional level until this matrix shows that it's supported for our current Exchange version. Thanks for any insight. Supported Active Directory environments The following table lists the supported Active Directory environments for Exchange Server. Version Active Directory servers Forest Functional Levels Exchange Server SE Windows Server 2025 Windows Server 2022 Windows Server 2019 Windows Server 2016 Windows Server 2012 R2 Windows Server 2016 Windows SI_triedNov 30, 2025Copper Contributor177Views1like1CommentI am receiving DMARC errors
Hello Please i need your help on this issue. Last night I started receiving DMARC and other errors when trying to send emails. I dont believe my business email is receiving messages either. Please help me 'fix' resolve these bounce back errors. I did try to find the solution on my own,, but its just out of my wheelhouse. Please help as my business is being affected by these errors and bounce backs.IBN22Nov 30, 2025Copper Contributor51Views0likes1CommentConfigure Dedicated Exchange Server Application
Currently our product ranning exchange 2019 CU15 with Exchange hybrid, so what else need configure other task for configuration of the dedicated application for Exchange Server. HCW8126 - Admin consent was not granted during the configuration of the dedicated application for Exchange Server. The application will be created but will not function until consent is provided. Please re-run the Hybrid Configuration Wizard (HCW) or grant consent via the Entra ID portal before using the application.JackLee1222Nov 30, 2025Copper Contributor75Views0likes1CommentWe have set RejectDirectSend to true
Hello Please i need your help on this issue. We have set RejectDirectSend to true, but it is still possible to send mail anonymously through tenant Last Friday 3 oct 2025 we configured the tenant not to allow DirectSend from anonymous sources by setting the RejectDirectSend value to true using Powershell command. When we check the status with the Get-command it looks like it is set but it is not working - it is still possible to spoof emails by sending through the mx record as anonymous.IBN22Nov 30, 2025Copper Contributor43Views0likes1Comment
Resources
Tags
- exchange online2,579 Topics
- Exchange Server2,347 Topics
- office 3651,253 Topics
- hybrid904 Topics
- outlook780 Topics
- 2016760 Topics
- admin685 Topics
- 2013279 Topics
- 2010160 Topics
- 201982 Topics