Posts Tagged ‘Outlook Client’
Dynamics 365 App for Outlook “Can’t connect to Exchange”
The on-premise Dynamics 365 App for Outlook (version 9.1) stopped displaying the Track and Set Regarding buttons after “Legacy Exchange Tokens” were disabled for Exchange Online in October/November 2025 (see here). The message “Can’t connect to Exchange” is displayed instead.
To fix this, we need to use the Graph API to authorise the app for Exchange Online, and update the server application files.
Step 1: Create an App registration in Entra
Log into https://entra.microsoft.com/ for the Exchange tenant as an administrator
Navigate to App registrations and click New registration
Set Name to ‘Dynamics Outlook App’
Set Support account type to the Single tenant option
Set Redirect URI to Single-page application (SPA) and the URL to https://your_org_url/crmmailapp/msalAuth.html
Click Register at the bottom of the page
Note the Application (client) ID and Directory (tenant) ID for later
Navigate to API permissions and click Add a permission
Select Microsoft Graph, then Delegated permissions
Select the permissions Mail.ReadWrite, Mail.ReadWrite.Shared, Calendars.ReadWrite and Calendars.ReadWrite.Shared, then click Add permissions
Click Grant admin consent
On the Authentication tab, select Access Tokens and ID tokens, then click Save
Note the Client ID and Tenant ID from the Overview tab for the next step
Step 2: Install the managed solution into the Dynamics organisation
Download the managed solution from here, then install it into the affected organisation. The solution contains a new entity called ‘mailapp_setting’.
Once installed, navigate to https://your_org_url/main.aspx?pagetype=entitylist&etn=mailapp_setting
Add 2 new records:
Name: graph_appid
Setting value: The Application (client) ID noted from Entra
Name: azure_tenantid
Setting value: The Tenant ID noted from Entra
Add read permission to the new MailApp Settings entity to all users via Security Roles. (I added it to the Dynamics app for outlook role which we assign to all users using the app) and full permissions to other admin users
Step 3: Replace the crmmailapp files on the Dynamics servers
On the CRM server(s), backup the folder C:\Program Files\Dynamics 365\CRMWeb\crmmailapp
Download crmmailapp-updated.zip from here
Delete the contents of C:\Program Files\Dynamics 365\CRMWeb\crmmailapp
Copy the contents of crmmailapp-updated.zip to the C:\Program Files\Dynamics 365\CRMWeb\crmmailapp folder
Step 4: Test
Clear browser cache or open an incognito window to test the Outlook app
If working correctly, you should be prompted to sign into Dynamics, then Office 365 and the Track and Set Regarding buttons will be available again.
Note: We may need to copy the original contents of crmmailapp back before running future update rollups, so keep the backup safe.
Dynamics 365 Outlook Client Not Rendering Views After September 2018 Update
The 5th September 2018 Office 365 update has stopped the Dynamics 365 Outlook client from rendering views.
This is not resolved by the ‘EnableRoamingFolderHomepages’ registry key that fixed a similar issue after the October update.
To get it working again, you’ll need to roll back to the previous update, then turn off automatic updates until it is resolved:
See the edit at the bottom for a better workaround!
Rollback the update
To roll back to the previous update, run the below from a command prompt
Read the rest of this entry »
Outlook Client Repeated Login Prompts Post V9 Upgrade
After your Dynamics 365 organisation has finally been updated to the July 2017 October 2017 December 2017 February 2018 V9 version, you may find that your Outlook client (full version, not the lightweight app) no longer works.
Uninstalling and re-installing the version offered via the ‘Get Apps’ page within Dynamics 365 doesn’t help as you are repeatedly prompted for your login when trying to configure the organisation.
Viewing the trace log gave the error:
Metadata contains a reference that cannot be resolved: 'https://crm_url/XRMServices/2011/Organization.svc?wsdl&sdkversion=8.2
This is because the Outlook client is still using the old SDK (8.2) which is still using SSL rather than the TLS1.2 protocol for authentication required by V9.
The solution is to install update KB4054414 after installing the Outlook client.
CRM Outlook Client Spell Check
Recently, a customer has found that spell checking is not available when typing into forms on the CRM Outlook client. Spell checking is built into Internet Explorer and works fine on the web client, so I wanted to find a way to get it working in Outlook.
Using this MSDN article, I found that adding a registry key may help. After some trial and error, the following key and value had the desired effect. Read the rest of this entry »
Neil McDonald's Dynamics 365 and Power Platform Blog 