Add audit events for folder recovery and cleanup#3058
Conversation
|
@shengchen-ms : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. |
|
Learn Build status updates of commit 81f49bd: ✅ Validation status: passed
For more details, please refer to the build report. |
Adds two new operations to the Fabric audit log operation list: - RecoveredSubfolder: emitted when one or more soft-deleted folders are recovered as part of artifact recovery. - HardDeletedSubfolderByCleanupScheduler: emitted when the cleanup scheduler hard-deletes an expired soft-deleted folder.
81f49bd to
9143370
Compare
|
Learn Build status updates of commit 9143370: ✅ Validation status: passed
For more details, please refer to the build report. |
|
Can you review the proposed changes? IMPORTANT: When the changes are ready for publication, adding a #label:"aq-pr-triaged" |
There was a problem hiding this comment.
Pull request overview
This PR updates the Fabric audit log operation list to document two new folder-recovery/cleanup audit events so admins can identify when soft-deleted folders are recovered or permanently removed by retention cleanup.
Changes:
- Added
RecoveredSubfolderto the audit operation list for folder recovery during artifact recovery. - Added
HardDeletedSubfolderByCleanupSchedulerto the audit operation list for retention-based hard deletion by the cleanup scheduler. - Updated
ms.dateto reflect the documentation change date.
| | Goals Delete Role | :::no-loc text="GoalsDeleteRole"::: | | | ||
| | Goals Get Role | :::no-loc text="GoalsGetRole"::: | | | ||
| | Goals Update Role | :::no-loc text="GoalsUpdateRole"::: | | | ||
| | Hard-deleted a folder by cleanup scheduler (Preview) | :::no-loc text="HardDeletedSubfolderByCleanupScheduler"::: | Generated when the cleanup scheduler hard-deletes a soft-deleted folder after the retention period expires. Available when [item recovery](item-recovery.md) is enabled in tenant admin settings. | |
| | Rebind Report | :::no-loc text="RebindReport"::: | | | ||
| | Received Power BI dataflow secret from Key Vault | :::no-loc text="ReceiveDataflowSecretFromKeyVault"::: | | | ||
| | Recovered an item (Preview) | :::no-loc text="ArtifactRecovered"::: | Generated when a soft-deleted item is recovered. Available when [item recovery](item-recovery.md) is enabled in tenant admin settings. | | ||
| | Recovered folder (Preview) | :::no-loc text="RecoveredSubfolder"::: | Generated when one or more soft-deleted folders are recovered as part of artifact recovery. Available when [item recovery](item-recovery.md) is enabled in tenant admin settings. | |
Adds two new operations to the Fabric audit log operation list:
RecoveredSubfolder: emitted when one or more soft-deleted folders are recovered as part of artifact recovery.
HardDeletedSubfolderByCleanupScheduler: emitted when the cleanup scheduler hard-deletes an expired soft-deleted folder.
Thank you for contributing to Microsoft Fabric documentation
Fill out these items before submitting your pull request:
If you are working internally at Microsoft:
Provide a link to an Azure DevOps Boards work item that tracks this feature/update.
Who is your primary Skilling team contact? @mention them individually tag them and let them review the PR before signing off.
For internal Microsoft contributors, check off these quality control items as you go
1. Check the Acrolinx report: Make sure your Acrolinx Total score is above 80 minimum (higher is better) and with no spelling issues. Acrolinx ensures we are providing consistent terminology and using an appropriate voice and tone, and helps with localization.
2. Successful build with no warnings or suggestions: Review the build status to make sure all files are green (Succeeded).
3. Preview the pages:: Click each Preview URL link to view the rendered HTML pages on the review.learn.microsoft.com site to check the formatting and alignment of the page. Scan the page for overall formatting, and look at the parts you edited in detail.
4. Check the Table of Contents: If you are adding a new markdown file, make sure it is linked from the table of contents.
5. #sign-off to request PR review and merge: Once the pull request is finalized and ready to be merged, indicate so by typing
#sign-offin a new comment in the Pull Request. If you need to cancel that sign-off, type#hold-offinstead. Signing off means the document can be published at any time. Note, this is a formatting and standards review, not a technical review.Merge and publish
#sign-off, there is a separate PR Review team that will review the PR and describe any necessary feedback before merging.#sign-offagain. The PR Review team reviews and merges the pull request into the specified branch (usually the main branch or a release- branch).