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

Matching and Mapping Gateways

Prerequisites

Gateways must be configured in the target tenant at any time before matching or mapping the Gateways, and migrating any Connections or Workspaces.

There are two ways to match Gateways from the source to a target tenant:

Matching Gateways from the Gateways list

  1. Log in to Quest On Demand and choose an organization if you have set up multiple organizations.
  2. From the navigation pane, click Migrate > Projects to open the My Projects list.
  3. Create a new project or open an existing project.
  4. From the Power BI tile on the project dashboard click Open. Then select the Gateways tab.
  5. Select one or more Gateways that you want to match to a target tenant.
  6. Click Match in the List View menu and then select Match Selected. The New Match Gateways Task wizard starts. Each step is described below:
  7. 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.
  8. Summary
    1. Verify the task specifications as described below:
      1. Name - name of the task. The default name is Match Gateways. You can specify a custom name.
      2. Scheduled start - date and time when the task will start. Now indicates that the task will start immediately.
    2. Click Back to revise or review a previous step or click Finish to complete the task wizard and start the task as scheduled.
  9. When the task completes, the Target Gateway column in the Gateways list indicates the matched Gateway in the target tenant.

Mapping Gateways from a file

To match source Gateways to target Gateways with different names, a CSV file is used to indicate the mapping between source and target Gateways, as described below.

To create the mapping file:

  1.  Prepare a comma-separated values (CSV) file with the source and target Gateway names.
  2. The header row defines the names of the source and target attributes used for mapping. Subsequent rows list the mapping values of the attributes.

    The columns are as follows:

    • Name - unique name of the source Gateway. The column header is case sensitive.
    • Target Gateway - unique name of the Gateway in target tenant. The column header is case sensitive.
  3. Save the CSV file. You may rename the file if needed.

To upload the mapping file:

  1. Log in to Quest On Demand and choose an organization if you have set up multiple organizations.
  2. From the navigation pane, click Migrate > Projects to open the My Projects list.
  3. Create a new project or open an existing project.
  4. From the Power BI tile on the project dashboard click Open. Then select the Gateways tab.
  5. Select one or more Gateways that you want to map to a target tenant.
  6. Click Match in the List View menu and then select Map from File. The Import Gateways Matching Task wizard starts.
  7. Import Gateways Mapping Options
    1. Click Browse and select the CSV mapping file. The selected file name appears next to the Browse button.
    2. Click Next.
  8. 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.
  9. Summary
    1. Verify the task specifications as described below:
      1. Name - name of the task. The default name is Import Gateways Mapping. You can specify a custom name.
      2. Scheduled start - date and time when the task will start. Now indicates that the task will start immediately.
    2. Click Back to revise or review a previous step or click Finish to complete the task wizard and start the task as scheduled.
  10. When the task completes, the Target Gateway column in the Gateways list indicates the mapped Gateway in the target tenant.

Provisioning Workspaces

The provisioning task helps you with the following premigration preparations:

  • Automap and provision shared workspaces by source workspace name.
  • Provision shared workspaces that were mapped using the Map from File action.
  • Resolve workspace naming conflicts.
  • Apply permissions to target workspaces based on source permissions.
  • Reprovision workspaces to refresh permissions on target workspaces.

In this topic:

Considerations

  1. After all source-shared workspaces are discovered, you can begin provisioning workspaces in the target tenant using a Workspace Provisioning task.
  2. During provisioning of the workspace in the target tenant, the license mode set to Pro license.
  3. Workspaces must be provisioned before their contents can be migrated.
  4. Verify that all associated accounts are matched or migrated before creating the provisioning task.
  5. When workspaces are provisioned, the service principal used by ODMPBI in the target tenant will be assigned to the workspace with the Admin role.
  6. If workspaces are to be merged, the Quest service principal or security group created during the setup process in the target tenant must be added to the target workspace with the Admin role before performing provisioning.
  7. The Power BI service requires at least one user account or security group with the Admin role to manage a workspace in the Power BI portal.
  8. If workspace access permissions are changed in the source environment after a workspace is provisioned, you must re-provision the workspace to refresh the permissions on the target workspace.
  9. Workspaces in the target tenant can take up to 2 hours to become available and for permissions updates to be fully processed in the target tenant after a workspace is provisioned.

