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.
The term 'Get-MessageTraceV2' is not recognized as a name of a cmdlet
I am writing a function app to get message delivery status. I have the package defined in requirements.psd1 as such: # This file enables modules to be automatically managed by the Functions service. # See https://aka.ms/functionsmanageddependency for additional information. # @{ # For latest supported version, go to 'https://www.powershellgallery.com/packages/Az'. Uncomment the next line and replace the MAJOR_VERSION, e.g., 'Az' = '5.*' # 'Az' = 'MAJOR_VERSION.*' 'ExchangeOnlineManagement' = '3.*' } This is the error we get: The term Get-MessageTraceV2 is not recognized as a name of a cmdlet, function, script file, or executable program. Check the spelling of the name, or if a path was included, verify that the path is correct, and try again. The bizarre thing is that it sometimes works and sometimes doesn't without any changes to the code. Even when several of my colleagues and I try the command locally, we have the same error.Exchange 2016 and 2019 End of Life and Some Interesting Exchange Online Developments
On Oct 14, 2025, Exchange 2019 and 2016 reach end-of-life and Exchange SE becomes the only supported on-premises Exchange server. In other news, we discuss Microsoft guidance for moving to cloud first identity, HVE and ECS and the extension of basic authentication support to September 2028, the introduction of auto-archiving for Exchange Online, and why Microsoft is deprecating the Contact object from Exchange Online. https://office365itpros.com/2025/10/09/exchange-se-news/
How do you identify the "You've joined the xxx group" emails?
When you join a microsoft 365 group via Outlook you get an email (apparently from yourself) to say you have joined it. How do you actually identify these emails on Exchange? I've looked at the headers but nothing really stands out. I need to exclude these types emails from rules.
One 365 mailbox and several non 365 mailboxes
I am trying to configure the situation where I have one user on a microsoft 365 subscription and several other users on the domain using IMAP. I have configured the domain to send emails to the 365 subscriber and that works. However I am battling to get emails to the IMAP users. I have set up connectors to and from 365 and they validate correctly. However when I try to send a message from outside to one of the IMAP users I get Diagnostic-Code: smtp;554 5.4.14 Hop count exceeded - possible mail loop ATTR34 On researching this there are various tutorials which suggest loading exchangeonlinemanagement, connnect to the domain and execute Start-EdgeSynchronization I then get an error telling me the command is not recognised. Having searched it seems this command is only for on premises exchange servers and not the on line subscription model have. Any pointers to where I am going wrong would be gratefully received.
exchange online migration
So have Two office 365 tenants - that have to migrate, so it ends up in already existance of company-b.com Company/tenant = company-a.com Company/tenant = company-b.com So all company-a mailboxes must be migrated to company-b. What is the best way to archive that ? With the build in migration tool in exchange online or some third party tools. There are only about 5-10 users so not many. Overall requirement is also that if any send mail to company-a.com it should still end up in the migrated mailbox of company-b.com, so mails are not lost, if any use the old domain name
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.Missing Teams Contacts after Migration
Hello, We are currently migrating mailboxes from exchange 2019 to exchange online. The migration works absolute flawless. Now we have some employees complaining about missing teams contacts that were previously created in Teams only. The MS support told me that this is a teams limitation and the local contacts are gone. I know about unified contacts, thats contacts are synced now between outlook and teams and newly created contacts are stored in exchange online mailbox. But whatabout the old contacts ?? cant believe that theres no workaround to keep this contacts. Do you know something about this ? Rene
I am receiving DMARC errors
Hello Please i need your help on this issue. Last night I started receiving DMARC and other errors when trying to send emails. I dont believe my business email is receiving messages either. Please help me 'fix' resolve these bounce back errors. I did try to find the solution on my own,, but its just out of my wheelhouse. Please help as my business is being affected by these errors and bounce backs.
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?
