copilot studio agent end user issue

Question

hi, i have created an agent using copilot studio but end users are facing error that agent not available .

Answer 1

Use the following checks to resolve the “agent not available” issue for end users.

1. Verify the Copilot Studio environment

• If users see messages like “You can't use this environment” or similar environment errors, confirm that the environment meets Copilot Studio environment requirements.
• If the environment was turned off due to inactivity, recover or reactivate it according to the automatic cleanup policy.
• If the environment is blocked from publishing to Microsoft 365 and Teams, ask an admin to check for a connector policy on the Microsoft Teams + M365 channel in Copilot Studio and adjust it if needed.

2. Confirm the agent is published and in the correct environment

• Ensure the agent is published (not just saved). Unpublished agents can behave as unavailable or respond only partially.
• Confirm that end users have access to the same Copilot Studio environment where the agent is stored (agents are stored in Dataverse and managed via a Power Platform solution). If users lack environment access, the agent can appear unavailable.

3. Check Conditional Access and authentication

• If users see a blank chat window or “agent not available” on specific channels (for example, Teams), review Microsoft Entra ID Conditional Access policies.
• If Conditional Access blocks token acquisition for the Copilot Studio agent, the agent will not start a conversation or respond. An admin must adjust the Conditional Access policy so the agent can obtain an authentication token for those users.

4. Channel-specific limitations (Teams and Microsoft 365 Copilot)

• In Teams group chats and channels, agents cannot use knowledge sources that require end‑user authentication (for example, SharePoint). These agents are supported only in 1:1 chats; in other contexts they may appear unavailable or fail to respond.
• If the agent uses manual authentication with Teams SSO, group chats and meeting chats do not support it. Consider switching to “authenticate with Microsoft” or removing Teams SSO from manual authentication for those scenarios.

5. Generative AI availability

• If the agent relies on generative AI features and users see errors related to generative AI not being available, an admin must enable Move data across regions for the environment in the Power Platform admin center under Generative AI features.
• If this setting cannot be enabled, disable generative AI features (generative orchestration, web search, AI general knowledge, AI tools) in the agent so users do not hit availability errors.

If, after these checks, the agent is still reported as unavailable, capture the exact error text and channel (Teams, web, Microsoft 365 Copilot) and have an admin review environment, Conditional Access, and channel configuration together.

---

References:

• Copy an agent to Copilot Studio
• Connect and configure an agent for Teams and Microsoft 365
• Troubleshoot Conditional Access policy issues
• "Generative AI not available" error message
• Generative AI isn't available error message