Prepare your ChangePilot Enterprise deployment
Agree the environment, access, responsibilities and validation checks before deploying Enterprise.
Applies to: a new Dataverse-based ChangePilot Enterprise deployment. This is the preparation and acceptance checklist; use the current deployment pack supplied by ChangePilot for the installation and consent steps.
Who this is for: the customer’s Microsoft 365 and Power Platform administrators, the ChangePilot process owner and the deployment contact.
1. Confirm the deployment you are installing
Enterprise runs in your organisation’s Microsoft environment. Confirm the intended tenant and Power Platform environment with your deployment contact. Do not use the Free, Plus or Business cloud sign-in as the Enterprise installation route, or apply SharePoint/List and older canvas-app instructions to a Dataverse deployment.
Obtain the current architecture, deployment instructions and permissions list from your ChangePilot contact or support@changepilot.cloud. Keep the version of those documents with your deployment record.
2. Agree the administrators and licensing
Identify the administrator authorised to manage the environment, import the solution and configure connections. Identify who can review and grant any tenant consent requested by the current deployment pack.
All users of the Dataverse-based ChangePilot App require an appropriate Power Apps licence. Confirm the licence and environment capacity with your licensing administrator before rollout; do not assume a Microsoft 365 licence alone grants access to this app. See Granting users access.
3. Review permissions and the data path
Review the current consent screen and deployment documentation with your security team. Confirm what is read from Microsoft 365, where the ChangePilot components run, which environment holds your records, and which Teams or email destinations will receive information.
Record application identities, approved permissions and operational owners in your organisation’s deployment record. An older bot-permissions article describes the legacy SharePoint/List architecture and should not be used as the consent specification for a current Dataverse deployment.
4. Agree ownership and communications
Nominate the executive sponsor, M365 service owner, change process owner and communications lead. Map service categories to accountable people or teams, and agree whether all items or essential/actionable items will be automatically assigned.
Use the ownership guide. Agree who will own the Power Automate flows, Outlook connections and any separately configured integration connections, ongoing updates and support handover. Use your organisation’s account and service ownership policy.
5. Install and configure using the current pack
Follow the current deployment pack with your ChangePilot contact. Confirm the environment before each change. Configure required connection references and environment variables, grant the intended users access, and create the Configuration solution for customer-specific assets.
For an existing installation, follow the update guide instead of treating it as a new deployment.
6. Complete an acceptance review
- The installed version matches the agreed package.
- A representative licensed user can open the app and work with an appropriate item.
- Expected tenant items are present. Test optional notifications separately where they have been configured.
- Category ownership, role recipients and assignment policy match the agreed model.
- Required flows and connections are healthy; an agreed email check reaches its intended recipient.
- The team can record an assessment, action and status, and find the result after reopening the item.
- Dashboards available in the installed release open with the expected access.
Record exceptions and agree who will resolve them before wider rollout. Share the app link, Start here, the weekly review and the support checklist with the pilot team.
For the security review, see data location by deployment component. Obtain the required administrator roles and current consent steps from the deployment pack; the legacy bot-permissions page is not that specification.
Documentation reviewed: 12 November 2026.