Microsoft Agent Framework integration

Action security for Microsoft Agent Framework.

Wrap application-controlled Microsoft agent tools.

Get the Python SDK on PyPITry the local demoRead the documentation

Get the package and source.

Connect the execution boundary.

The tool-handler wrapper governs the handler you pass to it. Microsoft identity, platform settings and permissions remain authoritative.

An example to test

An agent proposes a customer-profile export while resolving a support ticket. Check the scope and recipient at the export handler.

Illustrative workflow, not a customer deployment or a measured result.

Before connecting live policy

  1. Identify the handler that actually performs the side effect.
  2. Provide trusted identity, purpose and final action arguments.
  3. Configure the tenant’s assigned runtime and keep API credentials server-side.
  4. Test allowed, blocked and unavailable paths before production.

Integration example

Adapt this existing SDK pattern to your application. Names such as the agent, handler and session refer to your own objects. Follow the package documentation for compatible versions and complete setup.

# Microsoft Agent Framework helper.
python -m pip install "agenticdome-python-sdk[microsoft]"

from agenticdome_sdk.microsoft_agent_framework import AgenticDomeMicrosoftAgentFirewall

firewall = AgenticDomeMicrosoftAgentFirewall()
secure_tool = firewall.wrap_tool_handler(
    tool_name="microsoft.customer.profile.export", handler=export_profile
)

agenticdome-demo --framework microsoft-agent --scenario metadata_exfil

Python demo commands evaluate fixed inputs against a bundled local policy; they do not instantiate the selected framework or prove a live integration. The TypeScript client and OpenClaw runtime plugin need their documented tenant configuration.

Read the integration researchUnderstand runtime verification

See the decision before the action.

Try a local scenario, then bring your workflow to a deployment review. Start with one agent and one tool, and see exactly where the action can be stopped.

Try the local demo Book a deployment review