Starting a Workspace Provisioning Task

  1. Log in to Quest On Demand and choose an organization if you have multiple organizations.
  2. From the navigation pane, click Migrate > Projects to open the My Projects list.
  3. Create a new project or open an existing project.
  4. Click Power BI from the project tiles, or click Open from the Power BI tile to open the Power BI migration workspace.
  5. Click the Workspaces tab and select one or more workspaces.
  6. From the Actions menu, click Provision. The New Workspace Provisioning Task wizard starts. Each step is described below:
  7. Provision Options

    Choose from the following options for the processing that the task should complete

    1. Provision workspaces using source workspace name or Map from File – Select this option to preform auto-mapping of the selected workspaces by source name to provision the workspaces in target or to complete provisioning for workspaces that were manually mapped using the Map from file action.

      If a source workspace name does not exist on target, a new workspace will be provisioned with the source name.

      If a workspace has been mapped from file, the target workspace name provided will be used to provision a new workspace or merge with an existing workspace.

      If a source workspace with the same name exists in the target environment, choose from the following options to determine how the task will manage collision handling to resolve naming conflicts:

      • Skip processing, and no changes will be made to the target environment - select this option to prevent a mapping from being performed and skip any processing of permissions for the workspace.
      • Merge with the existing workspace in the target environment - select this option to create a mapping to the target workspace and merge permissions if required.
      • Provision a new workspace in the target environment with the source name and a prefix or suffix - select this option to create a new workspace name based on the text provided. If the new workspace name also already exists it will be skipped.

        TIP: Use Map from file to provision the new workspace with custom name, or to create a custom mapping.

    2. Provision all workspaces with the source name and a prefix or suffix - select this option to rename all workspaces being processed and create new workspaces with the text provided. If the new workspace name already exists it will be skipped.

      TIP: Use this option to bulk archive selected source workspaces into the target environment.

    3. Refresh permissions for previously provisioned workspaces - select this option to re-provision workspaces based on the previously mapped name. This will allow for refreshing permissions on the target workspace in the event of changes to the source workspace permissions. The settings for processing the permissions can be completed on the Permissions step. This option will not create new workspaces.
  8. Permissions

    Choose from the following options to determine how permissions are managed:

    1. Default Target Admin User - specify a user account in the target environment that will be set with the Admin role on provisioned workspaces. This account is used to ensure that management access to a workspace in the Power BI portal is not lost.
    2. Set Default Target Admin User as workspace Admin - select this option to apply the Default Target Admin User to provisioned workspaces. If this option is not selected then the Default Target Admin User will not be applied to workspaces and this may result in cases where a target workspace cannot be managed in the Power BI portal post provisioning.

      Choose how the Admin account will be used:

      • Set Always - select this option to always apply the Default Target Admin User permissions during provisioning.
      • Set if no workspace Admin user is mapped - select this option to apply the Default Target Admin User only when there is no other account with the Admin role included in the account mapping.
    3. Set target workspace permissions - select this option to apply permissions from the source workspace to the target workspace using the account mappings. If this option is not selected the provisioning may still apply if the Default Target Admin User is selected.

      Choose how target permissions are set:

      • Add from source - source accounts and groups that are not in the target are added with the source roles. Existing target accounts and groups are not changed.
      • Update from source - source accounts and groups that are not in the target are added with the source roles. Source accounts and groups that are already in the target are changed to the source roles. Target accounts and groups that are not in the source are not changed.
      • Synchronize with source - target accounts and groups are set to the source accounts and groups roles. Target accounts and groups that do not exist in the source are removed.
  9. 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.
  10. Summary
    1. Verify the task specifications as described below:
      1. Name - name of the task. The default name is Provision Workspaces. You can specify a custom name.
      2. Provisioning options - indicates the provisioning options selected.
      3. Permissions - indicates the permission options selected.
      4. Scheduled start - date and time when the task will start. Now indicates that the task will start immediately.
    2. Click Back to revise or review a previous step or click Finish to complete the task wizard and start the task as scheduled.
  11. When the task completes, the Workspace State column value of the selected workspaces in the Workspaces list changes to Provisioned, and the.Target Workspace column indicates the mapped Workspace in the target tenant (unless there is a custom mapping, in which case it should remain the same).

Migrating Connections

In this topic:

Prerequisites and Considerations

  • Connections can be migrated to the target tenant at any time before performing a Workspace migration.
  • A profile must be assigned to the Connection before it can be migrated.
  • Gateways that are used by Connections:
    • must be matched before migrating a Connection.
    • must be in an Online state for a Connection migration.

