MC1483430 Low
Power Platform admin center – Update to the Copilot Studio Authors feature name
Summary AI-generated
The Copilot Studio Authors tenant setting is renamed to Copilot Studio pay-as-you-go users to clarify it controls PAYG billing access, not generic Copilot Studio access.
Written by Azure OpenAI (gpt-4.1) from the text of the post below. It can be incomplete or wrong; the original post is authoritative.
Similar posts
Search for more like this- MC1218332 Power Platform - Track, manage and scale Copilot adoption in PPAC new functionality
- MC1222980 Microsoft 365 Copilot: Pay-as-you-go consumption for the Copilot Retrieval API
- MC1451872 Power Platform - Granular Copilot credit consumption tracking and Pay As You Go (PAYG) consumption cap (Preview)
- MC1405498 (Updated) Microsoft 365 Copilot: Updated service plan behavior for Copilot experiences
- MC1454393 Microsoft 365 Copilot: Updates to Copilot Tuning and transition to Microsoft Copilot Studio
- MC1176363 (Updated) Microsoft Copilot Studio: Copy an agent from the lite experience into the full experience
Original post from Microsoft
We are announcing that we have updated the name of the Copilot Studio Authors tenant setting to Copilot Studio pay-as-you-go users in Copilot Studio. This feature controls who can use pay-as-you-go (paygo or PAYG) billing to create items in Copilot studio.
The Copilot Studio Authors tenant setting in the Power Platform admin center was not created as a governance feature. It was created as a licensing access-control mechanism, required to make the Copilot Studio Pay-As-You-Go meter usable at launch. Without it, a customer on a pure pay-as-you-go billing plan had no supported way to be granted access to the Copilot Studio maker portal.
How does this affect me?
With the introduction of the new Copilot Studio UI, we received feedback that this setting caused confusion for users mistakenly thinking that this feature was a way to control who had access to Copilot Studio. This name change will reflect the actual intent of the feature to prevent confusion.
What action do I need to take?
This message is for awareness, and no action is required.
The Copilot Studio Authors tenant setting in the Power Platform admin center was not created as a governance feature. It was created as a licensing access-control mechanism, required to make the Copilot Studio Pay-As-You-Go meter usable at launch. Without it, a customer on a pure pay-as-you-go billing plan had no supported way to be granted access to the Copilot Studio maker portal.
How does this affect me?
With the introduction of the new Copilot Studio UI, we received feedback that this setting caused confusion for users mistakenly thinking that this feature was a way to control who had access to Copilot Studio. This name change will reflect the actual intent of the feature to prevent confusion.
What action do I need to take?
This message is for awareness, and no action is required.