Using AI-plugin (Azure Logic App) with M365 Agents Toolkit

Question

Using AI-plugin (Azure Logic App) with M365 Agents Toolkit

Shreya Reddi 0

Hi, I'm currently working with the M365 Agents Toolkit to create an agent. The action the agent has connects to an Azure Logic App (which basically functions as a REST API by hitting an endpoint) and executes the workflow.

My agent was able to execute the Logic App up until Friday and is now running into errors. What might be the issue? The adaptive card to call the logic app appears and the parameters are formatted correctly, however, the run never shows up on the Azure portal. The agent tells me there was a problem calling the App but doesn't specify.

What might be the problem?

Karan Shewale 1,040 Reputation points Microsoft External Staff

2025-07-29T04:37:35.44+00:00

Thanks for bringing this issue to our attention. We will check and update you soon.

1 answer

Your answer

Karan Shewale 1,040 Reputation points Microsoft External Staff

2025-07-29T04:37:35.44+00:00

Thanks for bringing this issue to our attention. We will check and update you soon.

Answer 1

Hi Shreya,

Since your M365 Agent with Azure Logic App integration was working until Friday and now fails without showing runs in Azure Portal, this suggests an authentication, connectivity, or service-level issue rather than a code problem.

Most Likely Causes (Weekend Issues)

Authentication Token Expiration

Common weekend issue:

Service principal tokens often expire on weekends
OAuth tokens may have expired
API keys or connection strings might have been rotated

Azure Logic App Service Issues

Check Azure Status:

Azure Service Health for Logic Apps in your region
Potential service outages over the weekend
Maintenance windows affecting Logic App execution

Network/Firewall Changes

IT changes over weekend:

Firewall rules modified
Network policies updated
Conditional Access policies changed

Immediate Troubleshooting Steps

Step 1: Verify Logic App Status

Azure Portal → Logic Apps → Your Logic App
Overview → Check Status (should be "Enabled")
Run History → Verify no runs appearing since Friday
Monitoring → Check for any error logs

Step 2: Test Logic App Directly

Bypass the agent:

Copy Logic App HTTP endpoint
Test with Postman/curl directly
Use same parameters the agent sends
Check if Logic App responds

Step 3: Check Agent Plugin Configuration

In M365 Agents Toolkit:

AI-plugin manifest → Verify endpoint URLs unchanged
Authentication settings → Check if tokens/keys expired
Test plugin independently from agent

Step 4: Review Azure Logic App Logs

Azure Portal → Logic App → Monitoring → Diagnostics Look for: - Authentication failures - Network connectivity issues - Timeout errors - Service unavailable errors

Common Solutions

Fix 1: Refresh Authentication

If using service principal:

Azure AD → App registrations → Your app
Certificates & secrets → Renew client secrets
Update agent configuration with new credentials

Fix 2: Logic App Restart

Simple restart often fixes weekend issues:

Azure Portal → Logic App → Overview
Disable the Logic App
Wait 2-3 minutes
Enable the Logic App
Test immediately

Fix 3: Check Resource Limits

Azure subscription limits:

Logic App pricing tier → Check if limits reached
Consumption plan → Verify execution quota
Resource group → Check resource limits

Fix 4: Update Agent Plugin

Re-register the plugin:

M365 Agents Toolkit → Re-import AI-plugin
Test connection to Logic App
Verify adaptive card still renders correctly

Debugging Strategy Test This Sequence: 1. Direct Logic App test (Postman) ✓/✗ 2. Agent plugin test (without full agent) ✓/✗ 3. Full agent execution ✓/✗ 4. Check where the chain breaks

Log Analysis:

Check these logs in order:

Azure Logic App diagnostics
M365 Agents Toolkit logs
Teams/M365 Copilot logs (if applicable)
Network/firewall logs

Expected Findings

If Logic App Direct Test Fails:

Authentication issue (expired tokens/keys)
Logic App service problem
Azure resource limits reached

If Logic App Works but Agent Fails:

Plugin configuration issue
Agent authentication to Logic App
M365 Agents Toolkit service connectivity

If Everything Tests Fine:

Caching issues in M365 services
Regional service problems
Intermittent connectivity issues

Quick Resolution Steps

Try these in order:

Restart Logic App (2 minutes)
Test direct Logic App endpoint (5 minutes)
Refresh agent plugin registration (10 minutes)
Check Azure service health (2 minutes)

The fact that it worked Friday and failed over the weekend strongly suggests an authentication expiration or service maintenance issue. Start with the Logic App restart and direct endpoint test first.

Thanks,

Karan Shewale.

*************************************************************************

If the response is helpful, please click "Accept Answer" and upvote it. You can share your feedback via Microsoft Teams Developer Feedback link. Click here to escalate.

