Add instructions to undelete / restore deleted files via Microsoft Az… #1495
Conversation
…ure Storage Explorer
|
@jugi92 : Thanks for your contribution! The author(s) have been notified to review your proposed change. |
|
Learn Build status updates of commit 39758f5: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
PRMerger Results
|
|
Can you review the proposed changes? Important: When the changes are ready for publication, adding a #label:"aq-pr-triaged" |
| ### Restore soft deleted files via Microsoft Azure Storage Explorer | ||
|
|
||
| You can restore files which were deleted from a Lakehouse by connecting via Microsoft Azure Storage Explorer with the following steps: | ||
| 1. Download, Install and Open Microsoft Azure Storage Explorer |
There was a problem hiding this comment.
It would be better to link to the instructions for connect to ASE here: https://learn.microsoft.com/en-us/fabric/onelake/onelake-azure-storage-explorer for completeness and make sure it's up to date.
| 1. Enter connection Info | ||
| Blob Container or Directory URL: https://onelake.dfs.fabric.microsoft.com/ + your workspace ID, | ||
| e.g. `https://onelake.dfs.fabric.microsoft.com/8ebe7fed-acac-4905-8e5c-027c55521e54`. You can get the workspace ID from the URL, it is the Id which follows the groups/ part in the URL. | ||
| Note: the undelete API call will not work using the workspace name as the container name. |
There was a problem hiding this comment.
I want to double check this issue and use consistent terminology in the description. " Note: the undelete API call will not work using the workspace name as the container name."
|
Adding this content would be great but there are some edits to make before it's done. |
…ure Storage Explorer
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).