Skip to content

Document Agent Identity object details and new built-in tags for NTM 3.3 - #1333

Open
kdejoyce wants to merge 16 commits into
feature/ntm/3.3from
kevin/ntm-3.3-agent-identity-tags
Open

Document Agent Identity object details and new built-in tags for NTM 3.3#1333
kdejoyce wants to merge 16 commits into
feature/ntm/3.3from
kevin/ntm-3.3-agent-identity-tags

Conversation

@kdejoyce

@kdejoyce kdejoyce commented Aug 5, 2026

Copy link
Copy Markdown
Contributor

Adds new built-in tags (Agent Blueprint, Agent Identity, Agent User, Disabled) and backfills two pre-existing tags (Certificate Authority, Azure Files Storage Account) that were missing from the docs. Adds Agent Identity Blueprint fields/tabs to the Application Details page, Agent User fields to the User Details page, and a new Service Principal Details page covering Agent Identity and Agent Identity Blueprint Principal objects.

Generated with AI

Adds new built-in tags (Agent Blueprint, Agent Identity, Agent User,
Disabled) and backfills two pre-existing tags (Certificate Authority,
Azure Files Storage Account) that were missing from the docs. Adds
Agent Identity Blueprint fields/tabs to the Application Details page,
Agent User fields to the User Details page, and a new Service Principal
Details page covering Agent Identity and Agent Identity Blueprint
Principal objects.

Generated with AI

Co-Authored-By: Claude Code <ai@netwrix.com>
@kdejoyce
kdejoyce requested a review from a team as a code owner August 5, 2026 22:14
@github-actions

github-actions Bot commented Aug 5, 2026

Copy link
Copy Markdown
Contributor

Auto-Fix Summary

38 issues fixed, 8 skipped across 5 files

Category Fixes
Dale: passive-voice 30
Dale: positional-references 1
Dale: wordiness 6
Dale: xy-slop 1
Skipped (needs manual review) Reason

| docs/threatmanager/3.3/administration/configuration/integrations/tagmanagement.md:26 — Dale: passive-voice | 'An account with automated authentication behavior detected' is a terse glossary label; rewording risks changing whether 'detected' modifies the behavior or the account |
| docs/threatmanager/3.3/administration/configuration/integrations/tagmanagement.md:47 — Dale: passive-voice | 'An Active Directory user account marked as stale' is a terse glossary label; the agent that marks the account is unspecified |
| docs/threatmanager/3.3/administration/threats/entraidobjects/entraidobjects.md:55 — Dale: passive-voice | 'threats detected for a Microsoft Entra ID object' is a terse table description; the detecting agent is unstated |
| docs/threatmanager/3.3/administration/threats/entraidobjects/entraidapplication.md:71 — Dale: passive-voice | 'Membership Type - How the group membership was assigned' — the actor (administrator, dynamic rule, or Entra ID) is unknown, so an active rewrite would add unverified meaning |
| docs/threatmanager/3.3/administration/threats/entraidobjects/entraidapplication.md:114 — Dale: passive-voice | 'Assignment Type - How was the active role assignment assigned' — the assigning actor is unknown; an active rewrite would invent it |
| docs/threatmanager/3.3/administration/threats/entraidobjects/entraidapplication.md:140 — Dale: passive-voice | 'Agent Identity service principals instantiated from this blueprint' — reduced relative clause reads as a noun modifier; rewriting would be more verbose without gaining clarity |
| docs/threatmanager/3.3/administration/threats/entraidobjects/entraiduser.md:116 — Dale: passive-voice | 'Membership Type - How the group membership was assigned' — the actor is unknown, same as in entraidapplication.md |
| docs/threatmanager/3.3/administration/threats/entraidobjects/entraiduser.md:159 — Dale: passive-voice | 'Assignment Type - How was the active role assignment assigned' — the assigning actor is unknown |

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

…ity docs

