Agent 365 SDK validation checklist

Use this Agent 365 SDK validation checklist after you integrate an agent and before you deploy it. It's the last step in the onboarding path: Agent 365 Skills or manual setup applies the integration. These checks help you confirm each capability works so you can deploy with confidence.

If your coding assistant exposes the internal Agent 365 Validate & Diagnose capability, also referred to as a365-code-validator, you can ask it to validate this Agent 365 integration for a code-level preflight. It checks the project for gaps in instrumentation, Microsoft Entra artifacts, messaging, tool access, and related configuration. Availability and invocation depend on the assistant and Skills package. Use the checklist to confirm the findings in your target environment. The validator doesn't replace end-to-end testing or platform review.

The capability sections are independent, so skip any capability you didn't adopt. The behavior, configuration, and deployment sections apply to every integration.

Work through this checklist if you:

  • Onboarded an agent and want to confirm the integration before deploying.
  • Added a capability to an agent that you already integrated.
  • Inherited an agent from another team and need to establish what's configured.

Verify existing behavior

The SDK extends your agent, so integration shouldn't change how the agent already works.

  • The agent starts without new errors.
  • The agent responds to a normal request as it did before integration.
  • Model calls, orchestration, and tool execution behave as they did before.

Note

If core behavior changed, investigate before deploying. Generated code, dependency conflicts, configuration, and SDK compatibility are all possible causes. See Troubleshooting.

Verify identity

  • The agent identity blueprint is registered in Microsoft Entra.
  • An agent identity exists, created from that blueprint. The make-a365-agent skill creates it on the standard agent path, and make-ai-teammate on the AI teammate path; see Quickstart: Connect an existing agent to Agent 365.
  • At least one sponsor is assigned.
  • If the agent requires a user account, that account exists and is linked to the agent identity.
  • If the agent has a user account, required licenses are assigned and dependent resources such as a mailbox are provisioned.
  • API permissions and Microsoft Graph scopes are granted and scoped correctly.
  • The agent authenticates and acts under the expected identity.

Important

Agents with their own user account are available only to tenants participating in the Frontier preview program. Skip the user account checks if your tenant isn't enrolled.

Note

After you assign licenses, resource provisioning for a user account typically completes within 10 to 15 minutes, but it can take up to 24 hours.

Verify observability

  • At least one user in the tenant has a Microsoft 365 E7 or Microsoft Agent 365 license assigned. Without this license, telemetry is dropped even though ingestion returns HTTP 200.
  • The observability packages are installed and configured.
  • A test request produces spans for agent invocation, tool execution, and inference.
  • The run has a valid invoke_agent span at its root. Without one, spans stay queryable in Defender advanced hunting but don't reach the three surfaces.
  • Telemetry appears in Microsoft Defender, Microsoft Purview, and the Microsoft 365 admin center.
  • Span attributes match the operations you expect.

Verify tooling

Complete this section if the agent invokes Model Context Protocol (MCP) servers.

  • A Microsoft 365 Copilot license is available in the tenant. Work IQ MCP is in preview and requires one.
  • The agent discovers the MCP servers it should have access to.
  • A test tool invocation succeeds end to end.
  • The agent runtime catches a tool failure, returns a controlled error, and stays available.

Verify notifications

Complete this section if the agent receives notifications.

  • The agent receives notifications from the configured sources, such as Teams, Outlook, Word comments, or email.
  • The agent responds to a test notification as designed.

Important

Notifications require an agent's user account, which is available only to tenants participating in the Frontier preview program. Skip this section if your tenant isn't enrolled.

Verify configuration

  • Store credentials and secrets securely and don't commit them to source control.
  • Separate development, test, and production settings.
  • Ensure the integration works in your target host.

Confirm deployment readiness

  • All applicable checks pass.
  • Run at least one end-to-end test in a nonproduction environment.
  • Check telemetry after deployment to confirm agent health.

Resolve failed checks

Run the relevant setup step again, or ask your coding assistant to complete the specific capability.

For common symptoms and their resolutions, see Troubleshooting. For symptoms specific to Skills-based setup, see the troubleshooting table in Quickstart: Connect an existing agent to Agent 365.

For answers to related questions, see Agent 365 SDK frequently asked questions.

Related content

  • Last updated on