Recent Discussions
Help~After installing Exchange 2019, mail is stuck in Draft in OWA
Hi all I dont undertand this symptom. Now I installed one new DC, one new Exchange 2019(CU13) in active directory domain. and I just set recieve connector(check anonymous user in Default Exchange) and created send connector and I sent mail to my own mailbox(administrator), and I also sent mail to other mailboxes, but I only have stuck Draft folder in OWA. before install Exchange 2019 CU13, I installed Exchange 2029 CU15 but it was same symptom so after removing Exchange 2019 CU15, I reinstalled Exchange CU 13. but it was same. DC and Exchange OS are Windows Server 2022 Standard on Dell H/W. ipv4 192.168.10.202 subnet 255.255.255.0 GW 192.168.10.1 Dns1 192.168.10.201(DC) It's the same as the link below, but there's nothing solved. T.T https://www.reddit.com/r/exchangeserver/comments/1daxga2/exchange_server_2019_emails_get_stuck_in_drafts/#:~:text=Here's%20some%20information%20about%20emails%20getting%20stuck,lots%20of%20space%20may%20not%20always%20work. If anyone knows how to solve this problem, please help me
Exchange Server 2019 to Subscription Edition (SE) Licensing and Migration Guidance
1. Current Infrastructure Setup Component Detail Notes Product Microsoft Exchange Server 2019 Enterprise Edition Servers 3 Virtual Servers (VMware) Configured in a Database Availability Group (DAG) Version Cumulative Update (CU) 15 Licenses Server License and 1100 CALs (Standard/Enterprise) Purchased in 2019 without Software Assurance (SA). 2. Core Licensing and Compliance Queries We require definitive guidance on the following compliance and purchase requirements: Software Assurance (SA) Requirement: Is Software Assurance mandatory for our existing Exchange Server 2019 setup for ongoing compliance and full support? Please advise on the status of our current setup without SA. Standalone SA Purchase: As our Exchange Server licenses/CALs were purchased in 2019 without SA, is it possible for us to purchase standalone Software Assurance for our existing Exchange Server 2019 licenses now, or must we purchase a completely new license with SA? Client Access License (CAL) Migration: Will our existing Exchange Server 2019 Standard/Enterprise CALs be compatible and automatically migrate to the Subscription Edition (SE) requirement, or must we purchase new CALs specifically for Exchange Server SE? Please clarify if the old CALs will become obsolete. 3. Recommended Migration Path (Budgeting Focus) Based on the licensing realities, we need advice on the most financially responsible path to move to Exchange Server SE. Please guide us on which of the following scenarios is recommended: Option A: Purchase Software Assurance for our existing Exchange Server 2019 infrastructure, and then migrate to SE, utilizing the same 2019 CALs (if permissible). Option B: Forego purchasing SA for the 2019 environment and directly purchase new Exchange Server Subscription Edition (SE) licenses and corresponding new CALs (if necessary). We look forward to your detailed guidance to ensure full compliance and a smooth transition to Exchange Server SE. Thank you, Narayan Das Senior System AdministratorGames hardware vendors play
Regretfully, some hardware vendors continue to play games with the server and storage configurations they publish through Microsoft's ESRP (Exchange Solution Reviewed Program). Of course, the solution isn't really reviewed in any realistic sense of the word... https://www.petri.com/games-vendors-play-exchange-hardware-configurations
Exchange synch/profile issue
Dear community, I need help to solve a problem. 1.) I'm using Outlook classic 2016 2.) I need two mail accounts in outlook a.) my gmail account - all good with that one b.) my AWS Workmail account 3.) all used to work fine till I had another problem with teams integration into my calendar which I tried to fix without success. After a while I thought, that when I setup outlook from scratch that this could solve the problem - but it got worse. 4.) when I started the newly installed outlook, I can load my gmail account, and when I add my AWS Workmail account, I get the message that the account was successfully added and need to restart Outlook. 5.) After the restart I get the two messages: - The name cannot be matched to a name in the address list. - Cannot start Microsoft Outlook. Cannot open the Outlook window. The set of folders cannot be opened. An unexpected error has occurred. 6.) so the AWS Workmail is not loaded. I also tried to add the account manually in all different ways but without success. The integration of the AWS mail account on my Android Outlook works perfectly fine. I dont know where the problem is and tried to get answers from AI and Microsoft Support without success. Anyone has an idea? Many thanks, Rob
Arbitration mailbox
Issue: Arbitration Mailbox Issue During Exchange 2016 to 2019 Migration. Environment Overview: Mixed Exchange environment: Exchange 2016: EX1-16, EX2-16, DR1-16, DR2-16 Exchange 2019: EX1-19, EX2-19 Currently migrating mailboxes from Exchange 2016 to Exchange 2019. Issue Description: One system mailbox was found on an orphaned Exchange server and i removed manually. Post-removal, errors were observed related to the Migration and Federation arbitration mailboxes. Both mailboxes appeared under the User container but were not functioning correctly. A user-type mailbox with the display name “Migration” appeared. I thought this may cause issue with arbitration mailboxes. Remediation Steps Taken: Removed the user-type mailbox with the display name “Migration.” Manually removed both FederationMailbox and MigrationMailbox objects. Verified that the Exchange Trusted Subsystem has correct permissions on the Microsoft Exchange Security Objects (MSEO) container. Executed Setup.exe /PrepareAD, Its Re-created the Federation and Migration related users. Executed the following command to enable the arbitration mailbox: Enable-Mailbox -Identity <GUID-of-MigrationMailbox> -Arbitration (command executed successfully). Current Problem: Despite successful execution of the Enable-Mailbox command, the msExchRecipientTypeDetails attribute is not updating to the expected value. Current value: 8388608 and display name also looks wrong because its show “Microsoft Exchange Approval Assistant” seems to be incorrectly tied to the migration mailbox. This issue is preventing proper functionality of the migration mailbox, and as a result, the remaining mailboxes cannot be moved from Exchange 2016 to Exchange 2019.new 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 mameUse PowerShell to Analyze Junk Email and Intercept Traffic from Spammy Domains
Despite the best efforts of anti-spam solutions, some unwanted messages usually get through to user inboxes. This article explains how to analyze messages that end up in Junk Email and use the results to create a transport rule to block future traffic from the spammy domains. https://practical365.com/analyze-junk-email-block-spammy-domains/Policy for limiting external domains and allowing particular external receivers
Hi community, According to the guide https://learn.microsoft.com/en-us/defender-office-365/outbound-spam-policies-external-email-forwarding i have created the following rule for our test domain: Rule description Apply this rule if 'X-MS-Exchange-Inbox-Rules-Loop' header matches the following patterns: '.' Do the following Set audit severity level to 'Medium' and reject the message and include the explanation 'Delivery not authorized, message refused' with the status code: '5.7.1' Except if recipients's address domain portion belongs to any of these domains: 'xyz.com' Rule Idea is to block all external mail forwardings except the ones directed to the domain xyz.com. ______________________________________________ Another rule testing i performed: Apply this rule if Is sent to 'Outside the organization' and sender's address domain portion belongs to any of these domains: 'localdomain.com' Do the following Set audit severity level to 'Medium' and reject the message and include the explanation 'external forwarding is not allowed' with the status code: '5.7.1' Except if recipients's address domain portion belongs to any of these domains: 'xyz.com'. Unfortunately this is not working and if i create mailbox-based rules that forward to mails lets say to gmail and to xyz.com both , the mails get dropped with explanation: Reason: [{LED=250 2.1.5 RESOLVER.MSGTYPE.AF; handled AutoForward addressed to external recipient};{MSG=};{FQDN=};{IP=};{LRT=}] For both cases i made sure the auto forwarding is enabled under "anti spam" rules in the security admin center. I receive in the mail flow logs messaged dropped for a mail located in xyz.com and in gmail.com. The forwarding configured in outlook on a mail from localdomain.com is intended to auto forward messages to a mail address in gmail.com and in xyz.com, where they mails should arrive. I am wondering what would be the correct policy in order to being able to except particular ext domain/ext mailbox. Another approach i found is to disable the auto fwd globally and to enable it for particular users only, but unfortunately can not be limited to whom the mailbox can forward and this is not useful solution for us. Regards Sofia
Problem with Teams and Exchange Integration
Hi everyone, My goal is to integrate Exchange Server (Exchange 2016 CU23) with Teams so that the Teams calendar can be used. I have set up Hybrid Configuration (Classic Full Hybrid) and completed the setup without any errors. I have also checked Entourage, and it shows that Exchange has been registered, but the Teams calendar is still not working. Check items: 1. Get-AuthServer 2. Get-IntraOrganizationConnector → Confirm the "Enabled" status. 3. Get-PartnerApplication → Confirm it's enabled. 4. External resolution of the Autodiscover and EWS virtual directories 5. Run Teams Exchange Integration → The only thing that works is "Verifying if the user's mailbox is discoverable by the Teams service," and everything else is fine.The user's mailbox is not discoverable by the Teams service. Please ask your administrators to verify the user has a mailbox and to confirm the connectivity between Teams and Exchange. Does anyone have any other ideas or suggestions to help me? Thanks!
Free/Busy Hybrid Exchange 2019
Hello everyone, I have a hybrid environment with Exchange Server 2019, with a dedicated Exchange application, we renewed the Exchange Auth certificate and then re-ran the HCW, however, free/busy is not working for 365 Pro local users. Has anyone had this problem? Could you help me?
Multiforest migration to Office 365
Hi Community, One of our customer has the below environment: Goal: All below forests needs to be synchronized to a single office 365 tenancy ( which could be a brand new tenancy ) so they can keep single email name space, single SharePoint, single one drive organisation for all forests. FOREST A Exchange 2013 on-prem and EXO in Hybrid ADFS is installed to sync Security enabled AD groups to O365. Users using SharePoint Multiple sites and OneDrive SSO enabled by ADFS, no write back 2250 mailboxes hosted in EXO FOREST B Local AD in on-prem No hybrid AAD sync installed to sync to O365 1700 mailboxes hosed in EXO No SPO/OneDrive users FOREST C Local AD in on-prem No hybrid AAD sync installed to sync to O365 1800 mailboxes hosed in EXO No SPO/OneDrive users FOREST D on-prem Exchange 2013 500 mailboxes hosted on-prem Questions: How can we plan for it? Any Best practices? Many thanks in advance.Migration Exchange 2016 to 2019 then SE
Hello, we replaced our old Exchange 2016 Server, to Exchange SE. After the update users notified me, that the search is taking long. We also have a lot of Errors in the Eventlog 3056 Scenario: UpdateMasterTable. The app master table could not be saved due to a conflict. Mailbox: x Error: Property conflict: DisplayName: 'BigFunnelPoiNotNeededReason', Resolvable: 'True', OriginalValue: 'Object is null', ClientValue: '2', ServerValue: '2' Property conflict: DisplayName: 'BigFunnelCorrelationId', Resolvable: 'True', OriginalValue: 'Object is null', ClientValue: 'Property: [{0b63e350-9ccc-11d0-bcdb-00805fccce04}:'BigFunnelCorrelationId'] BigFunnelCorrelationId, PropertyErrorCode: NotFound, PropertyErrorDescription: .', ServerValue: 'Property: [{0b63e350-9ccc-11d0-bcdb-00805fccce04}:'BigFunnelCorrelationId'] BigFunnelCorrelationId, PropertyErrorCode: NotFound, PropertyErrorDescription: .' Property conflict: DisplayName: 'BigFunnelIndexingStart', Resolvable: 'True', OriginalValue: 'Object is null', ClientValue: 'Property: [{0b63e350-9ccc-11d0-bcdb-00805fccce04}:'BigFunnelIndexingStart'] BigFunnelIndexingStart, PropertyErrorCode: NotFound, PropertyErrorDescription: .', ServerValue: 'Property: [{0b63e350-9ccc-11d0-bcdb-00805fccce04}:'BigFunnelIndexingStart'] BigFunnelIndexingStart, PropertyErrorCode: NotFound, PropertyErrorDescription: .' Property conflict: DisplayName: 'BigFunnelMessageUncompressedPOIVersion', Resolvable: 'True', OriginalValue: 'Object is null', ClientValue: 'Property: [0x36660003] BigFunnelMessageUncompressedPOIVersion, PropertyErrorCode: NotFound, PropertyErrorDescription: .', ServerValue: 'Property: [0x36660003] BigFunnelMessageUncompressedPOIVersion, PropertyErrorCode: NotFound, PropertyErrorDescription: .' Property conflict: DisplayName: 'BigFunnelPOIContentFlags', Resolvable: 'True', OriginalValue: 'Object is null', ClientValue: 'Property: [0x36630003] BigFunnelPOIContentFlags, PropertyErrorCode: NotFound, PropertyErrorDescription: .', ServerValue: 'Property: [0x36630003] BigFunnelPOIContentFlags, PropertyErrorCode: NotFound, PropertyErrorDescription: .' Property conflict: DisplayName: 'BigFunnelPOIUncompressed' Does somebody know how we can fix this problem? We find already that article that is similar but the workaround for the search (not the mirgration) doesnt work for us. We need Outlook cached. https://learn.microsoft.com/en-us/answers/questions/5508363/outlook-search-not-working-reliably-after-exchangeEmails delayed or not received.
Hello Please i need your help on this issue. Emails delayed or not received. We have noticed that since last Friday (3rd Oct) emails sent to @livener.net addresses have been delayed or not received. This is using the Outlook app, Apple Mail App and Outlook Online.so I do not believe it is a client issue. In particular a mail from massenzana @runeXXXX to Tony @liveXXXXX and Bernie @liveXXXXX on Friday evening has not been received. It was received by other recipients. Test mails from Tony @gmailXXXX to Tony @liveXXXXX and bernie @liveXXXXX sent at approx 09:40 have not been received. A mail from Bernie @soundXXXX sent at 07:02 this morning arrived at Tony @liveXXXX at 09:49Why would a hacker/scammer put a domain INTO my exchange online admin?
OK so this is a weird one. I've been doing this a fairly long time but I'm not a full time exchange admin. I help my clients with exchange online often, but I'm a local IT pro, doing all sorts of screwdriver and software work, not just exchange. So maybe this isn't as bizarre as I think it is, but let's see. My client stopped receiving email 2 days ago. Alerted me to it yesterday. They don't know their password but no devices are asking for passwords, so I suspect it's not a password issue. I get logged into my admin and reset their password so we can get into their account. Suddenly they start getting asked for PW on phone and outlook, so we know that the password hadn't been changed prior. I get into account and see new rules sending all emails into archive and trash. So that explains that. So someone broke into the account with the correct password. Easily enough explained. Though weird that it would happen if the user didn't know their own password. So, one question is how did the scammer get into the account. I have looked at the login logs but I don't know what to sort/filter by to really find out anything helpful. Any ideas? So I got into the account and upon resetting his password he is forced to enable MFA. So that's done. I'm in the admin and what do I find? Two NEW domains in the settings. They are set up for exchange online. No users though. Not only that but I can't REMOVE the domains that aren't mine. I get this error when trying to remove it: "The domain coburnsfleetservices.com can't be removed at this time because it was purchased from Microsoft 365. It can only be used with your current Microsoft 365 account. You can remove it from the account once the subscription expires or is canceled." Also, in the emails missed in the past 48 hours we got one that said this: "A verified domain was added to your Avenue A Realty Advisors LLC account If this domain wasn't added by an admin in your organization, credentials might have been compromised and we suggest reviewing your password and multifactor authentication settings." I searched online and found contact info for one of the stolen/given domains. Called them and they said they had been hijacked 2 weeks ago, and their email used to send out payment requests to thousands of email addresses. Thought they had it solved a few days ago and it had been silent. Now this. So a second thing I'd like to find out is when exactly those domains were put into my exchange online account. Can I find that info from the logs? Additionally, WHY would someone move unrelated domains into my account? Maybe is the assumption that that happened before 2 weeks ago when that company's domain had been used to send out mass mail? Doesn't seem possible, because that company would have figured out that they no longer controlled their own domain and they couldn't have gotten control of the account again. Or...? I don't know. But while I've seen users tricked into giving out their passwords dozens of times, and their email used to try to solicit money from vendors, I've never seen another domain slipped in. Any ideas? And suggestions how to search the logs to get to the bottom of the missing puzzle pieces? Thanks for any leads!
M365 Business Standard - Email Aliases not displaying how we would expect
New Microsoft 365 Business Standard and setup custom domain (example: testdomain . com) One User and test @ testdomain . com Setup one alias alias1 @ testdomain . com Per this link: https://learn.microsoft.com/en-us/microsoft-365/admin/email/add-another-email-alias-for-a-user?view=o365-worldwide I can add an alias the document claims the user can send out as the alias: Your users can now send from their aliases when using Outlook on the web. When the Set-OrganizationConfig -SendFromAliasEnabled $true cmdlet is set, users within the organization will get access to a list of checkboxes where each entry corresponds to an alias in their Outlook settings. Selecting an alias will make it appear in the From dropdown in the Compose form. I did this and confirmed it is enabled. I then went to Outlook web and did not see the aliases to pick from, but found I needed to go into Settings / Compose and Reply / Addresses to Send From I now see the from drop down: HOWEVER, the recipient (some of my gmail accounts or other test accounts) do NOT see it coming from the alias, but looks like it comes from my primary user @ mydomain . com vs the alias1 @ mydomain . com. If the recipient digs into the message header you cannot see it from the alias either. QUESTION 1 So WHAT needs to be done so when the recipient receives the email it looks like it came from the alias. QUESTION 2 A sender sends me an email to alias1 @ mydomain . com and it does arrive in Outlook Web, BUT it looks like it came to my primary test @ mydomain . com. IF I dig into the message header behind the scenes I do see it was sent to the alias. HOW can I have Outlook Web display that it was to the alias email and not the primary email? I probably could create rules to tag and or move to folders, but it would be nice to just easily tell in the client. Thanks in a advance! GregResolved: Hybrid Exchange Duplicate (Ghost) Mailbox Created After Assigning Exchange Online License
Summary During a hybrid Exchange migration, a user’s mailbox failed to migrate and mail flow broke due to a duplicate (ghost) mailbox automatically created in Exchange Online. Root Cause An Exchange Online Plan 2 license was mistakenly assigned to the user before migration. Azure AD sync then provisioned a cloud mailbox, even though the user already had an on-prem mailbox. This caused a hybrid mismatch — the user appeared in both environments, and migration failed with mailbox lookup errors. Resolution Steps Removed the Exchange Online Plan 2 license from the user account. Forced a DirSync (AAD Connect) synchronization. Verified that the mailbox existed only on-prem via PowerShell Get-Mailbox -Identity email address removed for privacy reasons | fl Name,RecipientTypeDetails,ExchangeGuid Confirmed the ghost mailbox was removed from Exchange Online. Re-ran migration batch successfully to Exchange Online. Verification Get-MailboxStatistics -Identity email address removed for privacy reasons | fl TotalItemSize,ItemCount,LastLogonTime Ensure only one mailbox object exists and mail flow routes correctly. Prevention Tips Don’t assign Exchange Online licenses to hybrid mailboxes before migration. Always verify mailbox location prior to assigning any license. Use PowerShell or EAC to check where the mailbox resides (on-prem vs. cloud). Environment Hybrid Exchange Deployment Exchange 2016 On-Premises Exchange Online (M365) Azure AD Connect This issue is not caused by connectors or mail flow settings, but by improper licensing before migration. Removing the license and resyncing resolves the ghost mailbox problem.Multi-Tenant Microsoft Exchange Online support
Company I am working for is in the process of migrating our Exchange on premise clients to Microsoft Exchange online. We are partnering with Pax8 for licensing portion of it as well as Microsoft technical support. I want to be able manage all of these tenants through a single interface so we can control access to that select set of accounts so as technicians come and go in our team, we can manage access to that single interface. Wonder what 'best practice' would be in this scenario.
Recent Blogs
- We wanted to learn if there is interest to bring Copilot functionality to on-premises email.Oct 22, 2025
- Office Online Server retirement date has been Announced.Oct 21, 2025
