Added Windows Server 2025 and SQL Server 2025 as supported OS and data storage

[tay-caliguiri]

Update NAA Product documentation to reflect Windows Server 2025 and SQL Server 2025 as supported.

Updated the following sections:

• System Requirement
• SQL Server Requirement
• FSAA Proxy supported OS
• SPAA agent
• NAA Upgrade
• Database solution target
• AIC Requirement
• SDD Add-on supported OS (11.6)

AAL-1660

[github-actions]

Documentation PR Review

Reviewed the 18 changed files. The Windows Server 2025 / SQL Server 2025 additions are consistent and complete within Access Analyzer 11.6 and 12.0 — every supported-platform list that had a 2022 upper bound now includes 2025. One coverage gap and several editorial issues in the accompanying voice rewrites are listed below.

Editorial Review

docs/accessanalyzer/11.6/install/application/upgrade/overview.md

• Structure — Line 41: The license-key paragraph ("Granting access to additional Solutions … requires a new license key.") sits under the SQL Server Supported Version Change for the Enterprise Auditor Database subheading, where a reader scanning for SQL Server version information won't expect it — and where a reader looking for license information won't find it. Suggested fix: move this paragraph below the License Key Changes subheading at line 47.
• Clarity — Line 49: "The following licensing changes require the organization to get a new key:" contradicts the first two list entries, which say "This version requires no additional licenses." The list is a version-by-version licensing history, not a list of changes that force a new key. Suggested fix: "The following list shows licensing changes by version. Upgrading to a version that introduces a new licensable feature requires a new license key:"
• Structure — Lines 51–56: The list mixes loose and tight formatting — "Enterprise Auditor v11.6" has a blank line before its sub-bullet, "StealthAUDIT v11.5" doesn't. This renders with uneven spacing between entries. Suggested fix: use the same spacing for every top-level entry (no blank line before sub-bullets, matching lines 55–62).

docs/accessanalyzer/11.6/install/filesystemproxy/overview.md

• Clarity — Line 76: Expanding "FileSystemAccess (FSAA)" here is correct for first use, but it makes the second expansion at line 130 redundant. Suggested fix: change line 130 to "the FSAA Data Collector".

docs/accessanalyzer/11.6/install/sensitivedatadiscovery/overview.md

No issues found.

docs/accessanalyzer/11.6/requirements/databases/sql/sql.md

• Structure — Line 14: The blank line between "Azure SQL" (line 12) and "SQL Server 2025" splits the supported-platforms list into two separate lists, which Docusaurus renders with extra vertical spacing as though they were unrelated. Suggested fix: delete the blank line at line 13 so all five platforms form one list.
• Clarity — Line 39: "Configure SQL Server Audit Specifications on the target databases" is an imperative instruction inside a list of requirements whose other entries are noun phrases and must-statements ("Audit destination must be a binary file"). The break in parallelism makes the list read as a mix of steps and requirements. Suggested fix: "SQL Server Audit Specifications configured on the target databases".
• Completeness — Line 22 (context, lines 83–85 unchanged): The parallel sentence in 12.0 was rewritten in this PR to "Requires the SQL Full-Text and Semantic Extractions for Search feature on the target SQL instances when you use…", but the 11.6 copy at lines 83–85 still reads "…to be installed on the target SQL instances when using…". Suggested fix: apply the same rewrite here so the two versions match.

docs/accessanalyzer/11.6/requirements/filesystem/filesystems/filesystems.md

• Completeness — Line 55: "See the File System Supported Platforms topic for additional information" points at this page — the reader is sent back to where they already are, and the reference isn't a link. Suggested fix: link to the topic that actually documents per-mode permissions, for example "See the Scan Options topic for additional information."

docs/accessanalyzer/11.6/requirements/filesystem/scanoptions/proxymodescans/proxymodeserver.md

• Clarity — Lines 32–33: The SDD RAM example was rewritten to third person ("a job configured to scan 8 hosts at a time … requires an extra 32 GB"), but the identical example in install/filesystemproxy/overview.md (lines 146–150) uses second person ("if you configure the job to scan 8 hosts … you need an extra 32 GB"). A reader who sees both copies gets the same fact in two voices. Suggested fix: use the second-person wording in both places, per the "use 'you' for procedures" standard.

docs/accessanalyzer/11.6/requirements/overview.md

