docs: improve definition of a Backup #5316
Conversation
Current Aviator status
This PR was merged manually (without Aviator). Merging manually can negatively impact the performance of the queue. Consider using Aviator next time.
See the real-time status of this PR on the
Aviator webapp.
Use the Aviator Chrome Extension
to see the status of your PR within GitHub.
|
|
|
OrhanTozan
changed the title
Co-authored-by: ashmrtn <[email protected]>
|
@ashmrtn no problem, I added your apostrophe suggestion btw. |
|
@ashmrtn any idea why the build fails? It's only a textual docs change. |
|
Sorry! I forgot GH can be weird about displaying actions sometimes. Looks like a line too long linting error If you want to run the linter locally there's directions in a README in the website folder as well 😄 |
|
|
@ashmrtn aha, ok. I couldn't find that error in the logs. I fixed the line length. |
After some building, I realized that a backup is a snapshot of a resource, not the whole m365 service. Initially, I assumed that 1 backup takes the whole service per tenant (https://discord.com/channels/1022200980487557130/1022200981376745474/1231385151376719892). This doc update should help clear the confusion more.
Maybe there is a better way to word it, so any other suggestions are welcome.
Does this PR need a docs update or release note?
Type of change
Issue(s)
Test Plan