Tenant-to-Tenant Migration with Orchestrator – Technical Overview (Microsoft 365 | Preview)
Tenant-to-tenant migration with Orchestrator in Microsoft 365 introduces a native, API-driven, and highly validated approach for cross-tenant migrations. It is designed for enterprise scenarios where sequencing, dependencies, and governance are critical. Note: This capability is currently in preview. Features and behavior may change before GA. Architecture and execution model Migration is executed through batches (jobs) managed via Microsoft Graph (Beta) User-level execution: one user failing validation does not block others in the same batch Mandatory Standalone Validation before migration submission Date-driven cutover using completeAfterDateTime Supported workloads (actual scope) Exchange Online Microsoft Teams ODSP (OneDrive for Business) Important clarification on SharePoint Orchestrator does not migrate shared SharePoint content such as Team sites, Channel sites, or collaboration sites. The ODSP workload covers personal user data (OneDrive) only. SharePoint team/workload sites remain out of scope and require separate tooling or processes. Critical prerequisites Identity Mapping (CTIM) is mandatory and must remain stable during migration Target users must not have Exchange mailboxes or OneDrive sites provisioned before migration Licenses must be assigned only after Identity Mapping (ExchangeGuid stamping) Migration apps and service principals (Teams, Meetings, CTMS) must be correctly provisioned Organization Relationships and Migration Endpoints must be in place Exchange autoforwarding must be enabled for Meetings migration Validation and lifecycle Standalone Validation acts as a full “what-if” check Key states include: Cancellation or user removal is possible only before cutover Post-migration cleanup After completion, tenants must be returned to a non-migration state: Remove Identity Mapping data Remove Organization Relationships Remove Migration Endpoints Revoke migration app permissions and service principals Decide whether to retain or remove MailUsers in the source tenant Skipping cleanup leaves the tenant in an exception state. When this approach fits Mergers and acquisitions Divestitures and tenant splits Regulated environments requiring strict control Scenarios where dependency-aware sequencing matters more than speed Technical conclusion Orchestrator is not a one-click solution. It delivers native orchestration, deep validation, and predictable execution when Identity Mapping, licensing order, and scope boundaries are fully understood. For experienced administrators and architects, it represents a major step forward in tenant-to-tenant migrations within Microsoft 365, even while still in preview.
Delete, unshare, or hide an Office 365 Group's calendar
I see that when creating an Office 365 Group that a calendar is also automatically created for that group and that it appears in the list of calendars for all members of the Group regardless of their follow status of the group. My users would rather not have any calendars for Groups. How can I remove or hide them for the members of the Group?Hide Groups from a Guest User
How can I hide the list of Office 365 Groups in my tenant. When a guest account is added through Azure AD and the invite email is sent, they follow the instructions to login into the Guest tenant and end up on this landing page. https://account.activedirectory.windowsazure.com/r#/applications The Guest User can then click on Groups and Join Group and see a list of all the tenant groups and the members of any of the groups. How is this possible? A guest user shouldn't be able to see a list of internal groups. The names alone could possibly give away important information (internal project, other third party companies, etc.) Surely there should be a boundary for listing groups between an internal and external user?
Allow Sub-Folder creation Office 365 groups
We currently have a number of public folders ( I believe 1 for each study that is active) which is a bunch... Discussions have been had around Groups is a great place for public folder data... I would disagree unless.. 1. allow to create sub folders 2. allow to flag or assign categories These two are huge for us and the long term exchange online strategy, we would love to see (and I'm sure others would to) functionality much like a shared mailbox be incorporated into Groups.Can you bring Group Conversations to the Home Page Sharepoint Group?
Hello Everybody. We are having group conversations by email that are being saved in Groups and you can only see them through OWA (online) in the conversations page. Is there a way to bring those conversations to the Group's SharePoint Home Page? We use Groups mostly to store documents and email for conversations. If I can link conversations to the home page of the Group, people will engage more with other tools available at the home page (online notes for example) and may collaborate more in the comments section. Most probably you can do that already and I just couldn’t find it here and/or don't know how to do it! Thank you,
