Docs · Connector reference

Microsoft Azure connector reference

Operations, inputs, troubleshooting, and questions for the Microsoft Azure connection.

Set up and verify the Microsoft Azure connection

Choose one task and its account, and match the reads and actions on the overview page to it before granting provider permissions.
Prepare the connection settings from the overview page, connect the provider in Deixic, and choose which tools your agent can use.
Try a small task with a known result, and compare the returned identity and resource with what the account owner expects.
Review the retrieved information, retain its identifiers, and keep any later change in a separate, explicitly authorized step.

Information your agent can use

Resource	Record identity	Start with	Page coverage
Subscription resources	`id`	Top level	Next-page URL
Visible estate hierarchy	`id`	Top level	Next-page URL
Storage accounts	`id`	Top level	Next-page URL
Network security groups	`id`	Top level	Next-page URL
Role assignments	`id`	Top level	Next-page URL
Security assessments	`id`	Top level	Next-page URL

Record identity: Match on these fields before joining or deduplicating results; where none is specified, check the returned record first.
Start with: Resolve the parent identifier first.
Next-page URL: Next-page URL. Follow the continuation returned by the provider before treating the collection as complete.

When the Microsoft Azure task does not produce the expected result

Connected, but the expected data is missing

Check the identity behind the bearer token connection and its access to the specific resource; a successful connection does not establish access to every object.

Compare the lookup against one known record first, and keep an empty response separate from a permissions error.

The answer covers only part of the data

Check the resource’s page coverage, query filters, and result limit, and have the agent state the account and time window it inspected, so a partial response yields a scoped answer.

The agent keeps doing the same work

Inspect the action history for repeated targets and inputs, keep the successful result’s identifiers with the task, and refresh a lookup only when the information changed.

The next step needs a write

Use a separate authorized action or a person to make the change; broader credentials do not add a write operation to this connection.

See how an action proceeds and how to review an approval.

Questions about the Microsoft Azure connector

Can I use my existing agent with Microsoft Azure?

Yes: connect your agent to Deixic through MCP, choose which connected tools it can use, and Deixic checks calls routed through its gateway; Dex is available if your team also wants an agent.

Can an agent change data in Microsoft Azure?

This connector supports reads. Use a configured connection to retrieve information and prepare a recommendation; it provides no action for changing provider data, even if the provider’s API offers writes.

What do I need to connect Microsoft Azure?

Prepare Azure Resource Manager access token, Azure subscription ID; the connection uses Bearer token, and the connected identity’s provider permissions determine which resources it can access.

Does connecting Microsoft Azure keep every answer up to date?

No: an earlier answer is still an earlier answer, so for a decision that depends on current state, have the agent refresh the source and retain the lookup time, and save stable instructions separately from facts that can change.

Microsoft Azure connector overview Docs All connectors