# Resource exclusions

> Apply resource-level or test-level exclusions to reflect your audit scope and approved exceptions, with the original evidence retained for audit review.

Source: https://tidalcontrol.com/docs/tests/resource-exclusions

Resource exclusions align automated tests with your organisation's audit scope and approved exceptions. Tidal Control supports exclusions at resource level and test level, with the original evidence retained for review.

## Resource-level exclusions

Use resource-level exclusions when a resource is outside the audit scope across supported checks, such as a development resource explicitly excluded from the assessment.

See provider-specific instructions for supported resources and configuration steps:

- [Microsoft Azure](/docs/tests/excluding-resources-with-tags)
- [Amazon Web Services (AWS)](/docs/tests/excluding-aws-resources-with-tags)

## Test-level exclusions

Use test-level exclusions when a resource remains in scope but a specific requirement does not apply or has an approved exception. Excluding a resource from one test does not affect its inclusion in other tests.

These exclusions are managed within the test in Tidal Control. You can apply them to saved results, future runs or a selected period.

[Configure per-test exclusions](/docs/tests/excluding-resources).

## Evidence and test results

Excluded resources do not contribute to the affected test's Passed or Failed status. Their observed results, evidence and exclusion reasons remain visible. Exclusions do not resolve technical Errors.