授权 Office 365 连接器Authorizing the Office 365 Connector

Office 365 常见问题解答Office 365 FAQ

是否有不支持的文件和字符?Will there be unsupported files and characters?

从一个 Office 365 租户迁移到另一个 Office 365 租户意味着源限制和目标限制相同;因此,从 Office 365 下载数据并将数据上传到 Office 365 时,数据应满足兼容性要求。Transferring from one Office 365 tenant to another means the source and the destination have the same limitations; therefore, your data should meet the compatibility requirements when downloading data from Office 365 and uploading data into Office 365.

文件和文件夹的字符限制Character limits for files and folders

文件名最多可包含 256 个字符。Filenames can have up to 256 characters. 文件夹名称最多可包含 250 个字符。Folder names may have up to 250 characters. 文件夹和文件名组合的路径总长度最多可包含 400 个字符。Total path length for folder and filename combinations can have up to 400 characters. 有关详细信息,请参阅 下文For more info, see below.

OneNote 笔记本会发生什么情况?What happens to OneNote notebooks?

在应用中,OneNote 笔记本 被视为文件夹,其中包含目录 (.onetoc2) 文件,以及针对每个部分 (.one) 的文件。OneNote notebooks are viewed as folders in our app, with a table of contents (.onetoc2) file, and a file for each section (.one). 这些文件将迁移到目标,但可能需要在目标中重新配置。These files are transferred to the destination, but will likely require reconfiguration in the destination.

是否保留时间戳?Are timestamps preserved?

迁移到 Office 365 时,将保留来自 Office 365 的原始时间戳。The original timestamps from Office 365 are preserved when migrating to Office 365.

备注

时间戳仅适用于已转移的文件/数据,而不适用于文件夹。Timestamps are only applied to files/data transferred, and not folders. 在迁移过程中,将在目标位置创建文件夹和文件夹结构,并体现迁移的日期。Folders and folder structure are created in the destination during migration, and reflect the date of the migration.

是否保留文件的作者身份?Is file authorship preserved?

从 Office 365 迁移到 Office 365 时,将保留“修改者”作者。When migrating to Office 365 from Office 365, the modified by author is preserved. 但是,“创建人”被更改为用户。However, the created by is changed to the user.

Mover 应用是否与 OneDrive for Business 的同步客户端交互?Does the Mover app interact with the sync client in OneDrive for Business?

我们不将 Mover 应用与 OneDrive for Business 的同步客户端交互。We do not interact with the sync client in OneDrive for Business. 迁移之前,建议将其禁用。Before a migration, We recommend disabling it. 如果在迁移过程中使用它,它会尝试同步所有迁移数据。If you use it during a migration, it tries to sync all the migrating data.

已共享的数据会怎么样?What happens to shared data?

其他用户与用户共享的数据将显示在“与我共享”文件夹中。Data shared with a user by another user appears in the Shared with me folder. 用户拥有的数据将显示在用户的指定目标文件夹中。Data owned by a user will appear in the user's designated destination folder.

通知如何处理?What about notifications?

为了防止用户收到垃圾邮件,Mover 应用会在迁移过程中关闭通知。To prevent users from being spammed, the Mover app silences notifications during the migration.

将数据共享到 Office 365 组是否有变化?What happens to data shared to Office 365 Groups?

共享到 Office 365 组的数据不会显示在“与我共享”部分。Data shared to an Office 365 Group does not appear in the Shared with me section. Microsoft 也不会通知用户他们现在是 Office 365 组的成员。Microsoft also does not notify users that they are now a member of an Office 365 Group.

备注

这是 Office 365 组的一个限制,我们无法对此进行更改。This is a limitation of Office 365 Groups and cannot be changed on our end. 用户必须导航到其 Outlook 桌面客户端中的相应组,或通过 outlook.office.com 登录到其首选电子邮件。The user must navigate to the appropriate group within either their Outlook Desktop Client, or by logging into their preferred email through outlook.office.com.

用户登录后:After the user has logged in:

  1. 导航到左侧菜单。Navigate to the left hand menu.
  2. 在文件夹列表上,向下滚动到“组”。Scroll down the folder listings to Groups. a.a. 如果未显示可用组,但要打开组目录,请选择“组”列表旁边的小箭头。If the available groups are not visible, to open the group directory, select the small arrow beside the Groups listing.
  3. 选择所需的组。Select the desired group. 此时,左侧菜单应发生变化,可在所选的 Office 365 组中打开和编辑“文件/备注”。From here, the left-hand menu should change, enabling you to open and edit Files/Notes within the selected Office 365 Group.

支持哪些 SharePoint 网站格式?What SharePoint site formats are supported?

在应用中,新式和经典网站都受支持,并以相同方式显示。Both Modern and Classic sites are supported, and appear the same in our app.

文件路径在 SharePoint 中的显示效果如何?What will my file paths look like in SharePoint?

