Nextiva NEXT - Microsoft Dynamics Setup Guide

Overview

Use this guide to install and connect Microsoft Dynamics 365 from the NEXT Marketplace.

The integration uses Azure Active Directory (Azure AD) OAuth authentication. During installation, you will enter connection details generated from your Azure App Registration and Dynamics 365 environment.

Before You Begin

Ensure the following:

• You have Azure AD tenant admin access.

• You have Dynamics 365 admin permissions.

• An Azure App Registration has been created.

• The App Registration includes required API permissions and admin consent.

• You have the following values ready:

  • Subdomain (Dynamics environment URL)

  • Azure AD domain name

  • Client ID

  • Client secret

• You know whether you are connecting to Cloud or On-premise.

Important:
The Azure App Registration must exist in the same Azure tenant as your Dynamics 365 environment.

Install Microsoft Dynamics 365 in NEXT

Step 1: Open the App in Marketplace

1. Navigate to Marketplace.

2. Select Microsoft Dynamics 365.

3. Select Install.

You will see a confirmation screen titled:

You are about to add Microsoft Dynamics 365 for NEXT

1. Accept the Terms and Privacy Policy.

2. Select Next.

Enter Connection Details

On the Connection Details screen, complete the following fields.

Connection type

Select:

• Cloud for Dynamics 365 online environments.

Note:
If connecting to an on-premise environment, select the appropriate option and ensure required on-prem configuration is complete.

Authentication type

Select:

• Authorization code grant

This uses Azure OAuth 2.0.

Subdomain

Enter your Dynamics 365 environment subdomain.

Example:

If your environment URL is:

    https://abc.crm.dynamics.com

Enter:

    abc.crm.dynamics.com

Account type

Select:

• Cloud

AD domain name

Enter your Azure Active Directory domain.

Example:

    abc.onmicrosoft.com

Note:
If connecting to an on-premise environment, enter the AD domain associated with your ADFS server.

Client ID

Enter the Application (client) ID from your Azure App Registration.

To find it:

1. Log in to Azure Portal.

2. Navigate to Azure Active Directory → App registrations.

3. Select your app.

4. Copy the Application (client) ID.

Client secret

Enter the Client Secret generated in Azure.

To create a client secret:

1. In Azure Portal, open your App Registration.

2. Select Certificates & secrets.

3. Select New client secret.

4. Copy the secret value immediately.

Warning:
Azure displays the client secret only once. Store it securely.

Version

Select the supported Dynamics version (for example, Version 8).

Advanced Settings (Optional)

You may configure:

• Resource URI

• Custom OAuth profile

If left blank, default authorization settings will apply.

Most users do not need to configure Advanced Settings. Leave these fields blank unless your Microsoft Dynamics administrator or IT team specifically instructs you to use them.

Advanced Settings may be required if:

• You connect to multiple Dynamics environments.

• Your organization uses custom authentication requirements.

• You need to specify a custom Resource URI.

Note:
Resource URI typically follows this format:

    https://abc.crm.dynamics.com/api/data/v9.0/

Connect

After completing all required fields:

1. Select Connect.

2. Select Next.

You will be redirected to Microsoft to grant consent.

Approve the requested permissions.

Installation Complete

If successful, you will see:

Installation Complete

The summary displays enabled capabilities such as:

• Contact Sync to MS Dynamics

  • Lookup Contact

  • Manage Contact

• Ticket (Case) Management

  • Manage Case

  • Lookup Case

  • Sync Ticket Engagements synchronously

Select:

• Done to exit, or

• Manage apps to review the integration.

Verify the Connection

After installation:

1. Navigate to Manage Apps → Microsoft Dynamics 365.

2. Confirm the status shows Active.

3. Create a test contact in NEXT.

4. Confirm the contact appears in Dynamics 365.

5. Create a test case and confirm it syncs properly.

Troubleshooting

Invalid Client Secret

• Confirm the secret has not expired.

• Ensure no extra spaces were copied.

• Generate a new client secret if necessary.

Authorization Failed

• Confirm API permissions are assigned in Azure.

• Ensure admin consent was granted.

• Verify the AD domain name matches your tenant.

Records Not Syncing

• Confirm the integration user has appropriate security roles in Dynamics.

• Verify the correct subdomain was entered.

• Reauthorize the connection if prompted.