Forum Discussion

TeerX's avatar
TeerX
Copper Contributor
Oct 30, 2026

What entitlements users receive when they are enabled with Copilot Premium Licenses ?

Our scenario, users with just the Copilot premium license but not with Copilot studio are able to access

https://copilotstudio.microsoft.com/environments and connect to default environment.  The user who has built an agent was able to have a custom built connector active with its agent and started consuming credits ultimately exhausting it. 

The are able to create agents in Agent Builder and copy to Copilot Studio through the setting. How can we disable the same ?

So we are trying to figure if this is the license issue where the moment a user gets enabled with Copilot Premium, they get entitlements to POwer Automate or Power apps.

2 Replies

  • TeerX's avatar
    TeerX
    Copper Contributor

    Thanks ChrisL10​ . The issue with the default environment is where we are struggling. Currently everyone who is creating lands in the default environment. How do we control that ? WE want to lock down the default environment. Any suggestions.

  • ChrisL10's avatar
    ChrisL10
    Brass Contributor

    Having Copilot Premium/Microsoft 365 Copilot doesn't simply give the user full Power Apps or Power Automate licensing. Agent Builder is part of the Microsoft 365 Copilot experience, and agents can be copied from Agent Builder into Copilot Studio. Copilot Studio itself runs on Power Platform environments and supports Power Platform connectors, including custom connectors.

    I'd therefore treat this primarily as a Copilot Studio/Power Platform governance issue rather than trying to remove Power Automate or Power Apps entitlements. Control who has maker access to environments, restrict the Default environment, and use Power Platform data policies to block or constrain connectors and other Copilot Studio capabilities. You should also review Copilot Studio credit usage to establish exactly which capability is consuming the tenant's credits.