Office 365、SharePoint、OneDrive間でファイルを移動する方法

2023 著者: Peter John Melton | [email protected]. 最終更新日: 2023-08-25 03:28

昨年、MicrosoftはOffice 365を使用してファイルをコピーできると発表しました。しかし今では、MicrosoftはユーザーにOffice 365のムービーファイルをメタデータとバージョン管理の完全な忠実性で保護することを許可しています。したがって、より大きな画像を見れば、すべてのプロセスを簡単にするのに役立ちます。さて、このすべてのものがどのように結びついて物事をより簡単にするのかを見てみましょう。

Office 365、SharePoint、OneDrive間でファイルを移動する

SharePoint全体でファイルを移動する場合は、チュートリアルのこのセクションが最も役立ちます。ザ へ引っ越す コマンドは本当に役立ちます。

まず、SharePoint内のファイルのファイルリストを選択する必要があります。

それを選択したら、上のスクリーンショットに示すようにコマンドバーに向かわなければなりません。

そのコマンドバーで、移動ファイルを移動するために。

その後、下の図に示すような目的地を選択するメニューが表示されます。

このターゲットのリストには、自分の仕事に関連するターゲットが表示されます。これは、 Microsoft Graph.

さて、あなたのファイルを移動する場所を選んでクリックしてください ここに移動 。これには、OneDriveのロケーション、Office 365のロケーションなどが含まれます。目的のターゲットが表示されていない場合でも、カスタムロケーションを選択することもできます。

よくある質問（FAQ）


File copy was rolled out over a year ago – does the new feature change anything with copying files?
For long time followers of the cross-site Copy feature, you may be interested to know that cross-site move is built on the same API that also powers scenarios like migration, publishing and point-in-time restore. As we roll out Move, we will remove the limit on the size of files and size of packages that you can Move or Copy.
As with Copy, you should be able to move files anywhere within your SharePoint tenants where you have permission to write files including sites located in other geographies. The notable exception is that you will not be able to move or copy files out of Information Rights Management (IRM) enabled libraries.







How is the new feature different from Copy?
A few things to note that are different about Copy and Move:

When files move, they will retain all their original versions from the source while Copy only delivers the final version of a file.
When a file is moving, it will still appear in the source directory until its fully moved to the destination and then it will be deleted. The file will remain in the source sites recycle bin after the Move is complete and be subject to the normal recycle schedule unless a user recovers it from the recycle bin

What happens if the target location doesn’t support metadata?
Moving files between libraries or sites preserves metadata by matching column names. If the destination does not have a matching column, metadata in the source column will be lost. In this case, you will be informed and prompted to confirm proceeding with the move and deleting the unmatched metadata. This is unlikely to happen when moving a file from your personal files (which do not currently support metadata) to SharePoint sites, but can happen when moving files between SharePoint libraries or sites with mismatched columns.







Administrators can reduce the incidence of this error by making sure that the columns on team sites are consistent across their team sites. In cases where that’s not possible, admins can give users guidance about how moves will impact metadata.
How does this work with Retention and Records Management?
If you are using data governance labels to control information policies for retention or records management, the policy labels applied to the source location must exist in the destination location. If the destination does not support policies applied to the file in the source, you will be blocked from moving the file, as doing so would circumvent retention or records management.
Finally, trying to move files already in a Records Center library will leave the source file in place, resulting in two copies of the file.
Can I move a OneNote notebook?
OneNote notebooks contain a grouping of many files. Moving a OneNote notebook will break the notebook into subsections and is not recommended at this point.