Building an Agent 365 Blueprint connector for Power Platform

July 07, 2026

Every Agent 365 agent starts with a blueprint — an Entra ID application registration that serves as the enterprise template for compliant agents. The blueprint defines which Work IQ servers the agent can access, what permissions it holds, and how it authenticates at runtime. Every agent instance inherits its blueprint’s rules, ensuring consistent governance across Mail, Calendar, Teams, SharePoint, and other M365 workloads.

The Agent 365 CLI (a365 setup blueprint, a365 setup permissions) automates these operations for developers. This connector provides the same capabilities in Power Automate — letting IT admins automate agent provisioning at scale, governance flows create blueprints when new teams or projects spin up, and compliance monitoring audit permissions across the tenant.

How it relates to the Agent 365 MCP connector

These two connectors cover different halves of the Agent 365 lifecycle:

Blueprint creates and governs the agent definition. MCP provides the runtime tool access. Together they cover the full lifecycle.

Operations

The connector exposes 10 typed operations against Microsoft Graph:

End-to-end example: provision a sales agent blueprint

Here’s the typical five-step flow to create a fully configured blueprint:

1. CreateBlueprint
   → displayName: "Sales Agent Blueprint"
   → returns: blueprintId, appId

2. CreateServicePrincipal
   → appId: (from step 1)
   → returns: servicePrincipalId

3. GrantDelegatedPermissions
   → clientId: (SP from step 2)
   → resourceId: (Work IQ Mail MCP SP ID)
   → scope: "Tools.ListInvoke.All"

4. GrantDelegatedPermissions
   → clientId: (SP from step 2)
   → resourceId: (Work IQ Calendar MCP SP ID)
   → scope: "Tools.ListInvoke.All"

5. CreateBlueprintSecret
   → blueprintId: (from step 1)
   → displayName: "Runtime Secret"
   → returns: secretText (only returned once — store securely)

After these five steps, the blueprint is ready for agent instances to inherit. The agent uses the appId and secretText to authenticate at runtime and gets scoped access to only the Work IQ servers you’ve explicitly granted.

Work IQ permission model

Agent 365 uses a per-server permission model. Each Work IQ MCP server has its own Entra app registration, and you grant Tools.ListInvoke.All to each one individually:

To resolve server SP IDs in your tenant:

GET /v1.0/servicePrincipals?$filter=displayName eq 'Work IQ Mail MCP'

The legacy shared-scope model (McpServers.Mail.All, etc.) is deprecated. Use per-server Tools.ListInvoke.All for all new blueprints.

Authentication and prerequisites

The connector authenticates via OAuth 2.0 with the https://graph.microsoft.com/.default scope. The Entra app registration for the connector itself needs these application permissions (with admin consent):

• Application.ReadWrite.All — create and manage app registrations
• DelegatedPermissionGrant.ReadWrite.All — manage OAuth2 grants
• AppRoleAssignment.ReadWrite.All — manage app role assignments

The signed-in user needs at minimum the Agent ID Developer role for blueprint creation, and Global Administrator for OAuth2 permission grants.

Deployment

1. Import via Maker portal (Custom connectors > Import OpenAPI) or deploy with PAC CLI:

pac connector create `
    -df apiDefinition.swagger.json `
    -sf script.csx `
    -env <environment-id>

1. Configure OAuth in the Security tab with your app registration client ID and the https://graph.microsoft.com/.default scope
2. Create a connection — admin consent is required for the Graph permissions

Key behaviors

• All operations are idempotent — safe to retry
• Blueprint deletion does NOT cascade to agent instances; clean up instances separately
• Secret values are only returned once on creation — store them in Key Vault or a secure variable
• The connector uses script.csx only for request shaping (no MCP proxy logic needed since Graph is the direct backend)

Use cases

Automated agent provisioning — When a new project is created in your ITSM system, a Power Automate flow creates the blueprint, grants the appropriate Work IQ permissions, and stores the secret in Key Vault. The dev team gets a ready-to-use agent identity.

Compliance auditing — A scheduled flow calls ListBlueprintPermissionGrants across all blueprints and flags any that have overly broad permissions or missing expiry dates on secrets.

Self-service agent onboarding — A Power App lets team leads request agent blueprints with pre-approved permission sets. An approval flow provisions the blueprint with only the requested scopes.

The full source is available in the SharingIsCaring repository.