Fixes 14 of 16 editorial review findings on PR #1333 (wording, casing,
broken cross-references). Adds screenshots for the Sponsors and Agent
Identities tabs on the Application Details page, and for the profile
card, Sponsors, and Agent Users tabs on the new Service Principal
Details page. Screenshot review also surfaced a pre-existing gap: the
Owners tab was undocumented on both the Application and Service
Principal Details pages, so it's now documented on both.

Generated with AI

Co-Authored-By: Claude Code <ai@netwrix.com>
@github-actions

github-actions Bot commented Aug 5, 2026

Copy link
Copy Markdown
Contributor

Auto-Fix Summary

13 issues fixed, 8 skipped across 5 files

Category Fixes
Dale: misplaced-modifiers 2
Dale: passive-voice 3
Dale: positional-references 1
Dale: wordiness 7
Skipped (needs manual review) Reason

| docs/threatmanager/3.3/administration/configuration/integrations/tagmanagement.md:25 — Dale: misplaced-modifiers | 'An account with automated authentication behavior detected' — unclear whether 'detected' modifies the account or the behavior; a fix could change the tag's meaning |
| docs/threatmanager/3.3/administration/configuration/integrations/tagmanagement.md:60 — Dale: passive-voice | 'Date timestamp when the tag was created' — the actor is the product and irrelevant to the column gloss; every active rewrite either invents an actor or reads worse |
| docs/threatmanager/3.3/administration/threats/entraidobjects/entraidapplication.md:82 — Dale: passive-voice | 'How the group membership was assigned' — actor unknown (admin, dynamic rule, or sync); naming one would change the meaning |
| docs/threatmanager/3.3/administration/threats/entraidobjects/entraidapplication.md:84 — Dale: passive-voice | 'whether the "Security Enabled" flag is enabled' — stative description of a flag's state, not an action with an actor |
| docs/threatmanager/3.3/administration/threats/entraidobjects/entraidapplication.md:124 — Dale: passive-voice | 'How was the active role assignment assigned' has inverted word order and no identifiable actor; the intended meaning is ambiguous, so any rewrite risks changing it |
| docs/threatmanager/3.3/administration/threats/entraidobjects/entraiduser.md:24 — Dale: wordiness | '(will appear if a synced account exists)' — tense/style issue rather than a Dale pattern; Vale covers future tense |
| docs/threatmanager/3.3/administration/threats/entraidobjects/entraiduser.md:119 — Dale: passive-voice | 'How the group membership was assigned' — actor unknown; same as entraidapplication.md line 82 |
| docs/threatmanager/3.3/administration/threats/entraidobjects/entraiduser.md:161 — Dale: passive-voice | 'How was the active role assignment assigned' — inverted word order with no identifiable actor; same as entraidapplication.md line 124 |

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

Fixes 18 editorial review findings (circular/self-referential
definitions, comma splices, missing possessives, ambiguous pronoun
references, missing service principal mentions in shared object-type
enumerations). Also corrects a factual error found while validating
these docs against Microsoft's own Entra Agent ID documentation: Agent
Identity and Agent User objects are created by Microsoft Entra ID, not
by Threat Manager, which only observes and tags them.

Generated with AI

Co-Authored-By: Claude Code <ai@netwrix.com>
@github-actions

github-actions Bot commented Aug 5, 2026

Copy link
Copy Markdown
Contributor

Auto-Fix Summary

12 issues fixed, 9 skipped across 5 files

Category Fixes
WeakLinkText (rewrite) 1
Dale: misplaced-modifiers 3
Dale: passive-voice 7
Dale: wordiness 1
Skipped (needs manual review) Reason

