
Azure Log Analytics Workspace Connector
You're all set. Choose your MCP client and follow the setup instructions.
https://edge.vinkius.com/vk_preview_h8mzxcilFYlijQMfr5u3GIGk82xs7W4r1G5Um6EK/mcpConnecting Azure Log Analytics Workspace to Gemini
About a minute, right in your terminal
- 1Open the Gemini CLI in your terminal.
- 2Run: gemini mcp add --transport http Azure Log Analytics Workspace <your link>. Your Azure Log Analytics Workspace link above is the HTTP URL.
- 3Run /mcp and confirm the status shows CONNECTED. Azure Log Analytics Workspace is now part of your Gemini.
{
"mcpServers": {
"azure-log-analytics-workspace-mcp": {
"url": "https://edge.vinkius.com/vk_preview_h8mzxcilFYlijQMfr5u3GIGk82xs7W4r1G5Um6EK/mcp"
}
}
}Gemini + Azure Log Analytics Workspace
One chat. Your Azure Log Analytics Workspace, live inside Gemini.
Real prompts, answered with live data. This is the kind of conversation you will have in the Gemini CLI once the link is in.
Waiting for input…
Works with modern AI clients that support MCP, including ChatGPT, Claude, Cursor, and more.
These prompts ship with the Azure Log Analytics Workspace Connector. Once yours is connected, they work in your sessions.
The full capability set, the prompts and the observed latency live on the Azure Log Analytics Workspace Connector page.
Mission Control
See everything your Gemini agents do in Azure Log Analytics Workspace.
When Gemini runs a tool in Azure Log Analytics Workspace, it happens in the terminal: you see the result, but not the request itself, what data it carried, or whether a rule was broken.
Now every move lands on your screen.
Every execution is recorded, enforced, and shown to you: what ran, what it returned, what was blocked, and why.
Know exactly what needs your attention before you even look at the charts. One briefing. The full picture. The next move.
AI Agents Activities
last 30 daysRequest Volume & Latency
requests latencyEvery request your Gemini agents make through Azure Log Analytics Workspace is logged, enforced and auditable. See how AI Governance turns agent activity into accountability, and what it means for your Azure Log Analytics Workspace workflows.
What sets us apart
It's not just the Connector that stays safe. Everything your agents do through it is.
Connecting Azure Log Analytics Workspace to your AI is step one. But an open line between your agents and Azure Log Analytics Workspace is only half the story: without protection, every action they take runs unguarded.
That's why protection doesn't stop at the door.
Every action your agents take through the Connector runs inside our infrastructure: signed activity logs, automatic key rotation, spending limits that pause instead of surprise, and a sandbox that isolates every execution.
Tamper Proof Activity Log
Every request your agents make in Azure Log Analytics Workspace is recorded and signed, so any change to the history becomes detectable.
Automatic Key Rotation
We rotate security keys every 24 hours. Your Azure Log Analytics Workspace connection stays protected without any manual work.
Spending Protection
We enforce the spending limit you choose and pause actions that exceed it until approval is received. Your Azure Log Analytics Workspace actions never surprise you.
Isolated Sandbox
Every execution through Azure Log Analytics Workspace runs isolated, with 34+ security rules covering memory, CPU, network access, file handling and execution.
Security Event Streaming
Security events flow to Splunk, Datadog or your own webhook, so Azure Log Analytics Workspace activity lands in the tools you already rely on.
Instant Resume
Idle connections resume in 3 to 5 ms while preserving their state, keeping your Gemini sessions responsive.
Malicious File Protection
We detect compressed files designed to exhaust system resources and block them before they ever reach Azure Log Analytics Workspace.
Credential Validation
We test your Azure Log Analytics Workspace credentials before saving them. Invalid credentials are rejected instead of being stored.
Separate Usage Limits
Usage stays isolated per account, so activity in one connection never consumes another account's allowance.
One Connector, one link, and the whole operation is protected. Not just the connection: everything your agents do through it.
These guarantees are not add-ons: they are the infrastructure every Azure Log Analytics Workspace connection runs on. Read how our infrastructure protects everything your Gemini agents do, end to end.
Inside Vinkius
Get Azure Log Analytics Workspace ready for your AI. It's easy.
You choose Azure Log Analytics Workspace from the Vinkius Catalog, sign in to your Azure Log Analytics Workspace account, and get one connection link. That's it.
You choose Azure Log Analytics Workspace
You find Azure Log Analytics Workspace in the Catalog and install the Connector with one click.
Azure Log Analytics Workspace
Active
Enable ConnectorActivating…You sign in
You connect your Azure Log Analytics Workspace account and choose what you want your AI to access. Your credentials stay encrypted and separate from your AI.
Configure Credentials
Configure credentials for {{connectorName}}
RequiredEncryptedSave & ContinueYou add the link in the Gemini CLI
Vinkius gives you one connection link. In the Gemini CLI, you run one gemini mcp add command with the link as the HTTP URL, and the connection is ready.
Token generated successfully
MCP Connection URL
https://edge.vinkius.com/vk_preview_h8mzxcilFYlijQMfr5u3GIGk82xs7W4r1G5Um6EK/mcpGo to DashboardConnection Token
vk_live_••••••••
Set it up once. Use Azure Log Analytics Workspace with the AI you already use.
FAQ
Gemini access questions.
- 01
Does this work in the Gemini web and mobile apps?
Not yet. The Gemini apps use built-in Connected Apps that you toggle on and off, and they don't accept custom Connector links today. The supported path is the free Gemini CLI, where the same link runs Azure Log Analytics Workspace in your terminal.
- 02
If I connect Azure Log Analytics Workspace to Gemini, can I use the same connection in Claude or ChatGPT later?
Yes, and that's the point: the connection is yours, not Gemini's. You paste the same link in any AI you use, and there's nothing new to set up or pay again. Connect a new AI and Azure Log Analytics Workspace is already there.
- 03
Do I need to hand my Azure Log Analytics Workspace password to Gemini?
Never. You sign in once at Vinkius, and we keep your logins encrypted and away from your AI. Gemini only ever sees the link, and you can remove it whenever you want.
- 04
What can I actually ask Gemini to do with Azure Log Analytics Workspace?
Whatever the Connector covers: check data, run actions and bring answers back. The Connector page lists every capability your AI gains, with real examples you can copy.
- 05
Gemini doesn't show the Connector. What do I check?
Run gemini mcp list and check that the status shows CONNECTED, confirm the Connector is active in your Vinkius account, then run the add command again if needed. A deactivated Connector stops responding.
- 06
Can I remove the access later?
Anytime. Run gemini mcp remove and it's out of your terminal. Your Vinkius account keeps the connection and its history either way, ready for the next AI.
More questions about Azure Log Analytics Workspace? The Connector page answers them. See everything the Azure Log Analytics Workspace Connector can do
About the Connector
What Azure Log Analytics Workspace adds to your AI.
Once you connect it, your AI can take real actions in Azure Log Analytics Workspace when you ask. The Connector page lists every capability in detail, alongside the latency we measure in production and prompts worth trying first.
See everything the Azure Log Analytics Workspace Connector can do