web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

Welcome to the Power Platform Communities
News and Announcements icon
Community site session details

Community site session details

Session Id :
Power Platform Community / Forums / Copilot Studio / Prompts Error: ModelNo...
Copilot Studio
Suggested Answer

Prompts Error: ModelNotSupported, Message: This scenario is not supported in this environment

(0) ShareShare
ReportReport
Posted on by CU20090407-0 5
Hi, 

I am facing this error randomly within my copilot studio agents for prompts:

aiModelActionBadRequest: The prompt  failed to run with response code 403.
Error Details: Code: ModelNotSupported,
Message: This scenario is not supported in this environment.
 
These prompts were working before and are now throwing these errors in random cases. The same happens in the test interface of the prompts as well. No particular changes were made in the admin centre as well. Need help as this is hampering the development process. Thank you in advance! 
image (5)(1).png
Categories:
General topics
I have the same question (0)
  • Suggested answer
    frago Profile Picture
    frago 174 on at

    This usually points to one of these:


    • The model assigned to the prompt is no longer available in your region/environment

    • A temporary backend rollout / regression

    • A feature flag or capability mismatch (e.g., certain prompt orchestration features not supported with the selected model)

    • Policy enforcement or quota gating kicking in intermittently

     What you should check (in order)

    1. Model selection in your prompt

    Confirm which model is configured:


    • Try switching temporarily to another available model (if possible)

    • If you're using something like GPT-4.1 / GPT-4.x → test with a fallback mode

    •  

    👉 If switching models fixes it → model availability issue confirmed

    2. Environment region

    Copilot Studio environments are tied to regions.

    Check:


    • Your Power Platform environment region

    • Whether the model you’re using is supported in that region

    •  

    That banner in your screenshot is a big red flag here.

    3. Recent Microsoft backend changes (very likely)

    Even if you didn’t change anything:


    • Microsoft frequently rolls out updates to Copilot Studio + model routing

    • These can temporarily break previousl

    •  

    👉 The “random” nature strongly points to this.

    Sometimes this error appears when:


    • Capacity is exhausted

    • Requests get routed to a fallback environment where the model isn’t enable

    •  

    Check:

    • AI credits / usage

    • Any throttling alerts in admin center
     
    ------------------------------------------------------------
    If this solved your issue, please mark it as ✅ Accepted Answer.
    If it helped, feel free to give it a 🩷 Like!
     
    Best regards,
    Piotr
  • Sajeda_Sultana Profile Picture
    Sajeda_Sultana 44 on at
     
    I am seeing the same aiModelActionBadRequest / ModelNotSupported error with 403 in Copilot Studio prompts.

    Here is what I have checked so far, following the guidance above:
     
    • Model: Using GPT‑4.1 (also tested with <other models you tried>); switching models sometimes works, sometimes still throws the same error, so it does not look like a pure configuration issue.
    • Environment region: My Power Platform environment is in <your region>; these models are documented as supported there, and the prompts were working previously with no admin-center changes on our side.
    • Banner: I now see the red banner “This feature is not available in your region yet” in the prompt editor, which was not there before, suggesting a recent backend or feature-flag change.
    • Capacity / limits: AI credits and tenant usage look normal, and there are no throttling or quota alerts in the admin center.
    Because the failures are random and started without any tenant change, this strongly suggests a Microsoft-side rollout, routing change, or capacity issue rather than an issue with the agent logic itself. It would be helpful if Microsoft could confirm whether there is an ongoing incident or regression affecting these models in <your region> and, if so, recommend a temporary workaround (for example, a specific GA model or region that is stable).
     
    ✅ If this helped solve your issue, please Accept as Solution so others can find it quickly.

    ❤️ If it didn’t fully solve it but was still useful, please click “Yes” on “Was this reply helpful?” or leave a Like :).

    🏷️ For follow-ups  @Sajeda_Sultana

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

News and Announcements

Welcome to the Power Platform Communities

Quick Links

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Users!

Kudos to our 2025 Community Spotlight Honorees

Congratulations to our 2025 community superstars!

Congratulations to the March Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > Copilot Studio

#1
Valantis Profile Picture

Valantis 606

#2
chiaraalina Profile Picture

chiaraalina 170 Super User 2026 Season 1

#3
deepakmehta13a Profile Picture

deepakmehta13a 116

Last 30 days Overall leaderboard

Featured topics

Announcing the "Microsoft Copilot Studio ❤️ MCP" lab
Block PII/PCI in Copilot Studio agent user prompt
Welcome to the Copilot Studio forum!

Product updates

Microsoft Power Platform Community release plans