Many questions arose from the announcement of the Microsoft 365 multi-tenant organization (MTO) feature, In this article, I examine some practical aspects of multi-tenant organizations and examine why MTO does not replace the need for tenant-to-tenant migrations.
In this article, Damian Scoles discusses what DNS records should be in place for Exchange Online, why these records are needed, and how to validate that DNS is properly configured.
Microsoft has changed the way that the Search-UnifiedAuditLog cmdlet works without saying anything to Microsoft 365 customers. The results is that some scripts don't work and others won't return the expected results. This article explains what's happened and offers a workaround. Microsoft's actions are unexplainable, but it's the norm in this area where audit log changes happen without communication all the time.
The multi-tenant organization (MTO) is a Microsoft 365 solution built on top of Entra ID cross-tenant synchronization. An MTO can span up to five tenants each with up to 100,000 synchronized users. It's an interesting solution that should be of interest to many large enterprises.
In this blog, James Yip reviews Microsoft's Entra ID Cross-Tenant Sync feature, and how it can make things a lot easier when deploying a M&A project.
In this blog, Jaap Wesselius goes over how to set up an Exchange 2019 Edge Transport Server in an on-premises environment.
Microsoft 365 Copilot is only available for 4 Microsoft 365 SKUs. There's no technical reason why this is so. Instead, Microsoft is using Copilot as a selling point to convince customers to upgrade to Microsoft 365 E5 (preferably). All's fair in love and business, and this is just an example of product management for maximized profit.
In this blog, Becky Cross reviews some key Takeaways and next steps from the recent TEC Talk: What to Do About Exchange On-Premises After Microsoft Starts to Block Messages.