Guard workbook queries when an optional Log Analytics table is absent

Source facts

Microsoft describes using a workbook parameter query to check whether a table exists and hide dependent content when it does not. In that conditional-content pattern, the hidden dependent items are not run. Its example also uses a fuzzy union so a query can continue when some referenced tables are unavailable. Microsoft Learn.

Applicability

Use this review for a workbook distributed across workspaces with intentionally different data sources. Identify each optional table and the panels that depend on it. Do not treat an unexpectedly missing required table as an ordinary optional-data case. Review dependency graphs and merge references separately before relying on a conditional display guard.

DSE recommendation

DSE recommends documenting which panels are optional and displaying an understandable explanation when their data is unavailable. Review the source’s existence-check pattern and place dependent queries behind the corresponding condition. Keep the required-data panels separate so collection failures remain visible. Test a copy of the workbook before replacing the shared version.

Verification

Open the workbook against approved test workspaces with and without the optional table. Confirm the intended panels appear and execute only in the relevant case, while required-data failures remain apparent. Then restore the table or select a workspace containing it and verify that the dependent view becomes usable without editing its query. Preserve the workbook version and both test results.

Official references

Microsoft Learn: Create or edit an Azure Workbook.