在迁移设置(本指南后面将作介绍)中,你可以编辑路径来指定你希望数据在 SharePoint 中的位置。During the migration setup (described later in this guide), you can edit the path(s) to specify where in SharePoint you would like your data to go. 从 SharePoint Online 的根级别,你可以进入“网站集”,并在每个“网站集”内查找“网站内容”和“子网站”的目录。From the root level of SharePoint Online, you can go into Site Collections, and inside each Site Collection, find directories for Site Contents and Subsites.

“网站内容”将使你转到文档库(例如,“文档”部分),而“子网站”将使你转到该网站集的“子网站”。Site Contents takes you to document libraries (for example, the Documents section), whereas Subsites takes you to the Subsites of that site collection. 导航“子网站”可以浏览到相同的目录。Navigating Subsites takes you through the same dichotomy.

大多数云存储提供程序(例如 G Suite 驱动器)都从列出用户开始,例如 /user@example.com/Marketing FolderMost cloud storage providers, G Suite Drive for example, start the listing with a user such as /user@example.com/Marketing Folder. SharePoint Online 却不是这样,因此会看到 /Marketing/Site Contents/Documents 这样的路径。SharePoint Online does not do this, so you would be looking at a path such as /Marketing/Site Contents/Documents.

库权限继承对迁移有何影响?How does library permissions inheritance affect migration?

若要设置文档库中文件夹的特定权限,必须禁用继承。To set specific permissions on folders in a document library, inheritance must be disabled. 默认情况下,权限继承通常处于启用状态,这将使库中的所有数据受库中设置的权限的制约。Permissions inheritance is typically turned on by default, which makes all the data within the library subject to the permissions set on the library. 此行为与其他云服务中的团队文件夹或团队驱动程序类似,因此,如果用户可以访问根级别,那么他们就可以访问其中包含的所有内容。This is similar behavior to team folders or team drives in other cloud services, whereby if users have access to the root level, they have access to everything contained within.

如果根位置未禁用继承,则我们在每个文件夹中尝试设置的任何权限都会被库访问权限覆盖。If inheritance is not disabled at the root, any permissions we try to set on individual folders is overridden by the library access permissions.

禁用继承:To disable inheritance:

在“库设置”中,请访问“此文档库的权限”:In the Library settings, visit Permissions for this document library:

  1. 选择“停止继承权限”。Select Stop Inheriting Permissions. a.a. 这使你能够选择要删除的权限:This enables you to select the permissions you would like to remove:
    • 网站成员Site members
    • 网站访问者Site visitors
  2. 选择“撤消用户权限”。Select Remove User Permissions.

这可以防止网站成员/访问者继承对我们迁移到该库中的所有数据的权限,从而只允许向那些我们明确写入文件夹的网站成员授予权限。This prevents site members/visitors from inheriting permissions to all the data that we migrate into that library, allowing permissions to only those site members who we explicitly write to the folders themselves.

有关 SharePoint Online 权限继承的详细信息,请参阅 此处For more info about SharePoint Online permissions inheritance, see here.

Mover 是否支持 Microsoft Teams?Does Mover support Microsoft Teams?

Microsoft Teams 的显示和运行方式与 SharePoint Online 网站相同。Microsoft Teams appears and operates the same as a SharePoint Online site.

SharePoint Online 的项目限制是什么?What is the item limit for SharePoint Online?

许多网站声称 SharePoint 的项目限制为 5,000。Many sites claim that SharePoint has a 5,000-item limit. 其实不然。This is not true. SharePoint 5,000 个项目限制适用于搜索列表视图中显示的项目数:最大值为 5,000。The SharePoint 5,000-item limit applies to how many items appear in a search list view: a maximum of 5,000.

SharePoint 网站有文件大小和数量限制,具体如此处所述:SharePoint Online 限制SharePoint sites do have file size and number limits, which are covered in detail here: SharePoint Online limits

某些列表视图选项可能会阻止显示超过 5,000 个项目的搜索列表视图。Some list view options may prevent search list views with more than 5,000 items from appearing.

授权 Office 365Authorize Office 365

警告

若要完全授权 Office 365 连接器,需要全局管理员向 Azure 门户中的 Office 365 Mover 应用授予权限。To fully authorize the Office 365 Connector, a global admin is required to grant permissions to the Office 365 Mover app within the Azure portal.

全局管理员必须在主 Mover 应用中授权 *Office 365 连接器***后 授予这些权限。The global admin must grant these permissions after the Office 365 Connector is authorized within the main Mover app.

以下说明介绍了如何按正确顺序完成授权步骤。The following instructions show you how to complete the authorization steps in the right order.

