Duaer

Integrations

Set up Microsoft Dataverse credentials in Duaer

Store Microsoft Dataverse connection details in Duaer for digital-organization nodes to use at runtime. Secrets are protected by the instance encryption key and are not written into node parameters.

Register an Entra app

The Duaer Microsoft Dataverse OAuth2 API credential:

  1. In the Microsoft Entra admin center, create an app registration under App registrations and add the Duaer OAuth Redirect URL as a Web Redirect URI under Authentication, and add the Dynamics CRM user_impersonation permission under API permissions.
  2. Create a client secret under Certificates & secrets and use it with Authentication set to Client Secret; with Certificate, fill in the uploaded certificate and its PEM private key instead.
  3. Environment URL is the environment address, such as https://yourorg.crm.dynamics.com, found in the environment details in the Power Platform admin center. Tenant ID is the tenant ID or a verified domain. Pick National Cloud if the environment is not in the global public cloud.
  4. With Grant Type set to Authorization Code, click Connect my account. With Client Credentials, Tenant ID must be a specific tenant, and the app must be added as an Application user with a security role in the Power Platform admin center.

Microsoft Dataverse OAuth2 API fields in Duaer

In Duaer, choose Microsoft Dataverse OAuth2 API when you create a credential, then fill in these fields:

  • Grant Type: OAuth2 flow to use. "Authorization Code" signs in as a real user and uses refresh tokens for long-lived workflows (recommended). "Client Credentials" acts as the application itself — no signed-in user, access token re-acquired silently on expiry. Default: Authorization Code. Options: Authorization Code, Client Credentials.
  • Client ID (required)
  • Authentication: How Duaer authenticates to Microsoft Entra when exchanging and refreshing tokens. Certificate signs a client assertion (private_key_jwt) instead of sending a client secret. Default: Client Secret. Options: Client Secret, Certificate.
  • Client Secret (required, secret): Shown when Authentication is Client Secret.
  • Private Key (required, secret): PEM-encoded RSA private key paired with the certificate uploaded to the Entra app registration. Use the multiline editor, in standard PEM format: -----BEGIN PRIVATE KEY----- KEY DATA GOES HERE -----END PRIVATE KEY-----. Shown when Authentication is Certificate.
  • Certificate (required, secret): PEM-encoded public certificate registered on the Entra app registration (Certificates & secrets). Used to derive the x5t thumbprint that tells Entra which key verifies the assertion. Shown when Authentication is Certificate.
  • Tenant ID (required): Microsoft Entra tenant ID (GUID) or verified domain (e.g. contoso.onmicrosoft.com). Find it at portal.azure.com → Microsoft Entra ID → Overview. Default: common.
  • Environment URL (required): Base URL of your Dataverse environment. Find it in Power Platform admin center under your environment details, or inside the environment at Settings → Session details.
  • National Cloud: The Microsoft national cloud your Dataverse environment lives in. Controls the Entra login host used for authentication. Default: Global (Public Cloud). Options: Global (Public Cloud), US Government (GCC High), US Government (DoD), China (21Vianet).

In the provider’s app settings, register the OAuth Redirect URL that the Duaer credential dialog shows (https://<your-duaer-host>/rest/oauth2-credential/callback). Then click Connect my account in Duaer and approve access.

By default, Duaer requests these scopes: :.

Optional settings shared by every Duaer OAuth2 credential: Ignore SSL Issues (Insecure), Token Expired Status Code, Encrypted Tokens (JWE), JWKS URI. They are described under OAuth2 API.

When you save, Duaer tests the connection with these values.

Duaer nodes that use it: Microsoft Dataverse.

Save the connection in Duaer

Open Credentials and create Microsoft Dataverse. Fill in the key, OAuth, or server fields. After you save, digital-organization nodes reference this credential instead of putting the secret in a parameter.

Credential values are protected by the instance encryption key. If you change or lose that key, stored credentials cannot be decrypted. See the hosting notes on encryption keys. The matching node is under the related node.

Who can use this credential

Who can see or edit it follows projects and roles. Do not paste secrets into chat or variables. External vaults are covered under external secrets.

Questions

Do Microsoft Dataverse secret values appear in Duaer node parameters?

No. In Duaer, Microsoft Dataverse secrets stay in the credential. Nodes only reference the credential. Execution records should not show the plaintext secret either.

What usually stops a Microsoft Dataverse credential from saving in Duaer?

Wrong fields, an OAuth callback that does not match the instance URL, or a role that cannot create credentials. Check the fields Microsoft Dataverse expects, then confirm you can create credentials in that project.

In this section