Skip to content

Guidance in the Graph charges section to monitor/report custom#512

Open
EngageCloud wants to merge 1 commit into
MicrosoftDocs:publicfrom
EngageCloud:public
Open

Guidance in the Graph charges section to monitor/report custom#512
EngageCloud wants to merge 1 commit into
MicrosoftDocs:publicfrom
EngageCloud:public

Conversation

@EngageCloud
Copy link
Copy Markdown
Contributor

  • add guidance in the Graph charges section to monitor/report custom graph usage in Sentinel cost management
  • link to the corresponding section in billing-monitor-costs.md

@prmerger-automator
Copy link
Copy Markdown
Contributor

@EngageCloud : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change.

@learn-build-service-prod
Copy link
Copy Markdown
Contributor

Learn Build status updates of commit 062f55c:

✅ Validation status: passed

File Status Preview URL Details
sentinel/billing.md ✅Succeeded

For more details, please refer to the build report.

@EngageCloud EngageCloud marked this pull request as draft May 21, 2026 23:57
@EngageCloud EngageCloud marked this pull request as ready for review May 22, 2026 00:01
Comment thread sentinel/billing.md

Any notebook/Spark compute and Data lake storage consumed for data transformations to build node and edges for the graph is billed independently per existing Sentinel data lake meters (Data lake storage and Advanced Data Insights).

In addition, you can now monitor usage for custom graphs by using [Microsoft Sentinel cost management in the Microsoft Defender portal](billing-monitor-costs.md#microsoft-sentinel-cost-management-in-the-microsoft-defender-portal).
Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

@ManojRaheja adding this callout in the billing page to notify users of the new graph meter in cost analysis dashboard.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants