Connect Dataverse

1. Create an Entra ID app registration

1. In the Azure portal, open Microsoft Entra ID → App registrations → New registration.
2. Name it something like MigrateTo · <Workspace>.
3. Accounts in this organizational directory only is fine.
4. No redirect URI is required for server-to-server.

2. Add API permissions

1. Open API permissions → Add a permission → Dynamics CRM.
2. Choose Application permissions → user_impersonation.
3. Click Grant admin consent.

3. Create a client secret

1. Open Certificates & secrets → Client secrets → New client secret.
2. Set a 12- or 24-month expiry and copy the secret value (not the ID) immediately.

4. Create the Dataverse application user

1. Open Power Platform admin centre → your environment → Settings → Users + permissions → Application users.
2. Click New app user, pick the app registration you just made, assign a security role with read access to the tables you want to bind.

5. Add the connection in MigrateTo

1. Open Settings → Integrations → Dataverse.
2. Paste the environment URL (for example https://contoso.crm.dynamics.com), tenant ID, client ID, and client secret.
3. Click Test connection. We call /api/data/v9.2/WhoAmI with a client-credentials token and confirm a 200.

Sync tables

After connecting, click Sync tables. We pull table and column metadata into our schema cache so the mapping canvas can offer them without round-trips.

Supported column types

• String, Multiline text, URL, Email, Phone
• Integer, Decimal, Money, Percent
• Boolean, Choice (option set), Multi-select choice
• DateTime (date-only and full)
• Lookup → ID + primary-name field
• Image (binary attachments → exported as web files)

What we generate at runtime

{% fetchxml records %}
  <fetch top="20">
    <entity name="cr1f5_articles">
      <attribute name="cr1f5_title" />
      <attribute name="cr1f5_summary" />
    </entity>
  </fetch>
{% endfetchxml %}