microsoft-365-docs
microsoft-365-docs copied to clipboard
MicrosoftDocs
PST import caveat with autoexpansion
Adding caveat for network import into mailboxes that have autoexpanding turned on. (Premier support ticket 32045647)
Docs Build status updates of commit f408f94:
:warning: Validation status: warnings
| File | Status | Preview URL | Details |
|---|---|---|---|
| microsoft-365/compliance/enable-autoexpanding-archiving.md | :warning:Warning | Details |
microsoft-365/compliance/enable-autoexpanding-archiving.md
- Line 40, Column 62: [Warning: hard-coded-locale - See documentation]
Link 'https://docs.microsoft.com/en-us/microsoft-365/compliance/use-network-upload-to-import-pst-files?view=o365-worldwide' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites. - Line 40, Column 62: [Suggestion: docs-link-absolute - See documentation]
Absolute link 'https://docs.microsoft.com/en-us/microsoft-365/compliance/use-network-upload-to-import-pst-files?view=o365-worldwide' will be broken in isolated environments. Replace with a relative link. - Line 40, Column 62: [Suggestion: preserve-view-not-set - See documentation]
You've pinned this link to a specific version of content with the view parameter. It's recommended not to pin a version unless that version is A) not the default view and B) the context is about that version specifically. To proceed with pinning a version add the &preserve-view=true to the URL. Otherwise, remove the view parameter. URL: https://docs.microsoft.com/en-us/microsoft-365/compliance/use-network-upload-to-import-pst-files?view=o365-worldwide
For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link 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 docs.microsoft.com contributor guides
- Post your question in the Docs support channel
Docs Build status updates of commit bd1ffd3:
:warning: Validation status: warnings
| File | Status | Preview URL | Details |
|---|---|---|---|
| microsoft-365/compliance/enable-autoexpanding-archiving.md | :warning:Warning | Details |
microsoft-365/compliance/enable-autoexpanding-archiving.md
- Line 40, Column 62: [Warning: hard-coded-locale - See documentation]
Link 'https://docs.microsoft.com/en-us/microsoft-365/compliance/use-network-upload-to-import-pst-files?view=o365-worldwide' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites. - Line 40, Column 62: [Suggestion: docs-link-absolute - See documentation]
Absolute link 'https://docs.microsoft.com/en-us/microsoft-365/compliance/use-network-upload-to-import-pst-files?view=o365-worldwide' will be broken in isolated environments. Replace with a relative link. - Line 40, Column 62: [Suggestion: preserve-view-not-set - See documentation]
You've pinned this link to a specific version of content with the view parameter. It's recommended not to pin a version unless that version is A) not the default view and B) the context is about that version specifically. To proceed with pinning a version add the &preserve-view=true to the URL. Otherwise, remove the view parameter. URL: https://docs.microsoft.com/en-us/microsoft-365/compliance/use-network-upload-to-import-pst-files?view=o365-worldwide
For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link 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 docs.microsoft.com contributor guides
- Post your question in the Docs support channel
Yep perfect and thank you, wasn't sure how to make the relative URL work here given that every markdown file is in a different location.
Hi Yogesh. I believe we're cancelling this PR as document owners would want the information and context being added to be in a different location.
Thanks.
From: Yogesh Kumar @.> Sent: Tuesday, October 4, 2022 3:54 AM To: MicrosoftDocs/microsoft-365-docs @.> Cc: Patricia Dumas Bonnier (Sherweb Inc) @.>; Mention @.> Subject: Re: [MicrosoftDocs/microsoft-365-docs] PST import caveat with autoexpansion (PR #9720)
Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fmicrosoft-365-docs%2Fpull%2F9720%23issuecomment-1266545316&data=05%7C01%7Cv-padum%40microsoft.com%7Ce97d988884004466b43208daa5dd9731%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638004668412690945%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=m2rpsTo1ej3WPlMQncxIiSmA3DmrX5FPNYy%2B1cC2uJ0%3D&reserved=0, or unsubscribehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAPLQ4OMDDBNCMBR5DI7D32LWBPPBJANCNFSM6AAAAAAQMV225Y&data=05%7C01%7Cv-padum%40microsoft.com%7Ce97d988884004466b43208daa5dd9731%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638004668412690945%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=LjPRnk9CYtOO%2BF9Y2tHlocD%2FYTDO6FmJ3tPR7LcjX2g%3D&reserved=0. You are receiving this because you were mentioned.Message ID: @.***>
Yes, we agreed to move the support statement for PST files from the docs for auto-expanding to the PST import docs (with any new caveats) & I left this PR open in case you wanted to use this for the update & tracking.
Closing. We agreed offline that support statements for PST import belong with the PST import docs.