Skip to content

Add Azure Sentinel audit log export and split into sub-pages#18432

Merged
hlynnj merged 5 commits intomasterfrom
lynn/audit-logs-azure-sentinel
Apr 9, 2026
Merged

Add Azure Sentinel audit log export and split into sub-pages#18432
hlynnj merged 5 commits intomasterfrom
lynn/audit-logs-azure-sentinel

Conversation

@hlynnj
Copy link
Copy Markdown
Contributor

@hlynnj hlynnj commented Apr 8, 2026

Summary

  • Splits the audit logs doc into sub-pages: _index.md (overview, manual export, formats, events), aws-s3.md (AWS S3 export), and azure-sentinel.md (new Azure Sentinel export)
  • AWS S3 instructions are extracted as-is from the original page
  • Azure Sentinel instructions are new, based on the sentinel-audit-log-connector template README
  • The main audit logs page now has a stub "Automated Export" section linking to each provider sub-page

Test

  • Preview locally and makes sure the pages look right and existing content hasn't been changed. New automated export section looks like this:
Screenshot 2026-04-08 at 12 01 21 PM

Split the audit logs page into sub-pages per provider (AWS S3, Azure
Sentinel) to reduce crowding and make room for future export targets.
The main audit-logs page keeps overview, manual export, formats, and
event list. AWS S3 instructions are extracted as-is. Azure Sentinel
instructions are new, based on the sentinel-audit-log-connector template.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@claude

This comment was marked as resolved.

@pulumi-bot
Copy link
Copy Markdown
Collaborator

pulumi-bot commented Apr 8, 2026

- Fix menu parent/identifier so sub-pages nest under Audit Logs
- Add alt text to all images in aws-s3.md
- Use "select" instead of "click", "navigate to" instead of "go to"
- Fix "eg:" to "e.g.,", "arn" to "ARN", add missing article
- Rename "Azure Sentinel" to "Microsoft Sentinel" in titles and menu
- Use sentence case for headings ("Setup option" not "Setup Option")

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Use the actual template displayName from Pulumi.yaml:
"Pulumi Audit Log Export to Azure Sentinel"

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Apply review nits: sentence-case H2/H3/H4 headings in _index.md, add
alt text to the existing screenshot, hyphenate "three-dot menu", and
use backticks for the audit log filepath example.
Copy link
Copy Markdown
Contributor

@CamSoper CamSoper left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks great, Lynn! Nice job structuring the new Sentinel page — clear prereqs, two setup paths, schema reference, sample queries, teardown, and known limitations. Splitting into sub-pages is the right call and gives us a good template for future "export to X" pages.

I pushed a small follow-up commit cleaning up sentence-case headings in _index.md (carried over from the original page), an alt attribute on the existing audit-logs screenshot, a hyphen in "three-dot menu", and a backtick fix on 'Pulumi-audit-logs'. All cosmetic — feel free to revert if you'd rather keep the diff focused.

One thing worth a quick sanity check before merge: the KQL examples use lowercase hyphenated event names (stack-deleted, member-added, etc.), while _index.md lists them in Title Case ("Stack Deleted", "Member Added"). The KQL form is presumably what the connector emits into Event_s — just want to make sure the sample queries return rows for users who run them.

- Console flow links directly to prefilled New Project Wizard
- CLI flow uses pulumi/examples repo instead of sentinel-audit-log-connector
- Add enableAnalyticRules to config table, remove apiUrl

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@hlynnj
Copy link
Copy Markdown
Contributor Author

hlynnj commented Apr 9, 2026

confirmed the lowercase event names are what gets stored in the audit logs table!

@hlynnj hlynnj merged commit 876b4b7 into master Apr 9, 2026
7 checks passed
@hlynnj hlynnj deleted the lynn/audit-logs-azure-sentinel branch April 9, 2026 19:35
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.

3 participants