You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: microsoft-365/backup/backup-overview.md
+6-4Lines changed: 6 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -107,12 +107,14 @@ The following table summarizes expected performance for a normally distributed t
107
107
|1 |30 minutes |2 hours |
108
108
|50 |3 hours |2.5 hours |
109
109
|250 |4 hours | 3 hours |
110
-
|1,000 |10 hours |4 hours |
111
-
|More than 1,000|250/hour<br>Up to 3 TB/hour |250+/hour<br>Up to 2.7 TB/hour |
110
+
|1,000+|Up to 250 protection units per hour|4 hours |
111
+
|1,000+|Up to 250 protection units/hour<br>Up to 2 TB/hour*|250+ protection units/hour<br>Up to 2 TB/hour*|
112
112
113
-
<sup>*Single protection unit OneDrive and SharePoint restores using express restore points can take on average between 10 minutes and 120 minutes.</sup>
113
+
<sup>Restore performance notes:</sup>
114
114
115
-
<sup>**Exchange Online performance times based on an average sized mailbox of 26K items and a size of 10 GB. Actual times will depend on the number and size of the items in each mailbox. For a single mailbox, restore times typically fall in the 200 - 300 item/minute range.</sup>
115
+
<sup>*Single protection unit OneDrive and SharePoint restores using express restore points can take on average between 10 minutes and 120 minutes, depending on site size.</sup> <sup>For mailboxes, restore times typically fall in the 200 - 300 item/minute range.</sup>
116
+
117
+
<sup>*1,000+ protection unit restore speeds published here are based on internal benchmarking where SharePoint sites have an average of 12GB of stored content per site, Exchange Online mailboxes have an average of 26K items and an aggregate size of 10 GB. Those bulk recoveries use the in-place restore option, which is typical for large scale attack recovery scenarios. Actual times will depend on the number and size of the items in each site/mailbox.</sup>
description: "Step 5 of the OneDrive Cross-tenant migration feature"
17
+
description: "Step 5 of the OneDrive Cross-tenant migration feature, involving identity mapping."
18
18
---
19
+
19
20
# Step 5: Identity mapping
20
21
21
-
This is Step 5 in a solution designed to complete a Cross-tenant OneDrive migration. To learn more, see [Cross-tenant OneDrive migration overview](cross-tenant-onedrive-migration.md).
22
+
This article is Step 5 in a solution designed to complete a Cross-tenant OneDrive migration. To learn more, see [Cross-tenant OneDrive migration overview](cross-tenant-onedrive-migration.md).
22
23
23
24
- Step 1: [Connect to the source and the target tenants](cross-tenant-onedrive-migration-step1.md)
24
25
- Step 2: [Establish trust between the source and the target tenant](cross-tenant-onedrive-migration-step2.md)
25
-
- Step 3: [Verify trust has been established](cross-tenant-onedrive-migration-step3.md)
26
-
- Step 4: [Pre-create users and groups](cross-tenant-onedrive-migration-step4.md)
26
+
- Step 3: [Verify trust is established](cross-tenant-onedrive-migration-step3.md)
27
+
- Step 4: [Precreate users and groups](cross-tenant-onedrive-migration-step4.md)
@@ -34,43 +35,43 @@ In this step of the cross-tenant migration process, you're going to create a sin
34
35
35
36
We recommend that you take the time to verify your mappings, ensuring they're accurate before starting any migrations to the target tenant.
36
37
37
-
There's a one-to-one relationship in the identity mapping file. You can't map the same user to multiple users in the target tenant. For example, if you have instances where the admin is the owner of multiple OneDrive accounts, the ownership must be changed to match the corresponding user you wish to migrate from Source to Target. If you don't, those account files won't migrate.
38
+
There's a one-to-one relationship in the identity mapping file. You can't map the same user to multiple users in the target tenant. For example, you may have instances where the admin is the owner of multiple OneDrive accounts. In this circumstance, the ownership must be changed to match the corresponding user you wish to migrate from Source to Target. If you don't, those account files don't migrate.
38
39
39
40
**Example:** In this example, the admin owns multiple OneDrive accounts.
There are six columns needed in your CSV file. The first three are your source values, each providing detail about where your data is currently located. The remaining three columns are the corresponding info on the target tenant. All six columns must be accounted for in the file. Create your file in Excel and save it as a .csv file.
60
61
61
-
Users and groups are included in the same file. Depending on whether it's a user or group, what you enter in the column is different. In each of the columns enter values as shown in the examples. **Do NOT include column headings.**
62
+
Users and groups are included in the same file. Depending on whether it's a user or group, what you enter in the column is different. In each of the columns enter values as shown in the examples. **DON'T include column headings.**
> **Do NOT include column headings in your CSV file.** In the examples below we include them for illustrative purposes only.
74
+
> **DON'T include column headings in your CSV file.** In the examples below we include them for illustrative purposes only.
74
75
75
76
**Users**. Enter your values as shown in this example for Users:
76
77
@@ -79,15 +80,14 @@ Users and groups are included in the same file. Depending on whether it's a user
79
80
:::image type="content" source="../media/cross-tenant-migration/t2t-onedrive-csv-mapping-users-example.png" alt-text="example of csv for users":::
80
81
81
82
**Groups**. Enter your values as shown in this example for Groups:
82
-
</br>
83
+
83
84
:::image type="content" source="../media/cross-tenant-migration/t2t-onedrive-csv-mapping-groups-columns.png" alt-text="format for csv file for groups":::
84
-
</br>
85
85
86
86
*Example*:
87
87
88
88
:::image type="content" source="../media/cross-tenant-migration/t2t-onedrive-csv-group-example.png" alt-text="example of adding groups to csv file":::
89
89
90
-
**Guest users**. You can map guest accounts in the source tenant to member accounts in the target tenant. You can also map a guest account in the source to a guest account in the target if the guest has been previously created. Enter your values as shown in this example for guests:
90
+
**Guest users**. You can map guest accounts in the source tenant to member accounts in the target tenant. You can also map a guest account in the source to a guest account in the target if the guest was previously created. Enter your values as shown in this example for guests:
91
91
92
92
:::image type="content" source="../media/cross-tenant-migration/t2t-onedrive-csv-mapping-users-guests.png" alt-text="csv example when mapping a guest to a member":::
93
93
@@ -106,50 +106,50 @@ To obtain Source Tenant Company ID:
106
106
1. Sign in as Admin to your [Azure portal](https://ms.portal.azure.com/)
107
107
2. Select or Search for **Microsoft Entra ID**.
108
108
3. Scroll down on the left-hand panel and select **Properties**.
109
-
4. Locate the **Tenant ID Field**. The required Tenant ID will be in that box.
109
+
4. Locate the **Tenant ID Field**. The required Tenant ID is in that box.
110
110
111
111
:::image type="content" source="../media/cross-tenant-migration/t2t-onedrive-azure-tenant-id.png" alt-text="getting the source tenant ID":::
112
112
113
113
## To obtain source group object ID:
114
114
115
115
1. Sign in to source tenant as Admin to [Azure Groups](https://ms.portal.azure.com).
116
-
2. Search for your required group(s).
117
-
3. Select the required Group instance and then **Copy to clipboard**. Paste this value in the sourceGroupObjectId column of your mapping CSV file.
116
+
2. Search for your required groups.
117
+
3. Select the required group instance and then **Copy to clipboard**. Paste this value in the sourceGroupObjectId column of your mapping CSV file.
118
118
4. If you have multiple Groups to map, then repeat these steps for each group.
119
119
120
120
:::image type="content" source="../media/cross-tenant-migration/t2t-onedrive-source-group-objectid.png" alt-text="getting the source group object ID":::
121
121
122
122
### To obtain target group object ID:
123
123
124
124
1. Sign in to Target tenant as Admin to [Azure Groups](https://ms.portal.azure.com)
125
-
2. Search for your required group(s).
125
+
2. Search for your required groups.
126
126
3. Select the required group instance and then **Copy to clipboard**. Paste this value in the targetGroupObjectId column of your mapping CSV file.
127
-
4. If you have multiple groups to map, then repeat the above process to obtain those specific targetGroupObjectId's.
127
+
4. If you have multiple groups to map, then repeat this process to obtain those specific targetGroupObjectIds.
128
128
5. For the GroupName, use the same ID as the *TargetGroupObjectId* you obtained.
129
129
130
130
:::image type="content" source="../media/cross-tenant-migration/t2t-onedrive-target-group-objectid.png" alt-text="how to get the target object ID":::
131
131
132
132
## Upload the identity map
133
133
134
-
Once the identity mapping file has been prepared, the SharePoint Administrator on the target tenant uploads the file to SharePoint. This will allow identity mapping to occur automatically as part of the cross-tenant migration.
134
+
Once the identity mapping file is prepared, the SharePoint Administrator on the target tenant uploads the file to SharePoint. This file allows identity mapping to occur automatically as part of the cross-tenant migration.
135
135
136
136
> [!IMPORTANT]
137
-
> Before you run the *Add-SPOTenantIdentityMap -IdentityMapPath* command, save and close the identitymap.csv file on your Desktop/OneDrive/SharePoint. If the file remains open, you will receive the following error.
137
+
> Before you run the *Add-SPOTenantIdentityMap -IdentityMapPath* command, save and close the identitymap.csv file on your Desktop/OneDrive/SharePoint. If the file remains open, you receive the following error:
138
138
>
139
139
> *Add-SPOTenantIdentityMap: The process cannot access the file 'C:\Users\myuser\Test-Identity-Map.csv' because it is being used by another process.*
140
140
141
-
1. To upload the identity Map on the target tenant, run the following command. For *-IdentityMapPath*, provide the full path and filename of the identity mapping CSV file.
141
+
1. To upload the identity Map on the target tenant, run the following command. For *-IdentityMapPath*, provide the full path and filename of the identity mapping CSV file.
> If you make or need to make any changes to your Identity Map during the lifecycle of the migration you must run the `Add-SPOTenantIdentityMap -IdentityMapPath <identitymap.csv>` command **every time** a change is made to ensure those changes are applied to the migration.
148
+
> If you make or need to make any changes to your Identity Map during the lifecycle of the migration, you must run the `Add-SPOTenantIdentityMap -IdentityMapPath <identitymap.csv>` command **every time** a change is made to ensure those changes are applied to the migration.
149
149
150
-
Uploading any new identity map will overwrite the current one. Make sure that any revision or addition includes ALL users and groups for the full migration. Your identity map should always include everyone you're wanting to migrate.
150
+
Uploading any new identity map overwrites the current one. Make sure that any revision or addition includes ALL users and groups for the full migration. Your identity map should always include everyone you're wanting to migrate.
151
151
152
-
To look at the mapping entries in the identity mapping file for a particular user, use the command *Get-SPOTenantIdentityMappingUser* with Field as *SourceUserKey* and Value as the UPN of the user you are moving.
152
+
You can look at the mapping entries in the identity mapping file for a particular user. Use the command *Get-SPOTenantIdentityMappingUser,* with Field as *SourceUserKey* and Value as the UPN of the user you're moving.
- If the tenant status shows as **Compatible** or **Warning**, you can then proceed with the next step of starting cross-tenant migrations.
173
-
- If the tenant status shows as **Incompatible**, your tenants will need to be patched/updated to ensure compatibility.
173
+
- If the tenant status shows as **Incompatible**, your tenants need to be patched/updated to ensure compatibility.
174
174
175
-
|Status|Can proceed with migration|
176
-
|---|---|
177
-
|Compatible|Yes|
178
-
|Warning|Yes|
179
-
|Incompatible|No|
175
+
|Status|Can proceed with migration|
176
+
|-------------|---------------------------|
177
+
|Compatible|Yes|
178
+
|Warning|Yes|
179
+
|Incompatible|No|
180
180
181
181
> [!NOTE]
182
-
> We recommend waiting a period of 48 hours. If your tenants are still reporting as *incompatible*, contact support.
182
+
> We recommend waiting a period of 48 hours. If your tenants still report as *incompatible*, contact support.
183
183
>
184
-
> We recommend performing the compatibility status check on a frequent basis and prior to starting ANY instances of cross tenant migrations. If the tenants are not compatible, this can result in cross-tenant migrations failing.
184
+
> We recommend performing the compatibility status check on a frequent basis and before starting ANY instances of cross tenant migrations. If the tenants aren't compatible, it can result in cross-tenant migrations failing.
185
185
186
186
## Step 6: [Start a OneDrive cross-tenant migration](cross-tenant-onedrive-migration-step6.md)
0 commit comments