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-1
Microsoft 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 o365Allow MessageClass Filtering in Default Folder Retention Tags in Exchange Online
What do other Microsoft 365 Exchange Oline Admins think about this. While implementing online archiving the current filtering of message types is hindering adoption for Online Archiving. Summary:I Exchange Online currently restricts the -MessageClass parameter in default folder retention tags to only * or VoiceMail. This limitation prevents administrators from applying retention policies that target only standard email messages (IPM.Note)—a critical need for organizations that want to archive email while preserving user-facing data like calendar items, tasks, and notes. Problem: This restriction: Forces the archiving of non-email items (e.g., calendar invites, tasks, notes), which are often small in size but essential to users. Breaks user workflows by making these items inaccessible in the archive. Undermines compliance strategies by preventing precise policy enforcement. Renders personal tags ineffective in environments where users are not trained or incentivized to apply them. Impact: Compliance Risk: Organizations cannot enforce retention policies that reflect their actual compliance requirements. User Experience: Critical calendar and task data becomes inaccessible in the archive, leading to confusion and support overhead. Administrative Burden: Workarounds (e.g., mailbox rules) are fragile and inefficient. Reputational Harm: These limitations reduce trust in Microsoft 365 among educational institutions and other sectors. Proposed Change: Allow the -MessageClass parameter in default folder tags to accept: IPM.Note (standard email) Other valid message classes (e.g., IPM.Appointment, IPM.Task) as needed Custom values where applicable Justification: The retention engine already supports MessageClass filtering in personal tags—this is a policy restriction, not a technical one. Granular control enhances compliance, not weakens it. This change would align Exchange Online’s retention capabilities with real-world organizational needs.Enable Outlook and To Do Clients to Surface Archived Items
Description: Exchange Online’s retention architecture currently forces the archiving of calendar items, tasks, and notes when default folder tags are applied with MessageClass = '*'. However, Microsoft Outlook (on the web, Mac, and PC) and the Microsoft To Do app do not surface these archived items, resulting in a broken user experience and loss of access to critical data. Problem: Calendar items, tasks, and notes that are archived via retention policies become invisible to users in Outlook and To Do. Users are unaware that these items have been archived, leading to confusion and support requests. The Microsoft To Do app, which replaces legacy task workflows, does not integrate with the Exchange Online Archive, making archived tasks inaccessible. Outlook clients do not provide visibility or searchability for archived calendar and note items, even though they remain stored in the archive. Impact: User Experience Breakdown: Users lose access to important calendar and task data without warning. Support Overhead: IT teams must explain and troubleshoot why items “disappear” from view. Compliance Confusion: Organizations applying retention policies for email only are forced to archive unrelated item types due to Exchange Online limitations. Feature Inconsistency: Microsoft’s own apps (Outlook, To Do) do not fully support the data lifecycle created by Exchange Online’s retention engine. Proposed Change: Update Microsoft Outlook (Web, Mac, PC, iOS, Android) and Microsoft To Do to: Surface archived calendar, task, and note items from the Exchange Online Archive. Provide clear indicators and search capabilities for archived items. Ensure that retention policies do not result in silent data loss from the user’s perspective. Justification: This change would restore visibility and trust in Microsoft’s compliance and archiving tools. It aligns client behavior with backend retention logic. It reduces support burden and improves usability across Microsoft 36
