Exchange 2016 to SE and Exchange Online questions
Hi, We're currently in the process of migrating from Exchange 2016 to Exchange Subscription Edition (SE), along with moving a portion of our mailboxes to Exchange Online. We have approximately 3,000 mailboxes, and around 2,000 of those will eventually end up in Exchange Online—for various reasons (don’t ask why…). I have a few questions I'd like to clarify and hope you can assist: Exchange On-Premises Questions: If a user mailbox is moved to Exchange SE, can they still access shared or user mailboxes that remain on Exchange 2016? Do we need to migrate them in the same batch to preserve access/permissions? (should't be an issue in the same Exchange Org right?) If a shared mailbox is migrated to Exchange SE while the user mailbox remains on Exchange 2016, will access still work? Do we need to point the Hardware Load Balancer (HLB) to the new Exchange SE servers before mailbox moves to allow proper client connectivity and proxying back to Exchange 2016? Or is it okay to keep the HLB pointed to the Exchange 2016 servers until all migrations are complete and then switch it over? Proxy upwards from Exchange 2016 to Exchange SE? What’s the best practice here? Pros/cons? Exchange Online Questions: If we want all outbound mail to go through the on-prem Exchange environment—even for Exchange Online mailboxes—is this configured via the Hybrid Configuration Wizard (HCW)? Is the Litigation Hold status preserved when migrating a mailbox to Exchange Online? Can a mailbox hosted in Exchange Online access a shared mailbox still residing on-prem? (Should't be an issue right?) Can an on-prem mailbox access a shared mailbox that has been migrated to Exchange Online? For mailboxes with Full Access or Send As permissions (e.g. user mailboxes tied to shared mailboxes), do they need to be migrated together in the same batch to retain functionality? We’ll be using native Microsoft migration tools (no 3rd-party solutions). If I recall correctly, separate migrations will still allow Full Access?!?, but Send As may not work properly unless migrated together. Is that still accurate?Migrating on-prem functional shared mailboxes to 365
I have an on-premises Exchange environment (SE Edition) with Edge servers, configured in a hybrid setup. New users are provisioned directly in Office 365, but many legacy users still exist solely on-premises. In addition, we have around 800 shared/functional mailboxes that are local and were not created as hybrid objects. I need to migrate these on-prem shared mailboxes to Office 365. I’m unsure of the best approach—should I: Convert them to full hybrid and migrate using the hybrid tools? Recreate them manually in Office 365? Or is there another recommended method? My goal is to make the transition as seamless and transparent as possible for users, while keeping the process simple and efficient on the admin side.
How to consistently differentiate Microsoft service notification emails from normal user emails?
I receive a large number of notification mails from Microsoft services (SharePoint, Teams, etc.) and they clutter my mailbox. I’ve tried: Inbox rules filtering by sender (e.g., email address removed for privacy reasons) → doesn’t work since Microsoft uses many changing domains. Filtering by Microsoft IP ranges → some internal org mails also get caught. Filtering by domains from Microsoft endpoint list → works, but the list updates monthly, so not reliable. Question: Is there a consistent way (e.g., via Internet message headers or any other property) to reliably identify Microsoft-generated notification emails vs normal user emails?
Licensing question: Exchange Server SE for CSP M365 E3/E5 customers without Extended Use Rights
Does anyone have any information on licensing the new Exchange Server SE for customers who have M365/O365 E3/E5 purchased via CSP but do not have Extended Use Rights (i.e., no EA/EAS -> no on-prem Office server licenses included)? Specifically: Is it enough to license Exchange Server SE per node only, or Do customers also need to purchase Exchange Server CALs per user (even if they already have M365 E3/E5)? I’ve spoken with multiple licensing distributors and a Microsoft partner contact, but I still haven’t been able to get a definitive answer. According to a comment from Jeremy Carlson and Microsoft’s licensing documentation, certain licenses appear to include "CAL-equivalency rights". Can anyone here confirm whether these CAL-equivalency rights cover access to Exchange Server SE in the CSP E3/E5 (no Extended Use Rights) scenario? licensing reference: https://www.microsoft.com/licensing/terms/product/CALandMLEquivalencyLicenses/MCA#clause-2165-h3-1Microsoft some server IP not in SPF List?
We Have add DNS record v=spf1 include:spf.protection.outlook.com -all , but find to SPF is failed spf:demo.com:2603:1096:301:11b::15 how can we solve this problem , because we need increase the security Level , would like quarantine / set to junk mailbox for SPF Fail mail Thank
Exchange 2019 Mailbox Migration Error - Folder conflicts with Exchange Online folder
Hi Exchange Experts, I'm migrating a small Exchange 2019 environment to 365. Been pulling my hair out becuase of just one mailbox giving this error Error description --------------------------- Error: AggregateMailboxFolderConflictPermanentException: The folder 'Files' conflicts with Exchange Online folder 'Files', please move the messages to another folder and restart the job. Data migrated: 0 B (0 bytes) Migration rate: -------------------------------------- Migration user report: 5/14/2025 12:32:05 PM [MEUP300MB0105] Request processing continued, stage CreatingFolderHierarchy. 5/14/2025 12:32:05 PM [MEUP300MB0105] Stage: CreatingFolderHierarchy. Percent complete: 10. 5/14/2025 12:32:12 PM [MEUP300MB0105] Stage: CreatingFolderHierarchy. Percent complete: 10. 5/14/2025 12:32:12 PM [MEUP300MB0105] Fatal error AggregateMailboxFolderConflictPermanentException has occurred. ---------------------- It seems to be a system folder and I've tried to remove files from it (although there're no files in it) using MFCMAPI tool with no success. Renamed the folder and tried to re-run the migration with no luck. Has anyone experience this issue? any thoughts or tips are much appreciated ! Thank you.
Unable to Add Exchange 2019 Email Account (Ionos) to Outlook (New) on Windows 11
Hello everyone, unfortunately, I am unable to add my Ionos (Exchange 2019) email account to the Outlook Windows app. On Windows 10, it was still possible to manually configure an Outlook account, which worked fine. However, on Windows 11, this option is no longer available, and I can’t revert to the previous version of Outlook either. When I try to add the account by selecting Microsoft 365 - Office 365, Exchange and entering my email address, I always get the error message: We couldn't find a work or school account with that email address. I have already contacted Ionos, but they couldn’t solve the issue either. They mentioned that Microsoft doesn’t allow setting up an Exchange account this way, even though the option is listed in the selection menu. Does anyone know how to fix that? Thank you very much!
Local domain mailbox migration error
I ran into an issue while migrating from on-premise to O365. On-premise AD domain is “domain.local” so users have their mailboxes smtp address as follows: primary smtp mailto:email%20address%20removed%20for%20privacy%20reasons ( public domain ) aliases smtp proxy: mailto:user@domain.local We setup the hybrid environment and started the mailbox migration but they’re failing with the error that domain.local is not an accepted domain in O365. this is the first time it occurred to us since we made a lot of migration so far What can it be ? obviously is not possible to add domain.local as accepted domain in o365