Starting a Connections Migration Task

  1. Log in to Quest On Demand and choose an organization if you have set up multiple organizations.
  2. From the navigation pane, click Migrate > Projects to open the My Projects list.
  3. Create a new project or open an existing project.
  4. From the Power BI tile on the project dashboard click Open. Then select the Connections tab.
  5. Select a Connection that you want to migrate.
  6. Click Migrate in the List View menu. The New Migrate Connections Task wizard starts.
  7. Start
    1. Task Name - You can specify a custom name. The default name is Migrate Connections.
    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. Migration Options

    1. Default Target Admin User - specify the default target admin user to use for any user that has no match on the target. If a default admin user was configured from the project previously, it will automatically appear in this field.
    2. Privacy Level - select a privacy level from the following options:
      • Organizational - Data from a source with an organizational privacy level is considered to contain organizational data. It can be shared with other organizational data sources, but it won't be shared with external data sources.
      • Private - Data from a source with a private privacy level is considered to be highly sensitive. It won't be shared with any other data source, even if they are within the same organizational boundary.
      • Public - Data from a source with a public privacy level can be shared with other data sources without any restrictions. It's assumed that the data at this level doesn't contain sensitive information.
      • None - all data will be migrated regardless of privacy level.
    3. Incremental migration - select this option to migrate modified or missing data. This option is very helpful in subsequent migrations to keep your migrated data synchronized between source and target tenants.
    4. Click Next.
  9. 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.
  10. Summary
    1. Save task settings as a migration template - select this option to save the settings in this wizard as a reusable migration template.
      1. 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:
      1. Name - name of the task. The default name is Migrate Connections. You can specify a custom name.
      2. Default Target Admin User - name of the admin user specified for this task.
      3. Connection privacy level - privacy level selected in the wizard.
      4. Incremental migration - indicates whether or not this option has been selected.
      5. 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.
  11. When the task completes, the Connection State column in the Connections list is updated.

Reviewing the Connections Migration Task

  1. Open the Tasks tab.
  2. Select the Connections migration task that you want to review.
  3. In the task details pane that opens, the information presented is as described below:
    1. Task Status - current status of the task.
    2. Type - Type of the task. The type is MigrateConnections.
    3. Created - Date and time when the task was created.
    4. Modified - Date and time when the task was last updated.
    5. Last Operation - The action that was most recently performed in this task.
    6. Schedule - Date and time when the task started. Now indicates that the task started immediately after the task was created.
    7. Events (number) - Number indicates the count of events that the task encountered. The values indicate the type of the events and the event count for each type.
    8. Connections (number) - The number of Connections that were selected for migration and the number of Connections passing through the various states from Migrating to Migrated.

Reviewing the Connections Migration Task Events

  1. Open the Tasks tab.
  2. Select the Connections migration task for which you want to review the events.
  3. In the task details pane that opens, click Events (number). The Events tab opens with a filtered list of events for the selected task.
  4. Select an event that you want to review. In the event details pane that opens, the information presented is as described below:
    1. Object - name of the Power BI object if applicable.
    2. Task - Name of the task.
    3. Time - Date and time when the event occurred.
    4. Summary - a descriptive statement about the event if an exception occurs.

Migrating Workspaces

In this topic:

Prerequisites

Any Connections that are required by Reports must be migrated before scheduling a Workspace migration.

The Default Target Admin User configured in your Power BI project, is added to migrated Workspaces to ensure that access to migrated Workspaces is retained if a matching administrator account is not available for a migrated Workspace. We recommend that you retain this for safety.

Considerations

Your target tenant might already host Power BI Workspaces created before the migration. In cases where a Workspace name already exists in the destination, the migration will merge report, semantic model and Workspaces permissions data from the source tenant.

After Workspace migration, report users will remain the same as the users in semantic model.

We recommend that you run only one migration task at a time to avoid scheduling delays.

