Moved KB from NAA to AIC (#266)

* Moved KB from NAA to AIC

* Proofreading Edits

Fix broken links and style issue:

  - Fix broken links to dropping_file_system_data (2 occurrences)
    - Change from absolute path with .md to relative path without extension
    - Update path: ../../accessanalyzer/file-system-and-sensitive-data-discovery/dropping_file_system_data
  - Change "included/excluded" to "included or excluded"

* minor updates

- Updated sidebar label and title formatting for clarity.
- Changed 'Related Links' to 'Related Link'

* Fix broken links in AIC KB article

Changed relative paths to Docusaurus absolute paths to fix build errors
in versioned directories. Removed /docs/ prefix and .md extension per
Docusaurus path conventions.

Fixes: broken links to dropping_file_system_data from versioned docs

* Fix broken links using full documentation URLs

Changed from absolute Docusaurus paths to full docs.netwrix.com URLs
per KB linking standards. Uses 12_0 (underscore) in URL as per Docusaurus
URL conventions.

Fixes: broken cross-product KB links in versioned directories

* minor formatting revision

- changed lines 41 from 'going forward' to 'in the future'
- revised bold formatting

(per the Documentation Reviewer feedback)

---------

Co-authored-by: Hil-Ram-NWX <hilary.ramirez@netwrix.com>

Author: tay-caliguiri

docs/kb/accessanalyzer/reports-and-web-console/out-of-scope_resources_still_appear_in_the_aic_or_reporting_console_after_scoping_changes.md

@@ -0,0 +1,47 @@
+---
+description: >-
+  Learn why out-of-scope File System resources may continue to appear in the Access Information Center (AIC) or reporting console after scoping changes, and how to remove the retained data from the database.
+keywords:
+  - File System resources
+  - Access Information Center
+  - AIC
+  - scoping rules
+  - FSAA scan
+  - SEEK scan
+  - Netwrix Access Analyzer
+  - drop file system data
+  - reporting console
+products:
+  - access-analyzer
+  - access-information-center
+sidebar_label: "Out-of-Scope Resources in AIC"
+title: "Out-of-Scope Resources Still Appear in the AIC or Reporting Console After Scoping Changes"
+knowledge_article_id: kA0Qk0000002mDRKAY
+---
+
+# Out-of-Scope Resources Still Appear in the AIC or Reporting Console After Scoping Changes
+
+## Symptom
+
+File System resources that were previously scanned and imported continue to appear in the database, even after scoping options have been updated to exclude them. These resources do not appear in new FSAA or SEEK scans but still exist in the backend database, causing them to remain visible in the Access Information Center (AIC) and reports.
+
+## Cause
+
+Scoping options are applied at the time of a scan and are used to determine which resources are included or excluded in that specific FSAA or SEEK scan. If a resource was imported before the scoping rules were put in place, it remains in the database, regardless of whether it is currently in scope.
+
+## Resolution
+
+If you no longer want to retain or see data for out-of-scope resources:
+
+1. Delete all **File System data** for the specific host from the database.
+   See the following article for instructions to drop data for a specific file server:
+   [How to Drop File System Data from Netwrix Access Analyzer](https://docs.netwrix.com/docs/accessanalyzer/12_0/kb/file-system-and-sensitive-data-discovery/dropping_file_system_data)
+
+2. Rescan the host with the updated scoping rules in place.  
+   This ensures that only resources matching the current scoping criteria are imported and retained in the future.
+
+> **NOTE:** While out-of-scope resources remain in the database, they are not included in future scans or updated during bulk imports unless they are brought back into scope.
+
+## Related Link
+
+- [How to Drop File System Data from Netwrix Access Analyzer](https://docs.netwrix.com/docs/accessanalyzer/12_0/kb/file-system-and-sensitive-data-discovery/dropping_file_system_data)