• Clarity — Line 16: "Installing the application requires the following servers and applications:" overstates the case. The list that follows includes an optional add-on, Exchange/File System/SharePoint solution-specific components, and a proxy server needed only "in certain environments". Suggested fix: "Installing the application involves the following servers and applications, depending on which solutions you deploy:"
• Structure — Lines 23–30: The note repeats the bullet it follows. The bullet already says "You typically install this application on the Enterprise Auditor Console server"; the note says "You often install the Access Information Center on the same server as the Enterprise Auditor application." Only the "but you can install it separately" clause adds information. Suggested fix: keep the placement statement in the bullet, define the component first, and reduce the note to the exception — for example, bullet: "Access Information Center Application Server – A browser-based, interactive dashboard for exploring permissions, activity, and sensitive data. You typically install it on the Enterprise Auditor Console server."; note: "You can also install the Access Information Center on a separate server."
• Clarity — Lines 55 and 67: These bullets now use active voice ("You install this application…"), but the two neighboring bullets they sit between still use the old passive/conditional phrasing — line 48 ("a proxy server may be used", "The applet would be deployed") and line 61 ("this application can be installed"). The section now reads in two voices. Suggested fix: convert lines 48–52 and 61–64 the same way, matching the 12.0 wording at lines 39–44 and 48–52.
• Clarity — Line 186: "SQL Server must be an equal or newer version than the targeted version" is ungrammatical as a comparison ("equal … than"), and "the targeted version" doesn't say what is being targeted. Suggested fix: "The SQL Server hosting the Enterprise Auditor database must be the same version as, or newer than, any SQL Server you target for scanning."

docs/accessanalyzer/11.6/requirements/sharepoint/scanoptions/agentbasedscans/agentpermissions.md

• Clarity — Line 17: "Install the Enterprise Auditor SharePoint Agent on the:" breaks off mid-phrase before the colon. Suggested fix: "Install the Enterprise Auditor SharePoint Agent on the following server:"
• Clarity — Line 166: Dropping "last" from "this last permission requirement" removed the only thing that identified which requirement is meant. The preceding list has two entries (lines 162–163), so the reader can't tell which one is already satisfied. Suggested fix: "If scans include Web Application scoping, you have already met the WSS_CONTENT_APPLICATION_POOLS requirement on the SharePoint Configuration database."
• Completeness — Line 22: This change raises the supported OS floor for 11.6 from Windows Server 2012 to Windows Server 2016, which removes two previously documented platforms rather than adding one. It matches the 11.6 requirements overview (line 92) and 12.0, so it looks like a deliberate correction — please confirm, since dropping documented platform support is a substantive change that customers on 2012 will notice.

docs/accessanalyzer/11.6/solutions/databases/sql/overview.md

• Clarity — Line 49: "The SQL Job Group within the Jobs tree, as part of the Database Solution: Jobs > Database > SQL." is a sentence fragment with no verb. Suggested fix: "The SQL Job Group is in the Jobs tree, as part of the Database Solution: Jobs > Database > SQL." (matches 12.0, line 43).
• Clarity — Line 73: "provides insight into use login activity" — "use" should be "user". Suggested fix: "provides insight into user login activity".
• Structure — Line 18: Same split list as requirements/databases/sql/sql.md — the blank line after "Azure SQL" (line 16) breaks the supported-platforms list in two. Suggested fix: delete the blank line at line 17.

docs/accessanalyzer/12.0/install/application/upgrade/overview.md

No issues found.

docs/accessanalyzer/12.0/install/filesystemproxy/overview.md

No issues found.

docs/accessanalyzer/12.0/requirements/databases/sql/sql.md

• Clarity — Line 37: Same parallelism break as the 11.6 file — an imperative ("Configure SQL Server Audit Specifications on the target databases") inside a list of requirements. Suggested fix: "SQL Server Audit Specifications configured on the target databases".
• Clarity — Lines 81–83: "Requires the SQL Full-Text and Semantic Extractions for Search feature…" starts with a bare verb and no subject, unlike its sibling bullets ("Read access to SQL instance", "Grant Connect SQL to…"). Suggested fix: "SQL Full-Text and Semantic Extractions for Search feature installed on the target SQL instances, if you use the Scan full rows for sensitive data option on the Options wizard page".

docs/accessanalyzer/12.0/requirements/filesystem/filesystems/filesystems.md

• Completeness — Line 55: Same self-referential, unlinked cross-reference as the 11.6 file — "See the File System Supported Platforms topic" sends the reader to this page. Suggested fix: link to Scan Options instead.

docs/accessanalyzer/12.0/requirements/filesystem/scanoptions/proxy-mode-scans/proxymodeserver.md

No issues found.

docs/accessanalyzer/12.0/requirements/overview.md

• Clarity — Line 15: Same overstatement as 11.6 — "Installing the application requires the following servers and applications:" introduces a list containing conditional components (line 39, "In certain environments"; line 48, "For agent-based scans"). Suggested fix: "Installing the application involves the following servers and applications, depending on which solutions you deploy:"
• Structure — Lines 22–29: The edited note duplicates the bullet above it, and the two now disagree in voice: the bullet is passive ("This application is typically installed on the Access Analyzer Console server"), the note is active ("You often install the Access Information Center on the same server"). Suggested fix: move the placement statement into the bullet in active voice and reduce the note to the exception ("You can also install the Access Information Center on a separate server.").
• Clarity — Line 169: Same problem as 11.6 line 186 — "must be an equal or newer version than the targeted version" is an ungrammatical comparison with an unstated target. Suggested fix: "The SQL Server hosting the Access Analyzer database must be the same version as, or newer than, any SQL Server you target for scanning."

