Troubleshoot connected platforms in Microsoft Agent 365

Use this article for issues that apply across providers. For provider-specific permissions and telemetry requirements, open the relevant Connected platforms configuration guide.

Connection validation fails

Confirm that:

• The credentials are current and belong to the selected source account, project, workspace, compartment, or region.
• The platform administrator granted every permission required for discovery.
• The connection fields match the provider guide.
• The source platform allows the connection from the configured environment.

If the credentials expire or are revoked, rotate them in the source platform and update the connection.

Agents don't appear after synchronization

1. Open the connection and review the synchronization status and errors.
2. Confirm that the agents are in the account, project, workspace, compartment, or region selected for the connection.
3. Confirm that the source credentials can list the agents.
4. Select Sync agents again.
5. If the agent still doesn't appear, use the provider guide to verify the required discovery permissions.

Agents appear with limited metadata

Some providers use separate permissions for agent discovery and agent details. Grant the optional metadata permissions described in the provider guide when names, descriptions, models, tools, or knowledge sources are missing.

Activity does not appear

Confirm that:

• The provider supports observability for the environment.
• Source telemetry is enabled.
• Collect agent observability data is enabled for the connection.
• The connection scope matches the deployed source environment.
• The source platform has produced activity.
• The provider-specific ingestion interval has elapsed.

For cross-platform behavior and links to provider-specific setup, see Third-party agent observability (Frontier).

Duplicate agents appear

Confirm whether the source platform exposes the same agent through multiple resources or environments. Verify the connection scope and synchronization results before deleting or changing an agent.

Remove a connection

Before removing a connection:

1. Confirm which agents and management actions depend on it.
2. Revoke or rotate the source credentials as required by your organization's security policy.
3. Remove the connection in the Microsoft 365 admin center.
4. Confirm how the provider handles synchronized agent records after connection removal.