Microsoft Dynamics 365 Service Account — Setup Guide

Overview Use this guide to create and configure a Microsoft Dynamics 365 service account in MinuteView Console. This service account enables integration with your Dynamics 365 environment for:

• Record management — Create, read, update, and delete records in Dynamics 365 entities
• Workflow automation — Trigger Dynamics 365 actions from MinuteView automation workflows
• Data synchronization — Pull Dynamics 365 data into MinuteView for reporting and processing
• Custom entity access — Work with standard and custom Dynamics 365 entities

This service account uses Azure AD client credentials (client ID and secret) for server-to-server authentication with your Dynamics 365 instance.

---

Network Requirements

The MinuteView server communicates directly with Microsoft's identity platform and your Dynamics 365 instance to authenticate and make API calls. This means the server must have outbound internet access to the following domains.

Required Firewall / Proxy Whitelist

The following domains must be accessible via HTTPS (port 443) from the server where MinuteView is installed:

Domain	Purpose
login.microsoftonline.com	Azure AD token acquisition and refresh
*.crm.dynamics.com	Dynamics 365 API calls (your specific org URL, e.g. yourorg.crm.dynamics.com)

Server Access Required

These domains must be reachable from the server, not just from the user's PC. All Dynamics 365 API calls are made server-side by MinuteView. If the server cannot reach these domains, authentication and data operations will fail.

---

1) Register an App in Azure AD

Create App Registration

1. Sign in to Azure Portal at https://portal.azure.com
2. Navigate to Microsoft Entra ID → App registrations → New registration
3. Configure:
   • Name: MinuteView Dynamics 365 Integration
   • Supported account types: Single tenant
   • Redirect URI: Leave blank (not needed for client credentials)
4. Click Register

Collect Credentials

From the app's Overview page, note:

• Application (client) ID
• Directory (tenant) ID

Create Client Secret

1. Navigate to Certificates & secrets → Client secrets → New client secret
2. Description: MinuteView Integration
3. Expires: Choose appropriate duration
4. Copy and securely store the secret value

---

2) Configure Dynamics 365 Permissions

Add API Permissions

1. Navigate to API permissions → Add a permission
2. Select Dynamics CRM → Application permissions
3. Select user_impersonation (or delegated permissions as needed)
4. Click Grant admin consent for [Organization]

Create Application User in Dynamics 365

1. Sign in to Dynamics 365 → Settings → Security → Users
2. Switch view to Application Users
3. Click New → select Application User form
4. Enter the Application (client) ID from the Azure app registration
5. Assign the appropriate Security Role for the operations MinuteView will perform

---

3) Create Service Account in MinuteView Console

1. Navigate to Console → Service Accounts
2. Click New to create a new service account
3. Configure the following settings:

Configuration Fields

Field	Description	Example
Name	A descriptive name for this service account	Dynamics365-Production
Service Account Type	Select Microsoft Dynamics 365 from the dropdown
Server URL	The URL of your Dynamics 365 instance	https://yourorg.crm.dynamics.com
Tenant ID	Your Azure AD Directory (tenant) ID	87654321-4321-4321-4321-210987654321
Client ID	The Application (client) ID from your Azure app registration	12345678-1234-1234-1234-123456789012
Client Secret	The client secret value from Azure	(sensitive — stored securely)

4. Click Save to create the service account

---

4) Troubleshooting

Connection error / "Failed to retrieve authentication token"

• The most common cause is that the MinuteView server does not have outbound internet access. See Network Requirements above for the domains that must be whitelisted.

Unauthorized / Access Denied

• Verify the Application User exists in Dynamics 365 and has the correct security role assigned
• Confirm admin consent was granted for the API permissions in Azure AD
• Check the client secret has not expired

Invalid Client or Tenant

• Double-check the Client ID and Tenant ID match the Azure app registration
• Verify the app registration is in the correct Azure AD tenant