Getting started with Copilot Studio using a free developer sandbox
Diesen Beitrag auf Deutsch lesen
A practical setup path from a Microsoft 365 developer tenant to Dataverse, Power Platform and a Copilot Studio trial agent.
TL;DR
Use a Microsoft 365 Instant Sandbox, activate the Power Apps Developer Plan, verify Dataverse and start the Copilot Studio trial in the dedicated developer environment. The guide recommends building a SharePoint knowledge agent first, then adding a Power Automate action to learn retrieval and execution together.
Original by Divya Akula, on Divya Akula. Read the original
This is our own summary, not a republication or full translation.
Why it matters
- Makers: Activate the Power Apps Developer Plan and build in its dedicated Dataverse-backed environment, rather than the shared default environment.
- Admins/IT: Check the developer environment name, region and Dataverse provisioning before building, because the region cannot be changed later.
- Makers: Start with a SharePoint knowledge agent, then add a Power Automate action to practise knowledge retrieval and execution.
- Leadership/Business: Treat the Copilot Studio trial as an exploration period, because agents become read-only and stop responding when active Copilot Credits are unavailable after expiry.
Frequently asked questions
How do I create an Instant Sandbox for Power Platform development?
Use a personal Microsoft account to join the Microsoft 365 Developer Program, choose Instant Sandbox, and record the new sandbox work account.
What does the Power Apps Developer Plan add to a default environment?
It provisions a separate developer environment with Dataverse, app builders, standard connectors and cloud flows for learning and prototyping.
What happens to Copilot Studio agents after the 30-day trial ends?
Agents become read-only and stop responding until active Copilot Credits are assigned. They are not deleted, but publishing and running are unavailable.