Converse agora com nosso suporte
Chat com o suporte

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

Refreshing Permissions

This task ensures that service principal permissions for Workspaces and Connections in the source tenant are refreshed and fully updated.

NOTE: Permissions can be refreshed once per hour. When service principal permissions are updated in Power BI, they may not be immediately available to API calls.

To refresh permissions, follow the steps described below:

  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. From the Power BI tile on the project dashboard click Open. Then select the Workspaces tab.
  5. Select one or more workspaces to validate.
  6. Click More > Refresh Permissions in the List View menu. The New Refresh Permissions Task wizard starts.
  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 Refresh Permissions. 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, connection and workspace permissions are refreshed.

Mapping Workspaces

Use this method to map specific Power BI Workspaces from the source to a Power BI Workspace that may or may not exist in the target tenant. If the Workspace exists in the target tenant, it will be merged with the target Workspace and the source data is used to resolve any merge conflicts. If the target Workspace does not exist, a new Workspace will be created.

The CSV file lets you specify the Workspaces that you want to map and ignore the rest. You can then use this file in the New Mapping from File Task wizard to map the Power BI Workspaces from the source to the target tenant.

This is a two-step process as described below:

Creating a mapping file
  1.  Prepare a comma-separated values (CSV) file with the source and target Workspace names.

  2. NOTE:

    • You can download a CSV template when you start the New Mapping from File Task wizard and click Download Example File from the Mapping File step.
    • CSV file names with non-ASCII characters are not supported.
  3. 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:

    • Source Workspace Name - unique name of the source Power BI Workspace. The column header is case sensitive.
    • Target Workspace Name - unique name of the Power BI Workspace. The column header is case sensitive. In cases where a mapping is not applied and the Target Workspace does not have a value, the Name of the source Workspace will be used for the migration to the target tenant.
  4. Save the CSV file. You may rename the file if needed.
Starting a Map Workspaces From File 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 Migration 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. From the Actions menu, click More and then select Map from File. The New Mapping from File Task wizard starts. Each step is described below:
  6. Mapping File
    1. Click Browse and select the CSV mapping file. The selected file name appears next to the Browse button.
    2. Click Next.
  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 Map Workspaces From File. 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 Workspace column in the Workspaces list indicates the mapped Workspace in the target tenant.

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 Migration 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 Migration 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. Workspaces must be provisioned before their contents can be migrated.
  3. Verify that all associated accounts are matched or migrated before creating the provisioning task.
  4. When workspaces are provisioned, the service principal used by ODMPBI in the target tenant will be assigned to the workspace with the Admin role.
  5. 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.
  6. 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.
  7. 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.
  8. 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 Migration 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).

The document was helpful.

Selecione a classificação

I easily found the information I needed.

Selecione a classificação