授权过程中的某些步骤可以由 Office 365 中的全局或 SharePoint 管理员完成。Some steps in the authorization process can be completed by a global or SharePoint admin in Office 365. 在每步骤的开头,我们注明可以完成该操作的人员。At the beginning of each step, we indicate who can complete it.

  1. 全局管理员或 SharePoint 管理员:通过 app.mover.io 登录主 Mover 应用。Global or SharePoint admin: Log into the main Mover app via app.mover.io. 在“转移向导”中,选择“授权新连接器”。In the Transfer Wizard, select Authorize New Connector.

    备注

    无论 Office 365 连接器 是源连接器还是目标连接器(或两者都是),都需要执行此授权过程。Whether the Office 365 Connector is your source or destination connector (or both), you'll need to go through this authorization process.

    授权新连接器

  2. 全局管理员或 SharePoint 管理员:在“连接器”列表中,找到“Office 365”。Global or SharePoint admin: In the Connector list, find Office 365. 选择“授权”。Select Authorize.

    授权 O365

  3. 全局管理员或 SharePoint 管理员:此时将显示一个含“授权”按钮的窗口。Global or SharePoint admin: A window with an Authorize button appears. 它将提示你为 Office 365 连接器 提供显示名称 It prompts you to provide a display name for your Office 365 Connector. 选择“授权”。Select Authorize.

    授权 Windows

  4. 全局管理员或 SharePoint 管理员:按照屏幕上的说明进行操作。Global or SharePoint admin: Follow the on-screen instructions. 将重定向到 Microsoft 登录屏幕,可在其中使用 Microsoft 管理员权限登录,并继续对连接器进行授权。You are redirected to a Microsoft login screen where you can log in with your Microsoft admin privileges and continue to authorize the connector.

    警告

    如果你是 全局管理员,显示的登录屏幕会略有不同。If you are a global admin, a slightly different login screen appears.

    如果你在身份验证流过程中选择“代表你的组织同意”,你将授予对整个组织的管理员访问权限。If you select Consent on behalf of your organization during the authentication flow, you will grant admin access to your entire organization. 请不要这样做。DO NOT do this.

    o365 全局管理员

若要加强管理员以外的安全性,请在 Azure 门户的“Office 365 Mover”应用设置中,启用“需要进行用户分配”。To tighten your security beyond administrators, turn on "User assignment required" from the "Office 365 Mover" app settings in your Azure portal. 你将需要专门分配可能使用该应用的迁移器用户。You will need to specifically assign your migrator users who may use the app.

需要进行用户分配

  1. 全局管理员或 SharePoint 管理员:授权连接器后,你将重定向到“Mover 转移向导”,并显示如下所示的错误。Global or SharePoint admin: After authorizing the connector, you are redirected to the Mover Transfer Wizard, and an error appears, like the following. 这意味着现在,租户中的全局管理员可以向 Azure 门户中的 Office 365 Mover 应用授予权限了。This means it is now time for a global admin in your tenant to grant permissions to the Office 365 Mover app in the Azure portal.

如果你是 SharePoint 管理员:若要授予权限并完成授权过程(步骤 6 – 9),请将全局管理员指向 **https://aka.ms/office365moverauth**。If you're a SharePoint admin: To grant permissions and finish the authorization process (Steps 6 – 9), point your global admin to https://aka.ms/office365moverauth.

如果你是 全局管理员:当收到该消息时,请继续执行步骤 6 – 9 以授权连接器:“无法检索用户数:全局管理员需授权 Azure 租户中的 Office 365 Mover 应用程序……”If you're a global admin: Continue with Steps 6–9 to authorize the connector when you receive the message: "Could not retrieve user count: A Global admin needs to authorize the Office 365 Mover application in the Azure tenant…"

授权错误图像

  1. 全局管理员:通过 https://aka.ms/office365moverauth 登录到 Azure 门户。Global admin: Log in to the Azure Portal via https://aka.ms/office365moverauth. 此时将显示“企业应用程序”列表。A list of Enterprise applications appears.

    企业应用程序

  2. 全局管理员:查找并选择 Office 365 Mover 应用。Global admin: Find and select the Office 365 Mover app. 此时将显示一个页面,其中提供了我们的应用概述。A page appears that provides an overview of our app.

    O365 Mover 应用

  3. 全局管理员:在左侧菜单中,查找并打开“权限”。Global admin: In the left menu, find and open Permissions. 选择“授予对 Mover 的管理员许可”。Select Grant admin consent for Mover. o365 mover 权限o365 mover permissions

  4. 全局管理员:将显示一个弹出窗口,指导你完成其余的权限过程。Global admin: A pop-up window appears that guides you through the rest of the permissions process. 完成后,它将自动关闭,并且你的 Office 365 连接器 已完全获得授权,随时可供访问。When complete, it closes automatically, and your Office 365 Connector is fully authorized and ready to go.

连接源 Office 365 帐户Connect your source Office 365 account

如果在授权源后尚未连接,请选择“Office 365”,然后加载连接器。If you are not already connected after you have authorized your source, select Office 365, and load the connector. 此时将出现一个图标,显示正在迁移的用户数。An icon appears, and shows you how many users you are migrating.

执行选择源 执行选择源