IT Operations · Integration
Microsoft Log Analytics
Add Microsoft Log Analytics to your product for your customers, and give your AI agents governed access to it.
Embed a Microsoft Log Analytics integration so your customers can query the logs they already collect in their own workspace from inside your product. Log Analytics is the query layer under Azure Monitor: tables and retention differ per workspace, queries are written in KQL, and result volume is the thing that bites, so fastn handles per-tenant authentication, query result paging and deliberate throttling. Diagnostics then happen where your users already are instead of in a separate portal tab.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let customers connect their own Log Analytics workspace so your product runs saved KQL queries against their logs.
Read the workspace's table list and schema so your product only offers queries the customer's data supports.
Render query results inside your product, scoped per tenant, so support and engineering stop switching tools.
Bound result sets and time ranges so a broad query does not stall your product or the customer's workspace.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent runs a scoped KQL query to explain an error spike before a human opens the portal.
An agent checks which tables exist in the workspace so it queries what is actually collected.
An agent correlates log results with an incident record and summarises the likely cause.
Example prompt
Query the last two hours of application logs for failed requests and group them by operation and status code.
Set up Microsoft Log Analytics in 4 steps
- 01Open the Microsoft Log Analytics connector from your fastn dashboard.
- 02Have each customer authorise their own Azure subscription with read access to the workspace.
- 03Map the workspaces, tables and saved queries your product uses, then enable the actions you need.
- 04Call them from your product, or expose them to an agent through the MCP server.
Why teams use the Microsoft Log Analytics integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Microsoft Log Analytics integration without building it. Your customers connect their own Microsoft Log Analytics account inside your product and work their incidents, alerts and on-call schedules there, with no per-customer code on your side.
- Handle the part that actually costs time: alerting is latency-critical and noisy, so filtering and deduplication matter. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a Microsoft Log Analytics update is not your on-call problem.
- One integration serves your product and your agents. The same governed Microsoft Log Analytics connection powers in-product features and gives AI agents scoped, audited access, so you route operational signal to the people and systems that act on it without wiring it twice.
Used by these teams
Compare with
Azure Monitor
DatadogWorks well with
Often used alongside
Tools the same teams tend to run next to Microsoft Log Analytics, across other categories.
AWS Secrets Manager
AppViewXMicrosoft Log Analytics integration FAQ
How do I add a Microsoft Log Analytics integration to my product?
Enable the Microsoft Log Analytics connector in your fastn dashboard, then let each customer authenticate their own Microsoft Log Analytics account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Microsoft Log Analytics client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Microsoft Log Analytics account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Microsoft Log Analytics account and only ever sees their own incidents, alerts and on-call schedules. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this Microsoft Log Analytics integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. An agent runs a scoped KQL query to explain an error spike before a human opens the portal.
Who maintains the Microsoft Log Analytics integration?
fastn does. When Microsoft Log Analytics changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
How fast does a Microsoft Log Analytics alert reach my product?
Alerts arrive through event triggers rather than polling, so your product reacts in near real time instead of on a schedule.
Can duplicate or flapping alerts be suppressed?
Yes. Events are deduplicated per incident, so a flapping check does not create a queue of identical records for your users to sift through.
What can I build with the Microsoft Log Analytics integration?
A common starting point: connect their own Log Analytics workspace so your product runs saved KQL queries against their logs. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the Microsoft Log Analytics integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Microsoft Log Analytics does not change your per-connector cost. You can start free with 3 connected accounts.
Add Microsoft Log Analytics to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.