microsoft-365-docs
microsoft-365-docs copied to clipboard
Update cross-tenant-onedrive-migration-step5.md
Moved the compatibility step to the top as it needs to be checked first.
Fixes https://github.com/MicrosoftDocs/microsoft-365-docs-pr/issues/23693
@JohanFreelancer9 Please copy review
Learn Build status updates of commit 477c437:
:bulb: Validation status: suggestions
| File | Status | Preview URL | Details |
|---|---|---|---|
| microsoft-365/enterprise/cross-tenant-onedrive-migration-step5.md | :bulb:Suggestion | Details |
microsoft-365/enterprise/cross-tenant-onedrive-migration-step5.md
- Line 32, Column 1: [Suggestion: duplicate-h2s - See documentation]
Duplicate heading: 'H2 'Verify cross-tenant compatibility status''. Each second level heading (H2) in an article must be unique. - Line 183, Column 1: [Suggestion: duplicate-h2s - See documentation]
Duplicate heading: 'H2 'Verify cross-tenant compatibility status''. Each second level heading (H2) in an article must be unique.
For more details, please refer to the build report.
Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:
- Try searching the learn.microsoft.com contributor guides
- Post your question in the Learn support channel
Learn Build status updates of commit e5e0a44:
:bulb: Validation status: suggestions
| File | Status | Preview URL | Details |
|---|---|---|---|
| microsoft-365/enterprise/cross-tenant-onedrive-migration-step5.md | :bulb:Suggestion | Details |
microsoft-365/enterprise/cross-tenant-onedrive-migration-step5.md
- Line 32, Column 1: [Suggestion: duplicate-h2s - See documentation]
Duplicate heading: 'H2 'Verify cross-tenant compatibility status''. Each second level heading (H2) in an article must be unique. - Line 182, Column 1: [Suggestion: duplicate-h2s - See documentation]
Duplicate heading: 'H2 'Verify cross-tenant compatibility status''. Each second level heading (H2) in an article must be unique.
For more details, please refer to the build report.
Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:
- Try searching the learn.microsoft.com contributor guides
- Post your question in the Learn support channel
@JoanneHendrickson Please merge this PR. Thanks
@JoanneHendrickson Gentle reminder