Fix cross-instance documentation links

Convert internal cross-instance links to external URLs:
- KB files can't link directly to other plugin instances
- Convert /docs/accessanalyzer/* and /docs/auditor/* to https://docs.netwrix.com URLs
- Fixes docusaurus multi-instance link resolution warnings

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <[email protected]>

Author: 2 people

docs/kb/accessanalyzer/console-migration-workflow-step-1-staging-the-backup.md

@@ -24,7 +24,7 @@ knowledge_article_id: kA0Qk0000002OnpKAE
 
 # Console Migration Workflow: Step 1—Staging the Backup
 
-> **NOTE:** Return to the main workflow page via this link: [Console Migration Workflow](/docs/accessanalyzer/console-migration-workflow.md).
+> **NOTE:** Return to the main workflow page via this link: [Console Migration Workflow](/docs/kb/accessanalyzer/console-migration-workflow.md).
 >
 > Proceed to the next section via this link: [Console Migration Workflow: Step 2—Prepare the Database](/docs/accessanalyzer/console-migration-workflow-step-2-prepare-the-database).
 
@@ -98,5 +98,5 @@ Within the `NAA_Migration` folder, create a folder named **AIC**, and add the fo
 
 ## Related Links
 
-- [Console Migration Workflow](/docs/accessanalyzer/console-migration-workflow.md)
+- [Console Migration Workflow](/docs/kb/accessanalyzer/console-migration-workflow.md)
 - [Console Migration Workflow: Step 2—Prepare the Database](/docs/accessanalyzer/console-migration-workflow-step-2-prepare-the-database)

docs/kb/accessanalyzer/console-migration-workflow-step-2-prepare-the-database.md

@@ -24,7 +24,7 @@ knowledge_article_id: kA0Qk0000002OpRKAU
 
 # Console Migration Workflow: Step 2—Prepare the Database
 
-> **NOTE:** Return to the main workflow page via this link: [Console Migration Workflow](/docs/accessanalyzer/console-migration-workflow.md).
+> **NOTE:** Return to the main workflow page via this link: [Console Migration Workflow](/docs/kb/accessanalyzer/console-migration-workflow.md).
 >
 > Return to the previous section via this link: [Console Migration Workflow: Step 1—Staging the Backup](/docs/accessanalyzer/console-migration-workflow-step-1-staging-the-backup).
 >
@@ -70,6 +70,6 @@ Where SA_Node = @OHost;
 
 ## Related Links
 
-- [Console Migration Workflow](/docs/accessanalyzer/console-migration-workflow.md)
+- [Console Migration Workflow](/docs/kb/accessanalyzer/console-migration-workflow.md)
 - [Console Migration Workflow: Step 1—Staging the Backup](/docs/accessanalyzer/console-migration-workflow-step-1-staging-the-backup)
 - [Console Migration Workflow: Step 3—Rebuild the Console](/docs/accessanalyzer/console-migration-workflow-step-3-rebuild-the-console)

docs/kb/accessanalyzer/console-migration-workflow-step-3-rebuild-the-console.md

@@ -22,7 +22,7 @@ knowledge_article_id: kA0Qk0000002Or3KAE
 
 # Console Migration Workflow: Step 3—Rebuild the Console
 
-> **NOTE:** Return to the main workflow page via this link: [Console Migration Workflow](/docs/accessanalyzer/console-migration-workflow.md).
+> **NOTE:** Return to the main workflow page via this link: [Console Migration Workflow](/docs/kb/accessanalyzer/console-migration-workflow.md).
 >
 > Return to the previous section via this link: [Console Migration Workflow: Step 2—Prepare the Database](/docs/accessanalyzer/console-migration-workflow-step-2-prepare-the-database).
 >

docs/kb/accessanalyzer/console-migration-workflow-step-4-validate-the-migration.md

@@ -23,7 +23,7 @@ knowledge_article_id: kA0Qk0000002OsfKAE
 
 # Console Migration Workflow: Step 4—Validate the Migration
 
-> **NOTE:** Return to the main workflow page via this link: [Console Migration Workflow](/docs/accessanalyzer/console-migration-workflow.md).
+> **NOTE:** Return to the main workflow page via this link: [Console Migration Workflow](/docs/kb/accessanalyzer/console-migration-workflow.md).
 >
 > Return to the previous section via this link: [Console Migration Workflow: Step 3—Rebuild the Console](/docs/accessanalyzer/console-migration-workflow-step-3-rebuild-the-console).
 
@@ -43,5 +43,5 @@ After completing Steps 1-3, please verify the following:
 
 ## Related Links
 
-- [Console Migration Workflow](/docs/accessanalyzer/console-migration-workflow.md)
+- [Console Migration Workflow](/docs/kb/accessanalyzer/console-migration-workflow.md)
 - [Console Migration Workflow: Step 3—Rebuild the Console](/docs/accessanalyzer/console-migration-workflow-step-3-rebuild-the-console)

docs/kb/auditor/cannot_execute_powershell_сommand_error_in_exchange_online_monitoring_plan.md

@@ -59,7 +59,7 @@ Update-Module -Name "ExchangeOnlineManagement"
 
 ### Resolution 2. For Netwrix Auditor v10.6
 
-> **NOTE:** Netwrix Auditor v10.6.12275 (GA) installs and requires ExchangeOnlineManagement PowerShell module v3.0 to operate. For Netwrix Auditor v10.6.12275 users, it is recommended to upgrade to the latest version available. For additional information, refer to the following link: [Upgrade to the Latest Version ⸱ v10.6](/docs/auditor/10.8/install/upgrade.md).  
+> **NOTE:** Netwrix Auditor v10.6.12275 (GA) installs and requires ExchangeOnlineManagement PowerShell module v3.0 to operate. For Netwrix Auditor v10.6.12275 users, it is recommended to upgrade to the latest version available. For additional information, refer to the following link: [Upgrade to the Latest Version ⸱ v10.6](https://docs.netwrix.com/docs/auditor/10.8/install/upgrade).  
 > Netwrix Auditor v10.6.12299 (Update 1) installs and requires ExchangeOnlineManagement PowerShell module v3.2 to operate.
 
 1. Netwrix Auditor v10.6.12299 (Update 1) uses the ExchangeOnlineManagement PowerShell (EXO) module v3.2 and newer.

docs/kb/auditor/determining_which_access_analyzer_collectors_support_gmsa.md

@@ -43,8 +43,8 @@ The following Netwrix Access Analyzer data collectors have been tested and confi
 
 Ensure that the gMSA account is granted all required permissions as described in the Help Center:
 
-[Configure a gMSA Account for Collector Connections](/docs/accessanalyzer/12.0/admin/settings/connection/gmsa.md)
+[Configure a gMSA Account for Collector Connections](https://docs.netwrix.com/docs/accessanalyzer/12.0/admin/settings/connection/gmsa)
 
 ## Related Link
 
-- [Configure a gMSA Account for Collector Connections](/docs/accessanalyzer/12.0/admin/settings/connection/gmsa.md)
+- [Configure a gMSA Account for Collector Connections](https://docs.netwrix.com/docs/accessanalyzer/12.0/admin/settings/connection/gmsa)

docs/kb/auditor/migrating_netwrix_access_analyzer_database_to_a_new_sql_server.md

@@ -77,7 +77,7 @@ GO
 ALTER USER [<SA User ID>] WITH DEFAULT_SCHEMA = dbo
 ```
 
-> **NOTE:** If Role-Based Access is used, make sure all required database roles are copied or recreated in the new database. For more information, see [Configuring Roles in Access Analyzer](/docs/accessanalyzer/12.0/admin/settings/access/rolebased/configureroles.md).
+> **NOTE:** If Role-Based Access is used, make sure all required database roles are copied or recreated in the new database. For more information, see [Configuring Roles in Access Analyzer](https://docs.netwrix.com/docs/accessanalyzer/12.0/admin/settings/access/rolebased/configureroles).
 
 ### 4. Update Access Analyzer Storage Configuration
 
@@ -87,20 +87,20 @@ After restoring the database and setting permissions, follow these steps to reco
 2. When the console opens, an error message may appear stating the database cannot be reached. This is expected.
 3. Close the error window.
 4. Select **Add New Storage Profile**.  
-   > **NOTE:** For more details, see [Add a Storage Profile](/docs/accessanalyzer/12.0/admin/settings/storage/add.md).
+   > **NOTE:** For more details, see [Add a Storage Profile](https://docs.netwrix.com/docs/accessanalyzer/12.0/admin/settings/storage/add).
 5. Enter the connection details for the new SQL Server and database.
 6. Test connectivity and ensure the console connects successfully.
 7. Select the **Set as Default** option on the new storage profile.  
-   > **NOTE:** For more details, see [Set a Default Storage Profile](/docs/accessanalyzer/12.0/admin/settings/storage/default.md).
+   > **NOTE:** For more details, see [Set a Default Storage Profile](https://docs.netwrix.com/docs/accessanalyzer/12.0/admin/settings/storage/default).
 8. Close and reopen **Access Analyzer** to verify persistent connectivity.
 9. Once you have confirmed successful reconnection, delete the old storage profile.  
-   > **NOTE:** For more details, see [Delete a Storage Profile](/docs/accessanalyzer/12.0/admin/settings/storage/delete.md).
+   > **NOTE:** For more details, see [Delete a Storage Profile](https://docs.netwrix.com/docs/accessanalyzer/12.0/admin/settings/storage/delete).
 
 ## Related Links
 
-- [Configuring Roles in Access Analyzer](/docs/accessanalyzer/12.0/admin/settings/access/rolebased/configureroles.md)
-- [Managing Storage in Access Analyzer](/docs/accessanalyzer/12.0/admin/settings/storage/overview.md)
+- [Configuring Roles in Access Analyzer](https://docs.netwrix.com/docs/accessanalyzer/12.0/admin/settings/access/rolebased/configureroles)
+- [Managing Storage in Access Analyzer](https://docs.netwrix.com/docs/accessanalyzer/12.0/admin/settings/storage/overview)
 - [Move a Database ⸱ Microsoft 🡥](https://learn.microsoft.com/en-us/data-migration/)
-- [Add a Storage Profile](/docs/accessanalyzer/12.0/admin/settings/storage/add.md)
-- [Set a Default Storage Profile](/docs/accessanalyzer/12.0/admin/settings/storage/default.md)
-- [Delete a Storage Profile](/docs/accessanalyzer/12.0/admin/settings/storage/delete.md)
+- [Add a Storage Profile](https://docs.netwrix.com/docs/accessanalyzer/12.0/admin/settings/storage/add)
+- [Set a Default Storage Profile](https://docs.netwrix.com/docs/accessanalyzer/12.0/admin/settings/storage/default)
+- [Delete a Storage Profile](https://docs.netwrix.com/docs/accessanalyzer/12.0/admin/settings/storage/delete)