New Outlook: "Changing the ImapRemoteServerInfo is not allowed" after host migration
Hi everyone! I've migrated my domain/mailbox from one IMAP host to another in May. It cannot be added to New Outlook for Windows — fails instantly with INVALID_CREDENTIALS INTERACTION_REQUIRED, even when I deliberately enter a wrong password (so it's failing before authentication is even attempted). Using DevTools (olk.exe -devtools), the Network tab shows the real rejection from Microsoft's backend: Changing the ImapRemoteServerInfo is not allowed. Attempted to change it from imap.olddomain.sk to imap.newdomain.sk So New Outlook has a cloud-mailbox / connected-account shadow record for this address, pinned to the old host from a previous add attempt, and the backend refuses to update it. What I've confirmed: Webmail and a second mailbox on the same domain/host both work fine → not credentials, not the host. The account does not appear in Settings → Accounts (so I can't use "Remove from all devices" which worked on my first account). It's on no other device or client. App reset didn't help (record is server-side, not local). It's been ~7 weeks, so any 30-day inactivity purge hasn't cleared it How do I get this stuck cloud-mailbox / connected-account record purged when it isn't attached to any removable account? Is there a way to force it, or does this need Microsoft backend action?New Outlook Comes With New Workflows: What Is Still Missing for You?
As a reminder, in March 2027, Enterprise organizations will enter the opt-out stage (Message ID 949965), where New Outlook becomes the default with the option to return to Classic Outlook. That is not too far away, especially if you need time to get your workflows and systems in place. That is why I keep coming back to this: New Outlook comes with new workflows. So I’m curious about where New Outlook workflows still fall short for you. A lot has changed. Users now have mail merge, Quick Parts, Unified Inbox, and partial PST support, with Advanced Mail Merge also on the way. New Outlook also has 30+ features and capabilities that are not available in Classic Outlook. What do you still do in Classic Outlook that you cannot accomplish, or cannot accomplish well, in New Outlook today? And if you tried New Outlook a year or two ago and went back to Classic Outlook, I’d be especially interested in what is still keeping you there now. I’m not looking for “I hate New Outlook.” I already know plenty of people do. I want to know the specific feature or workflow that still matters to you. PS: And be kind to me. I don’t work for Microsoft. I’m an MVP who teaches their products. 😉 traccreations4e-p26 8/26/2026
New Outlook Office.js Html body insert fails with error 9011 HtmlSanitizationFailure
I am building an Outlook web add-in for New Outlook on Windows. Calling mailbox.item.body.setSelectedDataAsync, prependAsync, or setAsync with CoercionType.Html fails with HtmlSanitizationFailure code 9011 on an empty HTML compose body, even for minimal Learn-style bold markup. CoercionType.Text works on the same client. Is 9011 a known New Outlook issue? Where is this error documented? What is the supported way to insert formatted HTML from an add-in?
Aptos preset font size in new installations
Hi, Can anyone confirm what the default Aptos font size in Outlook should be on first use, before any user changes are made to the settings? I’m seeing different default sizes depending on the application: 11 pt — Microsoft 365 Outlook for Windows (Classic) 12 pt — Microsoft 365 Outlook for Windows (New Outlook) 12 pt — Outlook for iOS 12 pt — Outlook for Android Based on the above, it appears that 12 pt may be the current standard default across most Outlook clients, with Classic Outlook for Windows being the exception. However, I haven’t been able to find any definitive Microsoft documentation confirming what the intended default Aptos font size should be. Can anyone confirm whether 12 pt is the official/default size?
Thousands of Sent Items moved to Deleted Items, no rules, no retention
Hello everyone, I'm investigating a very unusual Exchange Online mailbox issue and would appreciate any insights from anyone who has seen something similar. Environment Exchange Online (Microsoft 365) Mailbox: User mailbox Outlook for Mac Outlook for iOS Outlook Web (OWA) Incident Summary On August 13, 2026, approximately 4,997 messages were moved from: The activity occurred over roughly a 3-hour period. Mailbox audit logs show thousands of: Operation: MoveToDeletedItems events. Hourly breakdown: 01:00 - 2,046 events 02:00 - 1,540 events 03:00 - 1,408 events Audit Findings All sampled audit events show: LogonType = 0 (Owner) UserId = affected mailbox owner Result = Succeeded I sampled 5,000 records and all of them were: LogonType = 0 No events were recorded as: LogonType = 1 (Admin) LogonType = 2 (Delegate) Source and Destination Folders Examples from mailbox audit records: Folder : \Sent Items Destination : \Deleted Items Operation : MoveToDeletedItems Message Trace Findings Extended Message Trace was performed on one of the affected emails. The trace confirmed: CopiedToSentItems=True DeleteAfterSubmit=False which indicates: The email was successfully sent. The email was copied to Sent Items. Exchange did not delete the message during transport. So the message existed in Sent Items and was later moved to Deleted Items by a mailbox operation. Rules Investigation Checked: Get-InboxRule -Mailbox <mailbox> -IncludeHidden Findings: No Inbox Rules targeting Sent Items. No hidden Inbox Rules targeting Sent Items. Only two legitimate rules that delete messages from specific Jira/Confluence senders. Delegation Investigation Mailbox permissions reviewed. Known permissions exist, but mailbox audit logs show: 5000/5000 sampled events = LogonType 0 Therefore: No evidence of delegate activity. No evidence of administrative activity. Retention / Compliance Investigation Checked: Get-Mailbox Get-RetentionPolicy Get-RetentionPolicyTag Get-RetentionCompliancePolicy Get-RetentionComplianceRule Findings: No Sent Items retention tag. No retention policy targeting Sent Items. No Purview retention/compliance policy appears to explain this behavior. Activity pattern does not resemble normal retention processing. Add-ins Investigation Mailbox add-ins: Polls Share to Teams Send to OneNote Action Items Bing Maps My Templates Unsubscribe No third-party mailbox-management or archiving add-ins found. Client Information Seen During Investigation Examples observed in mailbox audit logs: Client=OutlookService;MacOutlook/16.112 a { text-decoration: none; color: #464feb; } tr th, tr td { border: 1px solid #e6e6e6; } tr th { background-color: #f5f5f5; } What Has Been Ruled Out ✅ Admin activity ✅ Delegate activity ✅ Inbox Rules ✅ Hidden Inbox Rules ✅ Outlook add-ins ✅ MRM retention policies ✅ Sent Items retention tags ✅ Purview compliance retention policies ✅ Exchange transport deleting the messages Question Has anyone encountered a similar case where: Thousands of messages were moved from Sent Items to Deleted Items Operation = MoveToDeletedItems LogonType = 0 (Owner) No rules No retention policy No delegate activity particularly involving: Outlook for iOS Outlook for Mac Client=OutlookService Any similar experiences, findings, or recommendations would be greatly appreciated. As we need to know the root cause for this issue. Thanks
The Unnecessary Complexity of Microsoft 365 & Outlook Classic: A UX Admin Nightmare for BYOD
I recently needed to remove a corporate Exchange account from a personal device running Microsoft 365. What should have been a one-click action exposed a deeply flawed and convoluted architecture: Primary Account Lock: Outlook Classic fundamentally prevents the removal of a "Primary Account" from its GUI. The only functional workaround is completely destroying the Outlook profile via the Control Panel or Registry. MDM Overreach on BYOD: When adding a work account, MDM and Entra ID policies immediately override local user control. There is zero clear exit strategy or automated cleanup for the end-user when that corporate relationship ends. Monolithic Click-To-Run Architecture: Attempting to simply uninstall the obsolete Outlook Classic application is impossible through standard Windows settings. It required deploying the Office Deployment Tool (ODT) and executing a custom XML configuration script just to exclude a single application from the Microsoft 365 suite. This forced integration and lack of modularity is a highly anti-user experience. Microsoft must separate corporate security enforcement from personal device ownership and provide standard, modular uninstallation options for its desktop applications. Forcing users to use PowerShell and ODT for basic software management is an unacceptable standard for modern UX.
Outlook.de DKIM and DMARC records broken
Outbound mail from outlook.de carries a DKIM-Signature with d=OUTLOOK.DE; s=selector1, but the corresponding DNS TXT record at selector1._domainkey.outlook.de does not exist. This causes receiving servers to report dkim=permerror (no key for signature). To reproduce: Send a mail from any @outlook.de account Check the DKIM-Signature header — it references selector1 Run: dig TXT selector1._domainkey.outlook.de — no record returned The domain outlook.de also has no DMARC record published (dmarc=none). Some header information: Received: by 2002:a05:6a11:e41c:b0:73b:6833:703f with SMTP id em28csp1732536pxc; Tue, 21 Jul 2026 07:23:10 -0700 (PDT) [...] ARC-Authentication-Results: i=2; mx.google.com; dkim=permerror (no key for signature) header.i=@OUTLOOK.DE header.s=selector1 header.b=mWWTJtqO; arc=pass (i=1); spf=pass (google.com: domain of email address removed for privacy reasons designates 2a01:111:f403:d20f::3 as permitted sender) [...] I leave out DNS this time as the discussion was marked as spam, but you can easily check it yourself: dig TXT selector1._domainkey.outlook.de and dig TXT _dmarc.outlook.de return no entries as all. So obviously the DNS records are not published. This leads to bad email reputation - so emails are either in SPAM folders or get rejected completely. Can someone from MS look into this and fix it. This is at least the case since June 2026 - see also https://borncity.com/blog/2026/07/02/patzt-microsoft-bei-dkim-fuer-outlook-de/ (which is in German unfortunately) - but that is the exact issue.Outlook icon in taskbar can start two outlook.exe processes
When the startup icon for Outlook Classic is pinned to the taskbar (laptop, Windows 11), a double-click can start two Outlook processes. I have been unable to convince my lovely wife that a taskbar icon should be clicked only once, but her trigger finger is too itchy. So we unpinned the icon from her taskbar and now she starts Outlook from a desktop shortcut (which is double-clicked). The problem: When Outlook is not running and the taskbar icon is clicked, it begins to start Outlook. But if the user double-clicks very quickly, the first process is not yet exposed and a second process starts. The window opens for the first process, and no window opens for the second process. Then, when the Outlook window is closed, it only exits the first process, and the second process is still active with no window. Later, the user clicks the taskbar icon to start Outlook again (because no window is visible), but no window will open (because a process is already active). The workaround is to open task manager and kill the bogus process (or logout or reboot), but my lovely wife doesn't know what the task manager is, so she asks me. Which is fine, I am happy to be my wife's workaround, but the real problem is that Windows is starting two Outlook processes. In some cases this causes problems with IMAP synchronization, and then my wife doesn't realize that a sent email is stuck in the outbox forever, waiting for a sync that never happens. In fact, my wife is a pretty capable Outlook user, but not when Windows can't manage M365 applications that should not be running twice.Shared Calendars No Longer Visible
For years, I've shared Outlook calendars between my Outlook accounts and with my husband's, without any issues. However, since mid-June the shared calendars have disappeared for no apparent reason. The sharing permissions are still in place, but the calendars are no longer visible or available to add on Android, in the Outlook desktop app, or on Outlook on the web. I've spent hours Googling and tried all the usual troubleshooting steps, but nothing has worked! As a workaround, I now have to invite all @outlook.com accounts to calendar events just so everyone can see them and avoid double bookings. Has anyone come across this before and found a fix that isn't one of the standard "how-to" suggestions? Note: these are personal paid Microsoft accounts.
