Skip to content

Commit f8dc8ec

Browse files
authored
add some more of the limitations documented elsewhere to this page as well
limitations about recovery and versioning are listed i those places, but not explicitly listed here. adding/cross linking
1 parent 345b9b1 commit f8dc8ec

File tree

1 file changed

+2
-0
lines changed

1 file changed

+2
-0
lines changed

articles/azure-monitor/visualize/workbooks-bring-your-own-storage.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -37,6 +37,8 @@ There are times when you might have a query or some business logic that you want
3737

3838
- When you save to custom storage, you can't pin individual parts of the workbook to a dashboard because the individual pins would contain protected information in the dashboard itself. When you use custom storage, you can only pin links to the workbook itself to dashboards.
3939
- After a workbook has been saved to custom storage, it will always be saved to custom storage, and this feature can't be turned off. To save elsewhere, you can use **Save As** and elect to not save the copy to custom storage.
40+
- Workbooks saved to custom storage cannot be recovered by the support team. Users may be able to recover the workbook content if soft-delete or blob versioning are enabled on the underlying storage account. See [recovering a deleted workbook](workbooks-manage#recover-a-deleted-workbook)
41+
- Workbooks saved to custom storage do not support versioning, only the most recent version is stored. Other versions may be available in storage if blob versioning is enabled on the underlying storage account. See [manage workbook versions](workbooks-manage.md#manage-workbook-versions).
4042

4143
## Next steps
4244

0 commit comments

Comments
 (0)