Chatta subito con l'assistenza
Chat con il supporto

On Demand Migration Current - User Guide

About On Demand Migration Working with On Demand Migration Account Migration Mailbox Migration OneDrive Migration Microsoft Teams Migration Microsoft 365 Groups Migration SharePoint Migration Public Folders Migration Power BI Migration Troubleshooting Finalizing the Migration Appendix A: Using PowerShell Appendix B: How Queuing Works

Migrating Public Folders

Make sure that all associated accounts in this project are matched or migrated:

  1. Log in to Quest On Demand and choose an organization if you have set up multiple organizations.
  2. From the navigation pane, click Migration to open the My Projects list.
  3. Create a new project or open an existing project.
  4. Click the Public Folders tile, or click Open from the Public Folders tile to open the Public Folders Migration Workspace.
  5. Go to the Public Folders tab and select the public folders that you want to migrate.

    TIP: Use search and filtering to quickly navigate through the list of public folders.

  6. Click Migrate. The New Public Folder Migration Task wizard starts. Each step is described below:
  7. Start
    1. Task name - You can specify a custom name. The default name is Public Folder Migration Task.
    2. Use the settings from an existing migration template for this task - select this option if you have already saved a previous migration templates. if this is the first time you are migrating mailboxes, keep this option unchecked.
      • Select template - select a template that you previously created, from the dropdown list.
    3. Go to Summary step - select this option to preserve the settings and go directly to the last step of the wizard. If you do not select this option, but you have selected a template, you can step through the wizard and edit the settings in the template.
    4. Click Next.
  8. Options
    • Include subfolders in migration scope - select this option to include all sub-folders during migration of selected public folders.
    • Migrate public folder content - select this option to migrate folder and sub-folder contents. You can clear this option for a test migration to create an empty public folder structure and transfer folder permissions.
    • Migrate public folder permissions - select this option to migrate permissions of selected public folders (and sub-folders if included).
    • Migrate mail enabled - select this option to migrate the mail-enabled property of selected public folders (and sub-folders if included). If this option is not selected, the mail-enabled property of selected public folders or sub-folders will not be migrated.
    • Migrate mailbox permissions - select this option to migrate mailbox permissions of selected public folders (and sub-folders if included)..
  9. Notification
    1. Send notification email once the task is completed - select this option to send a notification email when a discovery task completes.
      • Only in a case of failure - Select this option to send the email if the discovery task fails to complete successfully.
    2. Recipients - enter the email address of the recipients of this email. You can specify multiple recipient email addresses separated by semicolon.
    3. Click Next.
  10. Schedule
    1. Choose from one of three options to schedule the task. The scheduler will be activated after you complete the task wizard.
      • Run now - task runs immediately.
      • Run later - task must be started manually.
      • Schedule - task will be started at a future date and time entered in the corresponding calendar field.
    2. Click Next.
  11. Summary
    1. Save task settings as a migration template - select this option to save the settings in this wizard as a reusable migration template.
      • Migration Template Name - specify a name for the template. If you have changed the settings of a preselected template, specify the same template name to apply the changes to the template when you complete the wizard. All saved templates are displayed in the Templates tab.
    2. Verify the task specifications as described below:
      • Name - name of the task. The default name is Public Folder Migration Task. You can specify a custom name.
      • Source tenant - name of the tenant where the source URLs exist.
      • Target tenant - name of the tenant where the target URLs may or may not exist.
      • Scheduled start - date and time when the task will start. Now indicates that the task will start immediately.
    3. Click Back to revise or review a previous step or click Finish to complete the task wizard and start the task as scheduled.

The migration task is created. You can track its progress in the Tasks, view the summary on the Dashboard or monitor alerts and notifications in the Events.

Power BI Migration

Power BI is a business analytics tool developed by Microsoft for creating interactive reports and dashboards. While Power BI is not automatically included in Office 365, Microsoft seamlessly integrates Power BI with Excel and other Office 365 applications through various subscription plans that provide advanced features and capabilities.

On Demand Migration helps you migrate your Power BI assets from a source to a target tenant, with easy-to-use discovery, assessment and migration services.

In this chapter:

What We Migrate

The On Demand Migration Power BI migration service migrates Power BI assets like shared workspaces between Microsoft 365 tenants, based on the source data connection types to which Power BI reports are connected.

On Demand Migration migration support for Power BI components is indicated in the following table. Migrations are limited to 1 GB for supported Power BI components.

Power BI Component Support Notes
Microsoft public preview features  
On Premises Power BI  
Power BI Service Object
Admin Group Workspaces  
Dashboards  
On Premises Gateways Requires manual creation in destination Tenant
Personal Workspaces  
Pipelines  
Power BI Account Licensing  
Power BI Applications  
Reports Subject to Source Data Connection Type
Semantic Models Subject to Source Data Connection Type
Shared Workspaces Subject to Source Data Connection Type
Power BI Service Object Permissions
Gateway Access Permissions Requires manual creation in destination Tenant
Report Permissions Inherited from Workspace. Requires account matching
Semantic Model Permissions Inherited from Workspace. Requires account matching
Workspace Permissions Requires account matching
Source Data Connections Connections not listed are considered as unsupported
Microsoft Azure SQL Server  
Microsoft Excel Imported  
Microsoft SQL Server  
M365 security and compliance features
Legal Hold  
M365 Compliance Customer Lockbox  
Microsoft Information Protection policies and labels  
Retention Labels  
Power Platform features
Power Apps  
Power Automate (Flow)  
Power Pages  
Power Virtual Agents  

 

Prerequisites and Limitations

Prerequisites

  • It is highly recommended that all accounts in the project be matched to ensure that membership and content ownership are processed correctly. See Matching and Mapping Accounts for more information.
  • The target tenant should already have the fully configured Power BI Service with licensing to match the source tenant.
  • The following admin consents should be granted for Power BI migration:
    • Migration - Basic
    • Migration – Power BI
Limitations

The limitations indicated below may not be an exhaustive list of limitations as some may appear in unique customer migration scenarios, or arise due to platform or legacy support restrictions.

  • Limited to shared workspaces, personal and admin group workspaces will not be migrated.
  • Limited to source data based on Excel, On Premises SQL Server, Azure SQL Server.
  • Connection migrations require credentials for source system access during migration.
  • On Premises Gateways are not migrated.
  • Explicit access to shared workspaces is required for migration.
  • Explicit access to on premises Gateways is required for discovery and mapping.
  • Applications, Pipelines, Dataflows and Dashboards are not supported.
  • Row-level permissions for data tables in the source tenant are ignored during migration because these permissions are inherited from the top-level semantic model in the target tenant.
  • User account licensing for Power BI is not processed.
  • Sensitivity labels are not transferred.
  • Third party reporting visualization plugins are not transferred.
Microsoft Power BI Limitations

Power BI migrations are subject to Microsoft limitations for the use of the Power BI migration service and the included APIs. These limitations are published by Microsoft on their public website. Power BI discoveries and migrations are subject to Microsoft Power BI REST API throttling during processing.

Related Documents

The document was helpful.

Seleziona valutazione

I easily found the information I needed.

Seleziona valutazione