IMAP Mail Migration
Hello Microsoft Community, We are currently performing a mailbox migration from Google Workspace (Gmail) to Microsoft 365 Exchange Online using the IMAP migration method. The customer's environment is configured for split routing/coexistence, where both Google Workspace and Microsoft 365 are actively being used during the migration process. Mail flow is functioning as expected; however, we are experiencing extremely slow migration performance. For example, a mailbox containing approximately 10 GB of data is taking nearly two weeks to migrate, which is significantly impacting the overall project timeline. We would appreciate guidance on the following: Is this migration speed expected when using the IMAP migration method from Google Workspace to Exchange Online? Does Exchange Online enforce any throttling limits that can affect IMAP migration throughput? Can split routing or coexistence between Google Workspace and Microsoft 365 impact IMAP migration performance? Is there a recommended number of concurrent mailbox migrations or migration batch size for optimal performance? Are there any Google Workspace-side limitations, API restrictions, or throttling settings that should be reviewed? What Microsoft-recommended configurations or best practices can help improve IMAP migration speed? If higher migration throughput is required, does Microsoft recommend an alternative migration approach instead of IMAP? If split routing/coexistence must remain active throughout the migration project, what is the recommended Microsoft-supported migration method? We are trying to identify whether the bottleneck is on the Exchange Online side, Google Workspace side, or related to the coexistence configuration. Any troubleshooting guidance, performance recommendations, or Microsoft documentation references would be greatly appreciated.
Business Standard with Exchange Plan 2 NOW only showing 100GB of email space
FOR THE PAST 3 YEARS, we have 15 users with Microsoft Business Standard with 100GB of email storage space and 11 with Microsoft Business Premium with 100GB of email storage. I have 1 Business Standard with Exchange On-line Plan2, and 1 with Exchange On-line Plan2. Both have always jhad 150GB of usable mailbox storage. Both users for several years, leading up to September 18, 2026 had over 100GB of mail in their mailboxes and had no problems sending or receiving email, ever. THEN ALL OF THE SUDDEN on 9/18/2026, these 2 users with Plan 2 are no longer able to receive any email and it now shows their mailbox is full Even though checking active users details about mail for both of these users shows 150GB storage. In investigating further, in the exchange area of the admin portal, checking mailboxes indeed both of these 2 USERS ONLY SHOW 100GB, which is the exact same as all my other users who are not paying for Exchange PLAN 2. HOW DO I REPORT this to Microsoft?
How to Recover Data from a Damaged or Corrupted OST File When Outlook Cannot Open It
Hi everyone, I have seen several cases where users still have an old OST file but cannot access the mailbox data inside it. This usually happens after an Outlook profile is removed, a Microsoft 365 or Exchange account is changed, a mailbox is no longer available, or the OST file becomes damaged or corrupted. One common misunderstanding is that an OST file can be opened on another computer in the same way as a PST file. However, an OST file is linked to the Outlook profile and mailbox that created it. If that connection is no longer available, Outlook may not be able to open the file normally. Before trying to recover the OST data, it is worth checking a few things: Is the original Microsoft 365 or Exchange mailbox still available? Can the Outlook profile be recreated and synchronized again? Is the issue related to the OST file itself or only the Outlook profile? Do you need the complete mailbox data or only specific folders/items? If the mailbox is still available, rebuilding the Outlook profile and allowing Outlook to create a new OST may be the better approach. However, if the mailbox no longer exists, the Outlook profile has been deleted, or the OST file is damaged and contains the only available copy of the mailbox data, recovery becomes a different process. In these situations, it is important to first check what information is still readable from the OST file. Scanning and previewing the mailbox data before export can help identify available folders, emails, attachments, contacts, and calendar items before creating a new PST file. A practical OST recovery workflow usually involves: Keeping a copy of the original OST file before making any changes. Checking whether the original mailbox can still be synchronized. Scanning the OST file to identify available mailbox items. Reviewing important folders and messages. Exporting the required data to PST. Validating the resulting PST in Outlook. A detailed overview of the OST to PST conversion process, including scanning, previewing, selecting mailbox items, and exporting recoverable data, is available here: https://www.edbmails.com/pages/ost-to-pst-converter.html One important point to remember is that recovery results depend on the condition and readability of the OST file. A conversion tool can help extract available mailbox information, but it cannot recreate data that is no longer present or readable inside the source file.
Error office 365 e3 developer license will be deleted on XXXXX. Currently disabled
My Office 365 E3 Developer has been marked for deletion and disabled today. No earlier comms from Micrsoft or any sort of messages.It just locked our my E3 Developer license has there a not supporting it any more. I wanted to try and backup/export my mail box and no luck - the option is greyed out. My SharePoint admin center has been blocked also can't backup any of my files. I'm just helpless.What a shame Microsoft What other plans can i move to and what should i do now since Teams and mail is not working. Can I at least get a a grace period. Any resources or advice would be appreciated
Office 2021 Classic not showing images in Signatures
Hello I work in IT and trying to find a solution to this problem that our outlook are not showing the images in the signatures. Our Outlook 2021 Version is 2608, Build 16.0.20326.20072. This occurs even when creating a completely new signature and inserting a new local PNG/JPG using Insert Picture. The image initially appears correctly when inserted, but after saving/reopening the signature it becomes a red X with the message "The linked image cannot be displayed. The file may have been moved, renamed, or deleted." Existing signatures have the same problem. Recreating the signature does not resolve it. Here are some details we tried already. BlockHTTPimages is not configured in either the normal Office registry location or the Policies location. Uninstall Reinstalling Office didn't work We are under AD profiles, with new profiles and even rebuilding current profiles didn't solve it. Attempted a full reset of windows 10/11 didn't work. This appears to be an Outlook/Word signature-image regression rather than a corrupted signature or externally hosted image. Per Microsoft status that this should've been resolved back in June but the issue still persisted. https://support.microsoft.com/en-us/support/known-issues/images-are-not-displayed-in-emails-newsletters-or-signatures-in-classic-outlook?utm_source=chatgpt.com I did try using ChatGPT to help with the issue. I will share the thread link here if you wish to look into of all troubleshoots that was attempted. https://chatgpt.com/share/6aac0312-a08c-83ea-b1a8-2192b3677136 If anyone has any better knowledge of finding a solution as we have reported this issue to Microsoft via the help feature in outlook classic, but gotten no response since the last month since the issue started.How to Fix Outlook Keeps Asking for Your Password
There are few things more frustrating than opening Outlook, getting ready to check your email, and seeing the same password prompt again and again. You enter the correct password, click Sign In, and everything seems fine until Outlook asks for your password once more. Link to the post
