When you try to chat with a Copilot Studio agent in Microsoft Teams or a custom website, the message “This bot is not available” appears instead of the expected conversation. This error usually means the agent is not properly configured for the channel you are using or the authentication settings block the connection. The issue can also occur if the agent’s publishing state or security policies prevent it from responding. This article explains why the error happens and provides step-by-step fixes to make the agent available again.
Key Takeaways: Fixing the “This Bot Is Not Available” Error in Copilot Studio
- Copilot Studio > Agents > Agent details > Channels: Ensure the channel you are using is enabled and configured with the correct endpoint URL.
- Copilot Studio > Agents > Agent details > Authentication: Verify that the authentication method matches the channel requirements and that the client ID and secret are valid.
- Copilot Studio > Agents > Agent details > Publishing: Confirm the agent is published to the production environment and not stuck in a draft or unpublished state.
Why Copilot Studio Shows “This Bot Is Not Available”
The error occurs when the Copilot Studio agent cannot establish a connection with the channel end user. The most common root cause is a mismatch between the authentication provider configured in the agent and the channel’s authentication requirements. Another frequent cause is that the agent has been published to a test environment but not to the production environment, so the channel only sees the unpublished version. Additionally, the agent may be disabled for a specific channel, or the channel endpoint URL may be incorrect. In Microsoft Teams, the agent must also be added to the Teams app catalog and assigned to the correct user or group policy. If any of these steps are missing or misconfigured, the channel returns the “not available” message.
Authentication Provider Mismatch
Copilot Studio agents can use Microsoft Entra ID, Azure Active Directory v2, or no authentication for demo purposes. When a channel requires a specific authentication type, such as Teams requiring Entra ID, the agent must be configured accordingly. If the agent uses “No authentication” and the channel expects a token, the connection fails.
Publishing State Conflicts
Agents have draft and published versions. The published version is the one available to end users. If you edited the agent after publishing and did not publish again, the channel still uses the old published version. If you never published the agent at all, the channel sees no available version.
Channel Configuration Errors
Each channel in Copilot Studio has its own settings. The Teams channel, for example, requires a manifest file and a valid app ID. The custom website channel needs a direct line secret. If these values are missing or incorrect, the channel cannot route messages to the agent.
Steps to Fix the “This Bot Is Not Available” Error
Follow these steps in order. After each step, test the agent in the channel where the error appeared.
- Check the agent’s publishing status
Open Copilot Studio. Go to Agents and select your agent. On the agent details page, look at the Publish section. If the status shows “Draft” or “Last published” with an old date, click Publish to push the latest version to production. Wait for the confirmation message, then test the agent again. - Verify the channel is enabled
In the agent details page, click Channels. Find the channel you are using, such as Teams, Webchat, or Direct Line. Ensure the toggle is set to On. If the channel is off, turn it on and save the changes. - Update the channel endpoint URL
For custom website channels, copy the direct line secret from the channel configuration. For Teams, regenerate the channel endpoint URL if it has expired. Go to Channels > [Your Channel]. Click Edit and copy the new endpoint. Replace the old endpoint in your website or Teams app registration. - Configure authentication for the channel
Go to Agent details > Authentication. Select the authentication provider that matches your channel. For Teams, choose Microsoft Entra ID or Azure AD v2. Enter the Client ID from your app registration in Azure. Enter the Client Secret and set the Tenant ID. Save the configuration. If you are testing in a demo environment, you can set authentication to No authentication, but this is not supported in production Teams channels. - Test the agent in the Copilot Studio test pane
Before checking the external channel, use the built-in test pane. In the agent details page, click Test. Type a message. If the agent responds, the issue is on the channel side. If the agent does not respond, review the agent’s topics and triggers for errors. - For Teams: Add the agent to the Teams app catalog
If the agent is for Microsoft Teams, go to Channels > Microsoft Teams. Click Open Teams admin center. Under Teams apps > Manage apps, upload the agent’s app package. Assign the app to users or groups using Setup policies. Wait 10 to 30 minutes for the policy to propagate, then test the agent in Teams. - Check firewall and network rules
If the agent is hosted on-premises or uses custom connectors, verify that the firewall allows outbound HTTPS traffic tobotframework.comand all subdomains. Also allow traffic tocopilotstudio.microsoft.comand all subdomains. Blocked traffic prevents the channel from reaching the agent.
If Copilot Studio Still Shows the Error After the Main Fix
Some issues require additional checks beyond the standard configuration steps. Below are three specific scenarios that cause the same error message.
Agent Uses Custom Connector and the Connector Is Not Published
If your agent relies on a custom connector to access an external API, the connector must be published separately. In Copilot Studio, go to Agents > Connectors. Select your custom connector and click Publish. If the connector is in draft mode, the agent cannot retrieve data and returns the “not available” error.
Channel Token Expired or Revoked
Direct Line secrets and Teams app tokens expire after a set period. In Copilot Studio, go to Channels > Direct Line or Teams. Click Regenerate to create a new secret or token. Update the endpoint in your application with the new value. Old tokens cause the channel to reject the connection.
Agent Exceeds Quota Limits
Copilot Studio agents have message quotas based on the license. If the agent exceeds the daily or hourly message limit, the channel blocks new conversations. In Copilot Studio, go to Settings > Usage. Check the message count. If the limit is reached, wait for the reset period or upgrade the license.
Copilot Studio Channel Options: Direct Line vs Teams vs Webchat
| Item | Direct Line | Microsoft Teams | Custom Webchat |
|---|---|---|---|
| Authentication required | Yes, with Direct Line secret | Yes, Microsoft Entra ID or Azure AD v2 | No, but can be added |
| Endpoint configuration | Copy secret from Copilot Studio | Upload manifest in Teams admin center | Embed JavaScript snippet |
| Publishing requirement | Agent must be published | Agent must be published and app added to catalog | Agent must be published |
| Common error cause | Expired secret | Missing app policy assignment | Incorrect direct line secret |
The “This bot is not available” error in Copilot Studio is almost always a configuration or publishing issue. After you check the agent’s publishing status, enable the correct channel, and update the authentication settings, the agent should respond normally. If the problem persists, examine the custom connector status and token expiration dates. For Teams deployments, verify that the app policy is assigned to the correct users. As an advanced tip, use the Copilot Studio diagnostic logs by going to Agent details > Settings > Diagnostic logs to see the exact HTTP error code returned by the channel, which pinpoints the failing step in the connection chain.