Shreya Reddi 0 Reputation points

2025-07-29T16:01:48.3666667+00:00

Hi, thanks for the response.

I went ahead and checked the following steps:

Restarted Logic App

Tested direct Logic App endpoint (this works fine)

Refreshed agent plugin registration (regenerated the action)

Checked Logic App logs for anything (nothing shows up)

Is there any other way I can retrieve the info from the agent to see what might be happening? Asking the agent itself for the error message doesn't provide much support.
Karan Shewale 1,040 Reputation points Microsoft External Staff

2025-07-30T06:59:28.0033333+00:00

Hi Shreya,

It sounds like you're troubleshooting a Logic App integration with your Copilot Studio agent. Here are additional diagnostic steps to help identify what might be happening:

Agent-Side Diagnostics

Check Agent Analytics:

Go to Analytics > Sessions in your Copilot Studio agent

Look for failed conversations or error patterns

Check the Topics analytics for plugin execution failures

Test in Bot Framework Emulator:
- Download Bot Framework Emulator - Connect to your agent's endpoint - This provides more detailed error messages than the standard chat interface **Enable Detailed Logging:** - In your agent settings, enable **Conversation transcripts** - Check **System** topics for error handling

Logic App Diagnostics

Check Run History:

Even if logs don't show errors, check the Run history tab

Look for runs that were triggered but may have timed out or failed silently

Add Diagnostic Actions:
- Temporarily add **Compose** actions in your Logic App to log input/output - Add **HTTP Response** actions with status codes to confirm execution points **Check Authentication:** - Verify the connection between Copilot Studio and Logic App is still valid - Regenerate authentication keys if needed

Additional Troubleshooting

Network/Timeout Issues:

Check if your Logic App response time exceeds Copilot Studio's timeout (usually 30 seconds)

Test with a simpler Logic App that just returns a static response

Plugin Configuration:

Double-check the OpenAPI definition matches your Logic App exactly

Verify parameter mapping in the agent's action configuration

Would you like me to elaborate on any of these steps.
Shreya Reddi 0 Reputation points

2025-07-30T16:25:44.4966667+00:00

Hi,

I'm not using Copilot Studio to create my agent. Are there ways to debug for an agent made with the M365 Agents Toolkit?

Runs do not appear in the Logic App logs when called by the agent unsuccessfully. Usually, the logic app takes <1sec so timeout may not be an issue.

This is my openapi spec as a YAML file.

openapi: 3.0.4 info: title: <LogicAppName> - Subset description: Azure Logic App. version: 1.0.0.0 servers: - url: https://<azure>/workflows/<WorkflowId>/triggers/<TriggerName>/paths/invoke?api-version=2016-10-01&sp=%2Ftriggers%2FS<TriggerName>%2Frun&sv=1.0&sig=<SIG> paths: /: post: description: This calls a logic app with the specific url and passes the data. This will <info>. operationId: <TriggerName>_invoke requestBody: description: The request body. content: application/json: schema: type: object properties: <request body> responses: '200': description: The Logic App Response. content: application/json: schema: type: object default: description: The Logic App Response. content: application/json: schema: type: object components: { }
Karan Shewale 1,040 Reputation points Microsoft External Staff

2025-08-12T04:21:46.1266667+00:00

Debug Commands Available

Use the GitHub Copilot: Debug Last Terminal Command command to debug terminal commands related to your agent.

[

{

"type": "command",

"details": {

"key": "github.copilot.chat.rerunWithCopilotDebug"

}

}

]

Enable Debug Logging

Enable verbose task logging with the task.verboseLogging setting to get more detailed logs during agent operations.

Show in Settings Editor

. Enable the Copilot debug command in terminal with the github.copilot.chat.copilotDebugCommand.enabled setting.

Show in Settings Editor

Debugging Logic App Integration Issues

For your specific Logic App integration issue where runs don't appear in logs:

Use the GitHub Copilot: Generate Debug Configuration with GitHub Copilot command to create a debug configuration for your agent.

Show in Command Palette

the GitHub Copilot: Open Logs to view detailed logging information.

Show in Command Palette

. Use the Developer: Show Logs... command to access additional diagnostic logs.

Show in Command Palette

Additional Troubleshooting

Your OpenAPI spec looks correct for Logic App integration. The missing runs in Logic App logs when called unsuccessfully suggests the requests may not be reaching the Logic App endpoint. Check:

Network connectivity

Authentication/authorization issues

Request format validation

Logic App trigger configuration

The debugging tools above should help identify where the request flow is failing in your M365 agent.

Share via

Using AI-plugin (Azure Logic App) with M365 Agents Toolkit

1 answer

Your answer