Starting a Migrate Workspace Objects Task

  1. Log in to Quest On Demand and choose an organization if you have set up multiple organizations.
  2. From the navigation pane, click Migrate > Projects to open the My Projects list.
  3. Create a new project or open an existing project.
  4. From the Power BI tile on the project dashboard click Open. Then select the Workspaces tab.
  5. Select one or more Workspace that you want to migrate.
  6. Click Migrate in the List View menu. The New Migrate Workspace Objects Task wizard starts.
  7. Start
    1. Task Name - You can specify a custom name. The default name is Migrate Workspace Objects.
    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. Migration Options

    1. Migrate objects using source names - If the objects do not exist in the target workspace they will be migrated using the source name. If a source object with the same name exists in the target workspace, choose from the following collision handling options:
      • Skip processing and no changes will be made to the target environment
      • Migrate the object and add a prefix or suffix to the source name

        Enter a prefix or suffix as described below:

        • Add prefix - specify a prefix for the workspace object name. Whitespaces are not supported.
        • Add suffix - specify a suffix for the workspace object name. Whitespaces are not supported.

      • Overwrite the target object
    2. Migrate objects with the source name and a prefix or a suffix - Select this option to always create new objects in the target workspace using the specified prefix or suffix for the object names. This task will skip any objects with the new name if they already exist in the target workspace..

      Enter a prefix or suffix as described below:

      • Add prefix - specify a prefix for the workspace object name. Whitespaces are not supported.
      • Add suffix - specify a suffix for the workspace object name. Whitespaces are not supported.

    3. Re-migrate previously processed objects - select this option to remigrate workspace objects that were previously migrated and replace the target workspace object with the source object.
    4. Refresh permissions for previously migrated objects - select this option will not migrate new objects. It will only update permissions for previously migrated objects based on the Permissions selections.
    5. Click Next.
  9. Processing Options
    1. Skip rebind - Select this option to prevent Power BI from retaining the data source connection for reports during migration. After migration, data in the reports cannot be refreshed in the target tenant because the original data source connection information has not been migrated. If you clear this option, data source connection will be migrated but some unsupported data sources connection types, like SQL with OAuth 2.0 authentication will be skipped. See What we migrate for supported data types.
      • Skip connection rebind for unsupported connections only - select this option to check the connection type for a semantic model. If the connection type is supported then the data source connection for reports is retained, otherwise the data source connection rebind is skipped during migration.
      • Always skip connection rebind - select this option to migrate all reports and semantic models without processing the connection to the original source data.
    2. Include reports created with a live connection to the Power BI Service - select this option to migrate reports that were created with a live connection to a previously published semantic model.

      NOTE: At least one report must be directly bound to a semantic model without a live connection.

    3. Maintain semantic model names during export - select this option to retain the source semantic model name when this is extracted though the Power BI export process, and not the default report name for the semantic model.
  10. Permissions
    1. Default Target Admin User - Specify the default target admin user to use as the workspace owner when any workspace user has no match in the target tenant.
    2. Set workspace content permissions - select this option to resolve source and target permissions if there is a mismatch between existing content permissions. If this option is not selected, and the Default Target Admin User is not specified, the settings from the existing default target admin user will be used.
      • Add from source - this option migrates accounts from the source to the target that are not already in the target. Existing target accounts, groups, and roles remain unchanged. If the source accounts are mapped to target accounts that already have workspace permissions, then those target accounts will not be updated.
      • Update from source - this option migrates only mapped accounts with workspace permissions to the target. The target accounts, groups, and roles are updated to match the source permissions. Any existing permissions on the target that do not exist in the source are ignored. Permissions of other accounts in the target workspace that are not mapped to a source account are not updated.
      • Synchronize with source - this option updates target accounts, groups and roles to the source permissions. Existing account permissions that are not in the source are removed. After synchronization, target permissions of mapped accounts are the same as the source.
  11. 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.
      • Priority - select a priority from the dropdown for the objects scheduled for migration with this task . Values are: Highest, High, Medium, Low and Lowest. The default priority is Medium. If the system is busy, the objects are queued (Migration state = Queued). When the system accepts new migration work, objects are taken from the queue based on the assigned priority and age in the queue.
    2. Click Next.
  12. Summary
    1. Save task settings as a migration template - select this option to save the settings in this wizard as a reusable migration template.
      1. 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:
      1. Name - name of the task. The default name is Migrate Workspace Objects. You can specify a custom name.
      2. Default Target Admin User - name of the admin user specified for this task.
      3. Incremental migration - indicates whether or not this option has been selected.
      4. 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.
  13. When the task completes, the Workspace State column in the Workspaces list is updated.

Reviewing the Migrate Workspaces Task

  1. Open the Tasks tab.
  2. Select the Workspace migration task that you want to review.
  3. In the task details pane that opens, the information presented is as described below:
    1. Task Status - current status of the task.
    2. Type - Type of the task. The type is MigrateWorkspaces.
    3. Created - Date and time when the task was created.
    4. Modified - Date and time when the task was last updated.
    5. Last Operation - The action that was most recently performed in this task.
    6. Schedule - Date and time when the task started. Now indicates that the task started immediately after the task was created.
    7. Priority - the priority of this task.
    8. Events (number) - Number indicates the count of events that the task encountered. The values indicate the type of the events and the event count for each type.
    9. Workspaces (number) - The number of Workspaces that were selected for migration and the number of Workspaces passing through the various states from Migrating to Migrated.

Reviewing the Migrate Workspaces Task Events

  1. Open the Tasks tab.
  2. Select the Workspace migration task for which you want to review the events.
  3. In the task details pane that opens, click Events (number). The Events tab opens with a filtered list of events for the selected task.
  4. Select an event that you want to review. In the event details pane that opens, the information presented is as described below:
    1. Object - name of the Power BI object if applicable.
    2. Task - name of the task.
    3. Time - date and time when the event occurred.
    4. Summary - a descriptive statement about the event if an exception occurs.

 

Related Documents

The document was helpful.

Seleziona valutazione

I easily found the information I needed.

Seleziona valutazione