Skip to content

Commit 2027b73

Browse files
authored
Merge pull request #218577 from Blackmist/main
removing tip
2 parents 8493ff9 + d33c30e commit 2027b73

File tree

1 file changed

+0
-3
lines changed

1 file changed

+0
-3
lines changed

articles/machine-learning/concept-soft-delete.md

Lines changed: 0 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -72,9 +72,6 @@ Optionally, you may permanently delete a workspace going to soft delete state fi
7272

7373
Permanently deleting a workspace allows a workspace name to be reused immediately after deletion. This behavior may be useful in dev/test scenarios where you want to create and later delete a workspace. Permanently deleting a workspace may also be required for compliance if you manage highly sensitive data. See [General Data Protection Regulation (GDPR) implications](#general-data-protection-regulation-gdpr-implications) to learn more on how deletions are handled when soft delete is enabled.
7474

75-
> [!TIP]
76-
> SDK/CLI options for deleting dependent resources are only possible in combination with permanently deleting a workspace, and fails in case a workspace is not permanently deleted to allow for best changes of recovering workspace data.
77-
7875
:::image type="content" source="./media/concept-soft-delete/soft-delete-permanently-delete.png" alt-text="Screenshot of the delete workspace form in the portal.":::
7976

8077
## Manage soft-deleted workspaces

0 commit comments

Comments
 (0)