| docs/threatmanager/3.3/administration/configuration/integrations/tagmanagement.md:25 — Dale: passive-voice | 'An account with automated authentication behavior detected' — the actor that detects the behavior isn't stated, and every active rewrite either invents an actor or reads worse than the original |
| docs/threatmanager/3.3/administration/configuration/integrations/tagmanagement.md:47 — Dale: passive-voice | 'An Active Directory user account marked as stale' — unclear whether Threat Manager or Active Directory applies the mark, so an active rewrite would assert something the source doesn't |
| docs/threatmanager/3.3/administration/configuration/integrations/tagmanagement.md:60 — Dale: passive-voice | 'Date timestamp when the tag was created' — table field gloss; naming an actor makes the column definition longer without adding information |
| docs/threatmanager/3.3/administration/threats/entraidobjects/entraidapplication.md:83 — Dale: passive-voice | 'How the group membership was assigned' — the assigning actor (admin, dynamic rule, or sync) is exactly what this column reports, so naming one would be wrong |
| docs/threatmanager/3.3/administration/threats/entraidobjects/entraidapplication.md:114 — Dale: passive-voice | 'How the eligible assignment was inherited' — same reason; the inheritance source is the value the column displays |
| docs/threatmanager/3.3/administration/threats/entraidobjects/entraiduser.md:9 — Dale: passive-voice | 'threats generated by the user' — Threat Manager generates the threat records from user behavior, so 'threats the user generated' would misattribute the action |
| docs/threatmanager/3.3/administration/threats/entraidobjects/entraiduser.md:121 — Dale: passive-voice | 'How the group membership was assigned' — same as entraidapplication.md line 83 |
| docs/threatmanager/3.3/administration/threats/entraidobjects/entraidserviceprincipal.md:55 — Dale: positional-references | 'A key for threat types appears below the chart' describes physical placement in the product UI, not a cross-reference to other documentation content |
| docs/threatmanager/3.3/administration/threats/entraidobjects/entraiduser.md:71 — Dale: positional-references | 'The tables appear below the charts' describes physical placement in the product UI, not a cross-reference to other documentation content |

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

…on symptoms

Grounds the remaining editorial feedback in docs/CLAUDE.md and
netwrix_style_guide.md rather than continuing to patch individual
wording nits, which was regenerating new review findings each round.

- Add examples and define "AI agent" on first use across the three
  new tags, per the "always provide examples" and "define terms on
  first use" rules
- Bridge the "Agent Blueprint" tag name to the "Agent Identity
  Blueprint" concept name consistently
