Dataverse “Developer resources”: the one panel every Power Platform builder should bookmark

The Developer resources panel in Power Apps/Dataverse quietly holds the IDs and endpoints that make integrations, PCF controls, plugins, and admin scripts work. Below, we’ll have a simple cheat sheet with what it means and when you'll use it.

Where to find it

Power Apps → Settings (top-right gear) → Developer resources. You’ll see environment IDs, the Dataverse Web API endpoint, the discovery URL, and links to docs/SDKs.

What each item means (and why you should care)

Developer resources cheat-sheet

Developer resources	What it means	When you’ll use it	Gotchas
Environment unique name	Short, immutable label for the environment.	ALM scripts, some SDK/tools, variable names in pipelines.	Not the display name; doesn’t have to match the URL.
Environment ID	Power Platform environment GUID.	Admin/DevOps (PowerShell, CLI), support tickets.	Different from Organisation ID.
Organization ID	Dataverse “org” GUID.	Plugin registration, Package Deployer, telemetry/licensing, Microsoft Support.	Easy to mix up with Environment ID—track both.
Web API endpoint	Base URL for Dataverse OData v9.2.	Read/write tables, call actions, FetchXML, $batch from code/flows/Postman/PCF.	Must include /api/data/v9.2; token’s resource must match host.
Discovery endpoint	Lists all environments for a tenant/region.	Multi-env tools, sign-in flows, and admin inventory.	Not for CRUD—use the Web API of a specific env.