What problem does it solve?
When a Power Platform environment is already associated with one Pipelines host, creating a deploymentenvironments record on a new host fails with "this environment is already associated with another pipelines host". This Skill performs the documented Force Link operation to move the environment's host association, which is otherwise a confusing manual remediation.
Core Features & Use Cases
- Force Link execution: Calls the documented ManageEnvironmentStamp Dataverse action (the API behind the Force Link button) to move an environment's stamp to a new host, then polls validation until it succeeds.
- Guided safety gates: Resolves the target host and dev environment from arguments, marker files, or PAC CLI, and requires explicit user consent before the destructive cross-host move.
- Record recovery and auditing: Recovers failed deploymentenvironments records by re-querying Dataverse, and writes a docs/alm/last-force-link.json marker validated by a stop-hook script.
- Use Case: A maker migrating environments from the Platform Host to a Custom Host hits the "already associated" error; run this Skill to relink the environment to the new host with confirmation and a full audit trail.
Quick Start
Ask the agent to force-link your development environment to the new pipelines host, optionally passing --host and --dev-env values.