- Fix three boilerplate cross-references ("...topic for additional
  information") that the Vale BoilerplateCrossRef rule doesn't catch
  (its regex only matches "for more information")
- Restructure the entraidapplication.md and entraidserviceprincipal.md
  admonitions to remove duplicated tab-visibility statements and
  split overloaded sentences
- Document how to distinguish an Agent Identity from an Agent Identity
  Blueprint Principal in the UI (verified via tag sync code)
- Add the four new tabs to the shared entraidobjects.md tab reference
  and unify its object-type enumeration
- Fix a pre-existing copy-paste bug on the Application page's Roles
  Tab ("the user" instead of "the application")

Generated with AI

Co-Authored-By: Claude Code <ai@netwrix.com>
@github-actions

github-actions Bot commented Aug 6, 2026

Copy link
Copy Markdown
Contributor

Auto-Fix Summary

12 issues fixed, 9 skipped across 5 files

Category Fixes
Dale: passive-voice 10
Dale: wordiness 2
Skipped (needs manual review) Reason

| docs/threatmanager/3.3/administration/configuration/integrations/tagmanagement.md:50 — Dale: passive-voice | 'Stale – An Active Directory user account marked as stale' — the agent performing the marking is unclear (Threat Manager, Active Directory, or an administrator), so an active rewrite would assert something the source doesn't state |
| docs/threatmanager/3.3/administration/configuration/integrations/tagmanagement.md:97 — Dale: n/a | Misspelled UI element 'Tag Managemetn' (also lines 144, 166). Not a Dale rule, and the same misspelling exists in 3.0, 3.1, 3.2, and Threat Prevention 7.4/7.5/8.0 — fixing only 3.3 would create cross-version inconsistency |
| docs/threatmanager/3.3/administration/configuration/integrations/tagmanagement.md:94 — Dale: n/a | Step numbering restarts at 'Step 6' in the Tag Details Page section instead of 'Step 1'. Not a Dale rule, and the same numbering appears in every other Threat Manager and Threat Prevention version of this topic |
| docs/threatmanager/3.3/administration/configuration/integrations/tagmanagement.md:155 — Dale: n/a | 'Click the arrow ()' has empty parentheses. Not a Dale rule, and supplying a character would be a guess — the source may have lost an icon reference. Pre-existing across all versions |
| docs/threatmanager/3.3/administration/threats/entraidobjects/entraidapplication.md:81 — Dale: passive-voice | 'Membership Type - How the group membership was assigned' — the assigning agent is ambiguous (administrator, dynamic rule, or Microsoft Entra ID), so an active rewrite would change meaning. Same issue at entraiduser.md line 121 |
| docs/threatmanager/3.3/administration/threats/entraidobjects/entraidapplication.md:112 — Dale: passive-voice | 'Inherited from - How the eligible assignment was inherited' — no identifiable actor; rewriting in active voice would require inventing one. Same issue at entraiduser.md line 152 |
| docs/threatmanager/3.3/administration/threats/entraidobjects/entraidapplication.md:123 — Dale: n/a | 'Assignment Type - How was the active role assignment assigned' uses interrogative word order. Grammar issue rather than a Dale rule, and pre-existing in 3.0, 3.1, and 3.2 |
| docs/threatmanager/3.3/administration/threats/entraidobjects/entraidapplication.md:90 — Dale: n/a | 'Tags - The tags associated with the group Image' has a stray trailing 'Image'. Not a Dale rule, and pre-existing in 3.0, 3.1, and 3.2. Same issue at entraiduser.md line 130 |
| docs/threatmanager/3.3/administration/threats/entraidobjects/entraidobjects.md:50 — Dale: n/a | '(will appear if a synced account exists)' uses future tense where present tense is the standard. Not covered by a Dale rule and pre-existing across versions. Same at entraiduser.md line 24 |

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

Fixes two accuracy issues flagged during review:

- The AI agent gloss in tagmanagement.md was placed as a lead-in to
  the entire built-in tags list ("Several built-in tags identify AI
  agents... The built-in tags include:"), which incorrectly implied
  the whole list is agent-related. Only 3 of 19 built-in tags are.
  Moved the gloss back to a local parenthetical on the Agent Blueprint
  entry only.
- Removed "Devices" from the Search box and Type filter additions.
  The TaggableType enum includes a Device value and sync code exists,
  but Devices aren't an actual supported/documented object type in
  the product - including them overstated scope.

Generated with AI

Co-Authored-By: Claude Code <ai@netwrix.com>
@github-actions

github-actions Bot commented Aug 6, 2026

Copy link
Copy Markdown
Contributor

Auto-Fix Summary

6 issues fixed, 8 skipped across 5 files

Category Fixes
Dale: passive-voice 4
Dale: positional-references 1
Dale: wordiness 1
Skipped (needs manual review) Reason

| docs/threatmanager/3.3/administration/threats/entraidobjects/entraidapplication.md:83 — Dale: passive-voice | 'Membership Type - How the group membership was assigned' has no stated actor; naming one would assert information not in the source |
| docs/threatmanager/3.3/administration/threats/entraidobjects/entraidapplication.md:114 — Dale: passive-voice | 'Inherited from - How the eligible assignment was inherited' is a UI column definition with no clear actor; an active rewrite would change the definition |
| docs/threatmanager/3.3/administration/threats/entraidobjects/entraidapplication.md:125 — Dale: passive-voice | 'Assignment Type - How was the active role assignment assigned' is passive and has inverted question word order, but the intended column meaning (Direct vs. Group, etc.) is ambiguous |
| docs/threatmanager/3.3/administration/threats/entraidobjects/entraiduser.md:126 — Dale: passive-voice | Same 'Membership Type' column definition as entraidapplication.md; no stated actor |
| docs/threatmanager/3.3/administration/threats/entraidobjects/entraiduser.md:157 — Dale: passive-voice | Same 'Inherited from' column definition; active rewrite would change the definition |
| docs/threatmanager/3.3/administration/threats/entraidobjects/entraiduser.md:168 — Dale: passive-voice | Same 'Assignment Type' column definition; intended meaning ambiguous |
| docs/threatmanager/3.3/administration/configuration/integrations/tagmanagement.md:49 — Dale: passive-voice | 'An Active Directory user account marked as stale' is a reduced relative clause; naming who marks the account would assert unverified behavior |
| docs/threatmanager/3.3/administration/threats/entraidobjects/entraidserviceprincipal.md:37 — Dale: idioms | 'To tell the two apart' is a standard phrasal verb rather than a culturally specific idiom |

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

Reviewed and agreed each of the 16 latest bot suggestions individually
rather than batch-applying:

- Spell out SMB on first use
- Fix circular Type filter descriptions (name the directory source)
- Move the Agent Identity Blueprint admonition above the tab list that
  references it, per the "define terms before use" style guide rule
- Fix a Roles tab self-contradiction (application and user pages)
- Correct an actor error: Microsoft Entra ID activates eligible role
  assignments for an application, not the application itself
- State the Owners tab appears for all applications
- Drop "devices" from entraidobjects.md - no Device Details Page
  exists in this doc set
- Fix Owners tab being incorrectly grouped under an "AI agent only"
  lead-in when it applies to all applications/service principals
- Narrow an overclaimed AI agent scope on the Service Principal page
- Restructure the entraiduser.md admonition: move profile card fields
  into the actual profile card list, fold in the sponsors pointer,
  and trim the admonition to just the tag definition and note

Skipped per author's call: adding per-tag links back to object detail
pages in tagmanagement.md, and promoting the Service Principal
admonition to body prose. Added and then reverted Group Membership/
Roles tabs on the Service Principal page pending further discussion.

Generated with AI

Co-Authored-By: Claude Code <ai@netwrix.com>
@github-actions

github-actions Bot commented Aug 6, 2026

Copy link
Copy Markdown
Contributor

Auto-Fix Summary

5 issues fixed, 7 skipped across 5 files

Category Fixes
Dale: idioms 1
Dale: wordiness 4
Skipped (needs manual review) Reason

| docs/threatmanager/3.3/administration/threats/entraidobjects/entraidapplication.md:126 — Dale: passive-voice | 'Assignment Type - How was the active role assignment assigned' is agentless passive with inverted word order. Fixing the word order alone would not remove the passive, and rewriting it actively would require asserting an actor the source does not specify. |
| docs/threatmanager/3.3/administration/threats/entraidobjects/entraiduser.md:160 — Dale: passive-voice | Same 'How was the active role assignment assigned' column description as entraidapplication.md:126 — agentless passive, no supported actor to make it active. |
| docs/threatmanager/3.3/administration/threats/entraidobjects/entraidapplication.md:84 — Dale: passive-voice | 'Membership Type - How the group membership was assigned' is an agentless passive UI column description; an active rewrite would have to name an actor that isn't stated. Same text at entraiduser.md:118 and entraidapplication.md:115. |
| docs/threatmanager/3.3/administration/threats/entraidobjects/entraidserviceprincipal.md:30 — Dale: wordiness | The sentence defining Agent Identity and Agent Identity Blueprint Principal is long, but every clause carries distinct information. Making it concise would require restructuring the info block into a list — a structural edit beyond a lint fix. |
| docs/threatmanager/3.3/administration/configuration/integrations/tagmanagement.md:34 — Dale: passive-voice | 'An account or object that's disabled in Active Directory or Microsoft Entra ID' reads as a stative predicate adjective rather than a true passive; rewriting risks changing the definition. |
| docs/threatmanager/3.3/administration/threats/entraidobjects/entraiduser.md:57 — Dale: positional-references | 'A key for threat types appears below the chart' describes the physical layout of the product UI, not a cross-reference to other documentation content. Same for entraiduser.md:68 and entraidserviceprincipal.md:55. |
| docs/threatmanager/3.3/administration/threats/entraidobjects/entraidobjects.md:73 — Dale: wordiness | 'the groups of which the user is a member' is formal but correct, and the surrounding two-item list has an unusual 'For a:' structure — trimming one branch without the other would break the parallelism. |

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

Removed redundant information about disabled objects in Active Directory.
@github-actions

github-actions Bot commented Aug 6, 2026

Copy link
Copy Markdown
Contributor

Auto-Fix Summary

3 issues fixed, 10 skipped across 5 files

Category Fixes
Dale: wordiness 3
Skipped (needs manual review) Reason

| docs/threatmanager/3.3/administration/configuration/integrations/tagmanagement.md:47 — Dale: passive-voice | 'An Active Directory user account marked as stale' is a reduced passive with an unstated agent; naming Threat Manager as the actor would assert something the source doesn't state. |
| docs/threatmanager/3.3/administration/configuration/integrations/tagmanagement.md:34 — Dale: passive-voice | "that's disabled" is a stative adjective describing account state, not an agentive passive. |
| docs/threatmanager/3.3/administration/threats/entraidobjects/entraidapplication.md:84 — Dale: passive-voice | 'How the group membership was assigned' — the actor could be an administrator, a dynamic rule, or Entra ID; any active rewrite would assert an agent the doc doesn't specify. |
| docs/threatmanager/3.3/administration/threats/entraidobjects/entraidapplication.md:116 — Dale: passive-voice | 'How the eligible assignment was inherited' — agent is unspecified and inheritance has no clear actor. |
| docs/threatmanager/3.3/administration/threats/entraidobjects/entraidapplication.md:126 — Dale: passive-voice | 'How was the active role assignment assigned' is passive and has inverted question word order, but the actor is unspecified so no confident active rewrite is possible. |
| docs/threatmanager/3.3/administration/threats/entraidobjects/entraiduser.md:118 — Dale: passive-voice | 'How the group membership was assigned' — unspecified agent, same as the parallel column gloss in entraidapplication.md. |
| docs/threatmanager/3.3/administration/threats/entraidobjects/entraiduser.md:149 — Dale: passive-voice | 'How the eligible assignment was inherited' — unspecified agent. |
| docs/threatmanager/3.3/administration/threats/entraidobjects/entraiduser.md:160 — Dale: passive-voice | 'How was the active role assignment assigned' — passive with inverted word order and an unspecified actor. |
| docs/threatmanager/3.3/administration/threats/entraidobjects/entraidobjects.md:50 — Dale: wordiness | '(will appear if a synced account exists)' could tighten to '(appears only if a synced account exists)', but the change is cosmetic and the phrasing is duplicated verbatim across versions. |
| docs/threatmanager/3.3/administration/threats/entraidobjects/entraidserviceprincipal.md:12 — Dale: misplaced-modifiers | 'AI agents (a software process ...)' has a plural noun with a singular appositive, but this is a number-agreement issue rather than a misplaced modifier, and the same parenthetical is repeated across the other changed files. |

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

@github-actions

github-actions Bot commented Aug 6, 2026

Copy link
Copy Markdown
Contributor

Documentation PR Review

Editorial Review

docs/threatmanager/3.3/administration/configuration/integrations/tagmanagement.md

  • Completeness — Lines 17–20: The Agent Blueprint tag definition says the tag identifies "an application registered in Microsoft Entra ID," but entraidserviceprincipal.md (lines 37–39, added in this PR) states that Threat Manager also applies the Agent Blueprint tag to Agent Identity Blueprint Principals, which are service principals. A reader who filters on the Agent Blueprint tag will see both object types and won't know why service principals appear. Suggested fix: extend the definition to cover both — "Agent Blueprint – An Agent Identity Blueprint, an application registered in Microsoft Entra ID that defines the identity configuration for an AI agent (a software process that authenticates and acts within Microsoft Entra ID without a human user). Threat Manager also applies this tag to the Agent Identity Blueprint Principal, the service principal that Microsoft Entra ID creates for each blueprint. For example, an agent that monitors support tickets and drafts responses authenticates using an Agent Identity Blueprint."
  • Completeness — Lines 17–26: The three new agent tag definitions are the only place in this version that defines Agent Blueprint, Agent Identity, and Agent User side by side, but they don't point to the pages where a reader acts on those objects. The reverse links already exist — entraidapplication.md, entraidserviceprincipal.md, and entraiduser.md all link back here. Suggested fix: add a cross-reference after the list, such as "For the details pages for these objects, see the Application Details Page, Service Principal Details Page, and User Details Page topics."
  • Clarity — Lines 128–131: The added lines expand Users and Groups to "Active Directory and Microsoft Entra ID," but Computers still reads "Active Directory computer objects." Because the surrounding entries now name both directories explicitly, the unchanged entry reads as a deliberate exclusion, and the reader can't tell whether Entra ID devices are filterable. Suggested fix: confirm the scope and make it explicit — either "Computers – Active Directory computer objects only" or "Computers – Active Directory and Microsoft Entra ID computer objects."
  • Structure — Lines 105–106: The Delete Tag entry sits in a list introduced by "This page provides the following information:", but the rewrite turned it into a two-step instruction ("Click Delete Tag, then confirm the deletion"). Every other entry in the list is a declarative description. Suggested fix: "Delete Tag button – Available only for custom tags; you can't delete built-in tags. Deleting a tag requires confirmation."
  • Structure — Line 34: The Disabled entry ends with a period, but the list's convention is that single-sentence entries have no terminal punctuation (Administrator, Automated Account, Certificate Authority, Computer Account) while only multi-sentence entries do. Suggested fix: drop the period — "Disabled – An account or object that's disabled in Active Directory or Microsoft Entra ID".

docs/threatmanager/3.3/administration/threats/entraidobjects/entraidapplication.md

  • Clarity — Lines 105–107: The rewrite changed the actor for eligible assignments from "a user or group can activate when needed" to "Microsoft Entra ID can activate for the application when needed." Microsoft Entra ID isn't the party that activates an eligible assignment — an administrator or the principal does, on request. The parallel passage in entraiduser.md (lines 139–141) kept the original actor, so the same concept is now described two different ways across sibling pages. Suggested fix: "Eligible Assignments – Lists the roles that the application is eligible for. An eligible assignment is a role assignment that can be activated when needed but that isn't permanently active".
  • Completeness — Lines 57–66: The new Owners Tab section is the only tab section on this page without a screenshot; Threats, Activity Summary, Group Membership, Roles, Sponsors, and Agent Identities all have one. A reader scanning for the tab won't have a visual anchor. Suggested fix: add an Owners tab screenshot under /images/threatmanager/3.3/administration/threatdetails/, matching the pattern used for the other new tabs in this PR.

docs/threatmanager/3.3/administration/threats/entraidobjects/entraidobjects.md

  • Clarity — Lines 77–78: The Owners Tab bullet uses "Agent Identity Blueprint Principals," a term that isn't defined anywhere on this page. The sentence that tells the reader where to find definitions appears at lines 80–83, after the bullet that first uses the term. Suggested fix: move the "Some tabs display only for AI agent objects…" pointer above the tab list, or gloss the term in place — "Doesn't appear for Agent Identity Blueprint Principals, the service principals that Microsoft Entra ID creates for each Agent Identity Blueprint".
  • Structure — Lines 80–83: This explanatory paragraph is inserted in the middle of the tab list, splitting one list into two. The three agent-specific bullets that follow read as a detached second list rather than a continuation of "the page may display the following tabs." Suggested fix: keep the tab list intact and give the agent-specific tabs their own labeled group, for example a bold lead-in "Tabs for AI agent objects" followed by the pointer sentence and the three bullets.
  • Clarity — Lines 94–99: The Add Tag object list now reads "a user, group, application, service principal, computer, or role," but this page covers Entra ID objects and its own object list (lines 9–11) doesn't include computers. Naming a computer here without qualification suggests an Entra ID device object. Suggested fix: either drop "computer" from both sentences or qualify it — "a user, group, application, service principal, on-premises computer, or role".

docs/threatmanager/3.3/administration/threats/entraidobjects/entraidserviceprincipal.md

  • Completeness — Lines 21–27: The profile card list omits the Agent Blueprint field, even though the admonition immediately below (lines 29–35) says two kinds of service principal display it. A reader comparing the list to the page in front of them will find a field the list doesn't account for. entraiduser.md handles the equivalent case by listing its agent fields inline. Suggested fix: add a bullet — "Agent Blueprint (Agent Identities and Agent Identity Blueprint Principals only) – Links to the Application Details Page for the service principal's Agent Identity Blueprint".
  • Clarity — Lines 12–14: "the page also displays Agent Identity details" is vague — "Agent Identity details" isn't a labeled element in the UI, so the reader can't tell what to look for. Suggested fix: name the additions — "For service principals related to AI agents (a software process that authenticates and acts within Microsoft Entra ID without a human user), the page also displays an Agent Blueprint field, a Sponsors tab, and an Agent Users tab."
  • Clarity — Lines 30–33: A single four-line sentence defines two distinct object types (Agent Identity and Agent Identity Blueprint Principal) with nested relative clauses. This is the first place either term appears, so the reader has to hold both definitions in mind at once. Suggested fix: break it into a short list — "Two kinds of service principal display an additional Agent Blueprint field: Agent Identity – Acts as the identity for an AI agent. Microsoft Entra ID creates it from an Agent Identity Blueprint. Agent Identity Blueprint Principal – Microsoft Entra ID creates one automatically for each Agent Identity Blueprint application."

docs/threatmanager/3.3/administration/threats/entraidobjects/entraiduser.md

  • Clarity — Lines 25–30: Both new bullets are qualified with "(Agent Users only)," but Agent User isn't defined until the admonition at lines 33–41, below the list. The reader meets the qualifier before the term it depends on. Suggested fix: move the :::info admonition above the profile card list so the definition precedes its first use.
  • Structure — Lines 25–30: Every other entry in the profile card list is a bare field name (Name, UPN, Manager, Department, ObjectID). The two new entries carry two- and three-line descriptions, so the list changes shape midway and the field inventory is harder to scan. Suggested fix: keep the list entries short — "Agent Identity (Agent Users only)" and "Agent Blueprint (Agent Users only)" — and move the explanation of what each field links to into the admonition below.

Summary

15 editorial suggestions across 5 files. 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.

edwin-narus
edwin-narus previously approved these changes Aug 6, 2026
…tity Blueprints

Per Dave's PR review comment: Threat Manager intentionally hides these
tabs for Agent Identity Blueprints and Agent Identities because the
Azure/Entra ID admin UI filters these objects out of group and role
assignment search results and omits the same sections from their own
details pages, indicating Microsoft doesn't intend for them to be
assignable this way.

Generated with AI

Co-Authored-By: Claude Code <ai@netwrix.com>
…port (#1340)

Splits the flat integration guidance into two sections grouped by
output mechanism: Active Directory and Microsoft Entra ID (native
Netwrix Threat Manager output via App Token) and file system activity
(Threat Manager Syslog template).

Documents that Azure Files storage accounts are monitored the same
way as other file system sources, with a link to Activity Monitor's
existing Azure Files monitored-host setup guide.

Also fixes a stale external link: helpcenter.netwrix.com/category/
activitymonitor redirected to the Activity Monitor v8.0 docs instead
of the current v10.0.

Generated with AI

Co-authored-by: Claude Code <ai@netwrix.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants