The Power Platform admin center only manages the Dataverse side of a linked environment. It never holds VM-level RDP credentials — those still live only in LCS, because the F&O infrastructure (VM, local accounts) is provisioned and tracked by LCS, not by PPAC. So there's no PPAC page that gives you a "VM name + username/password" like the one in your first screenshot.
Note: You develop directly from your own laptop's Visual Studio, connected straight to the cloud Dataverse-backed environment.
Step-by-step: connect the new PPAC environment to Dataverse for development:
In Power Platform admin center — confirm the environment is Sandbox type with a Dataverse database (mandatory for UDE).
Go to the environment → Resources → Dynamics 365 apps → install, in order:
Open the Provisioning app and check "Enable Developer Tools for Finance and Operations" — this is mandatory, it's what turns the sandbox into a developer-enabled environment.
Note the Environment URL field on the PPAC environment Details page (not the "Finance and Operations URL" — that's the wrong one for VS).
On your local machine (prerequisites):
Visual Studio 2022 (Enterprise/Professional) with Modeling SDK and DGML Editor components
SQL Server Express/Developer edition, or just LocalDB — needed locally to hold the cross-reference database
Power Platform Tools extension for VS (Extensions → Manage Extensions → Online → search "Power Platform Tools")
Connecting Visual Studio to the environment:
Close and reopen VS after installing the extension (install finishes on close).
Tools → Options → Power Platform Tools — set the recommended options.
Tools → Connect to Dataverse → choose Office 365 → Login.
Paste in the Environment URL from PPAC and select your environment/solution.
When prompted, accept the client asset download — this pulls down the F&O VS extension, cross-reference DB backup, and PackagesLocalDirectory zip.
VS may close automatically mid-process — that's expected, just reopen it.
Configure the local X++ environment fields (xRef DB server = (localdb)\., xRef DB name, etc.) using the downloaded BAK file — don't move that file from its download location.
Once that's done, you build/deploy X++ code straight from VS to the environment through managed Dataverse solutions — no deployable packages, no LCS, no VM RDP involved.