docs/accessanalyzer/12.0/requirements/sharepoint/scanoptions/agent-based-scans/agentpermissions.md

• Clarity — Line 17: "Install the Access Analyzer SharePoint Agent on the:" breaks off mid-phrase before the colon. Suggested fix: "Install the Access Analyzer SharePoint Agent on the following server:"
• Clarity — Line 158: Dropping "last" leaves "this permission requirement" pointing ambiguously at a two-item list (lines 154–155). Suggested fix: "If scans include Web Application scoping, you have already met the WSS_CONTENT_APPLICATION_POOLS requirement on the SharePoint Configuration database."

docs/accessanalyzer/12.0/solutions/databases/sql/overview.md

• Clarity — Line 60: "provides insight into use login activity" — "use" should be "user". Suggested fix: "provides insight into user login activity".

docs/accessinformationcenter/12.0/installation/overview.md

• Completeness — docs/accessinformationcenter/11.6/installation/overview.md, line 77: This PR updated the 12.0 Access Information Center to "Windows Server 2016 through Windows Server 2025" but the 11.6 copy still reads "Windows Server 2016 through Windows Server 2022" — even though Enterprise Auditor 11.6 gained Windows Server 2025 support in this same PR. Suggested fix: apply the same update to the 11.6 file, or confirm that AIC 11.6 intentionally stops at Windows Server 2022.
• Clarity — Lines 10–12: "Netwrix Access Analyzer (formerly Enterprise Auditor) and specific solutions are prerequisites for installing and using the Access Information Center." The compound subject reads as though Access Analyzer is one of the "solutions", and "specific solutions" never says which ones — the reader is left with an open question at the top of the page. Suggested fix: "You must install Netwrix Access Analyzer (formerly Enterprise Auditor) and run specific Access Analyzer solutions before you install and use the Access Information Center. See the Access Analyzer Solutions section for the required solutions."
• Completeness — Line 17: "See the Remote AIC Console Sever Requirements topic for additional information." misspells "Server", and it isn't a separate topic — it's the section at line 78 of this same page, with no link to get there. Suggested fix: correct the heading at line 78 to "Remote AIC Console Server Requirements" and link to it: "See Remote AIC Console Server Requirements for additional information."

Summary

25 editorial suggestions across 18 files (5 files clean). The version-support additions themselves are consistent across Access Analyzer 11.6 and 12.0; the one coverage gap is Access Information Center 11.6, and most remaining items come from the passive-to-active rewrites — dropped referents, broken list parallelism, and bullets whose neighbors weren't converted. Vale and Dale issues are auto-fixed separately.

---

What to do next:

Comment @claude on this PR followed by your instructions to get help:

• @claude fix all issues — fix all editorial issues
• @claude help improve the flow of this document — get writing assistance
• @claude explain the voice issues — understand why something was flagged

You can ask Claude anything about the review or about Netwrix writing standards.

Automated fixes are only available for branches in this repository, not forks.

[github-actions]

Auto-Fix Summary

53 issues fixed, 6 skipped across 18 files

Category	Fixes
Dale: misplaced-modifiers	1
Dale: passive-voice	42
Dale: undefined-acronyms	2
Dale: wordiness	7
Dale: xy-slop	1

Skipped (needs manual review)	Reason

| docs/accessanalyzer/11.6/install/filesystemproxy/overview.md:122 — Dale: wordiness | 'This allows it to execute three times as many concurrent hosts than would be possible without proxy servers. This provides a clear benefit in scalability and scan times.' - tightening this risks altering the throughput claim; multiple valid readings of 'three times as many' |
| docs/accessanalyzer/12.0/install/filesystemproxy/overview.md:118 — Dale: wordiness | Same sentence as the 11.6 counterpart; rewrite risks altering the technical claim |
| docs/accessanalyzer/12.0/requirements/filesystem/scanoptions/proxy-mode-scans/proxymodeserver.md:109 — Dale: passive-voice | 'The appropriate JDK (Java) version ... is installed on the server' - the actor is unstated and ambiguous (installer package vs. administrator); an active rewrite would assert a fact not in the source |
| docs/accessanalyzer/11.6/requirements/filesystem/filesystems/filesystems.md:55 — Dale: wordiness | 'See the File System Supported Platforms topic' is a self-reference to this same page; correcting it requires knowing the intended target topic |
| docs/accessanalyzer/12.0/requirements/filesystem/filesystems/filesystems.md:55 — Dale: wordiness | Same self-referencing cross-reference as the 11.6 counterpart; intended target unknown |
| docs/accessanalyzer/11.6/install/application/upgrade/overview.md:61 — Dale: wordiness | 'The new AWS Solution and the AWS Data Collector is now a licensable feature' has a subject-verb agreement problem, but fixing it requires knowing whether one or two licensable features are meant |

Ask @claude on this PR if you'd like an explanation of any fix.