Architecture Approaches For Microsoft Cloud Tenant-to-tenant Migrations
This topic is 1 of 5Architecture approaches for Microsoft 365tenant-to-tenant migrationsThis series of topics illustrates several architecture approachesfor mergers, acquisitions, divestitures, and other scenariosthat might lead you to migrate to a new cloud tenant. Thesetopics provide starting-point guidance for planning.Business scenarioArchitecture scenarioI sold a business unit andbrand identityTenant-to-tenant migrationwithout rebrandingContoso users will continue to beknown as user@contoso.com.Identities will migrate to a targettenant and will keep the existingdomain as part of the migration.I sold a business unit and thebusiness unit will adopt thetarget company’s brandingContoso users will be known asuser@fabrikam.com.Most customers work with Microsoft Consulting Services or aMicrosoft partner to migrate tenants, including using thirdparty tools to migrate content. In the examples provided inthese topics, Contoso is the source tenant and Fabrikam is thetarget (destination) tenant.Architecture approachSingle-event migrationAlmost everything is migrated in a singleevent. Higher risk, shorter timeline.Avoid single-event migrations larger than15,000 users or 7 TB of site content.Data volumes, network bandwidth, andhelpdesk capacity can be limiting factors toscale. Consider using an alternatetemporary domain for a phased migration ifyou are unable to accommodate a singleevent.Tenant-to-tenant migrationwith rebrandingIdentities will migrate to a new targettenant and will change the brandidentity as part of the migration.ChooseonePhased migrationGradual migration of users, services, anddata. Source domains are not transferred.Users assume new target domains. Lowerrisk, longer timeline.Coexistence limitations can cause issues.I need to split users across twotenantsMy company cannot use theregistered (*.onmicrosoft.com)tenant nameCloud tenant moveTenant move or splitIdentities remain in the source tenant,but all users in the affected domainand all workloads are moved to a newcloud tenant.Similar to single-event migration, exceptthis does not include migrating accounts toa new on-premises AD DS forest. For tenantsplits, this approach is not intended forlong-term coexistence.I’m moving from a commercialtenant to Microsoft Cloud forGovernmentTechnical questions Do you need to retain the domain in thetarget environment? (How do you want tobe known by the outside world in the endstate?)Are you migrating to a brand newenvironment (greenfield), or targeting anexisting tenant? What type of continued collaborationbetween environments is expected in theend-state? What on-premises Active DirectoryDomain Services (AD DS) domains do youhave and are they synchronizing withAzure Active Directory (Azure AD) tenants?Migration event includes additional work tore-establish existing identities to the newtenant.Non-technical questions How will you reconcile policy conflicts asthey arise? Which project metrics are fixed and whichcan be optimized (time, resources, scope,quality, user experience)? For moreinformation, see The project triangle. What are the “Day 1” requirements? Daytwo and beyond?Migration eventsBecause both tenants and services are live atthe same time, a user’s migration can bethought of as a ‘migration event.’ The activitiesmay vary, but include the following.Prior to the migration event: Send communication to each user. Put mailboxes and content into read-onlymode.At the migration event: Stop reverse forwarding mail to allow newemail to be delivered to the target tenant Enable target accounts, if required.Complete the final data migration. What workloads are being used in thesource tenant? How many accounts are in scope?Is mail forwarding required aftermigration? Users must recreate their mobile profiles. Is a unified GAL required?Client software needs to be reconfigured(Outlook, OneDrive Sync Client, Microsoft365 apps activation).May 2021Post-migration event: 2021 Microsoft Corporation. All rights reserved. To send feedback about this documentation, please write to us at CloudAdopt@microsoft.com.
Architecture approaches for Microsoft 365tenant-to-tenant migrationsThis topic is 2 of 5Design considerationsPre-stage vs dial-toneA typical strategy includes:You can pre-stage mailboxes and SharePointand OneDrive content before the cut-overevent (final domain name move), after the cutover event, or a combination of the two. One week of mail on the initialmigration. One month of mail at the next milestone. Remaining mail at the final milestone.Pre-stage contentIf the timeline permits, pre-stage content priorto the migration event. Start with the oldest content first. Migration tools typically do not replicatemailbox data changes from source. Formailbox data, stop performing deltas forcontent under 30 days. For SharePoint andOneDrive, do incremental syncs as needed. Migration is complete after running thefinal delta sync, in conjunction with thefinal completion events.Dial-toneRight after cutting over to the new tenant,migrate a minimal amount of content.Continue to migrate content after the initialdata migration. Requires continued access to the source. Useful if there’s not enough time to presync. SharePoint and OneDrive migrationAligning SharePoint and OneDrive datarequires careful planning. Data volumes can be quite large and,unlike mail data, the documents arefrequently changing.In single event migrations, the requiredUPN changes during the migration willrequire re-mapping source to target.Migrating user accounts to a newdomainBoth architecture approaches involve movinguser accounts from an existing domain to atarget domain. There are several approachesyou can take: Use third-party toolsBetter network performance for theinitial data migration content re-caching(as opposed to caching entire mailboxesover the network). Hire Microsoft Consulting Services (ActiveDirectory Migration Service) Hire a Microsoft partnerWorks best for mailbox data only. Thisapproach leads to a poor userexperience with OneDrive andSharePoint data migrations.Be sure to plan which properties to migratewith the user accounts. For example, migratingthe Exchange Legacy DN property allows usersto reply to old emails.Exchange hybrid configurationBoth approaches require an Exchangemanagement server on-premises with hybridconnectivity. This is necessary to manageproperties of the mailboxes and to forwardemail to the new tenant, if needed, in a phasedmigration. Consider running the minimalhybrid configuration option in the ExchangeHybrid Configuration Wizard (HCW) if you donot require additional functionality.For more information, see How and when todecommission your on-premises Exchangeservers in a hybrid deployment.If the target tenant already exist, considertheseadditionalcomplexities:Migratingto anexisting tenant The naming format for users might changeas well as the domain to match an existingpolicy. How will policy conflicts be resolved? Does the target tenant have accessrestrictions (for example, Azure ADConditional Access policies) that mayprevent access for migrated identities?Long term tenant co-existenceIf required, ongoing collaboration may berequired between tenants. See Microsoft 365inter-tenant collaboration.Current tenant-to-tenant workload migration capabilitiesServiceCan migrateNotesMicrosoft 365 Apps (Office 365 ProPlus)YesSee Reset Microsoft 365 apps for enterprise activation state.Exchange mailboxesYesMicrosoft Consulting Services (MCS) and/or third-party toolExchange public foldersYesMCS and/or third-party toolSharePoint sitesYesMCS and/or third-party toolOneDrive foldersYesMCS and/or third-party toolOffice 365 groupsYesMCS and/or third-party toolTeamsPartialContent migration requires a third-party tool andscripts to recreate the Teams structure and permissions.YammerPartialLimited scenarios supported – requires a service ticketwith Microsoft Support.Azure Information ProtectionPartialLimited scenarios supported – requires a service ticket withMicrosoft Support. Labels cannot be migrated across tenants.Stream, Flow, PowerApps, and PowerBINoIntuneYesWindows 10 SubscriptionActivation licenseYesMay 2021Users may have to unenroll their devices, and then reenroll inthe target tenant. For more information, see Tenant to tenantmigration for Intune.Windows users must join the Azure AD domain of the targettenant and sign in with their new target tenant account name.Ensure that the new user accounts have the Microsoft 365license with the Windows 10 Enterprise service enabled. 2021 Microsoft Corporation. All rights reserved. To send feedback about this documentation, please write to us at CloudAdopt@microsoft.com.
Architecture approaches for Microsoft 365tenant-to-tenant migrationsSingle-event migrationThis topic is 3 of 5In this example, Contoso holds multiple brands, includingFabrikam. Fabrikam is moving to a new tenant. Migrationevents take place during a single time period, such as over aweekend.Initial stateContoso synchronizes identitieswith Azure AD Connect.On-premisesMicrosoft .com, Fabrikam.com)UPN:Leon.Kruger@Contoso.comNote: Contoso.com is the primarydomain. Fabrikam.com is an addedcustom domain in the existing, sourceenvironment.Azure ADUPN:Sophie.Holter@Fabrikam.comExchangeContoso retains an Exchangemanagement server on premiseswith hybrid connectivity.SharePointPre-cutover eventReplicate identities in the existingAD DS domain (Contoso) to thetarget AD DS domain (Fabrikam).If identities in the source domainare using the same UPN in thetarget domain, assign atemporary UPN.Synchronize identities from thetarget AD DS domain to thetarget Azure AD tenant. Initially,the UPN will be in theonmicrosoft.com domain.On-premisesMicrosoft .com, Fabrikam.com)UPN:Leon.Kruger@Contoso.comAzure ADUPN:Sophie.Holter@Fabrikam.comExchangeExecute pre-stage contentmigrationCutover eventPrepare the target tenant(Fabrikam.onmicrosoft.com). Remove the domain from allobjects in the source tenant(Contoso). This includes SIPaddresses, email addresses,proxy addresses, groups, andpublic folders. Verify the domain on thetarget tenant (Fabrikam). Assign the correct UPNs(Fabrikam) for users on thetarget UPNs. This will flow tothe target tenant and replacethe default onmicrosoft.comdomain.Perform completion events foreach workload.Continued on next com(Fabrikam.com)Azure ADUPN:Sophie.Holter@Fabrikam.comExchangeSharePoint
End stateOn-premisesMicrosoft .com)UPN:Leon.Kruger@Contoso.comCleanup: Remove the migrated identities fromthe source domain (Contoso.com), ifmail forwarding is not required. Youcan create a contact object ifforwarding is still required. If an ongoing collaborationrelationship is required, considerusing Azure B2B between tenants.Azure kam.com)Fabrikam.AD.comAzure ADUPN:Sophie.Holter@Fabrikam.comMay 2021ExchangeSharePoint 2021 Microsoft Corporation. All rights reserved. To send feedback about this documentation, please write to us at CloudAdopt@microsoft.com.
Architecture approaches for Microsoft365 tenant-to-tenant migrationsPhased migrationThis topic is 4 of 5In this example, Contoso holds multiple brands, includingFabrikam. Fabrikam is moving to a new tenant. Migrationevents are phased over a longer period of time. While thisapproach works better for larger migrations, coexistenceissues can be challenging.Initial stateContoso synchronizes identitieswith Azure AD Connect.On-premisesMicrosoft .com)UPN:Leon.Kruger@Contoso.comAzure ADUPN:Sophie.Holter@Contoso.comExchangeContoso retains an Exchangemanagement server on-premiseswith hybrid connectivity.SharePointBridge statePrepare the target tenant(Fabrikam.onmicrosoft.com). Verify the domain on thetarget tenant (Fabrikam). Licenses must be availablefor both tenants.Replicate identities in the existingAD DS domain (Contoso) to thetarget AD DS domain (Fabrikam).Synchronize identities from thetarget AD DS domain to thetarget Azure AD tenant. Manycustomers disable user accountsuntil the user mailbox ismigrated, however this will bydefault block the account fromOffice 365 access.Enable forwarding and reverseforwarding SMTP.On-premisesMicrosoft Contoso.comFabrikam.AD.comPhased migration — Migrateuser mailboxes to the newtenant. Remove rosoft.com(Fabrikam.com)Azure ADUPN:Sophie.Holter@Fabrikam.comContinued on next pageAzure ADExchangeSharePoint
End stateOn-premisesMicrosoft .com)UPN:Leon.Kruger@Contoso.comCleanup: Remove the migrated identities from thesource domain, if mail forwarding is notrequired. You can create a contact object ifforwarding is still required. If an ongoing collaboration relationship isrequired, consider using Azure AD B2Bbetween tenants.Azure kam.com)Fabrikam.AD.comAzure Coexistence challenges during phased migrationsUser Experience Challenges Browser sessions can only authenticate to one tenant at a time. Skype contacts can be constantly changing. Single sign-on might make it difficult to access both tenants. Teams client confusion. Mail-enabled groups are challenging. During coexistence,replies to group threads are treated as Internet mail and mayresult in non-delivery reports (NDRs).May 2021Move integrated services together whenever possibleWhere there are strong integration and dependencies betweenservices, Microsoft recommends moving them at the same time.For example, if you do not move Exchange and Skype together,you may experience errors scheduling Skype meetings andconversation might not be saved. 2021 Microsoft Corporation. All rights reserved. To send feedback about this documentation, please write to us at CloudAdopt@microsoft.com.
Architecture approaches for Microsoft365 tenant-to-tenant migrationsThis topic is 5 of 5Tenant move or splitIn this example, Contoso is moving all users to a new tenantnamed Fabrikam. All users initially belong to the Contoso.comdomain. Users are migrated from the Contoso.com domain toFabrikam.com.Initial stateMoving a subset of user accounts to a new tenant is notdescribed.On-premisesContoso.AD.comMicrosoft cloudContoso synchronizes identitieswith Azure AD o retains an Exchangemanagement server on premiseswith hybrid connectivity.Note: If you are moving a subset of useraccounts to a new tenant, separate theseaccounts using organizational units(OUs), groups, domains, or by usingattributes.Azure ADExchangeSharePointPre-cutover eventPrepare the target tenant(Fabrikam.onmicrosoft.com). Create accounts in the targettenant. This can be accomplishedby scripting or provisioning cloudaccounts in the target tenant witha temporary UPN. Or, you canleave the default login(user@Fabrikam.onmicrosoft.com).Licenses must be available for bothtenants.On-premisesMicrosoft .com)Pre-stage the content in the targettenant for each workload.Azure ADCutover eventExchangeExecute the final content migration foremail.Initiate the domain transfer byremoving the domain from all sourceobjects.See sample scripts here: How tomigrate mailboxes from one Microsoft365 or Office 365 tenant to another.Register and validate the domain onthe target tenant.Reconfigure Azure AD Connect to pointto the target tenant.Identities should soft-match with thetarget. See How to use SMTP matchingto match on-premises user accounts toOffice 365 user accounts for directorysynchronization.Update Active Directory FederationServices (AD FS) if required.Continued on next pageDisable Exchange hybrid connectivity tothe source tenant. Configure Exchangehybrid connectivity in the target tenant.You cannot have a single Exchangeorganization be configured with hybridconnectivity to two tenants.Execute the final SharePoint andOneDrive content ikam.com)Azure ADExchangeSharePoint
End stateOn-premisesContoso.AD.comAt this point the source tenant is completelydisconnected from AD DS, and all contenthas been migrated to the target.The organization can decommission thesource tenant.Note: If you are moving a subset of useraccounts to a new tenant, the finalarchitecture includes two Azure AD Connectservers on premises, each synchronizingaccounts to different Azure AD tenants.The on-premises Exchange organization canbe configured for hybrid connectivity withonly one tenant.Fabrikam.onmicrosoft.com(Fabrikam.com)Azure ADExchangeMay 2021SharePoint 2021 Microsoft Corporation. All rights reserved. To send feedback about this documentation, please write to us at CloudAdopt@microsoft.com.
Architecture approaches for Microsoft 365 tenant-to-tenant migrations This topic is 1 of 5 Contoso users will continue to be known as user@contoso.com. Tenant-to-tenant migration without rebranding Architecture scenario Identities will migrate to a target tenant and will keep the existing domain as part of the migration. Single-event migration
Bruksanvisning för bilstereo . Bruksanvisning for bilstereo . Instrukcja obsługi samochodowego odtwarzacza stereo . Operating Instructions for Car Stereo . 610-104 . SV . Bruksanvisning i original
10 tips och tricks för att lyckas med ert sap-projekt 20 SAPSANYTT 2/2015 De flesta projektledare känner säkert till Cobb’s paradox. Martin Cobb verkade som CIO för sekretariatet för Treasury Board of Canada 1995 då han ställde frågan
service i Norge och Finland drivs inom ramen för ett enskilt företag (NRK. 1 och Yleisradio), fin ns det i Sverige tre: Ett för tv (Sveriges Television , SVT ), ett för radio (Sveriges Radio , SR ) och ett för utbildnings program (Sveriges Utbildningsradio, UR, vilket till följd av sin begränsade storlek inte återfinns bland de 25 största
Hotell För hotell anges de tre klasserna A/B, C och D. Det betyder att den "normala" standarden C är acceptabel men att motiven för en högre standard är starka. Ljudklass C motsvarar de tidigare normkraven för hotell, ljudklass A/B motsvarar kraven för moderna hotell med hög standard och ljudklass D kan användas vid
LÄS NOGGRANT FÖLJANDE VILLKOR FÖR APPLE DEVELOPER PROGRAM LICENCE . Apple Developer Program License Agreement Syfte Du vill använda Apple-mjukvara (enligt definitionen nedan) för att utveckla en eller flera Applikationer (enligt definitionen nedan) för Apple-märkta produkter. . Applikationer som utvecklas för iOS-produkter, Apple .
sites cloud mobile cloud social network iot cloud developer cloud java cloud node.js cloud app builder cloud cloud ng cloud cs oud database cloudinfrastructureexadata cloud database backup cloud block storage object storage compute nosql
An Asahi Kasei Group Company Inledning Den här manualen innehåller handhavandeinstruktioner för webbportalen Senseair Dashboard med dess användare som tänkta läsare. Inledningsvis beskrivs några begrepp som lägger grunden för behörigheter i systemet. Därefter följer steg för steg instruktioner av alla funktioner i systemet.
o Microsoft Outlook 2000 o Microsoft Outlook 2002 o Microsoft Outlook 2003 o Microsoft Outlook 2007 o Microsoft Outlook 2010 o Microsoft Outlook 2013 o Microsoft Outlook 98 o Microsoft PowerPoint 2000 o Microsoft PowerPoint 2002 – Normal User o Microsoft PowerPoint 2002 – Power User o Microsoft PowerPoint 2002 – Whole Test
